APAR status
Closed as program error.
Error description
When the template is built the attributes are not applied to the description in the correct order specified. Also when assets are created, the asset description is not generated based on the values supplied in the classification that was applied to the Asset Template. Steps to replicate Prior to testing we create a test classification Go to Administration<Classification and insert a new record and give it a unique ID Ensure Generate Description is checked GO to Use With data area and insert new roe Enter Asset GO to Attributes data area hit new row, Enter attrib1 and ok message to create Fill in Data Type=ALN, click Use with Object Detail on line and enter Sequence=1 hit new row, Enter attrib2 and ok message to create Fill in Data Type=ALN, click Use with Object Detail on line and enter Sequence=2 hit new row, Enter attrib4 and ok message to create Fill in Data Type=ALN, click Use with Object Detail on line and enter Sequence=4 hit new row, Enter attrib3 and ok message to create Fill in Data Type=ALN, click Use with Object Detail on line and enter Sequence=3 Save record Now the test to demonstarte the behavior that occurs which prompted the PMR 1) Go To Asset Templates 2) Click New record 3) Fill in Asset Template, Asset Description 4) Click on Specifications Tab, click on double arrow next to Classification, select classification created above 5) Fill in values for attributes ? Values used show where the attribute should appear in the asset description i.e. attrib1 given value post1, value attrib2 given value post2 etc. 6) Click the Save button. Note the template description was created ? the specifications were NOT applied in the correct order 7) Change Template Status to ACTIVE 8) Select Action ? Generate New Assets 9) Filled in Site BEDFORD, Click OK 10) Pick a Location from the Select Value List, Enter Quantity=3 in the Generate Asset Numbers 11) Click the Generate Asset button 12) Asset table populated, Click Ok. Receive Message :Template was applied. 13) Go to Assets 14) Find an asset that was created using the Template Note the Asset description does not contain the values from the classification. 15) Change value of some of the attributes and save the asset Note the description is created but with the attributes applied in the wrong order.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Maximo users using Asset Template * **************************************************************** * PROBLEM DESCRIPTION: * * Asset Template does not apply classification correctly based * * on the classification's sequence for attributes. * * Additionally,the new assets generated do not have * * description when the asset description on the template was * * blank but the asset template's description is generated by * * the classifica * **************************************************************** * RECOMMENDATION: * * none * ****************************************************************
Problem conclusion
This is fixed in code. he fix for this APAR is contained in the following maintenance package: | release\fix pack | Interim Fix for Release 7.5.0.9 Product
Temporary fix
Comments
APAR Information
APAR number
IV73397
Reported component name
ASSETS
Reported component ID
5724R46AS
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-05-19
Closed date
2015-06-19
Last modified date
2015-06-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
ASSETS
Fixed component ID
5724R46AS
Applicable component levels
R750 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":"750","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
09 April 2023