Sei sulla pagina 1di 7

GL REFERENCE

The mapping is actually documented in BUG:249623.


Following is from BUG:249623:
In detail mode, gl_interface.reference21 - reference30 maps to
gl_je_lines.reference1 - reference10.
In Summary mode, gl_interface.reference21 - reference30 maps to
gl_import_reference.reference1 - reference10.
Here is what we put in the gl_interface.reference21 - reference30 columns.
- reference1 to 20 have special uses as rel9
- reference1 : part of the je batch name
- reference2 : je batch description, not used by ARGLTP
- reference3 : not used
- reference4 : part of the je header name, not used by ARGLTP
- reference5 : je header description, not used by ARGLTP
- reference6,7,8,9 : not used by ARGLTP
- reference10: je lines descriptions
- reference11- 20 not used by ARGLTP
- reference21 - 30 corresponding to
gl_je_lines.reference_1 to 10
(For details on ref22,28,29,30, see Reference Columns section.)
Reference21 : Post ID
Reference22 : Balance Group ID (See below for detail)
Reference23 : Primary ID of Reference30
Reference24 : Trx Number (See below for detail)
Reference25 : Trx Number (See below for detail)
Reference26 : Trx Type of Reference5
(For Adjustments, it is trx type of reference4)
(Trx Type includes 'INV','CM','CB','DM','GUAR','DEP')
(For Inv, CM, DM, CB, it would say 'CUSTOMER'.)
Reference27 : Customer ID
Reference28 : Category Code
Reference29 : Account Code
Reference30 : Source Table Name

-----------------------------------------------------------------------------------------------------------------------------

GL REFERENCE

Reference 1 in GL_INTERFACE moves to BATCH NAME


Reference 2 in GL_INTERFACE moves to BATCH Description
Reference 4 in GL_INTERFACE moves to Header NAME
Reference 5 in GL_INTERFACE moves to Header Description.
Reference 7 in GL_INTERFACE moves to JE Reversal FLAG
Reference 8 in GL_INTERFACE moves to JE Reversal PERIOD
Reference 10 in GL_INTERFACE moves to JOURNAL LINE DESCRIPTION.

So if you want the info to flow the GE LINE description field then =
populate Reference 10 of GL _INTERFACE.
If you want to populate the reference fields of JE LINES then populate=20
Reference 21 in GL_INTERFACE moves to Reference 1 of JE LINES
Reference 22 in GL_INTERFACE moves to Reference 2 of JE LINES
Reference 23 in GL_INTERFACE moves to Reference 3 of JE LINES
Reference 24 in GL_INTERFACE moves to Reference 4 of JE LINES
Reference 25 in GL_INTERFACE moves to Reference 5 of JE LINES
Reference 26 in GL_INTERFACE moves to Reference 6 of JE LINES
Reference 27 in GL_INTERFACE moves to Reference 7 of JE LINES
Reference 28 in GL_INTERFACE moves to Reference 8 of JE LINES
Reference 29 in GL_INTERFACE moves to Reference 9 of JE LINES
Reference 30 in GL_INTERFACE moves to Reference 10 of JE LINES

--------------------------------------------------------------------------------------------------------------

GL REFERENCE

Reference columns are populated/updated in GL_INTERFACE, GL_JE_LINES and


GL_IMPORT_REFERENCES tables only in 11i EBS and not in R12. In R12, there are different
set of SLA tables which we need to refer to retrieve subledger data after transfer to GL.

Below is the detailed analysis of Reference columns in GL_INTERFACE

Reference 1 To 10

reference1 => BATCH NAME


reference2 => BATCH Description
reference4 => Header NAME
reference5 => Header Description.
reference7 => JE Reversal FLAG
reference8 => JE Reversal PERIOD
reference10 => JOURNAL LINE DESCRIPTION(GE LINE description field )

Reference 11 To 20

Not Used

Reference 21 To 30

In Summary mode, gl_interface.reference21 - reference30 maps to gl_je_lines.reference1 -


reference10.

In Detail mode, gl_interface.reference21 - reference30 maps to gl_import_reference.reference1


- reference10.

Below is the mapping for Reference 21-30 Columns with Subledgers (AP/ AR/ FA)

AP (Reference 21 To 30)

reference21 = vendor_name
reference22 = invoice_id
reference23 = distribution_line_number or check_id
reference24 = check_number
reference25 = invoice_num
reference26 = 'AP INV. JUST INSERTED' or 'AP PAYMT. JUST INSERTED'
reference27 = set_of_books_id
reference28 = invoice_distribution_id or distribution_line_number
reference29 = invoice_payment_id

For more details, Refer to Metalink Note ID- 1011799.6

AR (Reference 21 To 30)

Adjustments
-------------
REFERENCE21 = posting_control_id
REFERENCE22 = adjustment_id
REFERENCE23 = line_id
REFERENCE24 = trx_number
REFERENCE25 = adjustment_number
REFERENCE26 = cust_trx_type
RERENCE27 = bill_to_customer_id
REFERENCE28 = ADJ
REFERENCE29 = source_type prefixed by �ADJ_�
REFERENCE30 = AR_ADJUSTMENTS

Transactions
-------------
REFERENCE21 = posting_control_id
REFERENCE22 = customer_trx_id
REFERENCE23 = cust_trx_line_gl_dist_id
REFERENCE24 = trx_number
REFERENCE25 = cust.account_number
REFERENCE26 = CUSTOMER
REFERENCE27 = bill_to_customer_id
REFERENCE28 = type(CM/DM/CB/INV)
REFERENCE29 = type account_class
REFERENCE30 = RA_CUST_TRX_LINE_GL_DIST

Receipts
---------
REFERENCE21 = posting_control_id
REFERENCE22 = cash_receipt_history_id or cash_receipt_id for MISC
REFERENCE23 = line_id
REFERENCE24 = receipt_number
REFERENCE25 = null for CASH / cash_receipt_history_id for MISC
REFERENCE26 = null
REFERENCE27 = pay_from_customer
REFERENCE28 = MISC / TRADE
REFERENCE29 = MISC_sourcetype or TRADE_source_type
REFERENCE30 = AR_CASH_RECEIPT_HISTORY

Applications
--------------
REFERENCE21 = posting_control_id
REFERENCE22 = cash_receipt_id (receivable_application_id for CASH /
receivable_application_id for CM)
REFERENCE23 = line_id
REFERENCE24 = receipt_number for CASH / trx_number for CM
REFERENCE25 = trx_number if status = APP/ NULL for unapplied records
REFERENCE26 = cust_trx_type
REFERENCE27 = pay_from_customer for CASH / bill_to_customer_id for CM
REFERENCE28 = application_type (TRADE or CCURR for CASH / CMAPP for CM)
REFERENCE29 = application_type source_type
REFERENCE30 = AR_RECEIVABLE_APPLICATIONS

Bills Receivable
----------------
REFERENCE21 = posting_control_id
REFERENCE22 = transaction_history_id
REFERENCE23 = line_id
REFERENCE24 = trx_number
REFERENCE25 = customer_Trx_id
REFERENCE26 = cust_trx_type
REFERENCE27 = drawee_id
REFERENCE28 = cust_trx_type
REFERENCE29 = BR_source_type
REFERENCE30 = AR_TRANSACTION_HISTORY

FA (Reference 21 To 30)

reference21 = transaction_header_id
reference22 = asset_id
reference23 = distribution_id
reference24 = adjustment_line_id
reference25 = book_type_code
reference26 = period_counter
reference27 = FA_TRANSFER_TO_GL
reference28 = adjustment_type / lookup_code
reference29 = cje_id

--------------------------------------

Assigning Values to Optional Columns


You can enter values for many optional columns in the GL_INTERFACE
table. Enter values in these columns for maximum control over the way
Journal Import groups the journal entry lines it creates into journal entries.

If you have enabled average balance processing, Journal Import will group
transactions by Accounting Date. Transactions are grouped before they are
validated and, if the Effective Date Rule is Roll Date, rolled to the nearest
valid business day within the period.
If you do not enter a value in an optional column and a default value exists for
that particular column, Journal Import automatically enters the default value.

Enter values in the following optional columns of the GL_INTERFACE table:

REFERENCE1 (Batch Name): Enter a batch name for your import


batch. Journal Import creates a default batch name using the following
format: (Optional User-Entered REFERENCE1) (Source) (Request ID)
(Actual Flag) (Group ID). If you enter a batch name, Journal Import
prefixes the first 50 characters of your batch name to the above format.
REFERENCE2 (Batch Description): Enter a description for your
batch. If you do not enter a batch description, Journal Import
automatically gives your batch a description using the format: Journal
Import (Source) (Request Id).
REFERENCE4 (Journal entry name): Enter a journal entry name for
your journal entry. Journal Import creates a default journal entry name
using the following format: (Category Name) (Currency) (Currency
Conversion Type, if applicable) (Currency Conversion Rate, if
applicable) (Currency Conversion Date, if applicable) (Encumbrance
Type ID, if applicable) (Budget Version ID, if applicable). If you enter
a journal entry name, Journal Import prepends the first 25 characters of
your journal entry name to the above format.
REFERENCE5 (Journal entry description): Enter a description for
your journal entry. If you do not enter a journal entry description,
Journal Import automatically gives your journal entry a description
using the format: Journal Import - Concurrent Request ID.
REFERENCE6 (Journal entry reference): Enter a reference name or
number for your journal entry. If you do not enter a journal entry
reference, Journal Import automatically creates a journal entry
reference called Journal Import Created.
REFERENCE7 (Journal entry reversal flag): Enter Yes to mark
your journal entry for reversal. If you do not enter Yes, Journal Import
automatically defaults to No.
REFERENCE8 (Journal entry reversal period or effective date):
Enter the name of the period to which you want to reverse your journal
entry. If you have enabled average balance processing, enter the
effective date for the reversal.
Note: If you enter Yes in the REFERENCE7 column, you must enter a value
in this column.
REFERENCE10 (Journal entry line description): Enter a
description for your journal entry line. If you do not enter a journal
entry line description, Journal Import uses the subledger document
sequence value. If there is no document sequence value, Journal Import
creates a journal entry description called Journal Import Created.
REFERENCE21 through REFERENCE30: Enter a reference name
or number to further identify your import journal entry lines. Columns
REFERENCE21 through REFERENCE30 map into columns
REFERENCE_1 through REFERENCE_10, respectively, of the
GL_JE_LINES table.
Once in the GL_JE_LINES table, your General Ledger application
prints the value stored in REFERENCE_1 in standard reports run with
Line detail, and prints the value stored in REFERENCE_4 in standard
reports run with Source detail. The other reference columns are for
descriptive or tracking purposes only. The values in these columns are
not used in your General Ledger application.
GROUP_ID: Enter a unique group number to distinguish import data
within a source. You can run Journal Import in parallel for the same
source if you specify a unique group number for each request.
STAT_AMOUNT: Enter the statistical amount associated with your
journal entry line data. You define statistical units of measure in the
Statistical Units of Measure form of your General Ledger application.
You must use this column when you want to see statistical and
monetary amounts in the same journal entry line.
USSGL_TRANSACTION_CODE: Enter a valid USSGL transaction
code for your journal entry line. Journal Import validates and imports
the USSGL transaction codes when you have the profile option Enable
Transaction Code set to Yes, and you have defined your USSGL
transaction codes using the Public Sector Transaction Codes window.
Note: This column is ignored for commercial installations of General Ledger.
ATTRIBUTE1 through ATTRIBUTE 10: Enter values for your
descriptive flexfield "Journals - Journal Entry Line". The values you
enter depend on how you defined your descriptive flexfield in the
Descriptive Flexfield Segments form.
ATTRIBUTE11 through ATTRIBUTE 20: Enter values for your
descriptive flexfield "Journals - Captured Information". The values you
enter depend on how you defined your descriptive flexfield in the
Descriptive Flexfield Segments form.
CONTEXT: Enter the context field value for the descriptive
flexfield "Journals - Journal Entry Line" that identifies the structure of
your descriptive flexfield. If you enter a value, you can also enter some
combination of values in the columns ATTRIBUTE1 through
ATTRIBUTE10.
CONTEXT2: Enter Yes to identify your Value Added Tax Descriptive
Flexfield structure. You must use this column if you import data for the
Value Added Tax Descriptive Flexfield. Enter No to indicate that your
journal entry line is not a tax item. If you enter No, the four Value
Added Tax Descriptive Flexfield related columns must be null.
CONTEXT3: Enter the context field value (natural account) for the
descriptive flexfield "Journals - Captured Information" that identifies
the structure of your descriptive flexfield. Enter a value only if you are
importing the descriptive flexfield "Journals - Captured Information"
without validation. If you enter a value, you can also enter some
combination of values in the columns ATTRIBUTE11 through
ATTRIBUTE20.
INVOICE_DATE: Enter the date on which you paid or collected tax
on your tax journal entry line. Enter the date in the format DD-MON-
YY or the default date format for your language. Your invoice date
should correspond to the date when tax amounts were paid or received
for this invoice. You must use this column if you import data for
the Value Added Tax Descriptive Flexfield.
INVOICE_AMOUNT: Enter an invoice amount. Enter the net invoice
amount that relates to your tax journal entry line amount. You must use
this column if you import data for the Value Added Tax Descriptive
Flexfield.
TAX_CODE: Enter a valid tax code that identifies the type of tax paid
for this invoice. You define a list of valid tax codes for this field when
you define your descriptive flexfield values. You must use this column
if you import data for the Value Added Tax Descriptive Flexfield.
INVOICE_IDENTIFIER: Enter an invoice identifier. Enter reference
information about the source document or invoice upon which you paid
or collected tax. You must use this column if you import data for
the Value Added Tax Descriptive Flexfield.

Potrebbero piacerti anche