EAM: AM-USETAX_AMT, USETAX_AMT_BSE, SALETX_AMT, SALETX_AMT_BSE Stored With 3 Decimal Places In AM

(Doc ID 2420942.1)

Last updated on JULY 09, 2018

Applies to:

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

Symptoms

On : 9.2 version, Integration

ACTUAL BEHAVIOR
------------------------
USETAX_AMT, USETAX_AMT_BSE, SALETX_AMT, SALETX_AMT_BSE stored with three decimal places in AM tables for Purchasing/Receipt Transactions.

When creating a PO with an odd numbered quantity and serializing the receipt, the system is storing three decimals places for certain fields in the INTFC_PRE_AM, INTFC_PHY_A and ASSET_ACQ_DET tables. When processing the associated voucher, the system stored only two decimal places as expected

EXPECTED BEHAVIOR
--------------------------
Expect it to be two decimals, following suit with how the records are created when the voucher is interfaced through to AM

STEPS
--------
The issue can be reproduced at will with the following steps:
1. Create a PO and Receipt with odd numbered quantity
2. Interface to AM - notice the system is storing three decimals places for certain fields in the INTFC_PRE_AM, INTFC_PHY_A and ASSET_ACQ_DET tables.
3. Voucher the PO
4. Interface to AM- notice the system is correctly storing two decimals places for certain fields in the INTFC_PRE_AM, INTFC_PHY_A and ASSET_ACQ_DET tables.

BUSINESS IMPACT
----------------------
The issue has the following business impact:
This causes an issue when importing the data to our Data Warehouse as well as running custom reports.

Changes

 

Cause

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