APAR status
Closed as program error.
Error description
Users has a problem in service requests. They have configured the TKLOCATIONCROSSCI to automatically populate a second field in TICKET when the location field is populated. This works perfectly when a value is directly placed in location, but if the asset field is updated, location is filled in with the assets location and the crossover domain is not triggered. When user repeat this setup in work order tracking, it works as expected. Our customer is using 7.6.0.8 but we have also tested in 7.6.0.9. User could test it successfully only on Maximo 7.6.0.3 version. User would require a solution for 7.6.0.8. PROBLEM: Crossover not working the way it once did in 7.6.0.3 PERFORMANCE ISSUE: N STEPS TO REPRODUCE: SERVICE REQUESTS 1.Go to Domains. Find and open TKLOCATIONCROSSCI. 2.Add a new crossover field entry. Source Field: DESCRIPTION. Destination Field: TARGETDESC. (This will automatically populate the targetdesc field on the ticket object with the content of the location s description.) 3.Go to Service Requests and create a new SR. 4.Look up a location on the location field. The target description field will be automatically populated with the location description. 5.Create another new SR (not saving the previous one). This time look up an asset. The location field is updated, but the target description remains blank. WORK ORDER TRACKING 1.Go to Domains. Find and open LOCATIONCROSSCI. 2.Add a new crossover field entry. Source Field: DESCRIPTION. Destination Field: TARGETDESC. (This will automatically populate the targetdesc field on the ticket object with the content of the location s description.) 3.Go to Application Designer and open the design for WOTRACK. 4.Click on the Work Order tab. 5.Assuming there is no existing Target Description field in the design, use the Control Palette to add a new Textbox below Location. Click on the new field and open its Properties dialogue. Assign it WORKORDER.TARGETDESC. Close the dialogue and save the changes. 6.Go to Work Order Tracking and create a new WO. 7.Look up a location on the location field. The target description field will be automatically populated with the location description. 8.Create another new WO (not saving the previous one). This time look up an asset. The location field is updated, as is the target description field. CURRENT ERRONEOUS RESULT: Crossover not working EXPECTED RESULT: Crossover should work the way it did in earlier version. ADDITIONAL INFO: ENVIRONMENT (SYSTEM INFO): 7.6.0.8-IFIX20180302-1039 Build 20170512-0100 DB Build V7608-63 HFDB Build HF7608-14 7.6.0.9 Build 20171127-0100 DB Build V7609-45 LOCAL FIX:
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * YES * **************************************************************** * PROBLEM DESCRIPTION: * * When location set the flag included NOACTION which caused * * the crossover domain to not execute * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
The fix for this APAR is contained in releases 7.6.0.8, 7.6.0.9 and future releases.
Temporary fix
Comments
APAR Information
APAR number
IJ06099
Reported component name
SYSTEM CONFIG
Reported component ID
5724R46S1
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-05-01
Closed date
2018-07-09
Last modified date
2018-07-09
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
SYSTEM CONFIG
Fixed component ID
5724R46S1
Applicable component levels
R760 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":"760","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
09 July 2018