EAM: Copy Existing Asset Function Inserting Incorrect Dttm_stamp In Document Sequence

(Doc ID 1937242.1)

Last updated on APRIL 25, 2016

Applies to:

PeopleSoft Enterprise FIN Asset Management - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.


When 100 assets with Document Sequencing enabled are copied within a BU with translate books, the DTTM_Stamp is incremented between books on the PS_AM_DOC_SEQ table. This has caused multiple journals to be generated for the corresponding accounting entries in the PS_DIST_LN table. Please note that the replication steps show that this does not occur when only 50 assets are copied.

Expected Behavior
The expectation is the DTTM_Stamps will not be incremented when 100 assets are copied.

This issue can be replicated by performing the following steps:

1) Ensure that Document Sequencing is setup at the Installation Level and the GL BU Level.
2) Create an asset.
2) Make 100 copied of the asset via the AM Asset Copy component.
3) Create accounting entries for one of the assets.
4) Journal Generate the ADD accounting entries for the asset.

Business Impact
The issue is critical since all of the ADD asset amounts are getting duplicated when they go to General Ledger.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms