AR to GL Transfer (General Ledger Transfer Program)

AR to GL Transfer is a process which is concerned with the transfer to data from A to the GL
Module.
The General Ledger Transfer Program is a standard spawned program provided by Oracle to
transfer the data from AR to GL. The program picks up all the eligible records and transfers
them to the gl_interface. All the transactions that have been accounted and are complete,
and have not been transferred to GL will be picked up.
When submitting the program to transfer the records to GL form AR user can determine the
transactions to be transferred by specifying a General Ledger Date Range when submitting
the Interface Program. The user specifies a GL date that Receivables will use to select the
transactions for posting.
When you run General Ledger Interface, Receivables transfers transaction data into the
GL_INTERFACE table and generates the Posting Execution Report. This report provides the
list of transactions make up the entries to the general ledger.
Note: If you are using the Oracle Applications Multiple Reporting Currencies (MRC) feature,
you must run the General Ledger Interface program for your primary set of books and each
of your reporting set of books
The General Ledger Transfer Program consists of a number of Parameters some of which are
discussed below:
Post in Summary:
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.
If you select Detail(No), then the General Ledger Interface program creates
at least one journal entry in the interface table for each transaction in your posting
submission.
If you select Summary(Yes), then the program creates one journal entry for
each general ledger account.
Run Journal Import: If the user selects a value = YES Oracle will submit the Journal
Import process and create Journals for the transferred records. If the user selects the
parameter to be NO Oracle will not submit the Journal Import Program and the user will be
able to see the data in the GL Interface.
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. In order to enable the user to find out these details Oracle has

specified a field: POSTING_CONTROL_ID in the table : ra_cust_trx_line_gl_dist , If the value

of the columns is -3 it means that the record has not been transferred to GL.
RA_CUST_TRX_LINE_GL_DIST_ALL: POSTING_CONTROL_ID NOT NULL
Receivables posting batch identifier:
1 means the record was posted by the old posting program (ARXGLP);
2 means it was posted from old Release 8 Revenue Accounting;
3 means it was not posted;
4 means it was posted by the Release 9 RAPOST program.
How to identify a transaction which has been transferred to General Ledger?
The import puts rows into gl_import references REFERENCE21 to REFERENCE30
If the journal is imported in detail these are added to REFERENCE1 to REFERENCE10 in
GL_JE_LINES. In summary mode the references map from there to
GL_IMPORT_REFERENCES as there is no 1 to 1 relationship between the lines in gl and
there source references.
Below is list from Oracle on which reference fields are populated with what values depending
on the transaction category.
If you are customizing it should be note that these are subject to change without warning or
notice.
USER_JE_CATEGORY_NAME = Adjustment
Reference21
Reference22
Reference23
Reference24
Reference25
Reference26
Reference27
Reference28
Reference29
Reference30

:
:
:
:
:
:
:
:
:
:

POSTING_CONTROL_ID
AR_ADJUSTMENTS.ADJUSTMENT_ID
AR_DISTRIBUTIONS.LINE_ID
RA_CUSTOMER_TRX.TRX_NUMBER
AR_ADJUSTMENTS.ADJUSTMENT_NUMBER
RA_CUST_TRX_TYPES.TYPE
RA_CUSTOMER_TRX.BILL_TO_CUSTOMER_ID
'ADJ'
'ADJ_'||AR_DISTRIBUTIONS.SOURCE_TYPE
'AR_ADJUSTMENTS'

USER_JE_CATEGORY_NAME = Sales Invoice

Reference21
Reference22
Reference23
Reference24
Reference25
Reference26
Reference27
Reference28
Reference29
Reference30

:
:
:
:
:
:
:
:
:
:

POSTING_CONTROL_ID
RA_CUSTOMER_TRX.CUSTOMER_TRX_ID
RA_CUST_TRX_LINE_GL_DIST.CUST_TRX_LINE_GL_DIST_ID
RA_CUSTOMER_TRX.TRX_NUMBER
HZ_CUST_ACCOUNTS.ACCOUNT_NUMBER
'CUSTOMER'
RA_CUSTOMER_TRX.BILL_TO_CUSTOMER_ID
'INV'
'INV_'||RA_CUST_TRX_LINE_GL_DIST.ACCOUNT_CLASS
'RA_CUST_TRX_LINE_GL_DIST'

USER_JE_CATEGORY_NAME = Credit Memo

Reference21
Reference22
Reference23
Reference24
Reference25
Reference26
Reference27
Reference28
Reference29
Reference30

:
:
:
:
:
:
:
:
:
:

POSTING_CONTROL_ID
RA_CUSTOMER_TRX.CUSTOMER_TRX_ID
RA_CUST_TRX_LINE_GL_DIST.CUST_TRX_LINE_GL_DIST_ID
RA_CUSTOMER_TRX.TRX_NUMBER
HZ_CUST_ACCOUNTS.ACCOUNT_NUMBER
'CUSTOMER'
RA_CUSTOMER_TRX.BILL_TO_CUSTOMER_ID
'CM'
'CM_'||RA_CUST_TRX_LINE_GL_DIST.ACCOUNT_CLASS
'RA_CUST_TRX_LINE_GL_DIST'

USER_JE_CATEGORY_NAME = Debit Memo

Reference21
Reference22
Reference23
Reference24
Reference25
Reference26
Reference27
Reference28
Reference29
Reference30

:
:
:
:
:
:
:
:
:
:

POSTING_CONTROL_ID
RA_CUSTOMER_TRX.CUSTOMER_TRX_ID
RA_CUST_TRX_LINE_GL_DIST.CUST_TRX_LINE_GL_DIST_ID
RA_CUSTOMER_TRX.TRX_NUMBER
HZ_CUST_ACCOUNTS.ACCOUNT_NUMBER
'CUSTOMER'
RA_CUSTOMER_TRX.BILL_TO_CUSTOMER_ID
'DM'
'DM_'||RA_CUST_TRX_LINE_GL_DIST.ACCOUNT_CLASS
'RA_CUST_TRX_LINE_GL_DIST'

USER_JE_CATEGORY_NAME = Chargeback
Reference21
Reference22
Reference23
Reference24
Reference25
Reference26
Reference27
Reference28
Reference29
Reference30

:
:
:
:
:
:
:
:
:
:

POSTING_CONTROL_ID
RA_CUSTOMER_TRX.CUSTOMER_TRX_ID
RA_CUST_TRX_LINE_GL_DIST.CUST_TRX_LINE_GL_DIST_ID
RA_CUSTOMER_TRX.TRX_NUMBER
HZ_CUST_ACCOUNTS.ACCOUNT_NUMBER
'CUSTOMER'
RA_CUSTOMER_TRX.BILL_TO_CUSTOMER_ID
'CB'
'CB_'||RA_CUST_TRX_LINE_GL_DIST.ACCOUNT_CLASS
'RA_CUST_TRX_LINE_GL_DIST'

USER_JE_CATEGORY_NAME = Receipts
Receipts Journal
Reference21 : POSTING_CONTROL_ID
Reference22 : AR_CASH_RECEIPTS.CASH_RECEIPT_ID||'C'
||AR_CASH_RECEIPT_HISTORY_ALL.CASH_RECEIPT_HISTORY_ID
Reference23 : AR_DISTRIBUTIONS.LINE_ID
Reference24 : AR_CASH_RECEIPTS.RECEIPT_NUMBER
Reference25 : Null
Reference26 : Null
Reference27 : AR_CASH_RECEIPTS.PAY_FROM_CUSTOMER
Reference28 : 'TRADE'
Reference29 : 'TRADE_'|| AR_DISTRIBUTIONS.SOURCE_TYPE
Reference30 : 'AR_CASH_RECEIPT_HISTORY'
Application Journal
Reference21 : POSTING_CONTROL_ID

Reference22 : AR_CASH_RECEIPTS_ALL.CASH_RECEIPT_ID||'C'
||AR_RECEIVABLE_APPLICATIONS_ALL.RECEIVABLE_APPLICATION_ID
Reference23 : AR_DISTRIBUTIONS.LINE_ID
Reference24 : AR_CASH_RECEIPTS.RECIPT_NUMBER
Reference25 : RA_CUSTOMER_TRX.TRX_NUMBER
Reference26 : RA_CUST_TRX_TYPES.TYPE
Reference27 : AR_CASH_RECEIPTS.PAY_FROM_CUSTOMER
Reference28 : 'TRADE' or 'CCURR'
Reference29 : 'TRADE_' or 'CCURR_'|| AR_DISTRIBUTIONS.SOURCE_TYPE
Reference30 : 'AR_RECEIVABLE_APPLICATIONS'
USER_JE_CATEGORY_NAME = Misc Receipts
Header
Reference21
Reference22
Reference23
Reference24
Reference25
Reference26
Reference27
Reference28
Reference29
Reference30

:
:
:
:
:
:
:
:
:
:

POSTING_CONTROL_ID
AR_CASH_RECEIPTS.CASH_RECEIPT_ID
AR_DISTRIBUTIONS.LINE_ID
AR_CASH_RECEIPTS.RECEIPT_NUMBER
AR_CASH_RECEIPT_HISTORY.CASH_RECEIPT_HISTORY_ID
Null
AR_CASH_RECEIPTS.PAY_FROM_CUSTOMER
'MISC'
'MISC_' || AR_DISTRIBUTIONS.SOURCE_TYPE
'AR_CASH_RECEIPT_HISTORY'

Distributions
Reference21 : POSTING_CONTROL_ID
Reference22 : AR_CASH_RECEIPTS_ALL.CASH_RECEIPT_ID
Reference23 : AR_DISTRIBUTIONS_ALL.LINE_ID
Reference24 : AR_CASH_RECEIPTS_ALL.RECEIPT_NUMBER
Reference25 : AR_MISC_CASH_DISTRIBUTIONS_ALL.MISC_CASH_DISTRIBUTION_ID
Reference26 : null
Reference27 : null
Reference28 : 'MISC'
Reference29 : 'MISC_'AR_DISTRIBUTIONS.SOURCE_TYPE
Reference30 : 'AR_MISC_CASH_DISTRIBUTIONS'
USER_JE_CATEGORY_NAME = Credit Memo Application
Reference21
Reference22
Reference23
Reference24
Reference25
Reference26
Reference27
Reference28
Reference29
Reference30

:
:
:
:
:
:
:
:
:
:

POSTING_CONTROL_ID
AR_RECEIVABLES_APPLICATIONS.RECEIVABLE_APPLICATION_ID
AR_DISTRIBUTIONS_ALL.LINE_ID
RA_CUSTOMER_TRX.TRX_NUMBER
RA_CUSTOMER_TRX.TRX_NUMBER
RA_CUST_TRX_TYPES.TYPE
RA_CUSTOMER_TRX.BILL_TO_CUSTOMER_ID
'CMAPP'
'CMAPP_'||AR_DISTRIBUTIONS.SOURCE_TYPE
'AR_RECEIVABLE_APPLICATIONS'

USER_JE_CATEGORY_NAME = Bills Receivable

Reference21 : POSTING_CONTROL_ID
Reference22 : AR_TRANSACTION_HISTORY.TRANSACTION_HISTORY_ID

Reference23
Reference24
Reference25
Reference26
Reference27
Reference28
Reference29
Reference30

:
:
:
:
:
:
:
:

AR_DISTRIBUTIONS.LINE_ID
RA_CUSTOMER_TRX.TRX_NUMBER
AR_TRANSACTION_HISTORY.CUSTOMER_TRX_ID
RA_CUST_TRX_TYPES.TYPE
RA_CUSTOMER_TRX.DRAWEE_ID
'BR'
'BR_'||AR_DISTRIBUTIONS.SOURCE_TYPE
'AR_TRANSACTION_HISTORY'

Upon running the Program the data will be interfaced to the GL Module in the table GL
Interface where the user can identify any of the transferred record using the above
references.
Even After transferring the data to General Ledger the AR module will still retain all the
entries that have been transferred and can be used by for future reference
AR to GL transfer process is required for transferring all the AR data to GL so that financial
reports can be prepared for all the expected revenue, receivables for the business.
Posted 9th September 2012 by ashwini.agrawal