Project-Related Accounts Derivation for Oracle Applications

Account rules specify how the Account Combination is derived on subledger journal entry lines. You can specify the conditions under which a rule becomes applicable. Using this feature, you can develop complex rules for deriving accounts under different circumstances.

Accounts imported from third-party applications or the Oracle Application Desktop Framework Desktop Integration are available as sources in Oracle Fusion Subledger Accounting.

You can optionally create account rules with your specifications. If you define an account rule for an account combination, then the rule determines each segment of the Accounting flexfield. If you define an account rule for a segment, then the rule determines the value for a single Accounting flexfield segment. You can use both segment and account combination rules to derive a single account. If you assign both types of account rules to a single journal line definition, then Oracle Fusion Subledger Accounting uses the account segment rules first and then takes the remaining values from the account combination rule.

Deriving Projects-Related Accounts

The only method to derive project-specific accounts is to use project sources in the accounting method. You define account rules to derive project-related accounts for the following Oracle Fusion applications:

  • Oracle Fusion Purchasing: Project-specific accounts, such as the purchasing charge account and accrual account, are derived by using transaction account derivation rules

  • Oracle Fusion Cost Management: All project-specific accounts are derived during accounting creation in Oracle Fusion Subledger Accounting.

  • Oracle Fusion Payables: The project-specific accounts are not derived until the journal entries are created within Oracle Fusion Subledger Accounting. Oracle Fusion Expenses need not derive project-specific accounts because they are derived after the records are transferred to Oracle Fusion Payables.

  • Oracle Fusion Receivables: AutoAccounting generates a default account for invoices originating from Oracle Fusion Project Billing. This default account isn't based on the contract. If you need a contract-specific account, you must set up account rules in Oracle Fusion Subledger Accounting to override the default account when the final accounting is performed by Oracle Fusion Receivables.

You must update the account rules to derive project-specific accounting. Create project-specific rules by evaluating the Project Identifier. Derive a project-specific account combination or override a single account segment with a project-specific value. Use more than 100 project-specific sources to create mapping sets and account rule conditions. Examples of these sources include:

  • Billable Indicator

  • Capitalizable Indicator

  • Retirement Indicator

  • Project Type

  • Expenditure Type

  • Expenditure Type Descriptive Flexfield Attribute 1

  • Task Descriptive Flexfield Attribute 1