My Oracle Support Banner

EAM: The AM_COST_SUM Process Nullifies the Trans_DT on Summed Cost Rows When the Trans and Accounting Date Range on the Run Control is not Inclusive of the Trans and Accounting Dates on the Cost Row (Doc ID 2483091.1)

Last updated on JULY 22, 2020

Applies to:

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

Symptoms

When performing the cost summarization on multiple add rows with trans and accounting dates in different periods, if the from date in the date range is after the trans date but before the accounting date and the end date is after the accounting date, the trans date on the ps_cost table will be nullified on the summed cost row. In other words, the specific scenario has a Run Control with a date range that encompasses 1 period with cost transactions that are dated within the range based on the Acctg_Dt but outside of the range based on TRANS_DT. The transactions are summarized, but the TRANS_DT field is left NULL. Additionally, a new row is inserted into the ps_open_trans row for the summed cost row rather than replacing the original transactions with a summed transaction row as occurs on the ps_cost table.


Expected behavior
-----------------------
It is expected that the trans date will not be nullified as a result of this scenario and that the original rows in the ps_open_trans table will be replaced by a summed transaction row to correspond to the summed cost row.

Steps
---------

This issue can be verified by performing the following steps:
1) Create an asset on the Express ADD component with the trans and accounting dates in different periods.
2) Add an additional ADD row with the same chartfield and trans and accounting dates via the Cost Adjust/Transfer Asset component.
3) Run the depreciation process.
4) Create accounting entries.
5) Summarize the ADD rows on ps_cost for the CORP book by submitting the Cost Summarization process. Enter a date range that encompasses the period in which the accounting date occurs and beginning after the period in which the trans date occurs.
6) Review the cost table. Note that the trans date has been nullified on the summed row.
7) Review the open trans table. Note that instead of summing the transactions, a new transaction row has been inserted.

Business Impact
--------------------
This is particularly troublesome because COST records with no TRANS_DT are not selected in the COST_BAL_VW, which is used extensively in Reporting and Reconciliation. Further, the corruption to the asset this causes may have additional unpredictable results.

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.