APAR status
Closed as program error.
Error description
The PMWogenCronTask runs fine, however no workorders are generated if there is a crossover domain from PERSON to WORKORDER associated in the WORKORDER.REPORTEDBY field. The manual PM workoder generation works fine if it is done manually in the PM app, even for the same PM records. If the customer removes the crossover domain from WORKORDER.REPORTEDBY field, then the PMWogenCronTask will start generating PM workorders fine again. PMWogen it is definitely running, and is going through all the PM's... just it hits that error every time it should produce a work order. Also we've restarted the server twice since it started happening just in case...no change. What was added was a new cross-over domain to the location and user to a workorder. Customer created a crossover domain to get data from PERSON.LOCATION to WORKORDER.LOCATION when a new workorder is generated. However this is working fine if you generate PM workorders from the PM application itself manually, however when the PMWogenCrontask runs, no workorders are generated, even if the same PM records involved generate PM workorders fine from the PM application. PMWogen it is definitely running, and is going through all the PM's... What was added was a new cross-over domain to the location and user to a workorder. In the Cron Task application for the pmwogencrontask the Access Level is set to Full. And the user running the crontask has the same permissions as MAXADMIN. This was working fine before the crossover was created. After client removed the domain they had added for the default work order location in their test system, the PMWOGen cron task started generating workorders again... Go To Cron Task Setup app and make sure the PMWogenCronTask is scheduled to run shortly and that it is ACTIVE Go to Domains app and create a new CROSSOVER domain as below : Object >> PERSON Validation clause >> PERSONID=:REPORTEDBY List Where clause >> PERSONID=:REPORTEDBY Crossover Fields Source Field >> LOCATION Destination Field >> LOCATION Accept NULL value? >> Checked Go to Database Configuration app and associate the crossover that you created to the WORKORDER.REPORTEDBY field. Configure the Database, and then make sure that the ADMIN MODE is OFF. (otherwise the cron tasks will not run) Go to People app and make sure that the maxadmin user has a PERSON LOCATION defined. You can use BR200. Go to Preventive Maintenance app and create a new PM record, and set it to generate workorders with a frequency of 1 day, and estimated next due date for a day in the last week. Make sure that new PM is set to ACTIVE status Wait for about 5 minutes, then go to the Work Order Tracking app and serch in Advanced Search for the PM field, putting your new created PM, so that you can find any records generated by your new PM record. You will find no records with that PM number. Go to the Cron Task Setupo app and search for PMWogenCronTask record, and select the History subtab, to check whether the crontask is running or not. You will see it is running fine, however just not generating workorders. NOTE 1: If you go to Database Configuration app, and remove the crossover domain from the WORKORDER.REPORTEDBY, then the crontask will generate workorders with no problem. With the crossover domain in place, the crontask runs, however no PM workorders are generated. NOTE 2 : The PM workorder generation runs fine if you manually generate PM workorders from the Preventive Maintenance app (not using the crontask), even if the crossover domain is in place. NOTE 3 : The MAXADMIN user is the user on the "Run as User" in the crontask instance, and it has a PERSONID associated in the ACTIVE status.
Local fix
NA
Problem summary
**************************************************************** * USERS AFFECTED: * * Maximo users * **************************************************************** * PROBLEM DESCRIPTION: * * Crossover domain added to WORKORDER.REPORTEDBY causes null * * pointer exception during PM work order generation via the * * PMWogenCronTask. * **************************************************************** * RECOMMENDATION: * * Apply latest fix pack. * **************************************************************** Crossover domain added to WORKORDER.REPORTEDBY causes null pointer exception during PM work order generation via the PMWogenCronTask. Problem does not occur when manually executing PM wogen. The PMWogenCronTask runs fine, however no workorders are generated if there is a crossover domain from PERSON to WORKORDER associated in the WORKORDER.REPORTEDBY field. The manual PM workoder generation works fine if it is done manually in the PM app, even for the same PM records. If the customer removes the crossover domain from WORKORDER.REPORTEDBY field, then the PMWogenCronTask will start generating PM workorders fine again. PMWogen it is definitely running, and is going through all the PM's... just it hits that error every time it should produce a work order. Also we've restarted the server twice since it started happening just in case...no change. What was added was a new cross-over domain to the location and user to a workorder. Customer created a crossover domain to get data from PERSON.LOCATION to WORKORDER.LOCATION when a new workorder is generated. However this is working fine if you generate PM workorders from the PM application itself manually, however when the PMWogenCrontask runs, no workorders are generated, even if the same PM records involved generate PM workorders fine from the PM application. PMWogen it is definitely running, and is going through all the PM's... What was added was a new cross-over domain to the location and user to a workorder. In the Cron Task application for the pmwogencrontask the Access Level is set to Full. And the user running the crontask has the same permissions as MAXADMIN. This was working fine before the crossover was created. After client removed the domain they had added for the default work order location in their test system, the PMWOGen cron task started generating workorders again... Go To Cron Task Setup app and make sure the PMWogenCronTask is scheduled to run shortly and that it is ACTIVE Go to Domains app and create a new CROSSOVER domain as below : Object >> PERSON Validation clause >> PERSONID=:REPORTEDBY List Where clause >> PERSONID=:REPORTEDBY Crossover Fields Source Field >> LOCATION Destination Field >> LOCATION Accept NULL value? >> Checked Go to Database Configuration app and associate the crossover that you created to the WORKORDER.REPORTEDBY field. Configure the Database, and then make sure that the ADMIN MODE is OFF. (otherwise the cron tasks will not run) Go to People app and make sure that the maxadmin user has a PERSON LOCATION defined. You can use BR200. Go to Preventive Maintenance app and create a new PM record, and set it to generate workorders with a frequency of 1 day, and estimated next due date for a day in the last week. Make sure that new PM is set to ACTIVE status Wait for about 5 minutes, then go to the Work Order Tracking app and serch in Advanced Search for the PM field, putting your new created PM, so that you can find any records generated by your new PM record. You will find no records with that PM number. Go to the Cron Task Setupo app and search for PMWogenCronTask record, and select the History subtab, to check whether the crontask is running or not. You will see it is running fine, however just not generating workorders. NOTE 1: If you go to Database Configuration app, and remove the crossover domain from the WORKORDER.REPORTEDBY, then the crontask will generate workorders with no problem. With the crossover domain in place, the crontask runs, however no PM workorders are generated. NOTE 2 : The PM workorder generation runs fine if you manually generate PM workorders from the Preventive Maintenance app (not using the crontask), even if the crossover domain is in place. NOTE 3 : The MAXADMIN user is the user on the "Run as User" in the crontask instance, and it has a PERSONID associated in the ACTIVE status.
Problem conclusion
Crossover domain added to WORKORDER.REPORTEDBY no longer causes null pointer exception during PM work order generation via the PMWogenCronTask. PMs that previously ran into this problem and did not generate work orders now do generate work orders as expected. The fix for this APAR is contained in the following maintenance package: | release\fix pack\interim fix for 7.6.0.6 of Base Services
Temporary fix
Comments
APAR Information
APAR number
IV85417
Reported component name
WORK ORDERS
Reported component ID
5724R46WO
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-02
Closed date
2016-06-03
Last modified date
2024-10-29
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
WORK ORDERS
Fixed component ID
5724R46WO
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
30 October 2024