General ledger transfer program parameters

This feature is enabled under the feature name Subledger transfer to General Ledger performance optimization. The functionality for asynchronous transfer of subledger batches helps improve the transfer of data from the subledger to the general ledger. By grouping sets of smaller transactions and transferring the transactions in groups, the functionality processes transactions more efficiently.

When transactions are grouped, the batch server's resources are used more efficiently. Asynchronous transfer of subledger batches requires that the batch server be set up, online, and working because batch tasks are created for immediate execution on the batch server.

When the Subledger transfer to General Ledger performance optimization feature is enabled, the Process automation system batch job named Process automation polling system job must be also be enabled.

For more information, see Process automation. The efficiency change at the batch level uses a single recurring batch job for all legal entities in the system. At runtime, a new batch job is created to process the required records that haven't yet been transferred. When the user runs the General Ledger Transfer Program he has the option of choosing a parameter to perform a Summarized or Detailed Transfer. Choose a Posting Detail of Summary or Detail. This controls how Receivables creates journal entries for your transactions in the interface table.

When Submitting the General Ledger Transfer Program Oracle will also check if all the submitted code combinations are valid or not. In case there are any code combinations which are inactive or invalid in GL the Program will report it to the user and process the remaining records.

How to Identify if a record is transferred to GL : Once a transaction has been transferred to General Ledger the user must be abe to identify that the transactions have been transferred to GL. How to identify a transaction which has been transferred to General Ledger?

See: Subledger Accounting Setup Options Description, Oracle Subledger Accounting Implementation Guide Post in General Ledger Required if Mode is set to Final or Create Accounting is set to No; determines whether to post subledger journal entries in General Ledger If there is a primary ledger with secondary ledgers attached to it and the application is a nonvaluation method application, the journal entries of the secondary ledgers are automatically posted.

This is based on the application accounting definition that the user sets up. If the application is a valuation method application, then there is a different event for that secondary ledger and the accounting is not created in the same run for both ledgers. Transfer to GL option must be set to Yes.

Include User Transaction Identifiers Required; controls whether the report displays user identifiers' names and values. It lists the following: Successful events and the subledger journal entries created for those events Errors for failed events Users can run the report in summary or detail mode which are described as follows: Summary mode provides a summary of events processed and detailed information about their errors. Required; limits accounting events selected for processing to those of a particular ledger Subledger Accounting lists ledgers that have events that the responsibility can access due to transaction-based security.

Optional; restricts the events selected for accounting to a particular process category The Create Accounting program selects events with event types falling into the event classes assigned to the process category.

Required; end date for the Create Accounting program; processes only those events with event dates on or before the end date. Required; limits the creation of accounting to those events for which accounting has previously failed If Yes is selected, the Create Accounting program processes all events with a status of Error.