Restrict the GL import of Perpetual Accounting Entries for Organizations which uses Periodic Average Costing (PAC)
(Doc ID 2018637.1)
Last updated on MAY 07, 2019
Applies to:Oracle Cost Management - Version 12.1.3 and later
Information in this document applies to any platform.
If do not require the perpetual accounting in SLA, Can we prevent generating the perpetual accounting by which do not run the "Create Accounting-Cost Management" without any problems in oracle system? (e.g. Can not close any periods)
In NOTE:429105.1 Impact of R12 Design in Procure To Pay Accounting Flow, there are the following description related to PAC.
Impact of Periodic Average Costing on Create Accounting process (applicable for both Online accruals and Period end accruals)
R12 SLA design has no impact when Periodic Average Costing (PAC) is used as it follows the same 11i approach. Accounting entries created in PAC will not go to SLA and it will not undergo the create accounting process. Instead it will get transferred to GL via gl_interface from PAC distributions . But the perpetual accounting entries will also happen along with PAC entries where the perpetual accounting will follow the SLA design. But those entries should not get imported from SLA to GL as PAC accounting will be transferred to GL. To restrict the GL import of perpetual accounting entries, "Transfer to GL" option in organization parameters should be set to None for organizations which use PAC so that xla_ae_headers for perpetual accounting will have the gl_transfer_status_code as "NT" and it will not be picked by the journal import process.
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