APAR status
Closed as program error.
Error description
When receiving a rotating asset through the shipment receiving process the status of the asset is changed to NOT READY when saved. This is contrary to the Inventory Usage application which performs the same function of moving the asset from one storeroom to another where the status remains its current state. Steps: 1. The asset to be transferred currently has OPERATING status. 2. Create a transfer via Inventory Usage for this serialized item. 3. Change the status to shipped. 4. Enter the asset from step 1 and click OK. 5. Click Ok when prompted to create a shipment. 6. Navigate to the Shipment Receiving application and receive the asset. 7. The asset record changes storerooms but the status has changed to NOT READY. The status of the asset should not have changed. 8. Create another transfer inventory usage for the same rotating item and enter an asset in the Rotating Asset field that is in OPERATING status. This functions differently than using a shipment but the same result of the asset being moved from one storeroom to another occurs. 9. Change the status of the inventory usage to COMPLETE and click OK. 10. View the asset after it has been transferred. The storeroom has changed and the status remains OPERATING. . Additional COmments The shipment receiving application should not change the status of the asset to NOT READY, especially since the storerooms are within the same site. Version Information: App Server IBM WebSphere Application Server 7.0.0.31 Version IBM Maximo Asset Management 7.5.0.5 Build 20130903-1504 DB Build V7505-00 IBM Maximo for Transportation 7.5.1.0 Build 20140204-1308 DB Build V7510-10 HFDB Build HF7510-02Page 4 of 14 Tivoli's process automation engine 7.5.0.5-IFIX20140207-1756 Build 20130903-1504 DB Build V7505-43 HFDB Build HF7505-03 IBM Maximo Asset Configuration Manager 7.5.1.0 Build 20140205-1026 DB Build V7510-17 HFDB Build HF7510-07 IBM TPAE Integration Framework 7.5.1.0 Build 20130829-1209 DB Build V7510-28 Application Shipment Receiving Industry Solution N/A
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Maximo users * **************************************************************** * PROBLEM DESCRIPTION: * * Erroneous asset status change on inspection of rotating * * asset in Shipment Receiving * **************************************************************** * RECOMMENDATION: * * Apply latest fix pack. * **************************************************************** When a shipment receipt for a rotating asset is inspected, the status changes to NOT READY even if the destination and originating sites are the same. This should only happen when the receipt is cross-site. STEPS TO REPRODUCE SCENARIO 1 -- Incorrect Result 1. The asset to be transferred currently has OPERATING status. 2. Create a transfer via Inventory Usage for this serialized item. 3. Change the status to shipped. 4. Enter the asset from step 1 and click OK. 5. Click Ok when prompted to create a shipment. 6. Navigate to the Shipment Receiving application and receive the asset. 7. The asset record changes storerooms but the status has changed to NOT READY. The shipment receiving application should not change the status of the asset to NOT READY since the storerooms are within the same site. SCENARIO 2 -- Correct Result 8. Create another transfer inventory usage for the same rotating item and enter an asset in the Rotating Asset field that is in OPERATING status. This functions differently than using a shipment but the same result of the asset being moved from one storeroom to another occurs. 9. Change the status of the inventory usage to COMPLETE and click OK. 10. View the asset after it has been transferred. The storeroom has changed and the status remains OPERATING.
Problem conclusion
When a shipment receipt for a rotating asset is inspected, the status is not change to NOT READY if the destination and originating sites are the same. The fix for this APAR is contained in the following maintenance package: | release\fix pack\interim fix for Release 7.5.0.7 of Base Services
Temporary fix
Comments
APAR Information
APAR number
IV60825
Reported component name
ASSETS
Reported component ID
5724R46AS
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-05-22
Closed date
2014-06-13
Last modified date
2014-06-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
MAXIMO
Fix information
Fixed component name
ASSETS
Fixed component ID
5724R46AS
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
09 April 2023