Oracle R12.1 Subledger Accounting Implementation Guide PDF
Oracle R12.1 Subledger Accounting Implementation Guide PDF
Oracle R12.1 Subledger Accounting Implementation Guide PDF
Implementation Guide
Release 12.1
Part No. E13628-02
April 2009
Contents
iii
iv
Diagnostic Framework
Diagnostic Framework Overview............................................................................................. 5-1
Diagnostic Framework Business Process Flow Diagram......................................................... 5-1
Diagnostic Framework Features............................................................................................... 5-3
SLA: Enable Diagnostics Profile Option...............................................................................5-3
Diagnostic Framework Execution........................................................................................ 5-3
Transaction Objects Diagnostics Report............................................................................... 5-3
Purge Transaction Objects Diagnostics................................................................................ 5-5
Inquiries
Subledger Accounting Inquiries Overview..............................................................................7-1
Accounting Events Inquiry....................................................................................................... 7-1
Subledger Journal Entry Headers Inquiry................................................................................ 7-4
Subledger Journal Entry Lines Inquiry.................................................................................... 7-5
Viewing Supporting Reference Balances................................................................................. 7-7
Reporting Sequence
Reporting Sequence Overview................................................................................................. 8-1
Sequence Programs................................................................................................................... 8-2
Reporting Sequence Process Flow Diagram............................................................................. 8-3
Reporting Sequence Process Steps....................................................................................... 8-4
10
11
vi
Index
vii
Send Us Your Comments
Oracle Subledger Accounting Implementation Guide, Release 12.1
Part No. E13628-02
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Applications Release
Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the most
current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
ix
Preface
Intended Audience
Welcome to Release 12.1 of the Oracle Subledger Accounting Implementation Guide.
This guide assumes you have a working knowledge of the following:
If you have never used Oracle Applications, we suggest you attend one or more of the
Oracle Applications training classes available through Oracle University.
See Related Information Sources on page xii for more Oracle Applications product
information.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible
to all users, including users that are disabled. To that end, our documentation includes
features that make information available to users of assistive technology. This
documentation is available in HTML format, and contains markup to facilitate access by
xi
the disabled community. Accessibility standards will continue to evolve over time, and
Oracle is actively engaged with other market-leading technology vendors to address
technical obstacles so that our documentation can be accessible to all of our customers.
For more information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/.
Structure
1 Subledger Accounting Options Setup
2 Accounting Methods Builder
3 Create Accounting and Transfer Journal Entries to GL Programs
4 Conversion of Historical Data for Reporting Currencies and Secondary Ledgers
5 Diagnostic Framework
6 Subledger Journal Entries
7 Inquiries
8 Reporting Sequence
9 Subledger Accounting Reports
10 Open Account Balances Listing
11 Transaction Account Builder
A Oracle Subledger Accounting Navigation Paths
B Oracle Subledger Accounting Profile Options and Profile Option Categories
C Subledger Journal Entry Definition
xii
If this guide refers you to other Oracle Applications documentation, use only the
Release 12 versions of those guides.
For a full list of documentation resources for Oracle Applications Release 12, see Oracle
Applications Documentation Resources, Release 12, OracleMetaLink Document
394692.1.
Online Documentation
All Oracle Applications documentation is available online (HTML or PDF).
Related Guides
You should have the following related books on hand. Depending on the requirements
of your particular installation, you may also need additional manuals or guides.
Oracle Financial Services Accounting Hub Implementation Guide:
This guide provides detailed implementation information that leverages the features of
Oracle Subledger Accounting to generate accounting.
Oracle Applications Concepts:
This book is intended for all those planning to deploy Oracle E-Business Suite Release
12, or contemplating significant changes to a configuration. After describing the Oracle
Applications architecture and technology stack, it focuses on strategic topics, giving a
broad outline of the actions needed to achieve a particular goal, plus the installation and
configuration choices that may be available.
Oracle Applications Installation Guide: Using Rapid Install:
This book is intended for use by anyone who is responsible for installing or upgrading
Oracle Applications. It provides instructions for running Rapid Install either to carry
out a fresh installation of Oracle Applications Release 12, or as part of an upgrade from
Release 11i to Release 12. The book also describes the steps needed to install the
technology stack components only, for the special situations where this is applicable.
Oracle eBusiness Suite Electronic Technical Reference Manuals:
Each Electronic Technical Reference Manual (eTRM) contains database diagrams and a
detailed description of database tables, forms, reports, and programs for a specific
Oracle Applications product. This information helps you convert data from your
existing applications and integrate Oracle Applications data with non-Oracle
applications, and write custom reports for Oracle Applications products. Oracle eTRM
is available on OracleMetaLink.
xiii
Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the E-Business Suite. As your
instance is patched, the repository is automatically updated with content appropriate
for the precise revisions of interfaces in your environment.
xiv
database tools, you may store invalid information. You also lose the ability to track who
has changed your information because SQL*Plus and other database tools do not keep a
record of changes.
xv
1
Subledger Accounting Options Setup
Related Topics
For detailed implementation information on leveraging the features of Oracle Subledger
Accounting to generate accounting for front-office banking and other financial services
source systems, see: Overview of the Financial Services Accounting Hub for
Implementers, Oracle Financial Services Accounting Hub Implementation Guide
Subledger Applications
Access this page from the Accounting Setups page in General Ledger. This page is
displayed in the context of a primary or secondary ledger. All subledger
applications registered with Subledger Accounting are displayed. In this page,
select the application to update and the Update Subledger Accounting Options
page opens. You can choose to disable Subledger Accounting for a particular
application in the Update Accounting Options page of a secondary ledger.
See: Accounting Setups Page, Oracle Financials Implementation Guide
Note: If you have a ledger setup and want to add an event class,
2.
3.
Launch defaults and ledger options view that displays the accounting program
defaults and the event class options for the following:
Ledger options view that displays the event class options for the secondary
ledger for a non-valuation method subledger application
1.
2.
In the Results region, click the Update Accounting Options icon for a ledger.
3.
In the Primary Ledger region or the Secondary Ledger region, click the Update icon
for Subledger Accounting Options.
4.
In the Subledger Applications page, click the Update Accounting Options icon to
update accounting options or the Update System Options icon to define the
processing unit size.
5.
The General Ledger Journal Entry Summarization option determines whether subledger
journal entries are summarized when they are transferred to General Ledger as
described in the table below.
General Ledger Journal Entry Summarization Options
Option
Description
Summarize by GL Period
Summarize by GL Date
No Summarization
The table below describes the impact of the summarization options based on whether
the journal line type is Summary or Detail.
Impact of Summarization Option
Option
Summarize by GL Period
Option
Summarize by GL Date
No Summarization
Reversal Method
Use the Reversal Method option to determine how the reversal subledger journal
entries are generated in Subledger Accounting for a given application and ledger. The
options are:
Change Sign: The reversal entry keeps the same side as the original entity, but the
sign is changed.
below, assume that the precision is 2 and the minimum account unit is
0.01.
Description
Up
Down
Nearest
Description
No accounting update
No accounting effect
Note: The reporting currency ledgers inherit the third party merge
primary ledgers
Description
Draft
Used to create accounting to determine the accounting
impact of their entries. Draft entries can be included on
accounting reports but cannot be transferred to General
Ledger. A draft entry does not update balances and does
not reserve funds.
Draft entries can be deleted and recreated with
alternative information. Users can alter the associated
source transaction or accounting definition. They can
alter the application setups in a way that impacts how
the subledger journal entry is created.
The attributes that are common to both draft and final
entries are that they are balanced accounting entries;
they have an accounting date and all the data that is
populated for a final entry is also populated for a draft
entry.
Final
Used to create entries that cannot be changed once they
are created. Entries are transferred to General Ledger.
Option
Description
Transfer to GL
Post in GL
Option
Description
Error Limit
Description
Journal Category
2
Accounting Methods Builder
Descriptions that appear on the subledger journal header and lines which provide
additional information about the journal entry
For example, a subledger journal entry created for a Payables invoice can show the
supplier name and invoice number.
Account derivation rules to construct the accounts for a subledger journal entry line
Users define various rules in the AMB to determine how a journal entry account is
derived. Users can derive accounts segment by segment or as a complete
Accounting Flexfield.
Conditions that determine when subledger journal entry accounts and lines are
created
Some accounts can be used to create a journal entry only in certain circumstances.
For example, an asset account can only be used when the Assets flag for an invoice
distribution is enabled through the Oracle Payables Invoices window.
The different elements of a subledger journal and their relationships to the AMB are
displayed in the diagram below and explained in the subsequent text.
The AMB includes journal entry setup components to configure each of these elements:
Journal Line Types: Control journal entry line options such as balance type, side,
and summarization
Journal Entry Descriptions: Control the description for the journal entry headers
and lines
The journal entry setup components are associated with journal lines definitions that
are attached to application accounting definitions. You can group detailed subledger
accounting definitions for different kinds of transactions into consistent sets, each of
which addresses different needs. While one application accounting definition can
generate subledger journal entries to meet a particular set of requirements, another
definition can be defined to satisfy completely different requirements.
To use application accounting definitions, they must be included in a subledger
accounting method and then assigned to a ledger. Users can group accounting
definitions from multiple products, such as Oracle Payables, Oracle Receivables, and
Oracle Assets into a single accounting method. You can assign a subledger accounting
method to multiple ledgers.
As an example of these groupings and assignments, consider a set of definitions set up
to create accrual accounting for payables in the U.S. These definitions can be grouped
into the U.S. Payables Accrual application accounting definition. Accrual accounting
application accounting definitions for each application in the U.S., such as U.S. Payables
Accrual and U.S. Receivables Accrual, can be grouped into the U.S. Accrual Subledger
Accounting Method.
The relationship between the various AMB components are displayed in the diagram
below and is described in the succeeding text.
Accounting Methods Builder Components
The above diagram shows how the AMB predefined components, standard sources,
event entities, event classes, and event types, can be used to create journal entry
descriptions, journal line types, account derivation rules, and mapping sets. The
mapping sets are used in the setup of account derivation rules. The journal line types,
account derivation rules, and journal entry descriptions are assigned to journal lines
definitions. The journal lines definitions and optional journal entry descriptions for the
journal headers, are assigned at the application accounting definition level. Application
accounting definitions are grouped in a subledger accounting method.
Oracle Applications development provides startup application accounting definitions
and at least one subledger accounting method for all products using Oracle Subledger
Accounting. If users do not have any special accounting requirements, these startup
definitions may meet their needs and the only required setup step is to assign subledger
accounting methods to the ledger.
If users have specific accounting requirements that are not met by the startup
definitions, they can copy and modify the seeded definitions or create new definitions.
The components in the figure above are used by the Subledger Accounting program to
create subledger journal entries. Before creating or modifying any components or
definitions, check whether the seeded application accounting definitions meet your
requirements. In the event that more detail is required than that provided by the default
definitions, modify them or create new ones.
Since the flexibility for creating accounting definitions is dependent on source
availability, Oracle subledgers provide standard sources. Create custom sources for use
in accounting definitions.
definitions if those definitions use seeded components. Use the merge analysis feature
to assess whether any upgrades to the AMB impact any user-defined application
accounting definitions.
The copy and modify functionality is provided for the following components of the
AMB:
Supporting references
Assign custom components only to custom definitions. For example, assign a custom
account derivation rule (one that has been copied from an existing account derivation
rule and modified) only to a custom journal lines definition. Assign a journal lines
definition only to custom application accounting definitions and custom subledger
accounting methods.
Use seeded components in custom application accounting definitions.
the transaction chart of accounts. Use these source values in the AMB account
derivation rules and conditions.
same for the primary ledger. They can be different in cases where users
create secondary multiple representations.
Multiple Representations
Assign each subledger accounting method to many ledgers. The combination of a
subledger accounting method and ledger is called an accounting representation. The
primary ledger reflects the primary accounting representation. In the primary ledger,
the transaction and accounting charts of accounts are always the same.
Create multiple accounting representations by using secondary ledgers. Due to
regulatory or other requirements, the accounting for these ledgers can be different than
the accounting for the primary ledger. Each of these ledgers can have a different
subledger accounting method assigned to it and is a secondary accounting
representation. Create several secondary representations, each with a different
currency, chart of accounts, calendar, and set of accounting definitions. An example of
multiple accounting representations is described in the figure below.
Company
Department
Cost Center
Account
Product
Sub-Product
Assume that French local requirements include a statutorily mandated Reporting Chart
of Accounts for financial reporting. In most environments, both transaction entry and
accounting representation is done in the context of a single ledger. It is normal to create
the accounting for this transaction using the same chart of accounts as that used for
transaction entry. The Reporting Chart of Accounts is used for both transaction and
accounting charts of accounts. These two charts of accounts are always the same in the
primary ledger.
In addition to the Reporting Chart of Accounts, assume that the firm requires a detailed
Management Chart of Accounts for analytical purposes. This Management Chart of
Accounts has a four segment structure:
Company
Department
Cost Center
Account
Using the AMB, the firm can create accounting for a secondary representation in a
secondary ledger, which is based on a different currency, chart of accounts, calendar,
and set of accounting definitions.
In this example, it is assumed that the firm's management requires a different chart of
accounts for analytical purposes. This is a secondary representation and uses the
Management Chart of Accounts. When accounts and journal entries are created using
the AMB, they are created for the accounting chart of accounts. The creation of all
journal entries by Subledger Accounting in the secondary ledger is therefore done in the
context of this Management Chart of Accounts.
accounting chart of accounts is not defined, then you cannot set up rules to derive
values for individual segments with the exception of Accounting Flexfield qualifier
segments.
The transaction chart of accounts is different than the accounting chart of accounts.
The account derivation rule is by Accounting Flexfield with a value type of Source.
In this scenario, the account derivation rules create accounts based on the
transaction chart of accounts. In the case of the primary ledger, the derived account
is the same in both the transaction and accounting charts of accounts, which are the
same. However, in a secondary ledger, the account created by an account derivation
rule, based in this case on the transaction chart of accounts, has a structure different
than that of the secondary ledger's accounting chart of accounts. In this case, you
need to map Accounting Flexfield combinations from the transaction chart of
accounts to the accounting chart of accounts.
See: Account Derivation Rules, page 2-57
The use of a chart of accounts mapping imposes the following limitation: the level of
detail in the transaction chart of accounts must be greater or equal to the level of detail
in the accounting chart of accounts. There should be a many to one relationship in the
mapping of the transaction chart of accounts to the accounting chart of accounts. One or
more Accounting Flexfield combinations from the transaction chart of accounts can be
mapped to one and only one combination in the accounting chart of accounts.
Event Model
Accounting events represent transactions that have a financial accounting impact.
Examples of accounting events are issuing an invoice and disposing an asset. Financial
accounting information can be recorded for these events. Accounting events cannot be
compared to system events and programs that update transaction tables; instead they
should be analyzed from a business perspective. Events are captured when transactions
are committed in the subledgers.
As an example, a Payables invoice is created, then approved, possibly adjusted, and
then paid or canceled. The accounting events representing these transactions can create
one or more subledger journal entries and subsequently link the originating transaction
to its corresponding journal entries.
Accounting events are categorized into event types. Event types are grouped into event
classes that in turn are grouped into event entities. These groupings play a prominent
role in the setup of the AMB. The definition of several components in the AMB is by
event class or event type.
See:
Custom Sources
Extend the list of sources available to application accounting definitions. Using
standard and system source values as parameters, write PL/SQL functions that create
custom sources.
The table below describes selected fields in the Custom Sources window.
Selected Fields in the Custom Sources Window
Field
Description
Enabled
Segment
Accounting Flexfield
Lookup Application
Field
Description
Value Set
Seq
Type
Source type
Name
Parameter name
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 of this type are Entered Currency Code and
Entered Amount.
Values that control the behavior of the subledger program when processing a
specific accounting event or transaction object line
Examples of accounting attributes of this type are Accounting Reversal Indicator
and Multiperiod Option.
Post-Accounting Programs
A Post-Accounting program is a container for accounting classes. Subledger
applications use the Post-Accounting program assignment to determine which journal
entry lines to retrieve for a particular process. For example: for mass-additions, Oracle
Payables needs to define a Post-Accounting program to identify the journal entry lines
that need to be pushed to Assets.
The table below describes selected fields and buttons in the Post-Accounting Programs
window.
Selected Fields and Buttons in the Post-Accounting Programs Window
Field or Button
Description
Owner
Primary Application
Ledger
Field or Button
Description
Enabled
Accounting Class
Note: The following fields cannot be updated once the record is saved:
Program Code
Assignment Code
Ledger
Business Flows
Use business flows to establish a link between the accounting of transactions that are
related both within the same application and across applications. With this link, you can
preserve key accounting information across related transactions instead of using the
same set of rules to derive this information.
The purpose of business flows is:
1.
2.
The invoice is entered to acknowledge that the supplier is owed for the goods and
therefore references the receipt transaction.
3.
The payment is created to satisfy the amount owed on the invoice and therefore
references the invoice.
2.
3.
The invoice reverses this accrual entry and creates the invoice liability, and the
accounting for the payment reverses the invoice liability and generates the entry
reducing the company's cash account.
In a business flow, it may be unreliable to copy the General Ledger account entered on
an upstream transaction to the current journal entry. This is because the AMB provides
the flexibility to override certain Accounting Flexfield values such that the General
Ledger account on the transaction is different from the General Ledger account on its
journal entry. The accounting side of a business flow is not preserved if the downstream
journal entry copies the General Ledger account from the upstream transaction, which
was actually accounted to a different General Ledger account.
Additionally, you can implement accounting rules that have identical conditions, but
the source values used by these conditions can change between the time of the original
entry and the time of the current entry. For example, a source can be a date or a project
number.
However, you can copy accounting information from the actual journal entry of a
related transaction instead of evaluating the same set of conditions or copying static
transaction values. In the AMB, define rules that permit a transaction's accounting to
inherit certain values instead of having them determined from sources, rules, or
conditions. These values are inherited from either the journal entries of a related
transaction in the initial stage of the business flow or from the other side of the current
journal line.
Developers provide the identifiers that link transactions in the business flow. These
links are provided in the transaction objects. Subledger Accounting uses these links,
along with the accounting rules, to determine the means by which accounting data is
copied.
Description
None
Option
Description
Prior Entry
Same Entry
For Same Entry and Prior Entry, indicate that the journal lines definition inherits
the journal entry description for the journal line type
For the Same Entry and None business flows method, assign account derivation
rules
For the Same Entry and None business flows method, optionally inherit accounting
segment values
2.
For the purpose of Prior Entry inheritance, evaluate references between related
accounting events including links across applications, such as a Purchasing receipt
to a Payables invoice, and within the application, such as a Receivables invoice to a
Receivables cash receipt.
Applications involved in the accounting of transactions involved in the business
For the Same Entry Method, evaluate accounting needs within a single transaction
where key values need to be consistent across both sides of the journal entry for a
single transaction.
4.
5.
6.
Seed journal line types and journal lines definitions for business flows to act
effectively.
7.
Copy from the Prior Journal Entry Business Flow Method Process
The Prior Journal Entry method process is:
1.
2.
The Subledger Accounting program searches the accounting event for entries
having the same business flow class as the entry currently being created.
Note: In budgetary control mode, the Subledger Accounting
program ignores draft entries for business flows since Draft equates
to funds checking which does not persist.
3.
Upon finding a match, the Subledger Accounting program copies certain values
from this entry to the current entry.
Distribution Amount
Charge Account
Accrual Account
1011
75.00
01-101-Exp
01-101-Accr
1012
25.00
01-102-Exp
01-102-Accr
1.
2.
A receipt for this purchase order is entered and accounted as described in the table
below.
Journal Line
Types Name
Event Class
Side
Business Flow
Method
Business Flow
Class
PO Charges
Goods Received
DR
None
NULL
PO Accruals
Goods Received
CR
None
Purchased
Goods
The Subledger Accounting program uses the journal line types in the table above to
create journal entries as described in the table below.
Note: The journal line type used to create an entry is not stored on
PO
Distributi
on ID
GL
Account
Debit
1011
01-101 Exp
1012
01-102-Exp
Credit
Business
Flow
Class
Created
Using
Journal
Line Type
75.00
NULL
PO
Charges
25.00
NULL
PO
Charges
Line
Number
PO
Distributi
on ID
GL
Account
1011
01-101-Acc
r
75.00
1012
01-102-Acc
r
25.00
Totals
Debit
100.00
Credit
Business
Flow
Class
Purchased
Goods
Purchased
Goods
Created
Using
Journal
Line Type
PO
Accruals
PO
Accruals
100.00
3.
Lines 1 and 2 were created using the journal line type PO Charges, which does
not use business flow functionality and has no business class.
Lines 3 and 4 were created using the journal line type PO Accruals, which has
no business flow method but does have a business flow class of Purchased
Goods that is stored on the resulting lines. It is possible to have a journal line
that has no business flow method but does have a business flow class.
The GL account for all four lines was created using basic account derivation
rules that copy the account from the PO distributions.
4.
Distribution
Number
Distribution ID
Distribution
Amount
GL Account
Applied to
Distribution ID
201
75.00
01-117-Chrg
1011
202
25.00
01-118-Chrg
1012
table below to create a journal entry for the Invoice Validated accounting event.
Journal Entry for Invoice Validated Account
5.
Journal Line
Type Name
Event Class
Side
Business Flow
Method
Business Flow
Class
AP Accruals
Invoice
Validated
DR
Prior Entry
Purchased
Goods
AP Inv Liability
Invoice
Validated
CR
None
NULL
The accounting for the invoice creates the journal entry lines described in the table
below.
Invoice Validated Accounting Event Entry
Line
Number
Invoice
Distributi
on ID
GL
Account
Debit
201
01-101-Acc
r
202
01-102-Acc
r
201
01-000-Lia
bility
202
01-000-Lia
bility
Totals
Business
Flow
Class
Created
Using
Journal
Line Type
75.00
Purchased
Goods
AP
Accruals
25.00
Purchased
Goods
AP
Accruals
75.00
Purchased
Goods
AP Inv
Liability
25.00
NULL
AP Inv
Liability
100.00
Credit
100.00
Lines 1 and 2 of the journal entry of the Invoice Validated accounting event are created
as follows:
1.
These values are entered in the PO Distribution ID column of the Goods Received
Accounting Event Entry table, page 2-23.
2.
The Subledger Accounting program searches this entry for lines that have the same
business flow class as the current entry.
In this example, PO distributions 1011 and 1012 each occur twice in the journal
entry as described in the Goods Received Accounting Event Entry table, page 2-23.
Only lines 3 and 4 of the Goods Received accounting event have the same business
flow class as the current lines, which are described in the Invoice Validated
Accounting Event Entry table, page 2-25.
3.
The Subledger Accounting program copies the GL account in lines 3 and 4 of the
Goods Received Accounting Event Entry table, page 2-23, from these lines onto the
current lines, which are described in the Invoice Validated Accounting Event Entry
table, page 2-25.
Had the General Ledger account described in the Invoice Distributions table, page
2-24 from the invoice distributions been used, the accounts credited on lines 3 and 4
of the Goods Received Accounting Event table, page 2-23 would never have been
reversed leading to unbalanced General Ledger accounts.
Note: There is no special rule used to derive the invoice liability
Line
Number
Invoice
Distributio
n ID
GL
Account
Debit
201
01-101-Acc
r
202
01-102-Acc
r
201
01-000-Liab
ility
202
01-000-Liab
ility
Totals
Business
Flow
Class
Created
Using
Journal
Line Type
75.00
Purchased
Goods
AP
Accruals
25.00
Purchased
Goods
AP
Accruals
75.00
Purchased
Goods
AP Inv
Liability
25.00
NULL
AP Inv
Liability
100.00
Credit
100.00
It is not sufficient to create an account derivation rule that takes the cost center value
from the invoice distributions and overlays it onto the liability account from the invoice
header. To do so would result in the Invoice Validated event journal entry described in
the table below.
Invoice Validated Event Journal Entry
Line
Number
Invoice
Distributio
n ID
GL
Account
Debit
201
01-101-Acc
r
202
01-102-Acc
r
201
01-117-Liab
ility
202
01-118-Liab
ility
Credit
Business
Flow
Class
Created
Using
Journal
Line Type
75.00
Purchased
Goods
AP
Accruals
25.00
Purchased
Goods
AP
Accruals
75.00
Purchased
Goods
AP Inv
Liability
25.00
NULL
AP Inv
Liability
Line
Number
Invoice
Distributio
n ID
GL
Account
Debit
Credit
Totals
100.00
100.00
Business
Flow
Class
Created
Using
Journal
Line Type
This is incorrect because the cost center values (117 and 118) used on lines 3 and 4 are
not the same as those on lines 1 and 2 (101 and 102), which results in an imbalance in all
four General Ledger accounts. The values must be copied from actual journal entry
lines to ensure that the correct accounts are built.
The correct accounts are shown in the GL Account column in the table below.
Invoice Validated Accounting Event Entry
Line
Number
Invoice
Distributio
n ID
GL
Account
Debit
201
01-101-Acc
r
202
01-102-Acc
r
201
01-101-Liab
ility
202
01-102-Liab
ility
Totals
Business
Flow
Class
Created
Using
Journal
Line Type
75.00
Purchased
Goods
AP
Accruals
25.00
Purchased
Goods
AP
Accruals
75.00
Purchased
Goods
AP Inv
Liability
25.00
NULL
AP Inv
Liability
100.00
Credit
100.00
To accomplish this, the business flow method on the journal line type AP Inv Liability is
changed from None to Same Entry. To create the General Ledger account, the journal
lines definition has two rows in the Account Derivation Rules tab: one to derive an
entire account (All Segments) and the other enabled to inherit the balancing segment
value.
The journal entry is created as follows:
1.
The Subledger Accounting program determines that the business flow method on
journal line type AP INV Liability is Same Entry. For this journal line type, the Side
After the debit side lines are created, the Subledger Accounting program returns to
processing the credit lines and uses a basic account derivation rule to get the
liability account from the invoice header, which is 01-000-Liab in this example.
3.
The Subledger Accounting program copies the cost center segment value on the
debit lines and overlays it onto the balancing segment of the credit lines as
described in the GL Account column in the Invoice Validated Accounting Event
Entry table, page 2-28.
4.
The cost center segment values on the invoice distribution, described in the Invoice
Distributions table, page 2-29, are not used, thereby maintaining the integrity of the
General Ledger account balances for the appropriate cost center segment values
from the receiving through the invoicing parts of the business flow.
Invoice Distributions
Distribution
Number
Distribution ID
Distribution
Amount
GL Account
Applied to
Distribution ID
201
75.00
01-117-Chrg
1011
202
25.00
01-118-Chrg
1012
Subledger Accounting uses rounding class along with the transaction rounding
reference to group journal lines tighter and calculate transaction rounding.
The journal entry line can have an actual, budget, or encumbrance balance type.
For products like Oracle public sector applications that use encumbrance
accounting, separate journal line types can be created for encumbrance lines.
Journal line types specify if the journal line is to be a debit, credit, or gain/loss line.
For example, when a Payables invoice is generated, the liability account should
normally be credited. The journal line type must therefore specify the Side option as
Credit. On the other hand, the payment of the Payables invoice must be accounted
with a debit to the liability account. A separate journal line type must be defined to
create this debit line.
The gain/loss amount is the difference in the ledger currency due to foreign
currency fluctuations. Gain or loss amounts occur when two related transactions,
such as an invoice and its payment, are entered in a currency other than the ledger
currency, and the conversion rate fluctuates between the time that the two are
accounted.
Users can specify whether the gain or loss has been calculated in the primary ledger
so that the gain or loss amount is not converted to the reporting currency or
non-valuation method secondary ledgers.
Users can specify whether to derive journal entry components from a related
journal entry.
The business flow method determines if and how a journal line should inherit
journal entry values.
See: Business Flow Method, page 2-19 and To Define Journal Line Types, page 2-31
Users can specify whether to apply multiperiod accounting to a journal line type.
See: Multiperiod Accounting, page 2-90
Journal entry lines are transferred to General Ledger in summary or detail mode.
Users can define conditions to restrict the use of a journal line type by controlling
when a particular journal line type is used by the Subledger Accounting program.
The table below describes selected fields and buttons in the Journal Line Types window.
Selected Fields and Buttons in the Journal Line Types Window
Field, Region, and Button
Description
Application
Name
Description
Accounting Class
Rounding Class
Enabled
Encumbrance
Description
Side
Applied to Application ID
Multiperiod Option
Conversion Date
Conversion Rate
Entered Amount
Description
Switch Debit/Credit
Description
Accounting Class
Rounding Class
Multiperiod Option
Currency
Conversion Date
Conversion Rate
Third Party
Accounting Flexfield
Description
Reconciliation Reference
Description
Gain/Loss Reference
Encumbrance Type
Description
Transaction
Method
Class
Currency Code
Conversion Date
Conversion Rate
Party Type
Party Identifier
Encumbrance Types
Description
Multiperiod
Conditions
Description
Description
Inherited
Source
Example 1: Using the Value of a Source to Set up a Journal Line Type Condition,
page 2-41
Example 2: Using Multiple Conditions with the And/Or Operator, page 2-42
Example 1: Using the Values of a Source to Set Up a Journal Line Type Condition
This example describes how to create a journal line type to account for an invoice price
variance (IPV). Due to changes in price, Payables uses the IPV to account for the
difference between purchase order price and invoice price.
Consider an IPV journal line type. A condition is defined and attached to this journal
line type, to ensure that the IPV is applied only to IPV lines. This condition can be
expressed as follows:
Where
Distribution Type of the detailed distribution line = IPV.
Using the Value of a Source to Set Up a Journal Line Type Condition Example
Seq.
Source
Distribut
ion Type
Segmen
t
Operato
r
Value
Type
Value
Constant
IPV
Segment
And/Or
Now consider a case where an invoice is entered and approved. The invoice involves
variance distribution lines that need to be accounted. Assume the presence of a
distribution line with a Distribution Type of IPV and another with a line type of tax.
Using the Value of a Source to Set Up a Journal Line Type Condition Example: Distribution
Type and Distribution Lines
Source
Distribution Line 1
Distribution Line 2
Distribution Type
IPV
Tax
Using the Value of a Source to Set Up a Journal Line Type Condition Example: Journal
Line Type
Distribution Line
Distribution Line 1
Distribution Line 2
For distribution line 1, a journal entry line for the IPV is created based upon the journal
line type. Note that a separate journal line type and condition must be written to handle
the non-IPV line type.
Example 2: Using Multiple Conditions with The And/Or Operator
This example involves multiple conditions that can be set up with the use of the And/Or
operator. Consider requirements as follows:
For cost center #420, the gain/loss on retirements from the sale of assets must use a
specific journal line type.
This condition can be expressed as follows:
Where
Cost Center of the asset retired = 420 And Retirement Type = Sale
Based on the above, the account derivation rule is entered as follows:
Using Multiple Conditions with the And/Or Operator Example: Account Derivation Rule
Seq.
Source
Segmen
t
Operator
Value
Type
Value
Distributio
n Account
Cost
Center
Constant
Retirement
Type
Constant
Segment
And/Or
420
And
Sale
1.
2.
3.
In the ( field, use the "(" and ")" symbols for grouping a section of a condition.
This is useful when a condition spans multiple lines with the And/Or operators.
4.
5.
Nature of Source
Null
Accounting Flexfield
Not Null
Accounting Flexfield
N/A
Key Flexfield
6.
7.
In the Value Type field, select the value type of the second operand that is
evaluated in the condition line.
The value types are:
Source: This includes any source defined for the application. The source can be
seeded by Oracle or it can be a custom source.
Constant: Choose this value type for a comparison with constant values.
The table below describes the relationship between the source and the value
type fields based on the transaction chart of accounts.
Transaction Chart of
Accounts
Nature of Source
Value Type
Null
Accounting Flexfield
Transaction Chart of
Accounts
Nature of Source
Value Type
Not Null
Accounting Flexfield
N/A
When defining a condition, you can compare one data source with another data
source by using the comparison operator, for example, '=' or '<>'. In some cases, the
value of one side of the data source could be null or blank when the extract data
contains no value for the specific source that is being compared. In such cases,
Subledger Accounting will return 'TRUE' or 'FALSE' depending on which
comparison operators are used and which data source is being compared as shown
in the table below.
8.
Condition
Expected Value
false
true
true
false
If the Segment field to the left of the Independent Value field has a dependent
segment and the value type is Constant, in the Independent Value field, enter the
value of the segment that the dependent segment is based upon.
This is the value for the independent segment in the key flexfield that the
dependent segment value is based upon. For example, the following condition,
described in the table below, requires users to choose an independent value before
choosing a value for the dependent segment.
Source
Segment
Operator
Value Type
Independent
Value
Value
Asset Category
Flexfield
Minor Category
Constant
BUILDING
ADMINISTRAT
ION
9.
If a value type of Constant is selected, then enter a value for the constant and
this value is used as the second operand to evaluate the condition.
Segment
Value Type
Key Flexfield
Not populated
Constant
Complete key
flexfield
combination
Key Flexfield
Populated
Constant
N/A
Constant
Values based on
value set or lookup
type if specified for
the source
Key Flexfield
Not Populated
Source
Key Flexfield
Populated
Source
Includes all
segment and key
flexfield sources
Segment
N/A
Source
All segment
sources
N/A
Source
All sources of
matching data type
10. If a value type of Source and a value that represents an Accounting Flexfield code
combination identifier are entered, optionally select a segment name in the Segment
field.
This segment value is used as the second operand in the condition line.
11. In the ) field, use AND/OR values to concatenate two lines together when making
complex conditions.
Typically, the AND takes precedence over the OR. Parenthesis are only required to
overwrite this precedence. As an example, consider a condition that should use a
particular account derivation rule if the following are true:
Assign journal entry descriptions headers and lines in the Applications Accounting
Definition window.
The table below describes selected fields in the Journal Entry Descriptions window.
Selected Fields in the Journal Entry Descriptions Window
Field
Description
Application
Owner
Field
Description
Enabled
Priority
Description
Seq.
Constant
Field
Description
Source
Segment
Display Description
Mapping Sets
Use mapping sets to associate a specific output value for an Accounting Flexfield or
Accounting Flexfield segment. Based on the input value, a specific value can be
assigned to a single segment or to the entire Accounting Flexfield. Use mapping sets in
account derivation rules to build the Accounting Flexfield.
To define a Mapping Set, pairs of values are specified. For each input value, specify a
corresponding account segment or Accounting Flexfield output value. One or more
related pairs of these input values and segment or Accounting Flexfield output values
form a mapping set. Use value sets or lookup types for validating the input values of
the mapping set.
For example, it is possible to create a mapping set based on two input values, Yes and
No. Apply these input values to determine the balancing segment value of an account:
01 if the input value is Yes and 02 if it is No. Use this mapping set in one of the rules
that builds the segment values of an account. The rule compares the value of a source to
see if it is Yes or No and determines the segment value accordingly.
As another example, suppose a business has three major regions: East, South, and West.
Assume also that the business has a Region Code segment in the Accounting Flexfield.
Region names can be input values in applications such as transaction type names and
service codes. These input values can be included with other information about the
transaction and become part of the source information available to the AMB. Users can
create a mapping set that maps region names to the corresponding region code as
described in the table below.
Mapping Region Names to Region Codes
Input Value
Segment Value
East
01
South
02
West
03
It is possible to restrict a mapping set to a range of dates by entering the start and end
dates. The GL date of the potential subledger entry is compared to the effective date
range of the mapping set. This determines whether mapping set values should be
applied.
Description
Enabled
Type region
Segment
Value Set
Field
Description
Value Type
Input Value
Field
Description
Output Value
Enabled
In this example, assume that if procurement is from a small business supplier, then
cost center 100 should be used. A mapping set is defined with two input values Yes
and No as described in the following table.
Output Value
Yes
100
No
200
The first invoice is for the purchase of goods and services from a small business
vendor. Therefore, the input value is Yes.
2.
The supplier of the second invoice does not meet the criteria to be categorized as a
small business. Therefore the Input Value is No.
The output segment value is therefore derived as described in the following table.
Example 1 Output Segment Value
Invoice
Cost Center
100
200
Example 2
In this example, the chart of accounts is setup with four segments. A mapping set is
defined with a value set for Supplier Type as described in the following table.
Example 2 Mapping Set
Input Value
Output Value
Services
01-100-6120-000
Consulting
01-400-6110-000
Assume that two invoices are entered into Payables, one for a supplier with a type of
Services and one for a supplier with a type of Manufacturing.
When using the mapping set, the source value Supplier Type from the accounting event
data is compared with the Mapping Set Input Values to determine the Accounting
Flexfield. In this example, there is a match for the first case; the invoice with a supplier
type of Services maps to an Input Value. However, the invoice with a supplier type of
Manufacturing does not map to an input value. The accounts are derived and described
in the following table.
Example 2 Derived Accounts
Invoice
Supplier Type
Output Value
Services
01-100-6120-000
Manufacturing
No account generated
flexfield-based rule.
If the Create Accounting program returns an account that is end-dated or disabled and
a substitute account is defined in General Ledger, Subledger Accounting uses the
substitute account. The original account is stored on the journal line for audit purposes.
If the substitute account is invalid and a suspense account is defined, Subledger
Accounting uses the suspense account. An error message is displayed if a valid
suspense account is not available.
See: Adding or Changing Individual Accounts, Oracle General Ledger User Guide
Define account derivation rules based on value sets in the absence of an accounting
chart of accounts.
See: Overview of Values and Values Sets, Oracle Applications Flexfield Guide
Share account derivation rules across applications in the following ways:
Create an account derivation rule based on another account derivation rule from
another application and assign it to a journal line type
For example, create a new account derivation rule Invoice Expense Account
referencing Project Cost Account assigned in the Priorities region. Attach Invoice
Expense Account rule to the journal line type Expense in the Journal Lines
Definitions window.
Note: To share an account derivation rule across applications, all
sources used by the account derivation rule must be available for the
event class.
When an account derivation rule is assigned to a journal line type in the
Journal Lines Definition window, Subledger Accounting verifies
whether all sources used by the account derivation rule are available
for the journal line type event class.
Distribution Account in the rule. The Subledger Accounting program then obtains
the account by referencing the distribution Accounting Flexfield.
The transaction or accounting chart of accounts does not need to be known when
this type of rule is defined. If no chart of accounts is specified, the value derived
from the source uses the default chart of accounts for the subledger application.
Segment Rules
Set up segment rules as follows:
If the accounting chart of accounts is not specified, create a rule to derive the value
for an Accounting Flexfield qualifier.
Set up segment rules using the same four methods discussed for Accounting Flexfield
rules. By specifying different value types, users can choose the way in which the
segment value is derived.
specified. This enables you to share the same rule between more than one accounting
chart of accounts if the segments in these chart of accounts share the same value set. Set
up Value Set based rules using the same four methods discussed in Accounting
Flexfield Rules, page 2-58. By specifying different Value Types, you can choose the way
in which the segment value is derived.
Output Value
Manufacturing
01-100-2210-0000
Services
01-200-2210-0000
Consulting
01-300-2210-0000
For the given transaction, assume that the accounting event information includes a
Source called Supplier Type. This serves as the Mapping Set Input Source. The
account derivation rule is defined to use the mapping set as described in the
following table.
Accounting Flexfield Rules Example 1: Account Derivation Rule Mapping Set
Priority
Value Type
Value
Input Source
Mapping Set
Vendor Category
Supplier Type
To derive an account, the values of the Mapping Set Input Source specified in a rule
are compared with the input values of the mapping set. In this example, Mapping
Set Input Source values from the accounting event information include the Supplier
Type source values. These are now compared with the Vendor Category input
values to determine what the account should be.
Assume that the accounting event data of the transaction to which the account
derivation rule is applied has a value for the Source Supplier Type of
Manufacturing. The account built by the Subledger Accounting program is derived
by applying the account derivation rule to the transaction object data. Using the
mapping set defined, if the supplier type is Manufacturing, the account created is
01-100-2210-0000.
2.
In this example, a segment rule is created to derive the cost center segment of the
Accounting Flexfield. The structure of the charts of accounts is described in the
table below.
Segment Rules Example 1: Chart of Accounts Structure
Chart of Accounts
Name
Structure
Transaction
Italy
Balancing-Cost
Center-Natural
Account-Region
Accounting
Belgium
Balancing-Cost
Center-Natural Account
The account derivation rule is defined to derive the cost center segment value from
the Region segment of the Distribution Accounting Flexfield. Note that the account
is always derived for the accounting chart of accounts.
The table below describes the account derivation rule for Example 1.
Segment Rules Example 1: Account Derivation Rule
Priority
Value Type
Value
Segment
Source
Distribution
Account
Region
Assume that the data from the Italy transaction chart of accounts has the following
values for the distribution Accounting Flexfield:
02-640-2210-1234
The segment built by the Subledger Accounting program is determined by applying
the account derivation rule to the source values. According to the account
derivation rule, the segment to be used to derive the cost center segment of the
accounting chart of accounts is the Region segment, which has a value 1234.
Note that other segment rules must be defined to build the remaining segments of
the account.
Name
Structure
Transaction
(Blank)
(Blank)
Accounting
Belgium
Balancing-Cost
Center-Natural Account
Value Type
Value
Source
Distribution
Account
Segment
Navigate to the Account Derivation Rules window, and in the Find Account
Derivation Rules window, click New.
The application name defaults from the application associated with the
responsibility.
The Owner field is automatically populated by Subledger Accounting. For
components seeded by Oracle, the value is Oracle. For components created on site
by users, the value is User.
2.
Retain the default for the Enabled check box which is selected to make the account
derivation rule available for use for any application with reference objects used in
In the Chart of Accounts region, select values for the charts of accounts.
If a value for the accounting chart of accounts is not selected, users can create an
account derivation rule for an Accounting Flexfield qualifier, an Accounting
Flexfield, or a value set.
Note: Account derivation rules seeded by Oracle user are
Accounting
Flexfield Rule
Segment Rule
Null
Entered
Not allowed
In the Output Type region, select the option that the account derivation rule will be
based on.
5.
If the output type Segment is selected, in the Segment field, select a segment from
the list of values.
If the accounting chart of accounts is specified, the list of values includes all enabled
segments for the chart of accounts. If the accounting chart of accounts is not
specified, the list of values includes all segment qualifiers for the flexfield
application and title.
6.
If the output type Value Set is selected, in the Value Set field, select a value set from
8.
To specify the method of deriving the Accounting Flexfield or segment value, in the
Value Type field, select a value type.
9.
In the Value field, enter the value consistent with the value type selected.
The table below summarizes the relationship between accounting chart of accounts,
output type, value type, and values in the Value field.
Accounting Chart
of Accounts
Output Type
Value Type
Null
Flexfield
Source
Accounting Chart
of Accounts
Output Type
Value Type
Null
Accounting Flexfield
Qualifier
Source
If creating an
account derivation
rule for Accounting
Flexfield: all enabled
sources for the
application marked
as Accounting
Flexfield plus
sources marked as
the Accounting
Flexfield qualifier
corresponding to the
segment to be
derived in the
account derivation
rule
Null
Value Set
Source
If creating an
account derivation
rule for Accounting
Flexfield: all enabled
sources for the
application marked
as an Accounting
Flexfield qualifier or
Other that have the
same value set
Null
Value Set
Mapping Set
All enabled
mapping sets with
the same value set
Null
Value Set
Constant
Null
Value Set
Account Derivation
Rule
All account
derivation rules with
no account
derivation rule
assigned to it
Accounting Chart
of Accounts
Output Type
Value Type
Not Null
Flexfield
Source
Not Null
Flexfield
Mapping Set
All enabled
mapping sets with
the same accounting
chart of accounts
and whose output
type is Flexfield
Not Null
Flexfield
Constant
All enabled
combination for the
accounting chart of
accounts
Not Null
Flexfield
Account Derivation
Rule
All account
derivation rules with
no account
derivation rule
assigned to it are
available.
Not Null
Segment
Source
If creating an
account derivation
rule for Accounting
Flexfield: all enabled
sources for the
application marked
as Accounting
Flexfield plus
sources marked as
the Accounting
Flexfield qualifier
corresponding to the
segment to be
derived in the
account derivation
rule plus sources
marked as the Other
segment
Accounting Chart
of Accounts
Output Type
Value Type
Not Null
Segment
Mapping Set
All enabled
mapping sets with
the same accounting
chart of accounts
and whose output
type has the same
segment as the
segment to be
derived in the
account derivation
rule
Not Null
Segment
Constant
Not Null
Segment
Account Derivation
Rule
All account
derivation rules with
no account
derivation rule
assigned to it
10. If value type Mapping Set is selected, in the Input Source field, select the source
Subledger Accounting program evaluates the conditions for the next priority until a
valid account or segment value is derived or there are no more conditions to evaluate.
You can combine Accounting Flexfield rules with segment rules. In this case, Subledger
Accounting uses the segment value derived from the segment rule to override the
corresponding segment of the Accounting Flexfield. 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 Accounting Flexfield rule.
Account derivation rules conditions are created in the same manner as described in
Defining Conditions for Journal Line Types, page 2-41.
Lookup Types
If a source is a lookup code, Subledger Accounting displays its corresponding meaning
in the appropriate language when it is used in header and line descriptions or
supporting references. Also, when defining conditions in the AMB, Subledger
Accounting displays the translated meaning to the user and stores the untranslated
lookup code. Since the untranslated lookup code is used in conditions, conditions can
function independently of the language used by the ledger.
Lookup types:
Reduce the number of source values that need to be stored in the transaction object
Help prevent errors by displaying valid, user friendly LOV names for sources that
are lookup codes
Source
Segment
Operat
or
Value
Type
Value
Segment
And/Or
Distribution
Account
Cost Center
Source
Liability
Account
Cost
Center
And
Asset Flag
Constant
Yes
Now assume that the accounting event data, to which the account derivation rule and
therefore the condition is applied, has two rows of data to be processed with the values
described in the following table.
Account Derivation 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 table above, assume the cost center segment as the second segment. Based on this
set up, the account derivation rule is applied to derive the account of Invoice 1 only. For
the second invoice, 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.
Supporting References
Define supporting references to store transaction information on your journal entry.
You can choose to maintain balances for each account and supporting reference detail
value combination.
After the supporting reference is defined, assign it to the application accounting
definition on the journal line types or on the header for event class and type. The
accounting program will then associate values from the transaction to the journal entry
created, based on your application accounting definition. You can also enter supporting
references for manual journal entries. Use the online inquiry to view the account
balances for a specific ledger and supporting reference.
Journal Line
Type
Account
Amount
Supporting
Reference:
Project Number
Invoice/All
Invoice Expense
01-100-4001-0000
$400
100
As a result, $400 is added to the subledger balance for the account 01-100-4001-0000 and
the project number 100. It is possible to execute an online inquiry on the subledger
balances by project number for the account 01-100-4001-0000.
Users can also define supporting references without associated balances. These are
mainly used as journal entry references and can be assigned at the journal entry header
or line levels. In contrast, supporting references defined with balances can only be
assigned at the line level.
2.
3.
Step 3: Include the Supporting References in the Header and/or Line Assignments
of the Journal Lines Definition
4.
Example 1: users determine that they want to have subtotals by transaction types and
by salesperson for a revenue account. Therefore, they set up Transaction Type and
Salesperson as supporting reference details.
The account balance breakdown using this grouping order is described in the table
below.
Grouping Order Example 1
Account #01-100-3000-0000 - Sales
Revenue
Total
$4,000
$6,000
$6,500
$1,000
Example 2: Users determine that they want subtotals by project number, by project
expenditure types and by project task number for an expense account. Therefore, they
set up Project Number and Project Expenditure Types as supporting reference details.
In this example, there is no subtotal for Project 2010 and expenditure type Television
Ads. This would occur because no subledger journal entry lines have been posted to
account 01-100-4000-0000 for this combination of Project Number and Expenditure
Type.
Grouping Order Example 2
Account #01-100-4000-0000 - Advertising
Expense
Total
$2,000
$6,000
Total
$6,000
Step 2: Assign Sources to the Supporting References DetailsAfter users have decided
the supporting references structure, they must select the sources that provide the values
for the supporting references details. Each supporting reference detail can have one or
more sources associated. A single source can be assigned for each application and event
class that affects the account balance. This is particularly relevant when the supporting
reference is used across different applications.
Example 1: Users want to break down the balance of an asset account by asset category.
The source for this value in Oracle Assets can be called Asset Category, while in Oracle
Projects it can be called Project Asset Category. Therefore, both sources need to be
assigned to the support reference details for the applications Assets and Projects
respectively.
Example 2: Users want to create a supporting reference for an inventory account to
analyze the balance by inventory item. The source storing the inventory item for a
purchase order can be called Purchase Order Item, while the one storing the item for a
material receipt can be called Receipt Item. Therefore, both sources need to be assigned
to the supporting reference detail, for the event classes corresponding to Purchase
Orders and Material Receipts respectively.
Step 3: Include the Supporting Reference in the Header and/or Line Assignments in
the Journal Lines Definition An organization can use the same general ledger account
to record activity from different applications, event types and journal line types. This is
especially true when the same general ledger account is used in different parts of a
business cycle. To support this requirement, Subledger Accounting provides users with
the ability to assign a supporting reference to multiple event classes, event types, and
journal line types. This also allows the supporting reference to be independent from the
general ledger accounts so that users need not know in advance all the accounts that are
used in combination with certain supporting references.
Example 1: Users want to create a supporting reference to analyze revenue from
Projects Billing and Account Receivables, which share the same account. Therefore, the
same supporting reference must be assigned to all combinations of event class, event
type, and journal line type that affects the revenue account from either Project Billing or
Account Receivables.
Example 2: Users want to create a supporting reference to analyze capital projects
expenditures by asset category. Therefore, the supporting reference must be assigned to
all combinations of event class, event types, and journal line type used for capital
expenditures in Projects as well as to all the ones used for asset additions, transfers, and
retirements in Assets.
Example 3: Users want to create a supporting reference to analyze an inventory account
by inventory item. Therefore, the supporting reference must be assigned to all
combinations of event class, event type, and journal line type used for inventory
purchase in Payables as well as to all the ones used for inventory issuances and cost
adjustments in Oracle Inventory and Cost Management.
Step 4: Validate the Application Accounting Definition Once users have completed
the supporting reference assignments, the application accounting definition must be
validated so that the changes are taken into account.
To validate an application accounting definition, the user navigates to the Application
Accounting Definitions window and clicks Validate. This submits a concurrent process
that validates the application accounting definition and recreates the underlying
database stored procedures. Once this concurrent process completes, the status of the
application accounting definition changes to Valid. This indicates that the modified
definition can now be used to generate subledger journal entries.
Always: The supporting reference balances at the end of the fiscal year are always
carried forward to the next fiscal year.
Never: The supporting reference balances are reset to zero at the beginning of a new
fiscal year.
Based on Account: The ending supporting reference balances for balance sheet
accounts (accounts whose account type is Asset, Liability, or Owner's Equity) are
carried forward to the next fiscal year, while they are reset to zero for income
statement accounts (accounts whose account type is Expense or Revenue).
2.
Click Create.
3.
In the Code field, enter a unique code for the supporting reference using a
combination of upper case letters, digits, underscores and no spaces.
4.
5.
6.
7.
In the Detail Code field, enter a unique detail code for the supporting reference
detail.
8.
In the Detail Name field, enter a name for the supporting reference detail.
9.
In the Description field, optionally enter a description for the supporting reference
detail.
10. To assign a source to the selected supporting reference detail, click Assign Sources.
You can search for sources defined for a particular application or event class and
search by source name in the Assign Sources page.
11. Enter search criteria and click Go.
12. Select one or more sources from the search results and click Apply to assign the
2.
3.
Click Go.
4.
Click the Update icon next to the supporting reference you wish to update.
Note: The Update icon is disabled if the supporting reference is
5.
1.
2.
3.
Click Go.
4.
Click the Duplicate icon next to the supporting reference you wish to duplicate.
5.
In the Duplicate Supporting Reference Options page, enter the code and name of
the new supporting reference.
6.
Choose whether to copy the details or the details and the source assignments.
If you choose the details option, the detail code, name, and description are copied
from the original supporting reference. Source assignments are not copied.
If you choose the details and source assignments option, both supporting reference
details and the source assignments are copied.
7.
Click Continue.
8.
9.
Click Apply.
A confirmation page indicates that you have successfully copied the supporting
reference.
1.
2.
3.
Click Go.
4.
Click the Delete icon next to the supporting reference you wish to delete.
Note: The Update icon is disabled if the supporting reference is
5.
A warning message will ask if you are sure that you want to delete the supporting
reference, click Yes to continue or No to cancel.
Debit
DR Computer Equipment
$10,000
Credit
Equipment
Debit
CR Account Payable
DR Fund Balance
Credit
$10,000
$10,000
$10,000
To achieve the above journal entries, two journal lines definitions are required as
described in the following tables.
Standard Invoice Journal Lines
Journal Line Type
Expense
Liability
Example 2
This example describes how to allocate an invoice's liability amount across multiple
balancing segments on the invoice distributions.
The Accounting Flexfield structure is Balancing Segment-Cost Center-Account. The
default liability account for supplier site ABC is 000-000-2300. If automatic offsets using
the balancing method are enabled, an invoice entered for supplier site ABC is
distributed as described in the table below.
Account
Debit
DR Expense 101-200-1245
$30
DR Expense 201-300-3045
$50
Credit
CR Liability 101-000-2300
$30
CR Liability 201-000-2300
$50
To achieve the above journal entry, the journal line definition is defined as described in
the table below.
Invoice Journal Lines with Automatic Offsets
Journal Line Type
Expense
Liability
The Liability journal line type requires the following account derivation rules:
Segment
All Segments
Liability Account
Balancing Segment
This procedure describes selected fields in the Journal Lines Definitions window
1.
Navigate to the Journal Lines Definitions window, and in the Find Journal Lines
Definitions window, click New.
The application name defaults from the application associated with the
responsibility.
The Owner field is automatically populated. For components seeded by Oracle, the
value is Oracle. For components created on site by users, the value is User.
2.
Retain the default for the Enabled check box, which is selected, to make the journal
lines definition available for use for this application and the selected chart of
accounts.
3.
To indicate that the journal lines definition is to be used only if the Create
Accounting program is run in budgetary control mode, select the Budgetary
Control check box.
4.
To assign a journal line type to an event type, in the Journal Line Type field, select a
journal line type.
The Owner field is automatically populated based on the journal line type selected.
5.
To inherit the journal line description from another journal line, select the Inherit
Description check box.
This check box is enabled only if the business flow method of the journal line entry
is Prior Entry or Same Entry. If this check box is selected, the Line Description and
Owner fields are disabled and cleared of any data.
6.
In the Line Description field, enter the journal entry description to be used to
populate the subledger journal entry lines.
The list of values includes all journal entry descriptions for the application to which
the event class belongs that meets the following condition:
All sources used by the journal entry description have been assigned to the
event class associated with the journal lines definition.
The Owner field is automatically populated based on the line description entered.
7.
To use this line assignment to generate subledger journal entries, select the Active
check box.
8.
In the Line Assignments region, select an accrual journal line type and click
Multiperiod Accounting Assignment to define the multiperiod journal entry and
the multiperiod options.
See: To Define Multiperiod Accounting, page 2-95
9.
10. In the Segment field, select an Accounting Flexfield segment or All Segments.
If entering an accounting chart of accounts for the journal lines definition, the list of
values includes all segments in the Accounting Flexfield structure. Otherwise, the
list of values includes the following Accounting Flexfield qualifiers:
All Segments
Balancing Segment
Management Segment
Intercompany Segment
If assigning both segment and Accounting Flexfield rules to a journal line type,
segment rules take precedence over Accounting Flexfield rules enabling users to
overwrite specific segments from the chart of accounts. If defining only qualifier
segments in the Account Derivation Rules tab, the rule assignment is not complete.
Define an assignment for All Segments.
Alternately, select a segment and build the Accounting Flexfield one segment at a
time. A separate account derivation rule must be applied to each segment.
11. If the business flow method is Same Entry for the journal line type, to inherit the
value in the Segment field from one side (debit or credit) of the current entry to the
other, select the Inherit check box.
If this field is selected, the Rule Name, Owner, Description, and Side fields are
blank.
12. In the Rule Name field, select the account derivation rule to populate the complete
Accounting Flexfield or a particular segment based on the value for the Segment
field.
The list of values includes all account derivation rules associated with the
application for which the journal lines definition is created which meet the
following conditions:
All sources used by the account derivation rule are assigned to the event class
associated with the journal lines definition.
If the value All Segments is selected in the Segment field, the list of values
includes only Accounting Flexfield rules.
For segment rules, account derivation rules that map to the particular segment
or account derivation rules with a value set that maps to the particular segment,
the accounting chart of accounts matches the one entered for the journal lines
definition and the segment name matches the one entered in the Segment field.
If no accounting chart of accounts is specified, the Accounting Flexfield
qualifier associated with the segment rule matches the one entered in the
previous field.
The Owner and Description fields are automatically populated based on the
account derivation rule selected.
The list of values includes the following:
All account derivation rules associated with the application for which the
journal lines definition is created
Sources that belong to the event class for which the line assignment is created
and which meet the conditions described in the table below.
Transaction Chart
of Accounts
Accounting Chart
of Accounts
Segment
Rule Name
Null
Null
All Segments
Null
Null
Accounting
Flexfield
Qualifiers
Null
Not Null
All Segments
Transaction Chart
of Accounts
Accounting Chart
of Accounts
Segment
Rule Name
Null
Not Null
Segments
Not Null
Null
All Segments
Transaction Chart
of Accounts
Accounting Chart
of Accounts
Segment
Rule Name
Not Null
Null
Accounting
Flexfield
Qualifiers
Not Null
Not Null
All Segments
Transaction Chart
of Accounts
Accounting Chart
of Accounts
Segment
Rule Name
Not Null
Not Null
Segments
13. Select the Supporting References tab to assign a supporting reference to the journal
line type.
14. In the Name field, select the appropriate supporting reference.
The Owner and Description fields are automatically populated based on the
supporting reference selected.
Upgrade Account Derivation Rules Tab
Users can enter account derivation rules for Prior-Entry business flow journal line types
referring to non-upgraded journal entries. This tab is displayed only for federal
installation when the FV: Federal Enabled profile option is enabled.
See: Profile Options, Oracle U.S. Federal Financials Implementation Guide
Description
Transaction
Accounting
Multiperiod Accounting
Multiperiod accounting enables users to create accounting for a single accounting event
for more than one GL period. The functionality is primarily used to recognize revenue
or a prepaid expense or revenue across multiple GL periods.
In the Journal Line Accounting Attributes Assignments window, assign sources for
the following accounting attributes:
In the Journal Line Types window, define the journal line types to be used for
multiperiod accounting by setting the multiperiod option.
See: To Define Journal Line Types, page 2-31
3.
5.
Update the line description for the accrual journal entry line type, which
defaults from the Journal Lines Definitions window
6.
Submit the Create Accounting program to create the originating journal entry as
8.
Once the multiperiod journal entries are processed, view the multiperiod journal
entries in the inquiry pages for subledger journal entry headers, subledger journal
entry lines, and accounting events.
Number of Months
$1,200,000.00
12
$100,000.00
Assume that the multiperiod accounting duration is from 1-Jan-06 to 31-Dec-06 and that
the multiperiod accounting options are as follows:
The table below describes the schedule to expense $100,000.00 each month over the next
twelve months.
Period
Amount
January 2006
$100,000.00
February 2006
$100,000.00
March 2006
$100,000.00
April 2006
$100,000.00
May 2006
$100,000.00
Period
Amount
June 2006
$100,000.00
July 2006
$100,000.00
August 2006
$100,000.00
September 2006
$100,000.00
October 2006
$100,000.00
November 2006
$100,000.00
December 2006
$100,000.00
The following journal entry is created with GL Date 31-DEC-2005 to record the prepaid
rent expense.
Account
Entered DR
Prepaid Rent
Expense
$1,200,000.00
Liability
Total:
Entered CR
Account DR
(USD)
$1,200,000.00
$1,200,000.00
$1,200,000.00
Account CR
(USD)
$1,200,000.00
$1,200,000.00
$1,200,000.00
$1,200,000.00
The following journal entry with GL date 01-JAN-2006 recognizes the rent expense for
January.
Account
Entered DR
Rent Expense
$100,000.00
Prepaid Rent
Expense
Entered CR
Account DR
(USD)
Account CR
(USD)
$100,000.00
$100,000.00
$100,000.00
Account
Entered DR
Entered CR
Account DR
(USD)
Account CR
(USD)
Total:
$100,000.00
$100,000.
$100,000.00
$100,000.00
During the ensuing eleven months, the journal entry shown in the table above will be
created to recognize the monthly rent expense as it is incurred.
1.
In the Line Assignments region of the Journal Lines Definitions window, select the
accrual journal line type which will create the originating entry and click
Multiperiod Accounting.
The Definition Name and Journal Line Type fields default from the Journal Lines
Definitions window.
2.
Description
Header Description
Field
Description
Field
Description
GL Dates
Options are:
3.
Field
Description
Proration Type
4.
To assign journal line types to create the recognition journal line, enter data as
described in the table below.
Description
Accrual Reversals
Use accrual reversal to define how and when accrual reversals are automatically
performed. You can:
Assign the Accrual Reversal GL Date accounting attribute at the event class level in
the Accounting Attribute Assignments window.
Use this attribute to schedule the automatic reversal of a journal entry at the time it
is created. Assign any standard date source or one of the following system sources
to the accrual reversal GL date accounting attribute:
Next Day: The GL date of the accrual reversal will be the next day following the
GL date of the accrual entry. If there is a transaction calendar assigned to the
ledger, this will be the next business day.
First Day Next GL Period: The GL date of the accrual reversal entry will be the
first day of the following period. If there is a transaction calendar assigned to
the ledger, this will be the first business day.
Last Day Next GL Period: The GL date of the accrual reversal entry will be the
last day of the following period. If there is a transaction calendar assigned to
the ledger, this will be the last business day.
Note: Users can override the accrual reversal GL date accounting
2.
3.
GL Date
Open or Future
Entry GL Period
Closed or
Permanently Closed
GL Period
Never Opened GL
Period
The GL Date of
the accrual
reversal is on or
before the End
GL Date in the
mode specified in
the Create
Accounting
request
Creates the
journal entry with
the status
specified in the
Create
Accounting
request
Adjusts the GL
date to the next
open period
Adjusts the GL
date to the next
open GL period
GL Date
Open or Future
Entry GL Period
Closed or
Permanently Closed
GL Period
Never Opened GL
Period
GL Date of the
accrual reversal is
after the END GL
Date specified in
the Create
Accounting
request
Creates the
journal entry with
an incomplete
status
Adjusts the GL
date to the next
open GL period
If no open GL
period is found,
creates the journal
entry with an error
status
5.
Example 1
A company receives materials worth $100 on the 30th of the month but has not been
invoiced. The following journal entry is created when the material is received to record
the accrual.
Account
Entered DR
Accrual Expense
100.00
Accrual Liability
Entered CR
Accounted DR
(USD)
Accounted CR
(USD)
100.00
100.00
100.00
The accrual reversal GL date is First Day Next GL period and the following journal
entry is created to reverse the accrual.
Account
Entered DR
Accrual Liability
100.00
Accrual Expense
Entered CR
Accounted DR
(USD)
Accounted CR
(USD)
100.00
100.00
100.00
Example 2
Futures trading requires a margin account that is market-to-market on a daily basis.
This means that the investor or ledger's gains or losses on the position are reflected on a
daily basis. If the margin account drops below a specified amount (the maintenance of
the margin), a margin call is issued. This requires the holder of the account to replenish
the account to the initial margin level or close out the position. In this scenario, the
investor or ledger must mark the account to market each day and the entry booked
from the day before may need to be reversed to reflect the new position.
The following journal entry is created on June 1, 2006.
GL Date: 01-Jun-2006
Account
Entered DR
Loss
100.00
Margin Liability
Entered CR
Accounted DR
(USD)
Accounted CR
(USD)
100.00
100.00
100.00
The Accrual Reversal GL Date is set to Next Day and the following journal entry is
created to reverse the journal entry from June 1.
GL Date: 02-Jun-2006
Account
Entered DR
Margin Liability
100.00
Loss
Entered CR
Accounted DR
(USD)
Accounted CR
(USD)
100.00
100.00
100.00
On June 2, a new journal entry is created to reflect the new position, which will be
reversed on June 3.
GL Date: 02-Jun-2006
Account
Entered DR
Loss
105.00
Margin Liability
Entered CR
Accounted DR
(USD)
Accounted CR
(USD)
105.00
105.00
105.00
On June 3, the following journal entry is created to reverse the accrual from June 2.
GL Date: 03-Jun-2006
Account
Entered DR
Margin Liability
105.00
Loss
Entered CR
Accounted DR
(USD)
Accounted CR
(USD)
105.00
105.00
105.00
Description
Ledger
Process Category
End GL Date
Errors Only
Report
Parameter
Description
source assignments for the GL date and Accrual Reversal GL date, if enabled for the
event class
You can assign multiple journal lines definitions to an event class or event type.
Subledger Accounting generates a single journal entry per accounting event and ledger
using the line assignments from all the journal lines definitions assigned to the event
class or event type. The following can be assigned to a journal lines definition:
Supporting references
window.
Journal Lines Definitions can be assigned to the application accounting definition in the
Application Accounting Definition window.
Prerequisite
Define the following:
Description
Application
Owner
Enabled
Accounting
Description
Validation Status
Create Accounting
Description
Locked
Header Assignments
Description
Include region
Batch Name
Parameter
Import Option
Validate
Force Overwrite
Description
Versioning Mode
User Version
Export Comment
Description
Owner
Field
Description
Enabled
Application
The Transaction and Accounting charts of accounts defaults from the original subledger
accounting method. Note that if a value has defaulted for these fields, they cannot be
updated. However, if the original subledger accounting method does not have a
transaction or accounting chart of accounts, enter them in this window.
These entries serve as the charts of accounts for the subledger accounting method
created. If entered, only components defined with the same or no charts of accounts are
available for assignment to the new subledger accounting method. The accounting chart
of accounts, if entered, must match the chart of accounts of the ledger that this new
subledger accounting method is to be assigned to.
See: Transaction and Accounting Charts of Accounts, page 2-7
Use this inquiry to plan and assess the impact of modifications to the application
accounting definitions. For example, you may want to add the customer name to the
journal entry description for cash receipts, but they are unsure whether the same
journal entry description is being used for miscellaneous receipts which do not have an
associated customer. In another scenario, you can change an account derivation rule to
take the cost center from a mapping set based upon Oracle Projects expenditure types
but are unsure whether the same account derivation rule is used for other cases in
which the mapping set might not apply.
Assignments
3
Create Accounting and Transfer Journal
Entries to GL Programs
Transfers the final journal entries in the current batch run to General Ledger and
starts the General Ledger posting process
Generates the Subledger Accounting Program Report, which documents the results
of the Create Accounting program
The Transfer Journal Entries to GL program enables you to transfer any eligible journal
entries to General Ledger, including those from previous batch runs that have not yet
been transferred to General Ledger.
Description
Ledger
Process Category
End Date
Parameter
Description
Mode
Errors Only
Report
Parameter
Description
Ledger
Process Category
End Date
Please refer to the descriptions in the Create Accounting Programs Parameters table,
page 3-1 .
Successful events and the subledger journal entries created for those events
Users can run the report in summary or detail mode which are described as follows:
Detail mode provides details of subledger journal entries generated from the
processing of completed events and a detailed error report.
Transfer to GL Summary
General Errors
4
Conversion of Historical Data for Reporting
Currencies and Secondary Ledgers
Reporting Currency Ledger: Run the Reporting Currency: Create Opening Balance
Conversion of Historical Data for Reporting Currencies and Secondary Ledgers 4-1
Secondary Ledger: Use the Consolidation Workbench to copy initial balances. For
more information on using the Consolidation Workbench, refer to the Oracle
Financials Implementation Guide.
Restrictions:
The program cannot be used for a secondary ledger whose subledger accounting
method is different from that of the primary ledger.
All fully accounted transactions of the primary ledger must be transferred to Oracle
General Ledger before running the program.
2.
Select SLA Secondary/ALC Ledger Historic Upgrade from the LOV in the Name
field.
3.
2.
3.
Upgrade Start Period: Select the first period from which you wish to run the
historic upgrade.
4.
5.
6.
7.
Mode:
Final: Select this value after you run the program in the Validation mode.
This mode creates the journal entries within Oracle Subledger Accounting.
option, rate type, and rate date are picked up from the ledger
relationships defined in the Accounting Setup Manager.
Conversion of Historical Data for Reporting Currencies and Secondary Ledgers 4-3
5
Diagnostic Framework
Transaction objects
Ledger information
System sources
Source values
The following examples describe typical uses of the diagnostic framework features.
In the implementation phase, users can launch the Transaction Objects Diagnostic
report to review the source values available in the transaction objects.
On a daily basis, users can use the Transaction Objects Diagnostic report to analyze
issues related to the generation of subledger journal entries.
The following steps describe the diagnostic framework business process flow:
1.
The administrator sets the SLA: Enable Diagnostics profile option to Yes for the
user or responsibility.
See: SLA: Enable Diagnostics, page B-5
2.
Users submit the Create Accounting program which automatically executes the
diagnostic framework to populate the diagnostic tables.
3.
The diagnostic framework gathers source values and other information from the
transaction objects.
4.
Users submit the Transaction Objects Diagnostics concurrent request to view the
diagnostic report.
5.
Description
Ledger
Optional; limits the diagnostic data to the specified event class within
the application
List of values includes the event classes for the corresponding
application.
Optional; limits the diagnostic data to the specified event type within
the event class. To enable this event, users enter a transaction number.
List of values includes the event types matched with the current
application, entity, and event class.
If no event class is selected, users cannot enter a value. If an event
class is entered, the value from the list of values is dependent on the
value of the event class. If the event type field is blank, all the event
types are selected.
Transaction Number
Event Number
Optional; displays the data for the transaction object lines that are
equal to or higher than the number specified
To enable this field, users must enter a transaction number and an
event number.
List of values includes all transaction object line numbers for the given
event.
Field
Description
To Extract Line
Number
Optional; displays the data for the transaction object lines that are
equal to or lower than the number specified
To enable this field, users must enter a transaction number and an
event number.
List of values includes all transaction object line numbers for the given
event.
Accounting Program
Request ID
Errors Only
Required
If Yes is selected, displays the diagnostic framework data only for the
events that meet the selection criteria and whose status is Error.
Default is No.
Display Source Name
Required
If Yes is selected, the source name is displayed. If No is selected, the
source code is displayed. Default is No.
Display Accounting
Attributes
Required
If Yes is selected, the accounting attributes are displayed. Default is
No.
The table below describes the parameters for the Purge Transaction Objects Diagnostics
program.
Description
Application
End Date
Accounting
Program Request
ID
Purges the diagnostic data for a given request ID, which corresponds to
an execution of the Create Accounting program
The list of values includes all request IDs for previous executions of the
Create Accounting program with diagnostics enabled.
6
Subledger Journal Entries
Manually create subledger journal entries and assign supporting references at the
header and line level in the Create Subledger Journal Entry page.
See: Creating Manual Subledger Journal Entries, page 6-2
Use the Create Accounting program to process eligible accounting events to create
subledger journal entries.
See: Overview of Create Accounting and Transfer Journal Entries to GL Programs,
page 3-1
Use the Manual Subledger Journal Entries API to create, update, delete, complete,
and reverse subledger journal entries.
A manual subledger journal entry is not associated with a subledger transaction. When
the manual subledger journal entry is complete, Subledger Accounting assigns the
appropriate sequence names, sequence numbers, and creates the reporting currency
journal entries if appropriate.
Enter manual subledger journal entries only against a primary or secondary ledger.
Manual journal entries created for the primary ledgers are automatically posted to the
reporting currency and not to the secondary ledger.
See:
Description
Ledger
Journal category
GL Date
Reference Date
Opens the Assign Supporting References Lines page where you can assign and
unassign supporting references.
Select the supporting reference in the Name field and enter details as required.
To assign supporting references to the lines of a journal entry in the Lines region of the
Create Subledger Journal Entry page:
Select the supporting reference in the Name field and enter details as required.
Optionally enter third party information, description, and currency details for each
line of the subledger journal entry.
If third party control accounts are enabled for the application and the account
entered is a third party control account, third party information must be entered.
For example, if Payables is set up to support only Supplier, you cannot select third
party control accounts that have been set up to support only Customer.
See: Third Party Balances Report, page 9-33
View the total accounted amounts of all subledger journal entry lines in the ledger
currency.
Selected Fields and Buttons in the Create Subledger Journal Entry Page, Lines Region
Field and Button
Description
Conversion Rate
Calculate Totals
Continue
If budgetary control is enabled for the primary ledger and the subledger journal
entry fund status is Required and Failed, initiate funds check to reserve funds to
complete the subledger journal entry. Subledger Accounting returns a status of
Passed or Failed.
There is no manual reservation of funds and funds checking cannot be initiated for
Description
Draft
Final
Validates the accounts; same validation as that performed by the Create Accounting
program
See: Subledger Journal Entry Definition Overview, page C-1
Updates the pending subledger journal entry with the corresponding error message
if the subledger journal entry is not successfully created
ledger has a different chart of accounts, all lines are cleared because the
Accounting Flexfield structure is dependent on the new ledger.
Switch DR/CR
Change Sign
Supporting references for manual subledger journal entries with a status of Final
When a manual journal entry is updated, you can update all fields except Balance Type
and Ledger.
7
Inquiries
Perform an inquiry on accounting events, journal entries and journal entry lines
based on multiple selection criteria
View detailed information about the subledger journal entry headers for a given
accounting event
Compare subledger journal entry information for any two journal entries
Inquiries 7-1
2.
3.
4.
5.
View detailed entry information about the subledger journal entry header by
clicking the ledger link.
Note: The following conditions exist:
6.
7.
If viewing an accrual reversal journal entry in the View Subledger Journal Entry
page, the View Accrual Entry button is displayed to view the accrual journal entry
details. If viewing an accrual journal entry, the View Reversing Entry button is
displayed to view the accrual reversal journal entry details.
8.
View multiperiod lines associated with the accrual journal entry by clicking the
Multiperiod icon in the Lines region.
9.
Compare subledger journal entry header and line information for two selected
journals by clicking Compare in the View Subledger Journal Entry Headers page.
10. View the transaction associated with the accounting event by clicking View
11. View supporting references at the header or line level for the subledger journal
Inquiries 7-3
2.
Execute a search.
3.
4.
5.
View detailed header and line information by selecting the ledger link.
6.
7.
If viewing an accrual reversal journal entry in the View Subledger Journal Entry
page, the View Accrual Entry button is displayed to view the accrual journal entry.
If viewing an accrual journal entry, the View Reversing Entry button is displayed
to view the accrual reversal journal entry.
8.
View multiperiod lines associated with the accrual journal entry by clicking the
Multiperiod icon in the Lines region.
9.
Create journal entries page by clicking Create Journal Entry in the Subledger
Journal Entries page.
10. Compare subledger journal entries by clicking Compare in the Subledger Journal
Entries page.
Inquiries 7-5
2.
Execute a search.
3.
4.
View subledger journal entry lines and header for a selected journal entry line by
clicking View Journal Entry.
5.
View journal line information in t-account format by clicking View T-account in the
View Subledger Journal Entry page.
6.
7.
If viewing an accrual reversal journal entry in the View Subledger Journal Entry
page, the View Accrual Entry button is displayed to view the accrual journal entry
details. If viewing an accrual journal entry, the View Reversing Entry button is
displayed to view the accrual reversal journal entry details.
8.
View multiperiod lines associated with the accrual journal entry line by clicking the
Multiperiod icon in the Lines region.
9.
View the transaction associated with the subledger journal entry by clicking View
Transaction in the Subledger Journal Entry Lines page.
Note: This button appears only if the drilldown procedure is
Inquiries 7-7
2.
Enter required information: ledger, period range, and supporting reference name.
Optionally, enter an account and supporting reference detail values.
3.
Click Go.
4.
Click on the appropriate period activity to view the journal entry lines.
5.
On the View Journal Entry Lines page, click View Journal Entry to drill-down to the
Subledger Journal Entry page and view the journal entry to which the line belongs
or click View Transaction to drill-down to the subledger transaction that originates
the journal entry.
6.
Click the Supporting References icon to open the View Supporting References page.
7.
On the Supporting Reference Balances page, click Export to download the balances
to a spreadsheet.
8
Reporting Sequence
accounting sequence
The accounting sequence is assigned to Subledger Accounting journal entries at the
time that the journal entry is completed. The sequence is assigned in the completion
date order using the GL date as the date criterion for determining the sequence to
be used.
reporting sequence
The reporting sequence is assigned to both Subledger Accounting journal entries
and General Ledger journal entries when the General Ledger period is closed. This
sequence is used by most of the legal reports required in some countries as the main
sorting criterion to display the journal entries.
Note: In some related documents, this sequence is referred to as the
chronological sequence.
These two sequences are not mutually exclusive and can coexist in the same journal
entry.
In some cases, the completed journal entries can be functionally correct but the
sequence numbers assigned to them are wrong. For example, the user realizes that the
sequencing setup is not correct and wants to resequence all the journal entries that are
sequenced based on the wrong setup. Subledger Accounting provides an undo and
redo accounting feature to correct the original accounting. A key component of this
feature is the Re-sequencing of Journal Entries.
Reporting sequence is optional.
Sequence Programs
The reporting sequence feature is based on the following programs:
The reporting sequence program selects the journal entries to be sequenced and
performs the following:
Sequences the journal entries that are completed and transferred to General Ledger
Assigns sequence numbers that are consecutive with no gaps to journal entries that
share the same sequence
2.
Create, complete, and post journal entries as part of the daily operations.
3.
Close a General Ledger period as part of the period end operations and the
reporting sequence program is automatically run.
After selecting the journal entries that belong to this period and to all the
subsequent consecutive closed periods, the reporting sequence program calls the
accounting sequence numbering program to perform the actual sequencing. The
reporting sequence program selects the journal entries in chronological order based
on the sequencing order.
When a GL period is closed, the journal entries are sequenced if all the prior GL
periods are closed based on the sequence control date.
When there is one previous GL period open, the journal entries that belong to a
closed period are not eligible for sequencing.
4.
5.
You can decide to open a closed period as part of the reconciliation process and the
reporting sequence program is automatically run.
The program erases the sequences that are assigned to the journal entries that
belong to the reopened period. If there are other succeeding closed periods, the
sequences assigned to the journal entries that belong to these periods are also
erased. As the sequence assigned to the journal entries is a gapless sequence, the
reporting sequence program calls the accounting sequence numbering program in
erase mode with the lowest sequence assigned to the selected journal entries to
avoid gaps when the journal entries are resequenced.
6.
Enter new journal entries into the period that has been reopened.
7.
Close the period and the reporting sequence program is automatically run.
The reporting sequence program calls the accounting sequence numbering program
to sequence all the journal entries that belong to this period in chronological order
based on the sequencing order. The reporting sequence program selects the journal
entries that belong to the succeeding closed periods.
The following journal entries can be assigned a reporting sequence:
8.
Run the report that displays all the journal entries that belong to the closed periods
with their new sequence.
9
Subledger Accounting Reports
This chapter describes the parameters and data elements for each report.
System administrators can define new concurrent programs using any subset of the
parameters. Users can create new XML Publisher templates using any subset of the data
elements.
See: Overview of Concurrent Programs and Requests, Oracle Applications System
Administrator's Guide, Creating a Template, Oracle XML Publisher User's Guide
XML output files are composed of tag set elements. For example, in the figure above,
<BEGIN_BALANCE>-388650</BEGIN_BALANCE> is the beginning balance element,
which consists of a starting and ending tag. The data between the tags is the value of the
element. In the figure above, the value for the beginning balance element is -388650.
Parameters
The parameters in some of the following reports are categorized as follows:
The custom parameters described in the table below apply to all the Subledger
Accounting reports.
Custom Parameters
Parameter
Token
Required
Valid Values
Custom Parameter 1
P_CUSTOM_PARA
METER_1
No
No validation
Custom Parameter 2
P_CUSTOM_PARA
METER_2
No
No validation
Custom Parameter 3
P_CUSTOM_PARA
METER_3
No
No validation
Custom Parameter 4
P_CUSTOM_PARA
METER_4
No
No validation
Custom Parameter 5
P_CUSTOM_PARA
METER_5
No
No validation
Token
Required
Valid Values
P_LEDGER
Yes
Legal Entity
P_LEGAL_ENTITY
No
Transaction Legal
Entity
P_TRX_LEGAL_ENTI
TY
No
Yes
From
P_PERIOD_FROM
To
P_PERIOD_TO
No
Parameter
Token
Required
Valid Values
From
P_GL_DATE_FROM
To
P_GL_DATE_TO
No
From
P_CREATION_DATE
_FROM
To
P_CREATION_DATE
_TO
Transaction Date
[From, To]
No
From
P_TRANSACTION_
DATE_FROM
To
P_TRANSACTION_
DATE_TO
P_JE_STATUS
No
Posted
P_POSTING_STATU
S
No
Journal Source
P_JE_SOURCE
No
Parameter
Token
Required
Valid Values
Process Category
P_PROCESS_CATEG
ORY
No; requires a
source
associated
with a
subledger
application
Accounting Event
Class
P_EVENT_CLASS
No; requires a
source
associated
with a
subledger
application
Accounting Sequence
Name
P_ACCOUNTING_S
EQUENCE_NAME
No
Accounting Sequence
Version
P_ACCOUNTING_S
EQUENCE_VERSIO
N
No; requires
accounting
sequence
name
Accounting Sequence
Number [From, To]
No; requires
accounting
sequence
name and
version
From
P_ACCOUNTING_S
EQUENCE_NUMBE
R_FROM
To
P_ACCOUNTING_S
EQUENCE_NUMBE
R_TO
Reporting Sequence
Name
P_REPORTING_SEQ
UENCE_NAME
No
Parameter
Token
Required
Valid Values
Reporting Sequence
Version
P_REPORTING_SEQ
UENCE_VERSION
No; requires
reporting
sequence
name
Reporting Sequence
Number [From, To]
No; requires
reporting
sequence
name and
version
From
P_REPORTING_SEQ
UENCE_NUMBER_F
ROM
To
P_REPORTING_SEQ
UENCE_NUMBER_T
O
Document Sequence
Name
P_DOCUMENT_SEQ
UENCE_NAME
No
Document Sequence
Number [From, To]
No; requires
document
sequence
name
From
P_DOCUMENT_SEQ
UENCE_NUMBER_F
ROM
To
P_DOCUMENT_SEQ
UENCE_NUMBER_T
O
P_PARTY_TYPE
No
Customer or Supplier
P_PARTY_NAME
No; requires
third party
type
Parameter
Token
Required
Valid Values
No; requires
third party
type
From
P_PARTY_NUMBER
_FROM
To
P_PARTY_NUMBER
_TO
Journal Category
P_JE_CATEGORY
No
Balance Type
P_BALANCE_TYPE
No
Budget
P_BUDGET_NAME
No
Encumbrance Type
P_ENCUMBRANCE_
TYPE
No
P_INCLUDE_ZERO_
AMOUNT_LINES
No
Entered Currency
P_ENTERED_CURRE
NCY
No
Side
P_SIDE
No
Accounted Amount
Range [From, To]
No
From
P_ACCOUNTED_A
MOUNT_FROM
Parameter
Token
Required
Valid Values
To
P_ACCOUNTED_A
MOUNT_TO
Balancing Segment
[From, To]
No
From
P_BALANCING_SEG
MENT_FROM
To
P_BALANCING_SEG
MENT_TO
Natural Account
Segment [From, To]
No
From
P_ACCOUNT_SEGM
ENT_FROM
To
P_ACCOUNT_SEGM
ENT_TO
Parameter
Token
Required
Valid Values
Accounting Code
Combination [From,
To]
No
From
P_ACCOUNTING_F
LEXFIELD _FROM
To
P_ACCOUNTING_F
LEXFIELD_ TO
Valuation Method
P_VALUATION_ME
THOD
No
No validation
Security Id Integer 1
P_SECURITY_ID_IN
T_1
No
No validation
Security Id Integer 2
P_SECURITY_ID_IN
T_2
No
No validation
Security Id Integer 3
P_SECURITY_ID_IN
T_3
No
No validation
Security Id Char 1
P_SECURITY_ID_CH
AR_1
No
No validation
Security Id Char 2
P_SECURITY_ID_CH
AR_2
No
No validation
Security Id Char 3
P_SECURITY_ID_CH
AR_3
No
No validation
Post-Accounting
Program
P_POST_ACCOUNTI
NG_PROGRAM
No; requires a
source
associated
with a
subledger
application
Parameter
Token
Required
Valid Values
User Transaction
Identifier Column 1
P_USER_TRX_ID_CO
LUMN_1 (to 5)
No; requires
an event class
User Transaction
Identifier Value 1
P_USER_TRX_ID_VA
LUE_1 (to 5)
No; requires
an event class
No validation
GL Batch Name
P_GL_BATCH_NAM
E
No; requires a
journal entry
source
Include User
Transaction
Identifiers
P_INCLUDE_USER_
TRX_IDENTIFIERS
No
P_INCLUDE_TAX_D
ETAILS
No
P_INCLUDE_LEGAL
_ENTITY_INFO
No
Description
GL Date
GL_DATE
Transaction Created by
CREATED_BY
Creation Date
CREATION_DATE
LAST_UPDATE_DATE
GL Transfer Date
GL_TRANSFER_DATE
Reference Date
REFERENCE_DATE
Completed Date
COMPLETED_DATE
External Reference
EXTERNAL_REFERENCE
Period Year
PERIOD_YEAR
PERIOD_YEAR_START_DATE
PERIOD_YEAR_END_DATE
Period Number
PERIOD_NUMBER
Period Name
PERIOD_NAME
PERIOD_START_DATE
Field Name
Description
PERIOD_END_DATE
Transaction Number
TRANSACTION_NUMBER
Subledger transaction
number
Transaction Date
TRANSACTION_DATE
ACCOUNTING_SEQUENCE_
NAME
Accounting Sequence
Version
ACCOUNTING_SEQUENCE_V
ERSION
Accounting Sequence
Number
ACCOUNTING_SEQUENCE_
NUMBER
REPORTING_SEQUENCE_NA
ME
REPORTING_SEQUENCE_VER
SION
REPORTING_SEQUENCE_NU
MBER
Document Sequence
Category
DOCUMENT_CATEGORY
DOCUMENT_SEQUENCE_NA
ME
DOCUMENT_SEQUENCE_NU
MBER
Field Name
Description
Application Id
APPLICATION_ID
Application Name
APPLICATION_NAME
Ledger ID
LEDGER_ID
LEDGER_SHORT_NAME
Ledger Description
LEDGER_DESCRIPTION
Description of ledger
owning the journal entry
Ledger Name
LEDGER_NAME
Ledger Currency
LEDGER_CURRENCY
Header ID
HEADER_ID
Header Description
HEADER_DESCRIPTION
JOURNAL_ENTRY_STATUS
Transfer to GL Status
TRANSFER_TO_GL_STATUS
BALANCE_TYPE_CODE
Field Name
Description
BALANCE_TYPE
Budget Name
BUDGET_NAME
Encumbrance Type
ENCUMBRANCE_TYPE
FUND_STATUS
JE_CATEGORY_NAME
JE_SOURCE_NAME
Event ID
EVENT_ID
Internal identifier of
accounting event that
originated the journal entry
Event Date
EVENT_DATE
Event Number
EVENT_NUMBER
EVENT_CLASS_CODE
EVENT_CLASS_NAME
EVENT_TYPE_CODE
Field Name
Description
EVENT_TYPE_NAME
USER_TRX_IDENTIFIER_NAM
E_1 (to 10)
Additional transaction
information for identifying
the transaction
USER_TRX_IDENTIFIER_VAL
UE_1 (to 10)
Additional transaction
information for identifying
the transaction
Batch Name
GL_BATCH_NAME
GL Batch Status
GL_BATCH_STATUS
Posted Date
POSTED_DATE
GL Journal Name
GL_JE_NAME
GL Document Sequence
Name
GL_DOC_SEQUENCE_NAME
GL Document Sequence
Value
GL_DOC_SEQUENCE_VALUE
GL Line Number
GL_LINE_NUMBER
Line Number
LINE_NUMBER
Field Name
Description
ACCOUNTING_CLASS_CODE
Accounting Class
ACCOUNTING_CLASS_NAM
E
Line Description
LINE_DESCRIPTION
Code Combination Id
CODE_COMBINATION_ID
Accounting code
combination internal
identifier for the journal
entry line
Accounting Code
Combination
ACCOUNTING_CODE_COMB
INATION (concatenated
values)
Code Combination
Description
CODE_COMBINATION_DESC
RIPTION (concatenated
descriptions)
Concatenated descriptions
of the accounting code
combination for the journal
entry line
CONTROL_ACCOUNT_FLAG
Control Account
CONTROL_ACCOUNT
Entered Currency
ENTERED_CURRENCY
Conversion Rate
CONVERSION_RATE
CONVERSION _RATE_DATE
Field Name
Description
CONVERSION
_RATE_TYPE_CODE
CONVERSION_RATE_TYPE
Entered Debit
ENTERED_DR
Entered Credit
ENTERED_CR
UNROUNDED_ACCOUNTED
_DR
Unrounded Accounted
Credit
UNROUNDED_ACCOUNTED
_CR
Accounted Debit
ACCOUNTED_DR
Accounted Credit
ACCOUNTED_CR
Statistical Amount
STATISTICAL_AMOUNT
Reconciliation Reference
RECONCILIATION_REFEREN
CE
Attribute Category
ATTRIBUTE_CATEGORY
PARTY_TYPE_CODE
Field Name
Description
PARTY_TYPE
PARTY_NUMBER
PARTY_NAME
PARTY_TYPE_TAXPAYER_ID
PARTY_TAX_REGISTRATION
_NUMBER
PARTY_SITE_NUMBER
PARTY_SITE_NAME
PARTY_TAX_REGISTRATION
_NUMBER
PARTY_SITE_NUMBER
PARTY_SITE_NAME
PARTY__SITE_TAX_REGISTR
ATION_NUMBER
Balancing Segment
BALANCING_SEGMENT
Balancing Segment
Description
BALANCING_SEGMENT_DES
CRIPTION
Field Name
Description
Natural Account
NATURAL_ACCOUNT
NATURAL_ACCOUNT_DESC
RIPTION
Cost Center
COST_CENTER
COST_CENTER_DESCRIPTIO
N
Management Segment
MANAGEMENT_SEGMENT
Management Segment
Description
MANAGEMENT_SEGMENT_
DESCRIPTION
Inter-company Segment
INTERCOMPANY_SEGMENT
Inter-company Segment
Description
INTERCOMPANY_SEGMENT_
DESCRIPTION
Token
Required
Valid Values
P_LEDGER
Yes
Legal Entity
P_LEGAL_ENTITY
No
Yes
From
P_PERIOD_FROM
To
P_PERIOD_TO
No
From
P_GL_DATE_FROM
Parameter
Token
Required
Valid Values
To
P_GL_DATE_TO
Balance Type
P_BALANCE_TYPE
No
Actual
Encumbrance
Budget
Budget
P_BUDGET_NAME
No
Encumbrance Type
P_ENCUMBRANCE_
TYPE
No
Balance Side
P_BALANCE_SIDE
No
Debit
Credit
No
From
P_AMOUNT_FROM
To
P_AMOUNT_TO
Parameter
Token
Required
Valid Values
Balancing Segment
[From, To]
No
From
P_BALANCING_SEG
MENT_FROM
To
P_BALANCING_SEG
MENT_TO
Natural Account
Segment [From, To]
No
From
P_ACCOUNT_SEGM
ENT_FROM
To
P_ACCOUNT_SEGM
ENT_TO
Accounting Flexfield
[From, To]
No
From
P_ACCOUNTING_F
LEXFIELD _FROM
Yes
To
P_ACCOUNTING_F
LEXFIELD_ TO
Yes
Parameter
Token
Required
Valid Values
P_INCLUDE_ZERO_
AMOUNT_BALANC
ES
No
P_INCLUDE_ZERO_
AMOUNT_LINES
No
Include User
Transaction
Identifiers
P_INCLUDE_USER_
TRX_IDENTIFIERS
No
P_INCLUDE_TAX
DETAILS
No
P_INCLUDE_LEGAL
_ENTITY_INFO
No
Account Analysis Report Ledger and General Ledger Balance Information Data Elements
Field Name
Descriptions
Ledger ID
LEDGER_ID
LEDGER_SHORT_NAME
Ledger Description
LEDGER_DESCRIPTION
Ledger Name
LEDGER_NAME
Ledger Currency
LEDGER_CURRENCY
Period Year
PERIOD_YEAR
Period Number
PERIOD_NUMBER
Period Name
PERIOD_NAME
PERIOD_START_DATE
PERIOD_END_DATE
BALANCE_TYPE_CODE
BALANCE_TYPE
Budget Name
BUDGET_NAME
Field Name
Descriptions
Encumbrance Type
ENCUMBRANCE_TYPE
BEGIN_BALANCE_DR
BEGIN_BALANCE_CR
Period Activity Dr
PERIOD_NET_DR
Period Activity Cr
PERIOD_NET_CR
Code Combination Id
CODE_COMBINATION_ID
Accounting Code
Combination
ACCOUNTING_CODE_CO
MBINATION (concatenated
descriptions)
Code Combination
Description (concatenated
descriptions)
CODE_COMBINATION_DES
CRIPTION
CONTROL_ACCOUNT_FLA
G
CONTROL_ACCOUNT
Balancing Segment
BALANCING_SEGMENT
Balancing Segment
Description
BALANCING_SEGMENT_D
ESCRIPTION
Natural Account
NATURAL_ACCOUNT
Field Name
Descriptions
NATURAL_ACCOUNT_DES
CRIPTION
Cost Center
COST_CENTER
COST_CENTER_DESCRIPTI
ON
Management Segment
MANAGEMENT_SEGMENT
Management Segment
Description
MANAGEMENT_SEGMENT
_DESCRIPTION
Inter-company Segment
INTERCOMPANY_SEGMEN
T
Inter-company Segment
Description
INTERCOMPANY_SEGMEN
T_DESCRIPTION
BEGIN_RUNNING_TOTAL_
DR
BEGIN_RUNNING_TOTAL_
CR
END_RUNNING_TOTAL_D
R
Field Name
Descriptions
END_RUNNING_TOTAL_C
R
Description
GL Date
GL_DATE
Transaction Created by
CREATED_BY
Creation Date
CREATION_DATE
LAST_UPDATE_DATE
GL Transfer Date
GL_TRANSFER_DATE
Reference Date
REFERENCE_DATE
Completed Date
COMPLETED_DATE
Transaction Number
TRANSACTION_NUMBER
Transaction Date
TRANSACTION_DATE
ACCOUNTING_SEQUENCE
_NAME
ACCOUNTING_SEQUENCE
_VERSION
Field Name
Description
Accounting Sequence
Number
ACCOUNTING_SEQUENCE
_NUMBER
REPORTING_SEQUENCE_N
AME
REPORTING_SEQUENCE_V
ERSION
REPORTING_SEQUENCE_N
UMBER
DOCUMENT_CATEGORY
DOCUMENT_SEQUENCE_N
AME
DOCUMENT_SEQUENCE_N
UMBER
Application Id
APPLICATION_ID
Application Name
APPLICATION_NAME
Header Id
HEADER_ID
Header Description
HEADER_DESCRIPTION
FUND_STATUS
JE_CATEGORY_NAME
Field Name
Description
JE_SOURCE_NAME
Event Id
EVENT_ID
Internal identifier of
accounting event that
originated the journal entry
Event Date
EVENT_DATE
Event Number
EVENT_NUMBER
EVENT_CLASS_CODE
EVENT_CLASS_NAME
EVENT_TYPE_CODE
EVENT_TYPE_NAME
USER_TRX_IDENTIFIER_NA
ME_1 (to 10)
Additional transaction
information for identifying
the transaction
USER_TRX_IDENTIFIER_VA
LUE_1 (to 10)
Additional transaction
information for identifying
the transaction
Batch Name
GL_BATCH_NAME
Posted Date
POSTED_DATE
Field Name
Description
GL Journal Name
GL_JE_NAME
GL Line Number
GL_LINE_NUMBER
Line Number
LINE_NUMBER
ACCOUNTING_CLASS_CO
DE
Accounting Class
ACCOUNTING_CLASS_NA
ME
Line Description
LINE_DESCRIPTION
Entered Currency
ENTERED_CURRENCY
Conversion Rate
CONVERSION_RATE
CONVERSION
_RATE_DATE
CONVERSION
_RATE_TYPE_CODE
CONVERSION_RATE_TYPE
Entered Debit
ENTERED_DR
Entered Credit
ENTERED_CR
Field Name
Description
UNROUNDED_ACCOUNTE
D_DR
UNROUNDED_ACCOUNTE
D_CR
Accounted Debit
ACCOUNTED_DR
Accounted Credit
ACCOUNTED_CR
Statistical Amount
STATISTICAL_AMOUNT
Reconciliation Reference
RECONCILIATION_REFERE
NCE
Attribute Category
ATTRIBUTE_CATEGORY
PARTY_TYPE_CODE
PARTY_TYPE
PARTY_NUMBER
PARTY_NAME
PARTY_TAXPAYER_ID
Field Name
Description
PARTY_TAX_REGISTRATIO
N_NUMBER
PARTY_SITE_NUMBER
PARTY_SITE_NAME
PARTY__SITE_TAX_REGIST
RATION_NUMBER
Subledger journal entry lines that add up to the total period activity for each control
account, third party, and third party site
Token
Required
Valid Values
P_LEDGER
Yes
Parameter
Token
Required
Valid Values
P_JE_SOURCE
No
Legal Entity
P_LEGAL_ENTITY
No
Yes
From
P_PERIOD_FROM
To
P_PERIOD_TO
No
From
P_GL_DATE_FROM
To
P_GL_DATE_TO
Parameter
Token
Required
Valid Values
Balance Side
P_BALANCE_SIDE
No
Debit
Credit
No;
requires
Balance
Side
From
P_BALANCE_AMOU
NT_FROM
To
P_BALANCE_AMOU
NT_TO
P_PARTY_TYPE
No
P_PARTY_NAME
No
P_PARTY_SITE
No;
requires
Third Party
Name
No
From
P_PARTY_NUMBER
_FROM
Parameter
Token
Required
Valid Values
To
P_PARTY_NUMBER
_TO
Balancing Segment
[From, To]
No
From
P_BALANCING_SEG
MENT_FROM
To
P_BALANCING_SEG
MENT_TO
Natural Account
Segment [From, To]
No
From
P_ACCOUNT_SEGM
ENT_FROM
To
P_ACCOUNT_SEGM
ENT_TO
Accounting Flexfield
[From, To]
No
From
P_ACCOUNTING_F
LEXFIELD _FROM
Yes
To
P_ACCOUNTING_F
LEXFIELD_ TO
Yes
Parameter
Token
Required
Valid Values
P_INCLUDE_ZERO_
AMOUNT_BALANC
ES
No
Include User
Transaction
Identifiers
P_INCLUDE_USER_
TRX_IDENTIFIERS
No
P_INCLUDE_TAX
DETAILS
No
P_INCLUDE_LEGAL
_ENTITY_INFO
No
report templates.
Description
Ledger Id
LEDGER_ID
Field Name
Description
LEDGER_SHORT_NAME
Ledger Description
LEDGER_DESCRIPTION
Ledger Name
LEDGER_NAME
Ledger Currency
LEDGER_CURRENCY
PARTY_TYPE_CODE
PARTY_TYPE
Third Party Id
PARTY_ID
PARTY_NUMBER
PARTY_NAME
PARTY_TYPE_TAXPAYER_I
D
PARTY_TAX_REGISTRATIO
N_NUMBER
PARTY_ADDRESS_1
PARTY_ADDRESS_2
PARTY_ADDRESS_3
PARTY_ADDRESS_4
Field Name
Description
PARTY_CITY
PARTY_ZIP_CODE
PARTY_STATE
PARTY_PROVINCE
PARTY_COUNTRY
PARTY_COUNTY
PARTY_SITE_ID
PARTY_SITE_NUMBER
PARTY_SITE_NAME
PARTY__SITE_TAX_REGIST
RATION_NUMBER
PARTY_SITE_ADDRESS_LIN
E_1
PARTY_SITE_ADDRESS_LIN
E_2
PARTY_SITE_ADDRESS_LIN
E_3
PARTY_SITE_ADDRESS_LIN
E_4
PARTY_SITE_CITY
PARTY_SITE_ZIP_CODE
Field Name
Description
PARTY_SITE_STATE
PARTY_SITE_PROVINCE
PARTY_SITE_COUNTRY
PARTY_SITE_COUNTY
Application Id
APPLICATION_ID
Application Name
APPLICATION_NAME
JE_SOURCE_NAME
Period Year
PERIOD_YEAR
Period Number
PERIOD_NUMBER
Period Name
PERIOD_NAME
PERIOD_START_DATE
PERIOD_END_DATE
Beginning Balance Dr
BEGIN_BALANCE_DR
Beginning Balance Cr
BEGIN_BALANCE_CR
Period Activity Dr
PERIOD_NET_DR
Period Activity Cr
PERIOD_NET_CR
Field Name
Description
BEGIN_DRAFT_BALANCE_
DR
BEGIN_DRAFT_BALANCE_
CR
PERIOD_DRAFT_NET_DR
PERIOD_DRAFT_NET_CR
Code Combination Id
CODE_COMBINATION_ID
Accounting Code
Combination
ACCOUNTING_CODE_CO
MBINATION (concatenated
values)
Code Combination
Description
CODE_COMBINATION_DES
CRIPTION (concatenated
descriptions)
Concatenated descriptions of
the accounting code
combination for the journal
entry line
Balancing Segment
BALANCING_SEGMENT
Balancing Segment
Description
BALANCING_SEGMENT_D
ESCRIPTION
Natural Account
NATURAL_ACCOUNT
NATURAL_ACCOUNT_DES
CRIPTION
Cost Center
COST_CENTER
COST_CENTER_DESCRIPTI
ON
Field Name
Description
Management Segment
MANAGEMENT_SEGMENT
Management Segment
Description
MANAGEMENT_SEGMENT
_DESCRIPTION
Inter-company Segment
INTERCOMPANY_SEGMEN
T
Inter-company Segment
Description
INTERCOMPANY_SEGMEN
T_DESCRIPTION
BEGIN_RUNNING_TOTAL_
DR
BEGIN_RUNNING_TOTAL_
CR
END_RUNNING_TOTAL_D
R
END_RUNNING_TOTAL_C
R
Third Party Balances Report Journal Entry Header and Line Information
Field Name
Source
GL Date
GL_DATE
Transaction Created by
CREATED_BY
Creation Date
CREATION_DATE
LAST_UPDATE_DATE
GL Transfer Date
GL_TRANSFER_DATE
Reference Date
REFERENCE_DATE
Completed Date
COMPLETED_DATE
Transaction Number
TRANSACTION_NUMBER
Transaction Date
TRANSACTION_DATE
ACCOUNTING_SEQUENCE
_NAME
ACCOUNTING_SEQUENCE
_VERSION
Accounting Sequence
Number
ACCOUNTING_SEQUENCE
_NUMBER
REPORTING_SEQUENCE_N
AME
Field Name
Source
REPORTING_SEQUENCE_V
ERSION
REPORTING_SEQUENCE_N
UMBER
DOCUMENT_SEQUENCE_N
AME
DOCUMENT_SEQUENCE_N
UMBER
Header Id
HEADER_ID
Header Description
HEADER_DESCRIPTION
FUND_STATUS
JE_CATEGORY_NAME
Event Id
EVENT_ID
Event Date
EVENT_DATE
Event Number
EVENT_NUMBER
EVENT_CLASS_CODE
Field Name
Source
EVENT_CLASS_NAME
EVENT_TYPE_CODE
EVENT_TYPE_NAME
USER_TRX_IDENTIFIER_NA
ME_1 (to 10)
Additional transaction
information for identifying
the transaction
USER_TRX_IDENTIFIER_VA
LUE_1 (to 10)
Additional transaction
information for identifying
the transaction
JOURNAL_ENTRY_STATUS
Transfer to GL Status
TRANSFER_TO_GL_STATUS
GL Batch Status
GL_BATCH_STATUS
Posted Date
POSTED_DATE
Line Number
LINE_NUMBER
ACCOUNTING_CLASS_CO
DE
Field Name
Source
Accounting Class
ACCOUNTING_CLASS_NA
ME
Line Description
LINE_DESCRIPTION
Entered Currency
ENTERED_CURRENCY
Conversion Rate
CONVERSION_RATE
CONVERSION
_RATE_DATE
CONVERSION
_RATE_TYPE_CODE
CONVERSION_RATE_TYPE
Entered Debit
ENTERED_DR
Entered Credit
ENTERED_CR
UNROUNDED_ACCOUNTE
D_DR
UNROUNDED_ACCOUNTE
D_CR
Accounted Debit
ACCOUNTED_DR
Accounted Credit
ACCOUNTED_CR
Statistical Amount
STATISTICAL_AMOUNT
Reconciliation Reference
RECONCILIATION_REFERE
NCE
Field Name
Source
Attribute Category
ATTRIBUTE_CATEGORY
Multiperiod Accounting and Accrual Reversal Report: Created when user runs the
Create Accounting program and displays accrual, recognition, and accrual reversal
journal entries
Multiperiod Accounting Report (summary or detail): Created when user runs the
Complete Multiperiod Accounting program and displays recognition and accrual
reversal entries processed by the program
Description
Source Application
SOURCE_APPLICATION
Application
APPLICATION
Field Name
Description
End Date
END_DATE
Process Category
PROCESS_CATEGORY
ACCOUNTING_REPORT_LE
VEL
Create Accounting
CREATE_ACCOUNTING
Errors Only
ERRORS_ONLY
TRANSFER_TO_GENERAL_
LEDGER
POST_IN_GENERAL_LEDGE
R
Field Name
Description
GENERAL_LEDGER_BATC
H_NAME
Multiperiod Accounting and Accrual Reversal Report Journal Entry Summary Data
Elements
Field Name
Description
Event Class
EVENT_CLASS
Number of Documents
NUMBER_OF_DOCUMENTS
Number of documents
processed for the event class
Ledger
LEDGER
Type
JOURNAL_ENTRY_TYPE
Multiperiod Accrual
Recognition
Accrual
Accrual Reversal
Processed
JOURNAL_ENTRIES_PROCE
SSED
In Error
JOURNAL_ENTRIES_IN_ER
ROR
Multiperiod Accounting and Accrual Reversal Report Transfer to General Ledger Data
Elements
Field Name
Description
Ledger
LEDGER
Type
JOURNAL_ENTRY_TYPE
Count
JOURNAL_ENTRIES_TRANS
FERRED
Multiperiod Accrual
Recognition
Accrual
Accrual Reversal
Multiperiod Accounting and Accrual Reversal Report General Error Data Elements
Data Source Element
Template Field
Description
Error Number
G_ERROR_NUMBER
Error Message
G_ERROR_MESSAGE
Error description
Multiperiod Accounting and Accrual Reversal Report Event Level Data Elements
Field Name
Description
Event Class
EVENT_CLASS
Event Type
EVENT_TYPE
Field Name
Description
Event Number
EVENT_NUMBER
User-oriented number to
identify the events of a
document
Event Date
EVENT_DATE
USER_TRX_IDENTIFIER_PR
OMPT_XX
USER_TRX_IDENTIFIER_VA
LUE_XX
Multiperiod Accounting and Accrual Reversal Report Journal Header Data Elements
Field Name
Description
Ledger
LEDGER
GL Date
GL_DATE
Ledger Currency
LEDGER_CURRENCY
Application Accounting
Definition
APPLICATION_ACCOUNTI
NG_DEFINITION
Application accounting
definition name used to create
accrual journal entry
Application Accounting
Definition Version
AAD_VERSION
Application accounting
definition version of accrual
journal entry
JOURNAL_ENTRY_DESCRIP
TION
Field Name
Description
Type
JOURNAL_ENTRY_TYPE
Multiperiod Accrual
Recognition
Accrual
Accrual Reversal
JOURNAL_ENTRY_STATUS
ACCOUNTING_SEQUENCE
_NAME
ACCOUNTING_SEQUENCE
_VERSION
Accounting Sequence
Number
ACCOUNTING_SEQUENCE
_NUMBER
Multiperiod Accounting and Accrual Reversal Report Journal Entry Line Data Elements
Field Name
Description
Line Number
LINE_NUMBER
Account
ACCOUNT
Currency
CURRENCY
Entered Debit
ENTERED_DEBIT
Field Name
Description
Entered Credit
ENTERED_CREDIT
Accounted Debit
ACCOUNTED_DEBIT
Accounted Credit
ACCOUNTED_CREDIT
Description
Line Number
LINE_NUMBER
Error Number
ERROR_NUMBER
Error Message
ERROR_MESSAGE
Error description
Description
Application
APPLICATION
End Date
END_DATE
Field Name
Description
Process Category
PROCESS_CATEGORY
Errors Only
ERRORS_ONLY
TRANSFER_TO_GENERAL_
LEDGER
POST_IN_GENERAL_LEDGE
R
GENERAL_LEDGER_BATC
H_NAME
Description
Event Class
EVENT_CLASS
Number of Documents
NUMBER_OF_DOCUMENTS
Number of documents
processed for the event class
Ledger
LEDGER
Field Name
Description
Type
JOURNAL_ENTRY_TYPE
Recognition
Accrual Reversal
Processed
JOURNAL_ENTRIES_PROCE
SSED
In Error
JOURNAL_ENTRIES_IN_ER
ROR
Description
Ledger
LEDGER
Type
JOURNAL_ENTRY_TYPE
Count
JOURNAL_ENTRIES_TRANS
FERRED
Recognition
Accrual Reversal
Description
Error Number
G_ERROR_NUMBER
Error Message
G_ERROR_MESSAGE
Error description
Description
Event Class
EVENT_CLASS
Event Type
EVENT_TYPE
Event Number
EVENT_NUMBER
Event Date
EVENT_DATE
USER_TRX_IDENTIFIER_PR
OMPT_XX
USER_TRX_IDENTIFIER_VA
LUE_XX
Description
Ledger
LEDGER
GL Date
GL_DATE
Ledger Currency
LEDGER_CURRENCY
Application Accounting
Definition
APPLICATION_ACCOUNTI
NG_DEFINITION
Application accounting
definition name used to create
journal entry
Field Name
Description
Application Accounting
Definition Version
AAD_VERSION
Application accounting
definition version
Description
DESCRIPTION
Type
JOURNAL_ENTRY_TYPE
Recognition
Accrual Reversal
JOURNAL_ENTRY_STATUS
ACCOUNTING_SEQUENCE
_NAME
ACCOUNTING_SEQUENCE
_VERSION
Accounting Sequence
Number
ACCOUNTING_SEQUENCE
_NUMBER
Description
Line Number
LINE_NUMBER
Account
ACCOUNT
Currency
CURRENCY
Entered Debit
ENTERED_DEBIT
Field Name
Description
Entered Credit
ENTERED_CREDIT
Accounted Debit
ACCOUNTED_DEBIT
Accounted Credit
ACCOUNTED_CREDIT
Description
Line Number
LINE_NUMBER
Error Number
ERROR_NUMBER
Error Message
ERROR_MESSAGE
Error description
Description
Application
APPLICATION
End Date
END_DATE
Field Name
Description
Process Category
PROCESS_CATEGORY
Errors Only
ERRORS_ONLY
TRANSFER_TO_GENERAL_
LEDGER
POST_IN_GENERAL_LEDGE
R
GENERAL_LEDGER_BATC
H_NAME
Description
Event Class
EVENT_CLASS
Number of Documents
NUMBER_OF_DOCUMENTS
Number of documents
processed for the event class
Ledger
LEDGER
Field Name
Description
Type
JOURNAL_ENTRY_TYPE
Recognition
Accrual Reversal
Processed
JOURNAL_ENTRIES_PROCE
SSED
In Error
JOURNAL_ENTRIES_IN_ER
ROR
Description
Ledger
LEDGER
Type
JOURNAL_ENTRY_TYPE
Count
JOURNAL_ENTRIES_TRANS
FERRED
Recognition
Accrual Reversal
Description
Error Number
G_ERROR_NUMBER
Error Message
G_ERROR_MESSAGE
Error description
Description
Ledger
LEDGER
GL Date
GL_DATE
Ledger Currency
LEDGER_CURRENCY
Application Accounting
Definition
APPLICATION_ACCOUNTI
NG_DEFINITION
Application accounting
definition name used to create
journal entry
Application Accounting
Definition Version
AAD_VERSION
Application accounting
definition version
Description
DESCRIPTION
Type
JOURNAL_ENTRY_TYPE
JOURNAL_ENTRY_STATUS
Recognition
Accrual Reversal
Description
Line Number
LINE_NUMBER
Account
ACCOUNT
Currency
CURRENCY
Entered Debit
ENTERED_DEBIT
Field Name
Description
Entered Credit
ENTERED_CREDIT
Accounted Debit
ACCOUNTED_DEBIT
Accounted Credit
ACCOUNTED_CREDIT
Description
Line Number
LINE_NUMBER
Error Number
ERROR_NUMBER
Error Message
ERROR_MESSAGE
Error description
Required
Valid Values
Yes
Period From
Yes
Period To
Yes
Journal Source
No
Event Class
Journal Category
Description
Event Date
EVENT_DATE
Transaction Created by
CREATED_BY
Creation Date
CREATION_DATE
LAST_UPDATE_DATE
User Name
USER_NAME
Transaction Number
TRANSACTION_NUMBE
R
Transaction Date
TRANSACTION_DATE
Application Id
APPLICATION_ID
Ledger ID
LEDGER_ID
LEDGER_SHORT_NAME
Ledger Description
LEDGER_DESCRIPTION
Ledger Name
LEDGER_NAME
Field Name
Description
Ledger Currency
LEDGER_CURRENCY
Status
PRINT_STATUS
On Hold Flag
ON_HOLD_FLAG
On Hold
ON_HOLD_FLAG
JOURNAL_CATEGORY_
NAME
USER_JE_CATEGORY_N
AME
JOURNAL_SOURCE
USER_JE_SOURCE
Event Id
EVENT_ID
Event Date
ACCOUNTING_DATE
Event Number
EVENT_NUMBER
EVENT_CLASS_CODE
Field Name
Description
EVENT_CLASS_NAME
EVENT_TYPE_CODE
EVENT_TYPE_NAME
User Transaction
Identifier Name
USER_TRX_IDENTIFIER_
NAME_1 (to 10)
User Transaction
Identifier Value
USER_TRX_IDENTIFIER_
VALUE_1 (to 10)
Balance Type
BALANCE_TYPE
BALANCE_TYPE_CODE
10
Open Account Balances Listing
Create open account balance definitions in the Create Open Account Balances
Listing Definition page.
See: Open Account Balance Listing Definitions, page 10-2
Optionally, to update Open Account Balances Listing processing options, navigate
to the Update Open Account Balances Listing Processing Options page by clicking
Processing Options in the Open Account Balances Listing Definition Search page.
For each ledger used for open account balance reporting, Subledger Accounting
defaults the number of processors to 1 and the processing unit size to 5000. Change
these defaults to improve the performance of the Open Account Balances Listing
Data Manager.
Note: A processing unit is the number of transactions processed by
2.
3.
4.
Prerequisites
Define a ledger.
See: Primary Ledger Setup Steps, Oracle Financials Implementation Guide
Create journal entries and transfer to General Ledger using the Create Accounting
program.
See: Create Accounting Program, page 3-1
When the ledger is defined, the details region displays data according to the value
selected in the Defined By field.
Selected Fields in the Subledger Open Account Balances Listing Definitions Page
Field Name
Description
Code
Defined By
Journal Source
Balance Side
Enabled
Segment
Value From/Value To
Code
Ledger
Defined By
Journal Source
Balance Side
In the Submit Request window, select Open Account Balance Data Manager.
2.
Description
Ledger
Report Definition
General Ledger. Users can view the report in detail or summary mode.
This report displays information that originates from subledger journal entries only.
Journal entries created manually in General Ledger or anywhere outside of Subledger
Accounting are not included. Only transactions with nonzero outstanding balances are
displayed.
Subledger Accounting seeds the following templates:
Submission Parameters
Open Account Balances Listing Submission Parameters
Parameter
Required
Valid Values
Report Definition
Yes
Parameter
Required
Valid Values
Journal Source
No
Start Date
Yes
As Of Date
No
No
Yes
Yes
Account From/To
No
Account Balance
Yes
template.
Required
Valid Values
Security Parameter
No
Valuation Method
No
No validation
No
No validation
No
No validation
Custom Parameter 1
No
No validation
Custom Parameter 2
No
No validation
Custom Parameter 3
No
No Validation
open account balance templates. For the fields not included on the
seeded templates, the field name column shows the suggested label for
the field.
Source / Description
Account
ACCOUNT
GL Balance
GL_BALANCE
Source / Description
CODE_COMBINATION_ID
BALANCING_SEGMENT_V
ALUE
BALANCING_SEGMENT_D
ESC
NATURAL_ACCOUNT_SEG
MENT_VALUE
NATURAL_ACCOUNT_SEG
MENT_DESC
COST_CENTER_SEGMENT_
VALUE
COST_CENTER_SEGMENT_
DESCR
MANAGEMENT_SEGMENT
_VALUE
MANAGEMENT_SEGMENT
_DESC
INTERCOMPANY_SEGMEN
T_VALUE
INTERCOMPANY_SEGMEN
T_DESC
LEDGER_ID
Ledger
LEDGER_NAME
Ledger name
LEDGER_SHORT_NAME
Source / Description
Curr
LEDGER_CURRENCY_COD
E
Third Party
THIRD_PARTY_NAME
THIRD_PARTY_NUMBER
THIRD_PARTY_TYPE
THIRD_PARTY_TYPE_CODE
THIRD_PARTY_SITE_NAME
SOURCE_ENTITY_ID
SOURCE_TRX_APPLICATIO
N_ID
SOURCE_TRX_APPLICATIO
N_NAME
Transaction Type
SOURCE_TRX_TYPE
Transaction Number
SOURCE_TRX_NUMBER
Date
SOURCE_TRX_GL_DATE
SOURCE_TRX_CURR
SRC_ENTERED_UNROUND
ED_ORIG_AMT
Source / Description
SRC_ENTERED_UNROUND
ED_REM_AMT
Unrounded remaining
amount of the source
transaction in the entered
currency
SRC_ENTERED_ROUNDED_
ORIG_AMT
SRC_ENTERED_ROUNDED_
REM_AMT
SRC_ACCTD_UNROUNDED
_ORIG_AMT
SRC_ACCTD_UNROUNDED
_REM_AMT
Unrounded remaining
amount of the source
transaction in the ledger
currency
Original Amount
SRC_ACCTD_ROUNDED_O
RIG_AMT
Remaining Amount
SRC_ACCTD_ROUNDED_R
EM_AMT
APPLIED_TO_APPLICATIO
N_ID
USER_TRX_IDENTIFIER_NA
ME_1
USER_TRX_IDENTIFIER_NA
ME_2
USER_TRX_IDENTIFIER_NA
ME_3
Source / Description
USER_TRX_IDENTIFIER_NA
ME_4
USER_TRX_IDENTIFIER_NA
ME_5
USER_TRX_IDENTIFIER_NA
ME_6
USER_TRX_IDENTIFIER_NA
ME_7
USER_TRX_IDENTIFIER_NA
ME_8
USER_TRX_IDENTIFIER_NA
ME_9
USER_TRX_IDENTIFIER_NA
ME_10
USER_TRX_IDENTIFIER_VA
LUE_1
USER_TRX_IDENTIFIER_VA
LUE_2
USER_TRX_IDENTIFIER_VA
LUE_3
USER_TRX_IDENTIFIER_VA
LUE_4
USER_TRX_IDENTIFIER_VA
LUE_5
USER_TRX_IDENTIFIER_VA
LUE_6
USER_TRX_IDENTIFIER_VA
LUE_7
Source / Description
USER_TRX_IDENTIFIER_VA
LUE_8
USER_TRX_IDENTIFIER_VA
LUE_9
USER_TRX_IDENTIFIER_VA
LUE_10
APPLIED_THIRD_PARTY_N
AME
APPLIED_THIRD_PARTY_N
UMBER
APPLIED_THIRD_PARTY_T
YPE
APPLIED_THIRD_PARTY_T
YPE_CODE
APPLIED_THIRD_PARTY_SI
TE_NAME
APPLIED_TO_ENTITY_ID
APPLIED_TRX_APPLICATIO
N_ID
Application
APPLIED_TRX_APPLICATIO
N_NAME
Type
APPLIED_TRX_TYPE
Number
APPLIED_TRX_NUMBER
Date
APPLIED_TRX_GL_DATE
APPLIED_TRX_CURR
Source / Description
APPLIED_ENTERED_UNRO
UNDED_AMT
APPLIED
_ENTERED_ROUNDED_AM
T
APPLIED
_ACCTD_UNROUNDED_A
MT
Applied Amount
APPLIED
_ACCTD_ROUNDED_AMT
APPLIED_USER_TRX_IDEN
TIFIER_NAME_1
APPLIED_USER_TRX_IDEN
TIFIER_NAME_2
APPLIED_USER_TRX_IDEN
TIFIER_NAME_3
APPLIED_USER_TRX_IDEN
TIFIER_NAME_4
APPLIED_USER_TRX_IDEN
TIFIER_NAME_5
APPLIED_USER_TRX_IDEN
TIFIER_NAME_6
APPLIED_USER_TRX_IDEN
TIFIER_NAME_7
APPLIED_USER_TRX_IDEN
TIFIER_NAME_8
APPLIED_USER_TRX_IDEN
TIFIER_NAME_9
Source / Description
APPLIED_USER_TRX_IDEN
TIFIER_NAME_10
APPLIED_USER_TRX_IDEN
TIFIER_VALUE_1
APPLIED_USER_TRX_IDEN
TIFIER_VALUE_2
APPLIED_USER_TRX_IDEN
TIFIER_VALUE_3
APPLIED_USER_TRX_IDEN
TIFIER_VALUE_4
APPLIED_USER_TRX_IDEN
TIFIER_VALUE_5
APPLIED_USER_TRX_IDEN
TIFIER_VALUE_6
APPLIED_USER_TRX_IDEN
TIFIER_VALUE_7
APPLIED_USER_TRX_IDEN
TIFIER_VALUE_8
APPLIED_USER_TRX_IDEN
TIFIER_VALUE_9
APPLIED_USER_TRX_IDEN
TIFIER_VALUE_10
11
Transaction Account Builder
accounts may not be the ones that appear on the subledger journal
entries since these are generated by the Create Accounting program
based on the application accounting definitions.
If the application does not allow modification of the default accounts for a transaction
before it is accounted, you must use the AMB.
See: Accounting Methods Builder Introduction, page 2-1
Developers can assign sources to transaction account types. Developers and users can
use these sources to derive accounts for a transaction account type to create a
transaction account definition. For example, while the bank asset account can be used to
derive the cash account for a payment, it might not be useful when deriving the invoice
price variance account for a matched invoice. Consequently, the source for the bank
asset account is not assigned to the transaction account type for the invoice price
variance.
Examples of possible transaction account types for Receivables transactions are
Revenue, Tax, Receivable, Freight, Unearned Revenue, Unbilled Receivable, and Bills
Receivable. Examples of transaction account receipts are Cash, Unidentified Receipts,
Unapplied Receipts, On Account Receipts, Earned Discounts, Unearned Discounts,
Remitted Receipts, and Factored Receipts.
Developers and users can assign account derivation rules to transaction account types
The transaction and the accounting chart of accounts are both null or they are the
same.
All sources used by the account derivation rule are available to the transaction
account type to which it is assigned.
2.
3.
To make the transaction account definition available for assigning as part of the
application setup, select Yes in the Enabled drop-down list.
4.
5.
In the Account Derivation Rule field, enter the rule you want to use to derive the
value for the segment entered in the Segment field.
The list of values for this field includes all account derivation rules that:
Segment
Rule Name
Null
All Segments
Null
Accounting Flexfield
Qualifiers
Chart of Accounts
Segment
Rule Name
Not Null
All Segments
Not Null
Segments
7.
To create a new account derivation rule assignment for the transaction account
type, in the Assign Rule field, click the icon.
Step 5: Using the Transaction Accounts as Default Accounts for Accounting Methods
Builder
Use the accounts derived by TAB to generate subledger journal entries provided that
the sources for these accounts are defined by the developers. To do this, complete the
following steps:
1.
2.
Create account derivation rules using the sources that correspond to the accounts
generated by TAB.
3.
A
Oracle Subledger Accounting Navigation
Paths
Navigation Paths
This table lists each Subledger Accounting window and corresponding navigation path,
although your system administrator may have customized your navigator.
Navigation Paths
Window Name
Navigation Path
Window Name
Navigation Path
Accounting Events
Window Name
Navigation Path
Custom Sources
Window Name
Navigation Path
Entities
Window Name
Navigation Path
Header Assignments
Window Name
Navigation Path
Mapping Sets
Multiperiod Accounting
Window Name
Navigation Path
Post-Accounting Programs
Process Categories
Source Assignments
Sources
Subledger Applications
Window Name
Navigation Path
Supporting References
B
Oracle Subledger Accounting Profile
Options and Profile Option Categories
Oracle Subledger Accounting Profile Options and Profile Option Categories B-1
The Default column displays the default profile option value in italics or No Default
if none exists.
The User Access column indicates whether you can view or update the profile
option.
View Only: You can view the profile option but cannot change it.
Defaul
t
User
Access
System
Administration
: User
System
Administration
:
Responsibility
System
Administration:
Application
System
Administration
: Site
SLA: Accounting
Methods Builder
Context, page B3
Default
View
Only
Update
Update
Update
Update
Debug Category
This category includes profile options that enable debugging and diagnostic features.
Oracle Subledger Accounting Profile Options and Profile Option Categories B-3
Debug Category
Profile Option
Defaul
t
User
Access
System
Administration
: User
System
Administratio
n:
Responsibility
System
Administration:
Application
System
Administration:
Site
SLA: Display
Timestamp on
Trace, page B-5
No
View
Only
Update
Update
Update
Update
SLA: Enable
Diagnostics, page
B-5
No
View
Only
Update
Update
Update
Update
SLA: Enable
PL/SQL Profiler,
page B-5
No
View
Only
Update
Update
Update
Update
SLA: Enable
Trace, page B-5
No
View
Only
Update
Update
Update
Update
No
View
Only
Update
Update
Update
Update
Yes
View
Only
Update
Update
Update
Update
No
View
Only
Update
Update
Update
Update
SLA: Oracle
Forms Trace
Mode, page B-6
File
View
Only
Update
Update
Update
Update
Tracer
View
Only
Update
Update
Update
Update
No
Default
View
Only
Update
Update
Update
Update
Profile Option
Defaul
t
User
Access
System
Administration
: User
System
Administratio
n:
Responsibility
System
Administration:
Application
System
Administration:
Site
No
Default
View
Only
Update
Update
Update
Update
100
View
Only
Update
Update
Update
Update
SLA: Trace
Timeout, page B6
600
View
Only
Update
Update
Update
Update
Oracle Subledger Accounting Profile Options and Profile Option Categories B-5
Deployment Category
This category includes profile options set up to run the application.
Deployment Category
Profile Option
Default
User
Access
System
Administration:
User
System
Administration
:
Responsibility
System
Administratio
n: Application
System
Administration:
Site
SLA: Disable
Journal Import,
page B-7
No
No
Access
View Only
View Only
View Only
Update
Profile Option
Default
User
Access
System
Administration:
User
System
Administration
:
Responsibility
System
Administratio
n: Application
System
Administration:
Site
No
Access
View Only
View Only
View Only
Update
Security Category
This category includes profile options related to security.
Security Category
Profile Option
Default
User
Access
System
Administration
: User
System
Administration
:
Responsibility
System
Administration
: Application
System
Administration:
Site
SLA: Additional
Data Access Set,
page B-8
No
Default
View
Only
Update
Update
Update
Update
SLA: Allow
Reports Journal
Source Override,
page B-8
No
View
Only
Update
No Access
Update
Update
View
Only
No Access
Update
Update
Update
No
Oracle Subledger Accounting Profile Options and Profile Option Categories B-7
Profile Option
Default
User
Access
System
Administration
: User
System
Administration
:
Responsibility
System
Administration
: Application
System
Administration:
Site
SLA: Enable
Subledger
Transaction
Security in GL,
page B-9
No
View
Only
No Access
Update
Update
Update
Enable this option to change the Journal Source parameter during report submission. If
the option is set to No, then you cannot change the value defaulted during report
submission.
Oracle Subledger Accounting Profile Options and Profile Option Categories B-9
C
Subledger Journal Entry Definition
Actual and encumbrance journal entries must have at least two journal entry lines.
See: Subledger Journal Entry Line Validation, page C-9
Actual and encumbrance journal entries must be balanced in both entered and
ledger currencies. A journal entry need not be balanced if it is a STAT currency
entry.
In addition, actual and encumbrance entries must be balanced by balancing
segment.
Encumbrance journal entries can only be created for ledgers that are enabled for
encumbrance accounting.
The actual journal entry must be created in an open or future open GL period.
Similarly, a budget journal entry must be created in an open budget year and an
encumbrance journal entry created in an open encumbrance year.
All the lines on a subledger journal entry must have valid accounts.
Budget journal entries are not created for reporting currencies and secondary
ledgers.
2. Application (APPLICATION_ID)
A subledger journal entry belongs to one and only one subledger application. The
application identifier is the standard identifier for each Oracle e-Business Suite
application or custom application.
3. Ledger (LEDGER_ID)
A subledger journal entry belongs to one and only one ledger. The ledger identifier is
the standard identifier assigned to the ledger by the Accounting Setup Manager (ASM).
6. GL Date (ACCOUNTING_DATE)
The GL date determines the accounting period (PERIOD_NAME) of the subledger
journal entry and when the entry appears in fiscal reports and queries.
The following rules apply:
For actual journal entries, the GL date must be in an open or future enterable GL
period.
For a budget journal entry, the GL date must in an open budget year.
For a multiperiod journal entry, the GL date may fall in a never opened period. In
this case, the Transfer to GL process does not transfer the journal entry to General
Ledger until the GL period status is changed to either Open or Future Enterable.
timezone differences.
When a subledger journal entry is completed, the reference date must be in an open
or future open accounting period.
The reference date has no time component. It is not subject to considerations related
to timezone differences.
Actual
Budget
Encumbrance
For actual entries, the budget version identifier and encumbrance type identifier are
null.
For budget entries, the budget version identifier is not null, and the encumbrance
type identifier is null.
For encumbrance entries, the encumbrance type identifier is not null, and the
budget version identifier is null.
For manual and upgrade journal entries, users must provide the journal category.
For standard and multiperiod journal entries, the journal category is derived from
the category specified for an event class in the Subledger Accounting Options page
of the Accounting Setups.
Not transferred
Selected to transfer
Transferred
When a subledger journal entry is created and completed, the value of this column is
Not transferred. The Transfer to GL process updates this column when the subledger
journal entry is transferred to General Ledger.
The originating event has no errors. (All other subledger journal entries associated
with the same event are valid.)
All prior events for the same document have been accounted.
Final: The entry status is set to Final when the following conditions are met:
The originating event has no errors. (All other subledger journal entries associated
with the same event are valid.)
All prior events for the same document have been accounted.
Incomplete: The entry status is set to Incomplete when the following condition is met:
The subledger journal entry is incomplete and subject to further changes. This
status is applicable to manual and multiperiod journal entries.
Invalid: The entry status is set to Invalid when the following condition is met:
Invalid Related Entry: The entry status is set to Invalid Related Entry when the
following condition is met:
The subledger journal entry is valid, but one or more of the other subledger journal
entries associated with the same accounting event are invalid.
Standard
Upgrade
Manual
Multiperiod
They are not populated for manual, upgrade, or third party merge entries.
A header description is required for manual journal entries. It is optional for other
journal entry types.
This column is null for manual, third party merge, and upgrade subledger journal
entries.
The budget must exist, it must not be frozen or inactive, and it must be associated
with a ledger.
No budget subledger journal entries are created if it is created with a status or Error.
No encumbrance subledger journal entries are created if any of the above validations
fail.
Passed
Failed
In Progress
This is an optional column. The following rule applies to the funds status code:
If funds checking is enabled for a ledger, then there must be available funds for
each line. If this condition is not met, the status of the subledger journal entry is set
to Invalid and the funds status is set to Failed.
Users are not allowed to complete a manual subledger journal entry with a funds
status Failed.
The Accounting Program checks whether the code combination exists in the
table GL_CODE_COMBINATIONS. The Accounting Program assumes that
compliance with General Ledger cross validation rules has been met by the base
product.
Instead of deriving the account from sources in the transaction objects, the code
combination can also be derived from a constant value specified in an account
derivation rule. In this case, it is also assumed that no General Ledger cross
validation rules are violated.
If dynamic insertion is turned on and the code combination does not exist, then
a new combination is created. In this case, Subledger Accounting calls the
corresponding Applications Object Library APIs, which perform all needed
validations including General Ledger cross validation rules.
For actual and encumbrance type entries, the Allow Posting option for the account
code combination must be enabled.
For budget entries, the Allow Budgeting option for the account code combination
must be enabled.
When using a suspense account, the suspense option must be enabled. (Suspense
accounts are derived from the ledger setup in General Ledger.)
If it is a third party control account, then the party type on subledger application
registration must match the party type on the line.
If it is a third party control account, then the party type on the line must match the
party type on the account.
The user must have write access to the ledger; ledger or balancing segment value;
or ledger or management segment value.
If the account code combination does not exist, a -1 must be stored in the
CODE_COMBINATION_ID column.
For standard and deferred journal entry lines, the attribute value is derived from
the journal line type setup in the AMB.
For manual journal entries, it is derived from the Subledger Accounting options
entered for the ledger in the ASM.
If party type information is provided, then party information must also be provided
and vice versa. If party type information is not provided then party information
must be null and vice versa.
If the journal entry line account is a third party control account, then party
information must be provided.
The party identifier is null if any of the above validations fail. The journal entry is
marked as Invalid if party information is not provided when required.
If party site information is provided, then party information must also be provided.
The party site must be null if any of the other validations fail.
Customers
Suppliers
Since not all subledger products implement Oracle Trading Community Architecture at
the same time, third party identifiers can be identical. It is therefore necessary to
identify them based on third party type code.
If the entered currency is the same as the ledger currency and the accounting class
of the journal line is not Rounding, then entered and accounted amounts must be
the same.
If the entered currency is the same as the ledger currency and the accounting class
of the journal line is not Rounding, then entered and accounted amounts must be
the same.
If the profile option Journals: Mix Statistical and Monetary is set to Yes, then
statistical and monetary amounts can be entered on the same journal entry.
A journal entry is invalid if it contains both statistical and monetary currency lines.
If the currency code is STAT, then the entered amount is the same as the accounted
amount. The statistical amount (STATISTICAL_AMOUNT) is null.
STAT currency and other currencies cannot coexist in a single subledger journal
entry.
STAT currency lines are not created for budget and encumbrance journals.
When the entered and ledger currencies are the same, and the conversion rate and
the conversion rate type are populated, then the conversion rate and conversion
rate type values are ignored and not used.
When the entered currency is different from ledger currency, the conversion
information is not required to be stored in a journal entry line. However, if
conversion information is populated, the following conditions are considered
errors:
The rules described in this section apply to any given subledger journal entry as a
whole. Therefore, these conditions are not evaluated until the journal entry header and
all the journal entry lines are generated.
defined for the ledger in the Intracompany Balancing Rules page in the Accounting
Setup Manager (ASM). The Enable Intracompany Balancing option must be selected in
the ledger definition in order to enable the application of the balancing rules. The
Accounting Program does not provide an automatic balancing mechanism for manual
subledger journal entries unbalanced by the balancing segment. Manual subledger
journal entries must be balanced by balancing segment at the time of creation.
See: Intracompany Balancing Rules, Oracle Financials Implementation Guide
Intercompany balancing rules are not applied to encumbrance accounting entries.
Ledger.
They must have the same decimal precision as their associated currency.
For example, if the ledger currency has a decimal precision of two, the monetary
An amount must always be either a debit or a credit. Either the debit or the credit
must have a value, including zero.
Both entered and accounted amounts must be on the same side. In other words, if
an entered amount is a debit, then its associated accounted amount must also be a
debit and vice versa.
However, the entered and accounted amounts can have different signs. For
example, a journal entry line may have a debit rounding difference in the entered
amount and a credit rounding difference in the accounted amount. In this case, one
single rounding line is created with a positive entered debit amount and a negative
accounted debit amount.
A journal entry whose entered currency is the same as the ledger currency should
have the same entered and accounted amounts.
Note: This rule does not apply to a rounding line.
Validation of journals created via the accounting engine in budgetary control mode
ensures that budgetary control is executed. Budgetary control validation includes
Projects, Grants, Contract Commitments, and General Ledger budgetary control
when required.
Description
Message
Description
Entered
Dr (USD)
Entered
Cr (USD)
Accounte
d Dr
(USD)
Accounte
d Cr
(USD)
Unrounde
d Entered
DR
Unrounde
d Entered
CR
Unrounde
d
Accounte
d DR
Unrounde
d
Accounte
d CR
01-Receiva
ble
100.00
Null
100.00
Null
100.00
Null
100.00
Null
01-Revenu
e
Null
Null
Null
Null
01-Revenu
e1
Null
33.33
Null
33.33
Null
33.33333
Null
33.33333
01-Roundi
ng
Null
0.01
Null
0.01
Null
Null
Null
Null
Entered
Dr (USD)
Entered
Cr (USD)
Accounte
d Dr
(EUR)
Accounte
d Cr
(EUR)
Unrounde
d Entered
DR
Unrounde
d Entered
CR
Unrounde
d
Accounte
d DR
(EUR)
Unrounde
d
Accounte
d CR
(EUR)
01-Receiva
ble
70.09
Null
56.77
Null
70.088
Null
56.77128
Null
01-Revenu
e
Null
Null
Null
Null
01-Revenu
e2
Null
35.04
Null
28.39
Null
35.044
Null
28.38564
Account
Entered
Dr (USD)
Entered
Cr (USD)
Accounte
d Dr
(EUR)
Accounte
d Cr
(EUR)
Unrounde
d Entered
DR
Unrounde
d Entered
CR
Unrounde
d
Accounte
d DR
(EUR)
Unrounde
d
Accounte
d CR
(EUR)
01-Roundi
ng
<0.01>
Null
0.01
Null
Null
Null
Null
Null
01-Exchan
ge
Gain/Loss
Null
28.39
Null
Null
28.38564
Null
Entered Dr
(USD)
Entered Cr
(USD)
Accounted
Dr (USD)
Accounted
Cr (USD)
Reason
01-Revenue
100
200
100
200
01-Revenue
100
Null
The entered
amount is
populated on
both debit
and credit
sides.
01-Revenue
Null
Null
Null
Null
The amounts
cannot be
null
simultaneous
ly.
Account
Entered Dr
(USD)
Entered Cr
(USD)
Accounted
Dr (USD)
Accounted
Cr (USD)
Reason
01-Revenue
100
Null
Null
100
The entered
and
accounted
amounts
must be on
the same side
(either debit
or credit).
01-Revenue
100
Null
Null
-100
The entered
and
accounted
amounts
must be on
the same side
(either debit
or credit).
01-Revenue
Null
Null
Null
An accounted
amount must
be populated
for every
entered
amount, even
when the
amount is
zero.
01-Revenue
Null
Null
Null
The entered
amount must
be populated.
01-Revenue
Null
100
Null
If the entered
currency is
same as the
ledger
currency,
then entered
and
accounted
amounts
cannot be
different.
Entered Dr
(USD)
Entered Cr
(USD)
Accounted
Dr (EUR)
Accounted
Cr (EUR)
Reason
01-Revenue
Null
Null
100
Null
Both entered
and
accounted
amounts
must be
populated.
Index
A
Account Analysis Reports, 9-20
account derivation rules, 2-57
Accounting Flexfield rules, 2-58
conditions, 2-70
examples, 2-71
lookup types, 2-71
define, 2-64
examples, 2-61
Accounting Flexfield rules, 2-61
segment rules, 2-62
segment rules, 2-59
value set rules, 2-60
Account Derivation Rules window, 2-65
accounting attributes guideline, 2-14
accounting chart of accounts, 2-8
assigning, 2-11
mapping, 2-11
using, 2-10
Accounting Class Assignments window, 2-16
accounting definitions inquiry, 2-121
features, 2-122
accounting events inquiry
process steps, 7-2
Accounting Flexfield Rules
account derivation rules, 2-58
Accounting Methods Builder
See AMB
Accounting Methods Builder Components
diagram, 2-3
accrual reversal GL date, 2-99
Index-1
diagram, 2-9
multiple representations, 2-8
example, 2-9
process, 2-4
steps, 2-5
subledger accounting methods, 2-118
transaction chart of accounts, 2-7
using the transaction and accounting chart of
accounts, 2-10
application accounting definitions, 2-107
Application Accounting Definitions diagram,
2-108
Application Accounting Definitions window,
2-109
copy, 2-113
copy and modify, 2-113
copy to, 2-113
Copy to window, 2-113
define
prerequisite, 2-109
modify, 2-113
validate, 2-113
application accounting definitions loader
installation, patching, and migration
export, 2-116
applications accounting definitions
define, 2-109
B
Basic Business Flow Example diagram, 2-18
business flows, 2-17
Basic Business Flow Example diagram, 2-18
business flow class, 2-20
business flow method, 2-19
prior entry, 2-19
same entry, 2-19
copy from prior entry
example, 2-22
copy from prior journal entry, 2-22
copy from same entry, 2-26
example, 2-26
features, 2-19
Journal Lines Accounting Attributes window,
2-21
Journal Lines Definitions window, 2-21
Journal Line Types window, 2-21
Index-2
C
chart of accounts mapping, 2-11
charts of accounts, 2-7
accounting, 2-8
transaction, 2-7
Complete Multiperiod Accounting process, 2-106
Components for Building Accounting Definitions
diagram, 2-4
copy and modify functionality, 2-6
Copy to window, 2-113
Create Accounting program
Oracle Subledger Accounting Program Report,
3-5
overview, 3-1
parameters, 3-1
custom sources, 2-12
define, 2-12
Custom Sources window, 2-12
D
diagnostic framework
Diagnostic Framework Business Process Flow
diagram, 5-1
features, 5-3
execution, 5-3
purge, 5-5
SLA: Enable Diagnostics, 5-3
introduction, 5-1
Transaction Objects Diagnostics Report, 5-3
diagrams, 11-2
Accounting Events Inquiry Process Flow, 7-1
Accounting Methods Builder Components, 2-3
Application Accounting Definitions, 2-108
Basic Business Flow Example, 2-18
Components for Building Accounting
Definitions, 2-4
Diagnostic Framework Business Process Flow,
5-1
Elements of a Subledger Journal Entry, 2-2
Journal Entry Headers Process Flow, 7-4
Journal Entry Lines Inquiry Process Flow, 7-5
Multiperiod Accounting Process Flow, 2-90
Multiple Accounting Representations, 2-9
E
Elements of a Subledger Journal Entry diagram,
2-2
events
introduction, 2-12
export AADs, 2-116
I
inquiries
Accounting Events Inquiry Process Flow
diagram, 7-1
headers inquiry
process steps, 7-4
Journal Entry Headers Process Flow Diagram,
7-4
Journal Entry Lines Inquiry Process Flow
diagram, 7-5
journal entry lines inquiry process steps, 7-6
overview, 7-1
subledger journal entries
headers, 7-4
lines, 7-5
Subledger Journal Entry Lines window, 7-6
inquiry
accounting events
process steps, 7-2
J
Journal Entries Report, 9-3
data elements, 9-11
parameters, 9-4
journal entry description
conditions, 2-51
copy, 2-51
define, 2-48
Journal Entry Description window, 2-48
journal entry description details
define, 2-49
Journal Entry Description Details window, 249
journal entry descriptions, 2-47
Journal Entry Headers Process Flow diagram, 7-4
L
Line Assignments window, 2-94
M
mapping sets, 2-51
define, 2-53
examples, 2-55
Mapping Sets window, 2-53
prerequisite, 2-52
multiperiod accounting, 2-90
Complete Multiperiod Accounting process, 2106
define, 2-94
define line assignments, 2-94
example, 2-92
Line Assignments window, 2-94
Multiperiod Accounting Process Flow
diagram, 2-90
Multiperiod Accounting window, 2-94
process, 2-90
process steps, 2-91
Multiperiod Accounting and Accrual Reversal
Report, 9-47
Multiperiod Accounting Report (Detail), 9-47
Index-3
N
navigation paths, A-1
O
Open Account Balances
open account balances data manager, 10-5
procedure, 10-5
Open Account Balances Listing, 10-5
create definitions, 10-2
data elements, 10-8
introduction, 10-1
parameters, 10-6
process steps, 10-1
Oracle Subledger Accounting Program Report, 35
P
Post-Accounting Programs, 2-15
Post-Accounting Programs window, 2-16
procedures
copy, modify, and validate application
accounting definitions, 2-113
copy a subledger accounting method, 2-121
copy journal line types and their associated
conditions, 2-47
create or update Open Account Balances
Listing definitions, 10-3
create subledger journal entries, 6-2
create transaction account definitions, 11-4
define account derivation rules for Accounting
Flexfields, 2-65
define a journal entry description, 2-48
define custom sources, 2-12
define journal entry description details, 2-49
define journal lines definitions, 2-82
define journal line type conditions, 2-43
define mapping sets, 2-53
define Post-Accounting Programs, 2-15
Index-4
R
reporting sequence
overview, 8-1
process steps, 8-4
Reporting Sequence Process Flow diagram, 83
sequence programs, 8-2
reports
Account Analysis, 9-20
Export Application Accounting Definitions, 2118
Import Application Accounting Definitions, 2-
116
Journal Entries Report, 9-3
Multiperiod Accounting and Accrual Reversal
Report, 9-47
Multiperiod Accounting Report (Detail), 9-47
Multiperiod Accounting Report (Summary), 947
Open Account Balances Listing, 10-1, 10-5
Oracle Subledger Accounting Program Report,
3-5
Subledger Period Close Exceptions, 9-62
Third Party Balance, 9-33
Transaction Objects Diagnostics, 5-3
S
seed data
Accounting Class Assignments window, 2-16
Post-Accounting Programs, 2-15
downloading, 2-17
Post-Accounting Programs window, 2-16
segment rules
account derivation rules, 2-59
sequence programs, 8-2
SLA: Accounting Methods Builder Context, B-3
SLA: Additional Data Access Set, B-8
SLA: Disable Journal Import, B-7
SLA: Display Timestamp on Trace, B-5
SLA: Enable Data Access Security in Subledgers,
B-8
SLA: Enable Diagnostics, B-5
SLA: Enable SQL Trace, B-5
SLA: Enable SRS Log/Output, B-5
SLA: Enable Subledger Transaction Security in
GL, B-9
SLA: Enable Trace, B-5
SLA: Flush Trace File, B-6
SLA: Initial Date for Historical Upgrade, B-7
SLA: Oracle Forms Trace Mode, B-6
SLA: SRS Trace Mode, B-6
SLA: Trace File Override Directory, B-6
SLA: Trace File Override Filename, B-6
SLA: Trace Level, B-6
SLA: Trace Timeout, B-6
subledger accounting method
copy and modify, 2-120
Copy to window, 2-121
define, 2-119
Subledger Accounting Method window, 2-119
subledger accounting methods, 2-118
Subledger Accounting options
option descriptions, 1-3
prerequisites, 1-2
setup pages, 1-1
system options, 1-1
to update Subledger Accounting options, 1-3
to update system options, 1-3
Update Accounting Options window, 1-3
Subledger Accounting options setup
overview, 1-1
subledger accounting reports
introduction, 9-1
Subledger Period Close Exceptions, 9-62
parameters, 9-63
Subledger Period Close Exceptions Report
data elements, 9-63
XML output file, 9-2
Subledger Accounting reports
Account Analysis, 9-20
data elements, 9-24
parameters, 9-21
Journal Entries, 9-3
Journal Entries Report
data elements, 9-11
parameters, 9-4
Multiperiod Accounting, 9-47
Third Party Balances Report, 9-33
subledger journal entries
create, 6-2
headers inquiry, 7-4
lines inquiry, 7-5
overview, 6-1
Subledger Journal Entry Lines window, 7-6
viewing supporting reference balances, 7-7
subledger journal entry
definition, C-1
balancing rules, C-14
header validation, C-2
high level, C-1
line validation, C-9
monetary amounts validation, C-16
Subledger Journal Entry Lines window, 7-6
Subledger Period Close Exceptions Report, 9-62
Supporting References, 2-72
Index-5
defining, 2-76
deleting, 2-78
duplicating, 2-78
Example, 2-73
Setup, 2-73
updating, 2-77
Viewing Supporting Reference Balances, 7-7
Year-End Carry Forward, 2-76
system options, 1-1
T
TAB
introduction, 11-1
setup, 11-3
Transaction Account Builder Components
diagram, 11-2
transaction account definitions, 11-1
create, 11-4
Third Party Balances Report, 9-33
transaction account builder
See TAB
Transaction Account Builder Components, 11-2
Transaction Account Builder Components
diagram, 11-2
transaction account definitions, 11-1
create, 11-4
transaction chart of accounts, 2-7
assigning, 2-11
mapping, 2-11
using, 2-10
Transaction Objects Diagnostics Report, 5-3
transaction objects guidelines
accounting attributes, 2-14
Transfer Journal Entries to General Ledger
program
overview, 3-1
Transfer Journal Entries to GL Program, 3-4
Transfer Journal Entries to GL Report, 3-5
U
Update Accounting Options window, 1-3
V
value set rules
account derivation rules, 2-60
Index-6
W
windows
Account Derivation Rules, 2-65
Accounting Class Assignments, 2-16
Application Accounting Definitions, 2-109
Copy to, 2-113
subledger accounting method, 2-121
Custom Sources, 2-12
Journal Entry Description, 2-48
Journal Entry Description Details, 2-49
Journal Line Accounting Attribute
Assignments, 2-31
Journal Lines Definitions, 2-82
Journal Line Types, 2-31
Line Assignments, 2-94
Mapping Sets, 2-53
Multiperiod Accounting, 2-94
Post-Accounting Programs, 2-16
Subledger Accounting Method, 2-119
Subledger Journal Entry Lines, 7-6
Update Accounting Options, 1-3
X
XML output file, 9-2