GL Tables

GL_ACCOUNT_HIERARCHIES stores lists of the detail accounts associated with each summary account. When you create a summary account, the list of its detail accounts is stored in this table, one detail account per row. This table stores one such list for each summary account.

GL_ALLOC_BATCHES stores information about MassAllocation and MassBudget batches. Each row includes a batch’s unique ID, name, status, and description. This table corresponds to the Define MassAllocations and Define MassBudget windows of the Define MassAllocations and Define MassBudgets forms.

GL_ALLOC_FORMULAS stores information about MassAllocation and MassBudget formulas.

GL_ALLOC_FORMULA_LINES stores information about MassAllocation and MassBudget formula lines. This table corresponds to the Formula window of the Define MassAllocations and Define MassBudgets forms. There are four or five lines associated with each MassBudget formula, and there are five lines associated with each MassAllocation formula.

GL_ALLOC_HISTORY stores one row for each batch produced by generating MassAllocation and MassBudget journals. Use information in this table to determine when you generated your MassAllocation and MassBudget journals, and for which accounting periods.

GL_BALANCES stores actual, budget, and encumbrance balances for detail and summary accounts. This table stores functional currency, foreign currency, and statistical balances for each accounting period that has ever been opened.

GL_BUDGETS stores information about your budgets. Each row includes a budget’s name, first and last periods, date created, and status. This table corresponds to the Define Budget form. Oracle General Ledger supports only one budget type (’STANDARD’), so you can uniquely identify a row with only the budget name. The CURRENT_VERSION_ID column is not currently used.

GL_BUDGET_ASSIGNMENTS stores the accounts that are assigned to each budget organization.

GL_BUDGET_ASSIGNMENT_RANGES stores the account ranges that you want to assign to a budget organization.

GL_DAILY_RATES_INTERFACE is the interface you use to create, update, and delete daily conversion rates. Customers should use this table to load rates into the GL_DAILY_RATES table.
Foreign Keys
Primary Key Table Primary Key Column Foreign Key Column
FND_CURRENCIES CURRENCY_CODE FROM_CURRENCY
FND_CURRENCIES CURRENCY_CODE TO_CURRENCY
FND_USER USER_ID USER_ID
GL_DAILY_CONVERSION_TYPES USER_CONVERSION_TYPE USER_CONVERSION_TYPE
Not null columns
FROM_CURRENCY
TO_CURRENCY
FROM_CONVERSION_DATE
TO_CONVERSION_DATE
USER_CONVERSION_TYPE
CONVERSION_RATE
MODE_FLAG

GL_IEA_INTERFACE is used to import data into the Global Intercompany System from external systems. The data entered into this table is processed by the GIS Import program.
Foreign Keys
Primary Key Table Primary Key Column Foreign Key Column
FND_CONCURRENT _REQUESTS REQUEST_ID REQUEST_ID
FND_CURRENCIES CURRENCY_CODE CURRENCY_CODE
GL_CODE_COMBINATIONS CODE_COMBINATION_ID SENDER_CODE_COMBINATION_ID
GL_CODE_COMBINATIONS CODE_COMBINATION_ID SENDER_CODE_COMBINATION_ID
GL_IEA_SUBSIDIARIES SUBSIDIARY_ID SENDER_SUBSIDIARY_ID
GL_IEA_SUBSIDIARIES SUBSIDIARY_ID RECEIVER_SUBSIDIARY_ID
GL_IEA_TRANSACTION_TYPES TRANSACTION_TYPE_ID TRANSACTION_TYPE_ID
NOT NULL Columns
GROUP_ID
TRANSACTION_TYPE_ID
TRANSACTION_STATUS_CODE
CURRENCY_CODE
GL_DATE
SENDER_SUBSIDIARY_ID
RECEIVER_SUBSIDIARY_ID
LINE_TYPE

GL_INTERFACE is the table you use to import journal entry batches through Journal Import. You insert rows in this table and then use the Import Journals form to create journal batches. You must supply values for all NOT NULL columns.