APAR status
Closed as program error.
Error description
New asset assembly (CM) duplicate function does not use autonumber (SEED + PREFIX) anymore in ACM 7.1.1.2 . When creating a new asset assembly (CM) record, an auto number is used when duplicating a new asset assembly (CM) record, auto number is NOT used and the field is blank *(See attached file ) This behavior started after upgrade from ACM 7.1.1.0 to ACM 7.1.1.2 (it was working fine in ACM 7.1.1.0) (SEED + PREFIX) . update the Maxattributecfg and Maxattribute tables: update maxattributecfg set canautonum=1, autokeyname = 'ASSETNUM' where attributename='ASSETNUM' and objectname ='PLUSANEWASSET'; update maxattribute set canautonum=1, autokeyname = 'ASSETNUM' where attributename='ASSETNUM' and objectname ='PLUSANEWASSET'; commit; 3. Go to Database Configuration 4. Select PLUSANEWASSET object, ASSETNUM attribute 5. Insert &AUTOKEY& in Default Value field 6. Apply Configuration Changes 7. Launch the Organization application 8. From Select Action menu, select the Autonumber setup 9. Select Site Level 10. Select the site and click New Row 11. Enter your seed value and a prefix 12. Save 13. Go to Assets -> New Asset Assemblies (CM) 14. Create a new record 15. The autonumber is correctly set 16. Duplicate this record 17. The Autonumber is not used, the field is null
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: * * User of New Asset Assemblies (CM) duplicate function * **************************************************************** * PROBLEM DESCRIPTION: * * When duplicating a New Asset Assemblies (CM) record the * * autokey is not utilised to determine the new Assetnum. * **************************************************************** * RECOMMENDATION: * * Deploy the hotfix to resolve this issue. * **************************************************************** Code executed on duplicate clears out Assenum generated from autokey.
Problem conclusion
Code modified to skip assetnum population on duplicate. The fix for this APAR is contained in the following maintenance package: | release\fix pack | Interim Fix for Release 711 ACM
Temporary fix
Comments
APAR Information
APAR number
IV32330
Reported component name
MX ASSET CONFIG
Reported component ID
5724R4500
Reported release
711
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-11-20
Closed date
2012-12-07
Last modified date
2012-12-07
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
MX ASSET CONFIG
Fixed component ID
5724R4500
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLKSJ","label":"Maximo Asset Configuration Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"711","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
21 August 2024