APAR status
Closed as program error.
Error description
When deleting labor, Maximo validates against the data if it is possible to delete the labor. The validation checks against all open workorders instead of only the ORGID the Labor is located at. That means that we cannot delete labor records, when any other orgid has a workorder open that happens to have the same WONUM. STEPS TO REPRODUCE: User = Wilson/Wilson First Scenario: When the same workorder number exists in different organization and site 1)Wilson default information > set default insert site = Bedford/Org = EagleNA 2)Select an existing Labor record or create new test Labor = Oliver. receive message: a person record does not exist would like to create click yes 3)Crafts tab > click new row > Craft = ELECT 3)Save record 4)Workorder Tracking > create new workorder > wonum = MB1234, note:site = Bedord and belongs to Org =EagleNA 5)Update the location = BR240 6)Change status to approved (APPR) 7)Actuals tab > Labor subtab = click new row > Labor = Oliver (new labor created in Step#2) 8)Save record. 9)Change user (Wilson) default information > set default insert site = ChileHQ/Org = EagleSA 10)Workorder Tracking , create new workorder use the same wonum as created in step #4 wonum = MB1234. you do not need to populate any other fields . 11)Change status to Approved. At this point there are 2 workorders with the same workorder number 11a)Org EagleNA / Site Bedord = wonum =MB1234 status Appr - labor Oliver 12b)Org EagleSA/ Site ChileHQ = wonum = MB1234 status Appr - no labor 12)Change Wilson user default insert site back to Bedford. 13)Workorder Tacking > call up workorder MB1234 change status to Close Note: Workorder MB1234 site-Bedford /Org EagleNA - status = Close Workorder MB1234 site -ChileHQ/Org EagleSA - Status= APPR 14)Labor > select labor = Oliver (created instep #2) and was added to only one workorder(MB1234) actuals in the bedford site. 15)More actions > select Delete Labor 16)Receive message:"BMXAA2582E - Cannot delete labor because it is has labor transactions." This is not correct,it is looking at the workorder from the ChileHQ site/ org EagleSA and not allowing the Labor to be deleted. Now select the workorder MB1234 from the ChileHQ site and change the status to close , the delete of the Labor record is allowed. Second Scenario: when the same workorder number exists in different sites in the same organization 1)Wilson default information > set default insert site = Bedford/Org= EagleNA 2)Select an existing labor record or create new test Labor = Oliver. receive message: a person record does not exist would like to create click yes 3)Crafts tab > click new row > Craft = ELECT 3)Save record 4)Workorder Tracking > create new workorder > wonum = test123, note:site = Bedord and belongs to Org =EagleNA 5)Update the location = BR240 6)Change status to approved (APPR) 7)Actuals tab > Labor subtab = click new row > Labor = Oliver (new labor created in Step#2) 8)Save record. 9)Change user (Wilson) default information > set default insert site = McLean/Org = EagleNA 10)Workorder Tracking , create new workorder use the same wonum as created in step #4 wonum = Test123. you do not need to populate any other fields ,no labor added 11)Change status to Approved. At this point you now have 2 workorders with the same workorder number 11a)Org EagleNA / Site Bedord = wonum =Test123 status Appr - Labor Oliver 12b)Org EagleNA/ Site McLean = wonum = Test123 status Appr - no labor 12)Change Wilson user default insert site back to Bedford. 13)Workorder Tacking > call up workorder Test123 change status to Close Note: Workorder Test123 site-Bedford /Org EagleNA - status = Close Workorder Test123 site -McLean/Org EagleNA - Status= APPR 14)Labor > select labor = Oliver (created instep #2) and was added to only one workorder(Test123) actuals in the bedford site. 15)More actions > select Delete Labor 16)Receive message:"BMXAA2582E - Cannot delete labor because it is has labor transactions." This is not correct, it is looking at the workorder from the McLean site and not allowing the Labor to be deleted. Now select the workorder Test123 from the McLean site change the status to close , the delete of the Labor record is allowed. RESULTS: When the same workorder number exists within a different Org/Site or in same Org with different Site when trying to delete a Labor record that exists only on the specific workorder in a particular site that is in close status, you will receive message "BMXAA2582E - Cannot delete labor because it is has labor transactions." this is not correct. EXPECTED RESULTS: To be able to delete a Labor record that is no longer referenced on any active workorder when the same workorder numbers exist in different Org/Site or same Org with different site. REPORTED IN VERSION: IBM Maximo Asset Management 7.6.1.2
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * MAXIMO * **************************************************************** * PROBLEM DESCRIPTION: * * UNABLE TO DELETE LABOR RECORD WHEN THE SAME WORKORDER NUMBER * * EXISTS ON ANOTHER ORG /SITE * ****************************************************************
Problem conclusion
The fix for this APAR is contained in the following maintenance package: release\fix pack for Release 8.x Product
Temporary fix
Comments
APAR Information
APAR number
IJ47928
Reported component name
MAXIMO ASST MGM
Reported component ID
5724R46AM
Reported release
761
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-08-17
Closed date
2023-09-12
Last modified date
2023-09-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
MAXIMO ASST MGM
Fixed component ID
5724R46AM
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
12 September 2023