Running GL Interface
Run the GL Interface program to transfer receivables transactions to the general ledger and create either detailed or summarized journal batches. You determine which transactions to transfer by specifying a General Ledger date range. You specify the General Ledger date that Receivables uses to select transactions for posting when you create each transaction. You can transfer your transactions to your general ledger as often as you like within an accounting period.
Receivables creates journal batches when you transfer your receivables transactions through the Run General Ledger Interface window and invoke the General Ledger Journal Import program. You must post these batches in your general ledger before your general ledger accounts are updated.
If you have Oracle General Ledger installed, you can choose to run Journal Import to create journal entries to post to your general ledger; otherwise, you can use your feeder system to import data from the GL_INTERFACE table.
Before you run the GL Interface program, generate the Inter Company Invoice report to see a list of all transactions whose receivables and revenue accounts have different company segments. You can also generate the Inter Company Receipts report to review payments that were sent from one company and applied to another company, but have not yet posted.
When you run GL Interface, Receivables transfers transaction data into the GL_INTERFACE table and generates the Posting Execution Report.
Note: If you are using the Oracle Applications Multiple Reporting Currencies (MRC) feature, you should run the GL Interface program for both your reporting and your primary set of books. For more information, see: Multiple Reporting Currencies in Oracle Applications.
Prerequisites
To run the GL Interface program:
1. Navigate to the Run General Ledger Interface window.
2. Choose a Posting Detail of Summary or Detail. If you transfer transactions in detail, the General Ledger Journal Import Program creates at least one journal entry for each transaction in your posting submission. If you transfer in summary, it creates one journal entry for each general ledger account. If you set this option to Summary and set Run Journal Import to No, to post records to your GL in summary form you must submit the Run Journal Import program manually using the GL responsibility and set Create Summary Journals to Yes. For more information, see: Importing Journals.
3. Enter the GL Posted Date for this submission. The default is the current date, but you can change it. Receivables updates all of the posted transactions that you transfer to your general ledger or the general ledger interface area with the GL posted date you enter.
4. Enter the range of GL Dates for your submission. The dates must be within both an open receivables period and an open or future General Ledger period. When you enter a start date, the default GL end date is the last day of the period that you entered for the GL start date.
5. Choose whether to Run Journal Import. If you choose Yes, Receivables creates journal batches in your general ledger when your posting submission has completed. If you enter No, Receivables creates batches of your transaction records in the journal import interface area. The default is the value you entered for the Automatic Journal Import option in the System Options window.
Note: If you are using Oracle General Ledger, use the General Ledger Journal Import program to transfer these records from the journal import interface area into your general ledger as batches of journal entries. Use the Journal Entries Report to review either summary or detailed information about the transactions which make up your general ledger journal entries.
6. Save your work. Receivables displays the Request ID number for your concurrent process. Use this number to view the status of your request in the Requests window.
Receivables also creates the Posting Execution Report. Use this report to see a summary of transactions that are imported into the GL_INTERFACE table. See: Posting Execution Report. Transactions that failed validation appear in the Unposted Items Report. See: Unposted Items Report.
See Also
Recognizing Revenue
Inter Company Invoice Report
Monitoring Requests
Inter Company Receipts Report
Invoice Exception Report