My Oracle Support Banner

EAM ARG 9.1:Asset Reinstatement Transactions Are Not Calculated Correctly After the Inflation Adjustment Process (AMDPINFL) if the Reinstatement Accounting Period Is Different From the Retirement Period and AMDPINFL has "Error on line 71" on MSS Database (Doc ID 2926256.1)

Last updated on FEBRUARY 07, 2023

Applies to:

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

Symptoms

Asset Reinstatement transactions are not calculated correctly after the inflation adjustment process if the reinstatement accounting period is different from the retirement period.


The issue can be reproduced at will with the following steps:

Setup:
1. Enable "Proceso Inflación" on the following setup pages:
Menu Principal > Def Finanzas/Cadena Suministro > Instalación > Opciones de Instalación
and
Menú Principal > Def Finanzas/Cadena Suministro > Datos de Unidades de Negocio > Gestión de Activos > Definición Gestión de Activos
2. Make sure that "Tipo Transaccion" (Transaction Type) = 'INF' is present under the following navigation:
Menu Principal > Def Finanzas/Cadena Suministro > Datos de Productos > Gestión de Activos > Contabilización > Plantillas Entradas Contables

Replication Steps:
1. Add a new asset for ARS 10,000. Transaction and Accounting Date: 1/Dec/18
Menu Principal > Gestión de Activos > Transacciones de Activos > Activos en Propiedad > Alta Rápida de Activos
2. Calculate the Depreciation(a), Create the Accounting Entries(b), Close the Depreciation(c), and Calculate the Inflation(d) up to Jan. 2019.
(2.a) Menú Principal > Gestión de Activos > Cálculo de Amortización > Amortización de Activos > Cálculo de Amortización
(2.b) Menú Principal > Gestión de Activos > Entradas Contables > Creación de Entradas Contables
(2.c) Menú Principal > Gestión de Activos > Entradas Contables > Cierre de Amortización
(2.d) Menú Principal > Gestión de Activos > Entradas Contables > Cálculo de Inflación
3. Perform a Retirement as of Feb. 2019. Use disposal code Scrap and Save.
Menú Principal > Gestión de Activos > Transacciones de Activos > Enajenación de Activo > Baja/Reintegración de Activos > Baja de Activoss
4. Calculate the Depreciation, Create the Accounting Entries, Close the Depreciation, and Calculate the Inflation for Feb. 2019.

Note: On Database Type: Microsoft, the Inflation Calculation Process (AMDPINFL) fails with the below errors after applying Bug 34155847 and Bug 34614967.
Bug 34782669 addresses the error, this is why it is recommended to apply all three Bugs: Bug 34155847, Bug 34614967, and Bug 34782669

 *Error found in the AMDPINFL_xxx.out process monitor trace file

5. Review the inflation calculation for period 2 2019.
Menú Principal > Gestión de Activos > Transacciones de Activos > Historial > Revisión de Inflación
*It looks ok since it balanced out calculations.
6. Run the Depreciation Close and Calculate the Inflation for period 3 2019.
*Nothing happens since the asset has been retired.
7. Perform a Reinstatement with an accounting date in period 4 2019.
Menú Principal > Gestión de Activos > Transacciones de Activos > Enajenación de Activo > Baja/Reintegración de Activos > Baja de Activoss
8. Calculate the Depreciation, Create the Accounting Entries, Close the Depreciation, and Calculate the Inflation Adjustment for Apr. 2019.
*No calculations have been done. It is expected that the Inflation Calculation process would have calculated inflation for this period since
9. Review Inflation history for 2019 recategorization.
*The COST value is ok, however, the DPR value zeroes out between categories, which is not correct. It should have transferred the balance to the new category.
10. Run the Depreciation Close and Calculate the Inflation for period 3 2019
11. Review Inflation history for 2019 period 3
*Only the COST line is calculated. The DPR line is missing. DPR should have been calculated since the asset is fully depreciated however, it is still under the effect of inflation.

Detailed FSCM ARG 9.1 DEMO Replication Steps and Replication Steps w/Error attached.

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
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.