APAR status
Closed as program error.
Error description
When you set Maximo escalation to run as an user that does not have a default insert site agains the LABTRANS table, you will get the error message : BMXAA2634E - Mismatches between labor, craft, skill level, vendor and contract are not allowed. Use the Select Value lookup to see a list of valid choices. Steps to replicate : 1- Open Maximo as maxadmin 2- Go to Organizations app and make sure that in Labor Options for EAGLENA, the following options are NOT checked. Automatically Approve Inside Labor Transactions? Automatically Approve Outside Labor Transactions? Allow Mismatched Craft and Labor When Reporting Actual Labor 3- Save and ensure that in Profile link, there is not a default insert site for that user. 4- After that, create a workorder in Work Order Tracking app, and on Plans tab, add some labor line. (you can use BALL) 5- Create an action in Actions app like this : Action= 1029 (you can use any ID) Object = LABTRANS Type = Set Value Value = 1 Parameter/Attribute = genapprservreceipt Accessible from = ALL 6- Save action and go to Escalations app 7- Create an escalation with the following Condition : LABORCODE = 'BALL' AND REFWO = '3150' (change your REFWO by the WONUM you used) 8- Make sure there is an escalation point, it only needs to exist. 9- Associate the action you created above with the Actions tab of this escalation. 10- Ensure the escalation is active and that it is scheduled to run in a few moments from now. 11- After some time, after the escalation has run, go to your SQL tool and run this query : SELECT * FROM ESCSTATUS; ...and then you will see your escalation with the error information of this : BMXAA2634E - Mismatches between labor, craft, skill level, vendor and contract are not allowed. Use the Select Value lookup to see a list of valid choices. Important : Customer has a business requirement about having MAXADMIN user with no Default Insert Site in the environment. So, MAXADMIN user does NOT have any default insert site associated. Error seems to be happening because MAXADMIN is the Run as User for the escalation and it was configured not to have default insert site. For user with default insert site, the escalation runs fine. If the crontask Run as User has a default insert site, this works fine. But the customer has a business requirement about having MAXADMIN user with no Default Insert Site in the environment. So, MAXADMIN user does NOT have any default insert site associated. When escalations mapped to WORKORDER, PO, PURCHIVEW can work with run as user as MAXADMIN then why not LABTRANS?
Local fix
Use a default site for users running escalations.
Problem summary
**************************************************************** * USERS AFFECTED: * * MAXIMO * **************************************************************** * PROBLEM DESCRIPTION: * * If Login User's default insert site is null in Profile, * * updating existing Labor Reporting records could get * * BMXAA2634E error. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
The fix for this APAR is contained in the following maintenance package: | Release 7.6.0.8 of Base Services
Temporary fix
Comments
APAR Information
APAR number
IV92470
Reported component name
ADMINISTRATION
Reported component ID
5724R46A1
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-01-20
Closed date
2017-03-15
Last modified date
2017-03-15
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
ADMINISTRATION
Fixed component ID
5724R46A1
Applicable component levels
R760 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPP5","label":"System Related"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
15 March 2017