You are on page 1of 2
nar018 Document 1461453.1 Copyright (¢) 2018, Oracle, Al rights reserved, Orde Confident Fusion CS’ ‘AQ - Defining Subledger Accounting Rules (Doc ID 1461453.1) In this Document Purpose ‘Questions and Answers What segments of subledger accounting rules require manual setup? Using a purchase order charge account is not in any of the seeded SLA setup, What are some common accounting ‘scenarios that would require subledger accounting rules that are not seeded? {Is it possible to set up code combination identifiers using PL/SQLs? Oracle Fusion Cost Management - Version 11.1.11.1.0 and later Oracle Fusion Receipt Accounting - Version 11.1.11-1.0 and later Information in this document applies to any platform. Product: Oracle Fusion Cost Management Product Version: 1.0 Document Revision: 1.0 ‘Authors: Cost Management Development & Cost Management Support Guide Category: Set Up Product Management - Define Cost Management / Define Receipt Accounting - Define Subledger ‘Accounting Rules What segments of subledger accounting rules require manual setup? Almost all line types require establishment of the account derivation rules, Only the following do not require manual setup: (a) Offset entry to the miscellaneous transaction derives from the account entered on the transaction, (b) Supplier accrual account and PO charge account (expense destination cases) have accounts derived from purchase order distribution. Note: The PO derives the accounts from costing mapping set definition. Using a purchase order charge account is not in any of the seeded SLA setup. What are some common accounting scenarios that would require subledger accounting rules that are not seeded? Purchase order charge account is available as a source in the rules definition for expense destination flows. Refer to subledger accounting help for more information on how to set up the subledger accounting methods and account derivation rules. Is there any way to tie a pa icular setup to more than one chart of accounts but not all charts? itps1/suppor oracle. comlepmosfaces/DocumentDisplay?_adf ct-state=iqhf98g8_ 6608id=1461463.1 12 nar018 Document 1461453.1 ‘The account derivation rules can be set up in one of the following two ways: 1, Set up the rule without a specific chart of accounts by using the transaction attributes. For example, use the source account option to select the offset account directly from a miscellaneous transaction. 2. Specify a single, specific, chart of accounts and derive the accounts in the rules explicitly from that chart of accounts. You cannot include more than one chart of accounts in the same rule setup, For easier data entry, you can copy definitions from rule to another with Subledger Accounting setup pages. Is it possible to set up code combination identifiers using PLISQLs? Development has confirmed SLA is not going to provide functionality that allows customers to define pl/sql functions to use in rules. Didn't find what you are looking for? itps1/suppor oracle. comlepmosfaces/DocumentDisplay?_adf ct-state=iqhf98g8_ 6608id=1461463.1 22

You might also like