How To Transfer Transactions To GL (Summary) in Cost Management [ID 740215.

1] In this Document Goal Solution References

Applies to:

Oracle Cost Management - Version: 12.0.0 and later [Release: 12 and later ] Information in this document applies to any platform.
Goal

How to Transfer to GL in Summary in R12. In R12, inventory transactions are being imported to GL in Detail instead of in Summary format. All seeded Journal Line Types have Transfer to GL radio button set to Detail and cannot be updated.
Solution

Apply Patch 7506072 to update file patch/115/import/US cstxlaaad.ldt 120.22.12000000.27 or the latest. Patch 7506072 is only for the Costing application in SLA. It does not affect AP or AR. If user does not want to apply the patch, then please follow the manual approach as follows: To transfer to GL in Summary in R12 - R12.0.5, a custom Application Accounting Definition (AAD) needs to be setup. This involves creating a User owned Application Accounting Definition (AAD), Journal Line Definition (JLD) and Journal Line Types (JLT), then assigning this AAD to your Subledger Accounting Method (SLAM). In summary, 4 of the 8 steps outlined in the SLA Implementation Guide under the section 'Accounting Methods Builder Process' are required. This includes copy / modification of the seeded AAD, JLD and JLT. These 4 steps are: 7. 6. 1. 8. Define Define Define Define Application Accounting Definitions Journal Line Definitions Journal Line Types Subledger Accounting Methods

Steps are done in reverse order from what is shown in the Implementation Guide: 1. Start with Define Application Accounting Definitions (AAD): Copy the seeded one being used and modify it to a custom name. Navigation Path; Responsibility, Cost Management SLA > Accounting Setup > Accounting Methods Builder > Methods and Definitions > Application Accounting Definitions> Select seeded AAD then click on "Copy" button and create into a user defined AAD. ( Please review sample attached screen shot AAD-User defined.docx ) 2. Click "Validate" button to validate all Event Class and Event Type Assignments 3. In the user defined AAD, go through each attached Journal Line Definition (JLD) and copy the seeded one and modify to a user defined custom name. see example file JLD-User defines.docx Make sure to remove the link between the custom AAD and the standard JLD when adding the link between custom AAD with the custom JLD. 4. In the user defined Journal Line Definition (JLD), go through each attached Journal Line Type and copy the seeded one and modify as necessary, including selecting the Transfer to GL radio button = Summary see example file JLT-User defines.docx Note: a. Make sure to select the correct "Event Class": The event class between your custom "Journal Line Definition" and your custom "Journal Line Type" has to match. Please make sure to navigating to the next record after clicking on the Line Type button. Since multiple event classes are assigned to line type for example "Receiving Inspection", the first record shows event class as "Delivery to Expense Destination", user has to press the down arrow to get to the appropriate event class, in this case "Receipt into Receiving Inspection" and copy that for custom use. b. When linking your custom "Journal Line Type" to your custom "Journal Line Definition", you

need to: Provide the correct "Account Derivation Rule" name for example "Cost Management Default Account ". Also remove or inactivate the existing link between your custom "Journal Line Definition" and the standard "Journal Line Type" 5. Go to the Define Subledger Accounting Method (SLAM) screen and end date the old AAD and add a row for the new user defined AAD with a beginning effective date. This effective date needs to be at least a day later than the end date of the old AAD. The dates cannot overlap. Another option is to delete the seeded Application. Navigation Path; Responsibility, Cost Management SLA > Accounting Setup > Accounting Methods Builder > Methods and Definitions > Subledger Accounting Method 6. Need to remove ORACLE SEEDED JLD& JLT from the user defined AAD, otherwise double accounting entries will occur. 7.Need to run XLAABACR Validate Application Accounting Definitions request. 8. Need to run Create Accounting - Cost Management process 9. For release 12.1, the Journal Line Detail (JLT) default value for Transfer to GL is set to "Summary".
References

BUG:7420332 - INVENTORY TRANSACTIONS POST TO GL IN DETAIL INSTEAD OF IN SUMMARY BUG:7506072 - PRE-SEEDED JLT SETUP FOR SUMMARY TRANSFER TO GL FOR INVENTORY TRANSACTIONS

Attachments
AAD-User defined.docx (96.37 KB)

JLD-User defines.docx (110.6 KB)

JLT-User defines.docx (114.02 KB)