Last updated on AUGUST 23, 2017
Applies to:Oracle Purchasing - Version 12.0 and later
Oracle Cost Management - Version 12.0.0 and later
Information in this document applies to any platform.
On R12, When trying to use the “SLA” functionality for “PO Delivery into Inventory” transaction, the process fails.
Steps To Reproduce:
1) Defined two Journal Line types for event class “PO Delivery into Inventory”
a. POREC (for Inventory Valuation)
b. PORECRI (for Receiving Inspection)
2) Defined a Journal Entry Description
3) Define Mapping Set – to derive the actual account combinations
a. MAP (for Inventory Valuation)
b. MAP2 (for Receiving Inspection)
4) Define Account Derivation Rule
a. ADR1 (for Inventory Valuation) linked to “MAP” Mapping Set
b. ADR2 (for Receiving Inspection) linked to “MAP2” Mapping Set
5) Defined Journal Lines “POINV” consisting of following two Journal Line types :
6) Defined Application Accounting rule “AAD1” for
a. Event class – “PO Delivery into Inventory”
b. Event Type – “PO Delivery into Inventory”
7) Defined Subledger Accounting Method “SLAM1” with the “AAD1” account rule
8) All other setups are taken care.
1) Created Accounting for a PO receive Transaction:
The Accounting Process is completed and the output
1) Picked up correct Inventory Valuation Account
2) Debit and Credit - both Accounting entries went to Inventory Valuation Account
3) The Receiving Inspection Account is blank in the output.
SLA Program Report shows the following:
Ledger = PLG
Event Class = PO Delivery into Inventory
#of Docs = 3
Number of Events = in error = 3
There are events which could not be processed because no data could be found on transaction objects. Please enable profile option SLA: Enable Diagnostics create accounting again and run the report for Transactions Objects Diagnostics to identify the problem
No account is displayed although the inventory valuation account is populated
Subledger accounting was unable to derive an accounting code combination using the account
derivation rule ADR2 owned by User.
Please review the account derivation rule and make sure it delivers a valid accounting
flexfield combination for the source values passed for the transaction.
Message for all three of the erred transactions:
There is no application accounting definition available for the application Cost Management
and the subledger accounting method Standard Accrual owned by Oracle.
Either no application accounting defintion is assigned to the subledger accounting method or the GL date of the accounting event does not correspond to effective date range of any application accounting
definitions assigned to the subledger accounting method.
Please assign an application accounting definition to the subledger accounting method or update the effective date range of any application accounting defintions contained in the subledger accounting method.
The errors listed above were resolved by validating
1- Run the validate accounting definitions concurrent process for all ledgers.
The issue of the incorrect accounts and null accounts is still occurring.
The profile option "CST: Receiving Accounting Option" is set to "Concurrent".
It was expected that :
1) Credit should go to Receiving Inspection Account instead of Inventory Account
2) Correct Receiving Inspection Account should be picked up based on SLA.
1) Debit and Credit - both Accounting entries went to Inventory Valuation Account which is incorrect.
Debit should go to Inventory Valuation Account and Credit should go to Receiving Inspection
Account for PO Delivery to Inventory Transaction..
2) The Receiving Inspection Account is blank in the output.
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