Create subledger journal entries as follows:
Manually create subledger journal entries and assign supporting references at the header and line level in the Create Subledger Journal Entry page.
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
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:
Use the Subledger Journal Entries - Search page to search for all types of subledger journal entries, not just manual entries. In the search results region:
Drill down to view subledger journal entry details
View, assign, and unassign supporting references
Update, duplicate, complete, and reverse manual journal entries
In the Subledger Journal Entries page, click Create Journal Entry.
Field | Description |
---|---|
Ledger | The primary and secondary ledgers displayed in the ledger list of values are determined by the system profile option SLA: Enable Data Access Security in Subledgers. If this profile option is set to Yes, the list of values displays only the primary and secondary ledgers defined in the GL: Data Access Set and the SLA: Additional Data Access Set profile options. If the profile option is set to No, the list of values displays all primary and secondary ledgers. See:
If Encumbrance is selected in the Balance Type field, the list of values only displays ledgers that are enabled for budgetary control. |
Category | Journal category |
GL Date | GL date for posting the subledger journal entry. |
Reference Date | Reference date to be stored at the subledger journal entry header level. Used in reporting sequence for Actual journal entries. |
Assign Supporting References | Opens the Assign Supporting References - Lines page where you can assign and unassign supporting references. |
Use the Assign Supporting References page to view or modify current supporting reference values and to assign new supporting references to the journal entry or line. This page is available in view-only mode if you navigate from a final journal entry and the page title will be displayed as View Supporting References.
To assign supporting references to the journal entry in the Header region of the Create Subledger Journal Entry page:
Click Assign Supporting References.
Click Add 5 Lines.
Select the supporting reference in the Name field and enter details as required.
Click Apply to save the changes.
Note: Supporting references with line level source assignments on the details may not be assigned on the journal entry header.
To assign supporting references to the lines of a journal entry in the Lines region of the Create Subledger Journal Entry page:
Click the Assign Supporting References icon on the appropriate line
Click Add 5 Lines.
Select the supporting reference in the Name field and enter details as required.
Click Apply to save the changes.
Note: Supporting references maintaining balances can only be assigned on journal entry lines.
In the Lines region of the Create Subledger Journal Entry page:
Enter account, debit and credit amounts, and accounting class.
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.
View the total accounted amounts of all subledger journal entry lines in the ledger currency.
Field and Button | Description |
---|---|
Default Currency Options | Opens the Default Currency Options page to default an entered currency, conversion type, conversion date, and conversion rate information for each new subledger journal entry line. Use the currency controls available in the Details region of each journal entry line to override the default set. |
Third Party Type | Defaults from the application associated with the responsibility used to access the manual subledger journal entry pages. The values for name, site, number, and taxpayer ID must match the third party type. These values are required if the account on the line is a third party control account. If the account is not a third party control account, but party type is selected, party information should be provided. |
Conversion Rate | If the conversion type is User, you must enter a conversion rate. |
Calculate Totals | Updates the display in the Accounted Amounts region |
Continue | Select to review the manual subledger journal entry and complete it. |
The Third Party Control Account feature in the Oracle E-Business Suite enables organizations to maintain detailed balances by third party for an account code combination. Subledger Accounting checks that valid third party information is associated with the journal line if the account code combination is a Third Party Control Account. If it is not, then Subledger Accounting rejects the journal line. General Ledger prevents manual journal entries from posting to the third party control accounts. This ensures that journal lines that post to the control account codes such as Supplier Liability Account, Customer Receivables Account, are associated with the valid third party information in the respective subledger modules.
Restricting Natural Account Values in the General Ledger Manual Journal Entries
You might sometimes define an account code as a third party control account to prevent the GL manual journal entries from posting to these accounts. When such accounts are used in the subledger transaction without the third party information, Subledger Accounting prevents the accounting for such transaction with an error that the third party information is missing.
For example, when the unidentified receipts account code in the Oracle Receivables is defined as a third party control account, accounting for the unidentified receipts fails because no third party information is available for such receipts. Similar issues are observed with the rounding account and intercompany accounts.
The following solution helps overcome these issues. A new third party control account validation is provided that allows accounting to complete successfully without the third party information in the subledgers but to restrict that account code while entering in the GL manual journal entries.
A new value, Restrict Manual Journals, is added to the List of values of the Third Party Control Account segment qualifier.
You can assign Restrict Manual Journals value in the list of values of the Third Party Control Account segment qualifier to natural account segment values and prevent the GL manual journal entries from posting to these account code combinations containing the respective natural account segment values.
When you define the Unidentified Receipt account code as third party control account to prevent the GL manual journal entries from using this account code, you define the Unidentified Receipt account code as Restrict Manual Journals third party control account. When you use this account code for the unidentified receipt in the Oracle Receivables, Subledger Accounting creates the accounting successfully for this unidentified receipt without the party information. Hence, you cannot enter manual journal entries using this account code in General Ledger.
After you set up an account code as Restrict Manual Journals third party control account, you must run the concurrent program, Program - Inherit Segment Value Attributes to reflect the Third Party Control Account qualifier changes in the account code combinations.
After this, you cannot select this account code while creating a manual journal entry in General Ledger. Though, you can select these account codes without the third party information in the respective subledgers as the application treats this third party control account for the purpose of restricting the usage in General Ledger manual journal entries only.
In General Ledger the validation performed on entering manual journals in journal entry window has been modified to restrict users from using the third party control accounts defined as Restrict Manual Journals.
Subledger Accounting is modified to treat the third party control accounts defined as Restrict Manual Journals the same way as the third party control accounts defined as No.
If an account or a control account is updated as Restrict Manual Journals or No from either the Supplier, Customer, or Both, then the balances for the Third Party Balances Report is not maintained for such account code with the prospective effect. The balances prior to the modification will only be shown in the report output and thus the balance in the report output may not match with the General Ledger balance for such account or control code.
You can upload initial balance value for the prior period activities and synchronize them. The initial balance of a Third Party Control Account is defined in context of ledger and is the starting balance for which there is no journal entry in Subledger Accounting to support that balance.
The Third Party Control Account feature of the Oracle Subledger Accounting (SLA) enables organizations to maintain the breakdown of an account balance by third party for asset and liability accounts.
When a new third party control account is created, the account does not have an opening balance and all the transactions posted to the account contain the third party information. SLA updates the third party balances for every transaction posted to the account. This ensures that user can generate the third party balances report and successfully reconcile the closing balance of the account with the sum of the third party balances for that account. When an existing account having balance is converted into a control account there will not be any third party balances in the Subledger Accounting and the third party balances report cannot be generated for that account.
This new feature lets you upload the initial third party balances for a control account and synchronize the account and third party balances for accurate reporting and reconciliation. A new open interface table (xla_ctrl_balances_int) and an import program are provided to initialize the control account balances.
Initialize Control Account Balances
You can upload initial balance for a third party control account for a combination of ledger, application, party and party-site combination. An initial balance is in the ledger currency for a particular period. This initial balance is carried forward to the subsequent periods.
You define initial balances as Net of Debit (Dr) and Credit (Cr) balance. You cannot define initial balance as separate balances for Debit and Credit.
You can define an initial balance for a closed period only. You can also define initial balance even after the SLA has created balances and entries for third party control accounts.
Update or Delete Initial Balances
Once the initial balance has been entered, you can still modify the initial balance. Modifying the initial balance impacts the subsequent period balances. The following validations are performed:
The periods prior to the date of initial balance must not have any period activity for the combination of third party control account, application, ledger, third party and third party site for which the initial balance is uploaded
Initial balance is uploaded only for the third party control accounts.
The period closing status of the periods for which the initial balance is being uploaded must be “Closed”.
Submit Concurrent Program to Import Data from Interface table into the Base table
Insert the data into the interface table (xla_ctrl_balances_int)
Run the concurrent program, Import Initial Balance for Third Party Control Account, from the responsibility where the data is defined and the application where the control balance data is intended. For example, submit the concurrent program from Payables responsibility
The only parameter for this concurrent program is the Purge Option. The valid values are Purge successfully processed rows, Purge all rows and Do not purge.
If you specify Purge successfully processed rows, then only the successfully imported data in the interface table is deleted after processing.
If you specify Purge all rows, then all data in the interface table is deleted after processing.
If you specify Do not purge, then all the data in the interface table will be retained after processing.
The concurrent program once completed successfully generates a report.
The report is divided into the following sections:
Successfully Initialized Rows
Warnings - GL Balance does not match SLA Balance after initialization
Failed Initialization Rows
Error Code Details
In the Review Subledger Journal Entry page:
Review all subledger journal entry header and line information
View supporting references.
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 a budget journal entry that has a status of Final.
View the budgetary control validation results if the fund status is Failed by clicking the Funds Validation Results button.
Complete the journal entry
The Complete button is enabled if the journal entry:
Is a manual journal entry with a status of Draft, Error, or Incomplete
Is an accrual reversal or multiperiod accounting recognition entry with an Incomplete status
Does not belong to a reporting currency
Option | Description |
---|---|
Draft | Results cannot be transferred or posted to General Ledger; appears on Subledger Accounting reports or inquiries that are based upon draft entries; entries can be updated and deleted; and cannot perform funds reservation. |
Final | Subledger journal entry is completed; can be transferred and posted to General Ledger; appears on Subledger Accounting reports and inquiries that are based upon final entries; and funds reservation is performed. |
Final and Post | Completes the subledger journal entry with the status Final; transfers it to General Ledger and posts it; entry appears on Subledger Accounting reports or inquiries that are based upon final entries. If the entry is successfully completed and transferred, the status is Transferred. |
Subledger Accounting completes the subledger journal entry as follows:
Validates the accounts; same validation as that performed by the Create Accounting program
Assigns the corresponding sequence to the subledger journal entry if completed with Final status
Updates the status of the subledger journal entry
Updates the pending subledger journal entry with the corresponding error message if the subledger journal entry is not successfully created
Invokes the balance update program
Note: If the subledger journal entry is for a ledger with reporting currencies, Subledger Accounting creates subledger journal entries for these representations.
In the Duplicate Subledger Journal Entries page, create a new subledger journal entry from an existing subledger journal entry of any status except Error. When a journal entry is duplicated, you can update all fields except Balance Type.
Note: If changing the ledger in a duplicated journal entry and the new ledger has a different chart of accounts, all lines are cleared because the Accounting Flexfield structure is dependent on the new ledger.
In the Reverse Subledger Journal Entry page, reverse an existing manual subledger journal entry in Final status. Reversal options are:
Switch DR/CR
Change Sign
In the Update Subledger Journal Entries page, update:
A manual subledger journal entry of status Draft, Incomplete, or Error
Supporting references for manual subledger journal entries with a status of Final
A multiperiod recognition or accrual reversal journal entry of status Incomplete
When a manual journal entry is updated, you can update all fields except Balance Type and Ledger.
In the Delete Subledger Journal Entries page, delete a manual subledger journal entry for a primary or secondary ledger in Draft or Incomplete status.