Browser version script Skip Headers

Oracle® Fusion Applications Cost Accounting and Receipt Accounting Implementation Guide
11g Release 1 (11.1.2)
Part Number E22767-02
Go to contents  page
Contents
Go to Previous  page
Previous
Go to previous page
Next

18 Cost Management Configuration: Define Receipt Accounting

This chapter contains the following:

Define Subledger Accounting Rules

Define Subledger Accounting Rules

Creating Accounting Method: Explained

Accounting methods group subledger journal entry rule sets together to define a consistent accounting treatment for each of the accounting event classes and accounting event types for all subledger applications. The grouping allows a set of subledger journal entry rule sets to be assigned collectively to a ledger.

For example, a subledger accounting method entitled US GAAP can be defined to group subledger journal entry rule sets that adhere to and comply with US Generally Accepted Accounting Principles (GAAP) criteria.

By assigning a different subledger accounting method to each related ledger, you can create multiple accounting representations of transactions.

Accounting rules can be defined with either a top down, or a bottom up approach. When defining subledger accounting rules from the top down, you will initially define the accounting method followed by components of each rule, which will need to be assigned to it. When defining subledger accounting rules from the bottom up, you will initially define components for each rule and then assign them as required.

The Create Accounting program uses the accounting method definition with active journal entry rule set assignments to create subledger journal entries.

When an accounting method is initially defined, or after modifying a component of any accounting rule associated to the assigned journal entry rule set, its status changes to Incomplete.

The accounting method must be completed, by activating its journal entry rule set assignments, so that it can be used to create accounting.

The following definitions are utilized to define the journal entries, and are applied as updates to the accounting method:

Updates on Predefined Accounting Method

You may update a predefined accounting method by end dating the existing assignment and creating a new assignment with an effective start date.

Assignment of Journal Entry Rule Set for Accounting Event Class and Accounting Event Type

You create the assignment of a journal entry rule set for an accounting event class and accounting event type using the accounting method page.

The following should be considered for assigning rule sets:

Assignment of Accounting Methods to Ledgers

If the accounting method has an assigned chart of accounts, it may only be used by ledgers that use the same chart of accounts.

If the accounting method does not have an assigned chart of accounts, the accounting method can be assigned to any ledger.

Activation of Subledger Journal Entry Rule Set Assignments

You can activate the subledger journal entry rule set assignments from the Accounting Method page. You can also submit the Activate Subledger Journal Entry Rule Set Assignments program to validate and activate your accounting setups.

Fusion Setup Flow

The figure below shows the relationship of components making up an accounting method as described in the above text.

The image visually defines the flow
of subledger components. The subledger may be setup top down, or bottom
up, utilizing the components of the accounting method which include
journal entry rule set which are assigned journal line rules, account
rules and description rules. The journal entry rule set is assigned
to the accounting method, which is assigned to the ledger.

Creating Subledger Journal Entry Rule Sets: Explained

Subledger journal entry rule sets provide the definition for generating a complete journal entry for an accounting event.

Select the option to define the subledger journal entry rule set for a particular accounting event class or accounting event type.

If you are using multiple ledgers to meet divergent and mutually exclusive accounting requirements, you can vary journal entry rule sets by ledger. Each of the subledger journal entry rule sets can meet a specific type of accounting requirements.

For example, use US Generally Accepted Accounting Principles (GAAP) oriented subledger journal entry rule sets for a ledger dedicated to US GAAP reporting, and French statutory accounting conventions for a ledger dedicated to French statutory reporting. These two sets of definitions have differences based on the setup of the various components that make up their subledger journal entry rule sets.

Seeded subledger journal entry rule sets are provided for all Oracle subledgers. If specific requirements are not met by seeded subledger journal entry rule sets, users can create new ones of copy the seeded definitions and then rename and modify the new copied definitions and their assignments.

Subledger journal entry rule set assignments can be made at two levels, header and line. The following are the subcomponents of a subledger journal entry rule set:

Assignment at Header Level

Header assignments define subledger journal header information and line assignments define journal line accounting treatment.

A header assignment includes the following:

Assignment at Line Level

You can define multiple subledger journal entry rule sets for an accounting event class or accounting event type. A single journal entry is generated per accounting event per ledger using the line assignments from the journal entry rule set assigned to the accounting event class or accounting event type.

The following can be assigned to a journal entry line:

Assignment of Description Rules

If a description rule is defined with sources, the sources must also be assigned to the accounting event class that is assigned to the journal entry rule set. The description rule may be assigned at either the header or line level of the journal entry or to both levels.

Assignment of Journal Line Rules

When assigning the journal line rule, you must identify the line type: Gain, Loss, Gain or Loss, Credit, or Debit. The journal line rule must be assigned to the same accounting event class as the one assigned to the subledger journal entry rule set.

When assigning a journal line rule that is enabled for accounting for a business flow, the account combination and certain accounting attribute values are copied from its related journal line having the same business flow class as the current line. Optionally, copy the description rule into the current line instead of assigning a separate description rule.

When assigning a journal line rule that is enabled to copy from the corresponding line within the same journal entry, you have the option to copy the account combination, the segment value, or the line description from the corresponding line into the current line.

Assignment of Account Rules

The account rule assignment will define which accounts will be used for the subledger journal line. If the account rule is setup with a chart of accounts, it must have the same chart of accounts as the one assigned to the journal entry rule set. When account rules are defined with sources, the sources must also be assigned to the accounting event class that is assigned the journal entry rule set.

There are two types of account rules:

Assignment of Supporting References

Supporting references may be assigned at the header or line level of the journal entry to capture transaction values on the journal entry header or lines. If the supporting reference segments are assigned multiple sources, at least one source must also be assigned to the accounting event class that is assigned the journal entry rule set.

Journal Line Rules: Explained

Journal line rules are defined within the context of accounting event classes. A journal line rule can be used in a subledger journal entry rule set that has the same event class. You may also assign conditions to the journal line rule.

Journal Line Rules

Journal line rules are assigned to journal entry rule sets.

To create a journal line rule, select values for options such as:


Link Journal Lines Option

Description

None

No link is established.

Copy from corresponding line

Build account for a journal line using segments from the offsetting entry of the current journal line. For example, when the business process requires that a cost center incurring an expense must also bear the invoice liability and cash outlay.

Business flow

Link logically related business transactions. For example, when recording the closing of a loan, you can link to the account that was used to book the loan origination. Journal line rules that are linked must also be assigned the same business flow class.

Defining Conditions for Journal Line Rules

You may set conditions to specify whether the journal line rule will be used to create a subledger journal entry line. If the conditions are true, the line rule is used to create a subledger journal entry line. Use sources to create these conditions.

For example, you can set up a condition that will create a journal line to record tax, only if there is tax for an invoice. The line type and account class mentioned here are examples of sources.

Another example is a condition that creates a journal line for freight when there are freight charges on an invoice.

Journal line rule conditions determine whether a journal line rule and its associated account rules and description rules, are used to create the subledger journal entry line.

Creating Conditions: Examples

The following illustrates an example of defining an account rule with a condition.

Example 1: Custom Real Estate Application Account Rule Condition Example

This is an example to define an account rule for assignment for a loan journal line. The account rule has two priorities, a mapping set and a constant.

The following table describes the setup of the condition on the first priority:


(

Source

Operator

Value

)

(

"Credit Status"

is not null

 

)

The second priority will create an output from a constant value (0.9100030.50034206331.0.0.0). There is no condition associated with the second priority.

Example 2: Oracle Fusion Assets Account Rule Condition Example

This is an example of a rule for a capital purchase. The rule is to be applied only if the distribution account cost center is the same as the liability account cost center and the asset tracking option is Yes. This condition can be expressed as:

The following tables describe the setup of the condition:


(

Source

De-limiter

Segment

Operator

Value

De-limiter

Segment

)

And Or

(

"Dis-tribution Account"

.

"Cost Center"

=

"Liability Account"

.

"Cost Center"

)

'AND'

(

"Asset Flag"

 

=

Yes

 

)

 

The following two rows of data are used in the accounting event, to which the account rule and condition applies.

Account Rule Condition Example: Accounting Event Data


Account

Invoice 1

Invoice 2

Asset Flag

Distribution Account

02-640-2210-1234

01-780-6120-0000

Yes

Liability Account

01-640-2210-0000

02-782-2210-0000

Yes

In the Accounting Event Data table above, assume the cost center segment is the second segment. When the account rule with this condition is used to derive the account for the transaction, the account rule is applied to derive the account of Invoice 1 only. For Invoice 2, even though the assets tracking option is set to Yes, the cost center for the Distribution account and Liability account are not the same. Both conditions must be met in order for the rule to apply.

Note

When an account source is selected or entered, you must also select or enter a specific segment. If an entire account is required to be used in the condition instead of a specific segment, then select or enter All as the segment for the account.

The condition uses the account source, Distribution Account, and a segment must be provided. In this example, the Cost Center segment is provided.

Account Rules: Explained

Account rules are used to determine the accounts for subledger journal entry lines. In addition, you can specify the conditions under which these rules apply. Using these capabilities, you can develop complex rules for defining accounts under different circumstances to meet your specific requirements. You can define account rules for an account, segment, or value set.

Account Rules by Account

Define account rules by account to determine the entire account combination. For example, an account rule defined by account can be used to determine the complete supplier liability account in Oracle Fusion Payables.

Account Rules by Segment

Define segment rules to derive a specific segment of the general ledger account. For example, a particular segment like the company segment can be determined from the distribution account. Another segment can be determined with the use of a constant value. Creating the account one segment at a time offers greater flexibility, but also requires more setup.

Use both segment based and account based rules to derive a single account. Segment specific rules are used, where they are defined, and take the remaining values from an account based rule. For example, you can select an account rule which is for all segments and also separately select a rule which is for one particular segment. Segment specific rules take precedence over the all segments account based rule.

Combine account rules with segment rules. In this case, the segment value is derived from the segment rule to override the corresponding segment of the account. However, if the segment rule has conditions associated with the priorities and none of the conditions are met, no override occurs and therefore, the segment value is derived from the account rule.

Note

If the returned account is end dated with a date that is the same or before the subledger journal entry accounting date and a substitute account is defined in Oracle Fusion General Ledger, a substitute account is used. The original account is stored on the journal line for audit purposes. If the substitute account is invalid, and the Post Invalid Accounts to Suspense Account option is selected in the Create Accounting program, then a suspense account is used. An error message is displayed if a valid suspense account is not available.

Account Rules by Value Sets

In the absence of a chart of accounts, you may define account rules based upon value sets. This enables you to share the same rule between more than one chart of accounts if the segments in these charts of accounts share the same value set.

Sharing Account Rules across Applications

You may share account rules across applications in the following ways.

Note

To share an account rule across applications, all sources used by the account rule must be available for the event class.

If the sources are available, an account rule is assigned to a journal line rule in the journal entry rule set, and verification occurs to confirm that all sources used by the account rule are available for the journal line rule accounting event class. Journal line rules are only available if the sources are shared; such as reference objects.

Account Rules and Mapping Sets

Mapping sets can be used to associate a specific output value for an account or segment. You can use mapping sets in account rules to build the account.

Account Rules Conditions

In the account rules you may specify conditions for each rule detail line. Priorities determine the order in which account rule conditions are examined. When the condition is met, the rule associated with that priority is used. Depending on which of the defined conditions is met, a different account rule detail is employed to create the account.

The Create Accounting program evaluates conditions based on the priority of the rule detail. When the condition is met, the rule detail is applied.

Creating Account Rules: Points to Consider

You can define an account rule using the following rule types:

Account Combination Rules

Set up account combination rules based upon the following value types:

  1. Source Value Type: Derive the account combination by specifying a source. Sources that have been set up as accounts can be assigned to an account combination rule. Oracle Fusion Subledger Accounting then obtains the code combination identifier from the source.

  2. Constant Value Type: Establish the account as a constant value.

    For example, the constant could be a completed account combination from the chart of accounts specified. An example is the account combination, 01.000.2210.0000.000. This is the simplest way to derive an account.

  3. Mapping Set Value Type: Derive the account combination by referencing a mapping set. Set up a mapping set to determine the complete account combination from the chart of accounts specified.

  4. Account Rule Value Type: Derive the account by referencing another account rule.

    The chart of accounts does not need to be specified when defining this type of rule. If the account rule has a chart of accounts assigned, then all the related account rules must use the same or no chart of accounts.

Note

A chart of accounts must be specified for rules using constants.

Segment Rules

Set up segment rules as follows:

Set up segment rules using the same methods discussed in the preceding Account Combination Rules section. By specifying different value types, users can select the way in which the segment value is derived.

Note

A chart of accounts must be specified for rules using constants.

Value Set Rules

Value set based rules can be created when a chart of accounts is not specified. This enables you to share the same rule between more than one chart of accounts if the segments in these charts of accounts share the same value set.

Set up value set based rules using the same methods discussed in the preceding Account Combination Rules section.

Creating Description Rules: Explained

Use descriptions rules to define the elements of a description that appears on the subledger journal entry at the header and/or the line. The definition determines both the content and sequence in which the elements of the description appear. You can assign a condition to a description rule to determine that the description is selected for display if the condition is satisfied.

Description Rule Definition

A description rule can be defined with combinations of source and literal values. If sources are used in the rule, the accounting event class associated with the sources determines in which subledger journal entry rule set the description rule can be selected and used.

Build descriptions using the available sources for the application.

The following is the description details that have been entered, using a literal and a source:

Assuming that the source value of the Origination Date is 11/01/11, then a journal entry that has the above description rule attached will have the description, Loan Origination Date 11/01/11.

Creating Supporting References: Explained

Supporting references can be used to store additional source information about a subledger journal entry either at the header or line level.

Sources are assigned to supporting reference segments to indicate which transaction values should be captured on subledger journal entries. The segments are grouped into one supporting reference.

Supporting references that have the option for maintain balances set to Yes, establish subledger balances for a particular source and account.

You may want to use Supporting Reference balances for supporting:

Supporting Reference Assignment

If the information requirement is purely informational, and not needed for reconciliation or balances, you may consider using description rules to store the source values.

There are several key points to consider when assigning supporting references:

As an example:

Sources will be assigned to each of these segments and the source values for each of these segments will be used to create separate balances.

Accounting Event Model: Explained

Accounting events represent transactions that may have financial significance. Events with significantly different fiscal or operational implications are classified into different accounting event types. Event types categorize accounting events. Accounting definitions in the Oracle Fusion Accounting Hub are based on event types. An event type must be unique within an application, process category, and event class.

Examples of accounting events are issuing a loan and disposing of an asset. Financial accounting information can be recorded for these events and accounted by the Create Accounting process.

Accounting Process Overview

The figure below provides a high-level overview of the process used to create subledger journal entries and is described in the succeeding text.

Note

Accounting events are predefined for Oracle Fusion subledger applications. If you are using Subledger Accounting for a non-Oracle source system, define your accounting events from a business perspective. Determine what activities or transactions occur in your source system which may create a financial impact.

The above diagram illustrates the process
used to create subledger journal entries, which is described in the
following text.

The above diagram illustrates the process used to create subledger journal entries.

The Create Accounting program uses the transaction objects data to create subledger journal entries. For example, if a subledger journal entry rule set specifies that the customer name should appear in the description of a subledger journal entry line, then the customer name value is taken from the customer name source data provided by the transaction objects.

When transactions are committed in a subledger, accounting events are captured and stored in subledger accounting.

The Create Accounting program identifies all accounting events eligible to be processed. For each of these events, the transaction objects process provides the Create Accounting program with transaction objects data (source information). This is the contextual data of the transaction, such as amounts and accounting dates.

When the Create Accounting program is run, journal entry rule set definition and accounting transaction objects data are applied to the transaction object data to create subledger journal entries.

Subsequently, these entries are summarized and transferred to Oracle Fusion General Ledger.

Accounting Event Model

Define accounting events for non-Oracle source systems from a business perspective. Determine what activities or transactions occur in your source system which may create a financial impact.

Events are captured when transactions are committed in the subledgers, or they may be captured during end of day or period end processing. As an example, a loan is originated, possibly adjusted, interest is accrued, and then the loan is paid or canceled. The accounting events representing these activities can create one or more subledger journal entries, and subsequently link the originating transaction to its corresponding journal entries.

Note

The accounting event model, including the system and user transaction identifiers, is predefined for Oracle Fusion subledger applications, and therefore not updateable by subledger application users.

An example of an accounting event model setup for a loan application is shown below:

This graphic is a visual representation
of the process category, accounting event class and accounting event
types that are detailed in the following section.

Process Categories

Process categories can be used to restrict the events selected for accounting when users submit the Create Accounting program. Selecting a process category indicates that all associated accounting event classes and their assigned accounting event types are selected for processing.

Event Classes

You can assign a transaction view, system transaction identifiers, and optionally user transaction identifiers for an event class in the Event Class window.

At least one system transaction identifier must be defined for the accounting event class. System identifiers are used to link accounting events with transactions from subledger applications.

Optionally, you may define user transaction identifiers. You can specify up to ten columns from the transaction views that are available for inquiry and reports. The user transaction identifiers help provide contextual information for inquiry and reports.

The transaction view should include all columns that have been mapped to system transaction identifiers for the accounting event class as well as the user transaction identifiers.

Optionally, you can define the processing predecessor for an accounting event class. The Processing Predecessor establishes an order in which the Create Accounting program processes events selected for accounting.

Event Types

Specify whether an accounting event has accounting or tax impact for an accounting event type. When the Create Accounting program is submitted, it only accounts business events that are enabled for accounting.

Transaction Identifiers

There are two types of transaction identifiers:

System Transaction Identifiers

System transaction identifiers provide a link between an accounting event and its associated transaction or document.

System transaction identifiers constitute the primary key of the underlying subledger transaction. Typically, the identifier is the name of the surrogate key column on the transaction (header) associated with the accounting event.

Whenever an accounting event is captured, the values of the system transaction identifiers are stored on the accounting event record along with other event data. Whenever system transaction identifiers are defined for the accounting event, the event capture mechanism validates that the system transaction identifiers are populated.

User Transaction Identifiers

User transaction identifiers constitute the user-oriented key of the underlying subledger transaction. They are typically drawn from one or more database tables.

These identifiers are primarily used in accounting events inquiry and on accounting reports. Users use these identifiers to uniquely identify underlying transactions.

The Oracle Fusion Accounting Hub displays user transaction identifiers on accounting event reports and inquiries.

User transaction identifiers enable users to uniquely identify any subledger transaction. The transaction data that identifies the transaction varies by accounting event class. Accounting event reports and inquiries display the transaction identifiers and their labels appropriate for the corresponding event class. The user transaction identifiers can be displayed for an event regardless of its status. This includes the case where the accounting event has not been used to create subledger journal entries due to an error or the cases where it has not been processed. The user transaction identifier values are displayed at the time that the accounting event reports and inquiries are run. If a transaction identifier value has changed after the accounting event was captured, the accounting event reports and inquiries reflect the change.

Register Source Systems: Critical Choices

Subledger applications can support third party control account type and calculate reporting currency amounts.

Support Third Party Control Account Type

You can set up the subledger application to support customer, supplier, or both third party control account types (customer and supplier).

Calculate Reporting Currency Amount

If the subledger application is configured to calculate reporting currency amount, there is no need to provide reporting currency information in the transaction objects.

Additional Considerations

The following are additional considerations when creating a subledger application:

  1. Determine the subledgers requirement. For example, how many subledgers are to be created? This may depend on what security your company wants to have over its accounting rules.

  2. Determine the transaction objects requirements. These requirements determine what source data is required to successfully create subledger journal entries from transactions that are captured in transaction objects and shared in reference objects.

  3. Analyze accounting events to determine what events to capture for the subledger application.

    Create programs to capture accounting events using APIs (application programming interfaces) that are provided as follows:

  4. Determine how often to capture accounting events, populate transaction objects, and run the Create Accounting program. This may depend on the immediacy and volumes of accounting requirements in your company.

Transaction Objects: Points to Consider

You may assign transaction and reference objects for each accounting event class in the subledger application. Sources are generated based on the transaction objects and are assigned to the corresponding accounting event classes.

Sources are used to create accounting rules. Subledgers pass information to the application by populating transaction object tables. The columns in these tables are named after the source codes. Transaction and reference objects hold transaction information that is useful when creating journal entry rules for accounting. The transaction and reference objects are defined for an accounting event class so that source assignments to accounting event class can be generated using these objects.

Transaction Objects

Transaction objects refer to the tables or views from which the Create Accounting program takes the source values to create subledger journal entries. Source values, along with accounting event identifiers, are stored in the transaction objects. The Create Accounting program uses this information to create subledger journal entries.

You have several options. You can:

The transaction objects and or views must be accessible to the Create Accounting program. Typically, an ETL (extract, transformation, and load) program is used to take values from the source system and load them into the database used by the Create Accounting program. The ETL process is done outside of the Create Accounting program processing.

The following are transaction object types:

Reference Objects

Reference objects are useful for storing information that is used for creating subledger journal entries. This information may not be directly from the source system or may be used for many entries, thus making it redundant. Use reference objects to share sources information across applications.

For example, store customer attributes, such as the customer class or credit rating in a reference object, and then, use it to account for different journal entries in a loan cycle, such as loan origination or interest accrual. Store information, such as bond ratings and terms, and use it to account for entries across the life of bonds, such as interest accruals or bond retirement.

Reference objects can either have a direct relationship to transaction objects (primary reference object), or be related to other reference objects (secondary).

Managing Accounting Sources: Critical Choices

Sources are a key component for setting up accounting rules. Sources represent transaction and reference information from subledger applications or reference systems. Contextual and reference data of transactions that are set up as sources can be used in accounting rules definitions.

Oracle Fusion Applications predefines sources for its subledger. When determining what sources should be available for non-Oracle applications, it is helpful to begin the analysis by considering which information from your systems is accounting in nature. Examples of sources that are accounting in nature include general ledger accounts that are entered on transactions, the currency of a transaction, and transaction amounts. Sources that are not always required for accounting rules include items that are related to the transaction for other purposes than accounting. Examples of information that may not be specifically for accounting, but which may be useful for creating subledger journal entries, are transaction identification number (loan number, customer number, or billing account number), counter party information, and transaction dates.

Provide a rich library of sources from your subledger applications for maximum flexibility when creating definitions for subledger journal entries. Predefined sources are provided as part of the startup data of the application.

Sources are assigned to accounting event classes by submitting the Create and Assign Sources program.

There is a distinct difference between sources and source values. Sources are representations of the data from transactions used to create accounting rules. Source values are used by the Create Accounting program to create subledger journal entries based upon source assignments to accounting rules.

Sources

Sources must be registered prior to creating accounting rules. This is a predefined step which must be undertaken before the application can be used to create subledger journal entries.

To set up appropriate journal entry rule sets, users and those implementing need to understand the origins, meaning, and context of sources. Use business oriented names for sources to allow accountants and analysts to effectively create accounting rules.

Source Values

Source values are stored in transaction objects. They are used to create subledger journal entries for the events. To enable the creation of subledger journal entries, first complete the definition of the sources and storing of the source values in the transaction objects. Transaction objects can be tables or views.

Accounting Attribute Assignments: Points to Consider

The Create Accounting program uses the values of sources assigned to accounting attributes plus accounting rules to create subledger journal entries. Almost all accounting attributes have sources assigned at the accounting event class level. Depending on the accounting attribute, the accounting attribute assignment defaulted from the accounting event class can be overridden on journal line rules or subledger journal entry rule sets.

Once sources are assigned to accounting event classes, they are eligible for assignment to accounting attributes for the same accounting event classes.

The Create Accounting program uses these assignments to copy values from transaction objects to subledger journal entries. For example, you may map the invoice entered currency to the subledger journal entry entered currency.

Each accounting attribute is associated with a level:

  1. Header: To be used when creating subledger journal entry headers.

  2. Line: To be used when creating subledger journal entry lines.

The types of accounting attributes values are as follows:

Values that are Subject to Special Processing

You may have values that are subject to special processing or values that are stored in named columns in journal entry headers and lines.

Examples of accounting attributes are Entered Currency Code and Entered Amount.

Values that Control the Behavior of the Create Accounting Program

You may have values that control the behavior of the Create Accounting program when processing a specific accounting event or transaction object line.

An example of accounting attributes of this type is Accounting Reversal Indicator.

Accounting Attributes

Accounting attribute groups are represented in the tables below:

Accounted Amount Overwrite


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Accounted Amount Overwrite Indicator

Alphanumeric

Line

Event Class and Journal Line Rule

No

Y - Overwrite accounted amount

N - Not overwrite accounted amount

Accounting Date


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Accounting Date

Date

Header

Event Class and Journal Entry Rule Set

Yes

Should be in open general ledger period

Accrual Reversal GL Date

Date

Header

Event Class and Journal Entry Rule Set

No

Should be later than the accounting date

Accounting Reversal


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Accounting Reversal Distribution Type

Alphanumeric

Line

Event Class

Yes, if another accounting reversal accounting attribute is assigned.

 

Accounting Reversal First Distribution Identifier

Alphanumeric

Line

Event Class

Yes, if another accounting reversal accounting attribute is assigned.

 

Accounting Reversal Second Distribution Identifier

Alphanumeric

Line

Event Class

No

 

Accounting Reversal Third Distribution Identifier

Alphanumeric

Line

Event Class

No

 

Accounting Reversal Fourth Distribution Identifier

Alphanumeric

Line

Event Class

No

 

Accounting Reversal Fifth Distribution Identifier

Alphanumeric

Line

Event Class

No

 

Accounting Reversal Indicator

Alphanumeric

Line

Event Class

Yes, if another accounting reversal accounting attribute is assigned.

Y - Reverse without creating a replacement line

B - Reverse and create a new line as replacement

N or Null - Not a reversal

Transaction Accounting Reversal Indicator

Alphanumeric

Header

Event Class

No

Y - Reversal transaction object header

N or null - Standard transaction object header

Business Flow

Note

When enabling business flow to link journal lines in the Journal Line Rule page, certain accounting attribute values are unavailable for source assignment in the Accounting Attributes Assignments window of the same page because they will be copied from the related prior journal entry.


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Applied to Amount

Number

Line

Event Class and Journal Line Rule

No

 

Applied to First System Transaction Identifier

Alphanumeric

Line

Event Class and Journal Line Rule

Yes, if another accounting attribute in the same group has assignment.

 

Applied to Second System Transaction Identifier

Alphanumeric

Line

Event Class and Journal Line Rule

No

 

Applied to Third System Transaction Identifier

Alphanumeric

Line

Event Class and Journal Line Rule

No

 

Applied to Fourth System Transaction Identifier

Alphanumeric

Line

Event Class and Journal Line Rule

No

 

Applied to Distribution Type

Alphanumeric

Line

Event Class and Journal Line Rule

Yes, if another accounting attribute in the same group has assignment.

 

Applied to First Distribution Identifier

Alphanumeric

Line

Event Class and Journal Line Rule

Yes, if another accounting attribute in the same group has assignment.

 

Applied to Second Distribution Identifier

Alphanumeric

Line

Event Class and Journal Line Rule

No

 

Applied to Third Distribution Identifier

Alphanumeric

Line

Event Class and Journal Line Rule

No

 

Applied to Fourth Distribution Identifier

Alphanumeric

Line

Event Class and Journal Line Rule

No

 

Applied to Fifth Distribution Identifier

Alphanumeric

Line

Event Class and Journal Line Rule

No

 

Applied to Application ID

Number

Line

Event Class and Journal Line Rule

Yes, if another accounting attribute in the same group has assignment.

Must be a valid application ID

Applied to Entity Code

Alphanumeric

Line

Event Class and Journal Line Rule

Yes, if another accounting attribute in the same group has assignment.

Must be a valid Entity for the application selected in Applied to Application ID

Distribution Identifier


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Distribution Type

Alphanumeric

Line

Event Class

Yes

 

First Distribution Identifier

Alphanumeric

Line

Event Class

Yes

 

Second Distribution Identifier

Alphanumeric

Line

Event Class

No

 

Third Distribution Identifier

Alphanumeric

Line

Event Class

No

 

Fourth Distribution Identifier

Alphanumeric

Line

Event Class

No

 

Fifth Distribution Identifier

Alphanumeric

Line

Event Class

No

 

Document Sequence


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Subledger Document Sequence Category

Alphanumeric

Header

Event Class

Yes, if another accounting attribute in the same group has assignment.

 

Subledger Document Sequence Identifier

Number

Header

Event Class

Yes, if another accounting attribute in the same group has assignment.

 

Subledger Document Sequence Value

Number

Header

Event Class

Yes, if another accounting attribute in the same group has assignment.

 

Entered Currency


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Currency Code

Alphanumeric

Line

Event Class and Journal Line Rule

Yes

A valid currency code

Entered Amount

Number

Line

Event Class and Journal Line Rule

Yes

 

Ledger Currency


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Accounted Amount

Number

Line

Event Class and Journal Line Rule

No

 

Conversion Date

Date

Line

Event Class and Journal Line Rule

No

 

Conversion Rate

Number

Line

Event Class and Journal Line Rule

No

 

Conversion Rate Type

Alphanumeric

Line

Event Class and Journal Line Rule

No

A valid general ledger conversion rate type or User

Tax


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Detail Tax Distribution Reference

Number

Line

Event Class

No

 

Detail Tax Line Reference

Number

Line

Event Class

No

 

Summary Tax Line Reference

Number

Line

Event Class

No

 

Third Party


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Party Identifier

Number

Line

Event Class and Journal Line Rule

Yes, if another accounting attribute in the same group has assignment.

If party type C - Should be a valid customer account

If party type is S - Should be a valid supplier identifier

Party Site Identifier

Number

Line

Event Class and Journal Line Rule

Yes, if another accounting attribute in the same group has assignment.

If party type C - Should be a valid customer account

If party type is S - Should be a valid supplier identifier

Party Type

Alphanumeric

Line

Event Class

Yes, if another accounting attribute in the same group has assignment.

C for Customer

S for Supplier

Exchange Gain Account, Exchange Loss Account


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Exchange Gain Account

Number

Header

Event Class

No

 

Exchange Loss Account

Number

Header

Event Class

No

 

Gain or Loss Reference


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Gain or Loss Reference

Alphanumeric

Line

Event Class

No

 

Transfer to GL Indicator


Accounting Attributes

Data Type

Journal Entry Level

Assignment to Rules

Assignment Required?

Validation Rules

Transfer to GL Indicator

Alphanumeric

Header

Event Class

No

Should be Y or N

FAQs for Define Subledger Accounting Rules

How can I create subledger account rules and subledger journal entry rule sets for receipt accounting?

Create your subledger account rules on the Manage Account Rules page. It is recommended that you highlight the account rules predefined by Oracle, copy, and modify them as needed.

Create your subledger journal entry rule sets on the Manage Subledger Journal Entry Rule Sets page. It is recommended that you highlight the journal entry rule sets predefined by Oracle, copy, and modify them as needed. For each journal line rule specify the copied account combination rule.

Access both the Manage Account Rules page and Manage Subledger Journal Entry Rule Sets page from an Oracle Fusion Applications Functional Setup Manager implementation project.

Note

You must customize the predefined account rules and journal entry rule sets before proceeding with the setup of subledger accounting rules for receipt accounting.