APAR status
Closed as program error.
Error description
DESCRIPTION: When an item is entered on a Desktop Requisition, and the focus leaves the item field, and then the item is changed to a different item with the same Classification, the requisition presents an error when submitting. STEPS TO REPRODUCE: -Log in to maxdemo instance -Go To Administration | Classifications -Common Actions | New Classification -In the Classification field enter "CL-1" and tab out -Click Yes at the System Message to add it -In the Description field enter "CL ONE" -In the Order field enter 1 -In the Use With section click the New Row button -In the Use With Object field enter "item" and tab out -Click the New Row button -In the Use With Object field enter "mrline" and tab out -In the Attributes section click the New Row button -In the Attribute field | Select Value | click any ALN value, such as A/C -Click the checkbox for "Apply Down Hierarchy" -Click the New Row button -In the Attribute field | Select Value | click any other ALN value -Click the checkbox for "Apply Down Hierarchy" -Save the record -Common Actions | Duplicate Classification -In the Classification field enter "CL-2" and tab out -Click Yes at the System Message to add it -In the Description field enter "CL TWO" -In the Parent Classification field | Detail Menu | Double-click CL-1 -In the Attributes section click the New Row button -In the Attribute field | Select Value | click any ALN value that was not selected for the parent Classification -Click the checkbox for "Apply Down Hierarchy" -Save the record -Go To Inventory | Item Master -Common Actions | New Item -In the Item field enter "MR-1" -In the Description field enter "Selection 1" -In the Order Unit field enter "each" and tab out -In the Issue Unit field enter "each" and tab out -On the Specification tab | Classification field | Detail Menu | Classify -Expand the details for CL-1, then click CL-2 -Verify that the 3 Attributes are populated as expected -Verify that the Description field has updated to the value generated by the Classification as expected -Save the record -More Actions | Add Items To Storeroom -In the Storeroom field enter "central" and tab out -Click OK -In the Unit Cost field enter 12 -In the Current Balance field enter 4 -Click OK -Common Actions | Change Status -In the New Status field click the drop-down arrow, then click Active -Click the checkbox for "Roll New Status to Organizations and Inventory?" -Click OK -More Actions | Duplicate Item -In the Item field enter "MR-2" -In the Description field verify that the Classification had generated the value as expected" -On the Specifications tab verify that the 3 Attributes are populated as expected -Save the record -More Actions | Add Items To Storeroom -In the Storeroom field enter "central" and tab out -Click OK -In the Unit Cost field enter 12 -In the Current Balance field enter 4 -Click OK -Common Actions | Change Status -In the New Status field click the drop-down arrow, then click Active -Click the checkbox for "Roll New Status to Organizations and Inventory?" -Click OK -Go To Self Service | Desktop Requisitions | Create Requisition -In the Required Date field click the Select Date and Time button -Click on a date that is two days in the future, then click OK -In the GL Debit Account field | Select Value -Click 6000, then 200, then 000, then click OK -Click the Continue button -In the Requisition Line Items section click the New Row button -In the Item field | Detail Menu | Classification -Expand the details for CL-1, then click CL-2 -Click MR-1 -In the Quantity field enter 1 and tab out -In the Item field | Detail Menu | Classification -Expand the details for CL-1, then click CL-2 -Click MR-2 -Click the Submit button RESULT: The rows for the Item are duplicated in the Attributes section and a System Message is presented: "BMXAA4129E - The record for Reference Object ID=205, Attribute=AC, Section=,Reference Object Name=MRLINE already exists. Ensure that the key value for the given record is unique." EXPECTED RESULT: The Attributes will not be duplicated and the Requisition can be submitted REPORTED IN VERSION: Tivoli's process automation engine 7.6.1.1-IFIX20200124-1352 Build 20190514-1348
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Maximo users who use the Desk Top Requisition * **************************************************************** * PROBLEM DESCRIPTION: * * Duplicated attributes caused database errors when changing * * items with common classification attributes on the Desk Top * * requisition application. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
This is fixed in code. The fix for this APAR is contained in the following maintenance package: | release\fix pack | Interim Fix for Release 7.6.1.3 Product
Temporary fix
Comments
APAR Information
APAR number
IJ24038
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
2020-04-01
Closed date
2020-10-19
Last modified date
2020-10-19
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
MAXIMO ASST MGM
Fixed component ID
5724R46AM
Applicable component levels
[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]
Document Information
Modified date:
20 October 2020