Cannot Change Asset Management Default Category Set

(Doc ID 1614606.1)
Modified:15-Jan-2014

To
Bottom

Type:PROBLEM

In this Document
Symptoms
Cause
Solution

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and
therefore has not been subject to an independent technical review.

Applies to:
Oracle Enterprise Asset Management - Version 12.1.1 and later
Information in this document applies to any platform.

Symptoms
On : 12.1.1 version, SETUP
When attempting to create/update asset numbers with the new category set, the following error
occurs.
The Asset Management Default Category Set cannot be changed accordingly.

ERROR
----------------------Insert procedure failed with the following error message:
Invalid asset category

STEPS
----------------------The issue can be reproduced at will with the following steps:
1. Responsibility: Enterprise Asset Management
2. Go to Category Sets form

3. Create New category set for eam

4. Assign categories to new set
5. Assign Categories from new set to all existing Asset Groups and Asset Activities
6. Make the new set the default for asset management.
7. Create new asset number
8. Save and get an invalid category error

Cause
Customer had old code of the pertinent files ( EAMFANDF.fmb, EAMPASNB.pls and
EAMPASNS.pls).
Before upgrading to latest versions of the pertinent files, customer was not able to create/update
asset numbers with the new category set. The error 'Invalid asset category' would occur.

Solution
To implement the solution, please execute the following steps:
1. Download and review the readme and pre-requisites for Patch.10407644:R12.EAM.B and
13524856:R12.EAM.B.
2. Ensure that you have taken a backup of your system before applying the recommended patch.
3. Apply the patch in a test environment.
4. Confirm the following file versions:
EAMFANDF.fmb 120.105.12010000.69
EAMPASNB.pls 120.18.12010000.12
EAMPASNS.pls 120.3.12010000.3
You can use the following commands to verify the file version:
strings -a $EAM_TOP/forms/US/EAMFANDF.fmb | grep '$Header'
strings -a $EAM_TOP/patch/115/sql/EAMPASNB.pls | grep '$Header'
5. Retest the issue.
6. Migrate the solution as appropriate to other environments.