EAM: Project Costing Chartfield Feature Causes an Abend at Step AMDPREPT.DPRPT200.STEP16 (SQL) -- RC = 805 (Doc ID 1394795.1)

Last updated on MAY 19, 2023

Applies to:

Symptoms

The Transaction Loader (AMIF1000) populates the BUSINESS_UNIT_PC, ACTIVITY_ID, RESOURCE_TYPE, RESOURCE_CATEGORY, and RESOURCE_SUB_CAT information on the PS_COST table for transactions interfaced from AP where the PROJECT_ID has been defined as a chartfield for the voucher. This causes the Load Depreciation Reporting Table process (AMDPREPT) to abend with ORA-00001 - unique constraint (SYSADM.PS_DEPR_RPT).  The error is an abend at Application Engine Step AMDPREPT.DPRPT200.STEP16 (SQL) with RC = 805 (duplicate row error).
This occurs when AP transactions are interfaced for existing assets that were created prior to the posting of the Project Costing ChartField Feature (PCCF) feature in Bundle #9 of Release 9.1.

Another symptom of the problem is that the Depreciation Calculation process (AM_DEPR_CALC and AMDPCALC) fails to insert a row into the PS_DEPRECIATION table with TRANSACTION_TYPE = RET, although the Open Transaction appears to have been processed correctly (PS_OPEN_TRANS.CALC_DEPR_STATUS = C).  This means that the asset continues to depreciate after the retirement date.  The data in the PS_COST table shows that only PROJECT_ID is populated in the RET row, but one or more of the other PC ChartFields - BUSINESS_UNIT_PC, ACTIVITY_ID, RESOURCE_TYPE, RESOURCE_CATEGORY, RESOURCE_SUB_CAT - in the ADD row contain values.

Replication Steps
============
1) Post an adjustment to a voucher for which an asset has already been created. The voucher must have the project_id chartfield populated.
2) Interface the AP transaction into AM.
3) Calculate depreciation for the asset.
4) Run AMDPREPT to load the asset to the Depreciation Reporting Table (PS_AM_DEPR_RPT).

Changes

Cause