My Oracle Support Banner

EAM: Using Page & Field Config To Make Tag Number Required Results In Gap In Asset ID Generated (Doc ID 2650474.1)

Last updated on JULY 21, 2020

Applies to:

PeopleSoft Enterprise FIN Asset Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When using Page & Field Config to make Tag Number Required, the next asset ID assigned is skipping a number in the sequence.

Gap in Asset ID generated after installing PUM 35 which includes:

<Bug 30270015> - EAM: WHEN TAG NUMBER REQ PER PAGE & FIELD CONFIG, ABEND OCCURS ON NEXT ASSET ADD
<Bug 30718772> - EAM: ERROR ADDING ASSET WHEN TAG NBR REQUIRED PER PAGE & FIELD CONFIG CONT.
<Bug 30718801> - EAM: BASIC ADD - INVALID DECIMAL VALUE -- 99051-1. (180,106) ADD_WRK.CAPITALIZE_

The expectation is that the asset id auto number generator will generate numbers without skipping a number in the sequence.

The issue can be reproduced at will with the following steps:
1. Set up Page & Field Config (Enterprise Components) to make Tag Number Required
2. Add Asset via Basic ADD with and without Tag number.
3. Note the next asset ID assigned is skipping a number in the sequence.

Please find attached Replication Steps.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.