APAR status
Closed as program error.
Error description
The WORKORDER.PHONE is not displayed correctly when using WORKORDER.REPORTEDBYNAME as the field interface in Work Order Tracking application. PROBLEM DESCRIPTION If you use WORKORDER.REPORTEDBYNAME field in user interface in Work Order Tracking (SP) application, value in WORKORDER.PHONE field is not properly set when you have two people with the same value in "Display Name". PERFORMANCE=N STEPS TO REPRODUCE PRE-REQUISITES 1. Go to People application and duplicate REVIS (Tom Revis): Values for a new person: - Person ID: TOMREVIS - First Name: Tom - Last Name: Revis - Display name: Tom Revis - Phone: 222222 2. In the People app, for REVIS user ID, add the phone number: 111111 So, the phone for REVIS is 11111 and for TOMREVIS the phone is 22222 Have chose these phone numebrs in order to have a more visible scenario. - Save the changes 3. GoTo Aplication Designer, bring up WOTRACK app and add WORKORDER.REPORTEDBYNAME field on Workorder tab section, in Responsibility section: Textbox - Attribute: REPORTEDBYNAME - Lookup: PERSONNAME - Go To Application: Person - Menu Type: NORMAL 4. Save the changes REPRODUCTION STEPS 5. Create a new Workorder, or open any existing one. 6. Remove all values from Responsibility section 7. In the "Person Name" field (WORKORDER.REPORTEDBYNAME) find "Tom Revis" and select second person from the list (in my case: TOMREVIS) 8. Value in WORKORDER.PHONE was set from the first person (11111) on the list instead of value from second person (22222). This is NOT ok 9. If to go to "Reported by" field (WORKORDER.REPORTEDBY) and to bring the second person TOMREVIS , is shows the correct PHONE value (22222) CURRENT ERROUNEOUS RESULT Value in WORKORDER.PHONE was set from the first person (11111) on the list instead of value from second person (22222). EXPECTED RESULT: Value in WORKORDER.PHONE set from correct person, in this case TOMREVIS ID . ADDITIONAL INFO: Reproduced by L2 without Service Provider in core Maximo ENVIRONMENT (SYSTEM INFO): Tivoli's process automation engine 7.6.0.3-IFIX20160511-1156 Build 20160113-2204 DB Build V7603-151 HFDB Build HF7603-03 IBM TPAE Integration Framework 7.6.0.3 Build 20160108-1912 DB Build V7603-21 IBM Maximo for Service Providers 7.6.2.0-20160609-1601 Build 20160609-1601 DB Build V7620-10 HFDB Build HF7620-13 IBM Maximo Asset Management 7.6.0.3 Build 20160113-2204 DB Build V7603-01 IBM WebSphere Application Server 8.5.5.4 Server OS - Windows 6.3 Server DB - DB2/NT64 10.5 (SQL10054)
Local fix
Use the WORLORDER.REPORTEDBY field
Problem summary
**************************************************************** * USERS AFFECTED: * * Users with multiple Person entries with the same Displayname * * and different Phonenums. * **************************************************************** * PROBLEM DESCRIPTION: * * When multiple Person entries with the same Displayname and * * different Phonenums exist, the correct Phonenum is not * * always populated into a Work Order when a value is entered * * into ReportedByName in Work Order. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
The fix for this APAR is included in the following package: | Release 7.6.0.6 of Base Services.
Temporary fix
Comments
APAR Information
APAR number
IV88293
Reported component name
ADMINISTRATION
Reported component ID
5724R46A1
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-08-22
Closed date
2016-08-23
Last modified date
2016-08-23
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
R750 PSY
UP
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":"760","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
23 August 2016