APAR status
Closed as program error.
Error description
DESCRIPTION: The Attention field uses 2 different queries in the PO application to fetch data in the lookup for the Attention field on two different tabs. It is observed that the Labor table is used in one of the queries and not in the other. -The Attention field on the Ship To/Bill To tab in PO app: Field is mapped to PO.SHIPTOATTN; lookup is PERSON.PERSONID table; class=psdi.app.person.FldPersonID -The Attention field on the PO Lines tab in PO app: Field is mapped to POLINE.SHIPTOATTN; lookup is PERSON.PERSONID table; class= psdi.app.po.FldPOLineShipToAttn It is also observed that the class files use different tables to get the data as follows: -In class FldPersonID.class, this query is used: "status in (select value form synonymdomain where maxvalue='ACTIVE' and domainid='PERSONSTATUS')"); -In class FldPOLineShipToAttn.class, this query is used: " and personid in (select personid from labor where orgid in (select orgid from site where siteid = :tositeid)"); STEPS TO REPRODUCE: *General Condition - see Description 1. Log in to maxdemo instance 2. Go To Purchasing | Purchase Orders 3. Common Actions | New Purchase Order 4. On the PO Lines tab click the New Row button 5. In the Delivery Details section | Attention field | Select Value RESULT: Values in lookup are presented for selection 6. On the Ship To/Bill To tab | Ship To section | Attention field | Select Value RESULT: Different set of names appear in the lookup EXPECTED RESULT: Same set of names appear in the lookup for the Attention field on both tabs in the PO application REPORTED IN VERSION: Tivoli's process automation engine 7.6.1.2-IFIX20210920-2314 Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-46
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * MAXIMO * **************************************************************** * PROBLEM DESCRIPTION: * * ATTENTION FIELD LOOKUP IN PO APPLICATION SHOWS DIFFERENT * * VALUES IN LIST ON DIFFERENT TABS * ****************************************************************
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
IJ39555
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
2022-04-21
Closed date
2023-09-11
Last modified date
2023-09-11
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:
11 September 2023