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.
ACTUAL_FLAG is either â€™Aâ€™, â€™Bâ€™, or â€™Eâ€™ for actual, budget, or encumbrance balances, respectively. If ACTUAL_FLAG is â€™Bâ€™, then BUDGET_VERSION_ID is required. If ACTUAL_FLAG is â€™Eâ€™, then ENCUMBRANCE_TYPE_ID is required.
GL_BALANCES stores period activity for an account in the PERIOD_NET_DR and PERIOD_NET_CR columns. The table stores the period beginning
balances in BEGIN_BALANCE_DR and BEGIN_BALANCE_CR.
An accountâ€™s yearâ€“toâ€“date balance is calculated as BEGIN_BALANCE_DR â€“ BEGIN_BALANCE_CR + PERIOD_NET_DR â€“ PERIOD_NET_CR.
Detail and summary foreign currency balances that are the result of posted foreign currency journal entries have TRANSLATED_FLAG set to â€™Râ€™, to indicate that the row is a candidate for revaluation.
For foreign currency rows, the begin balance and period net columns contain the foreign currency balance, while the begin balance and period net BEQ columns contain the converted functional currency balance.Detail foreign currency balances that are the result of foreign currency translation have TRANSLATED_FLAG set to â€™Yâ€™ or â€™Nâ€™. â€™Nâ€™ indicates that the translation is out of date (i.e., the account needs to be reâ€“translated). â€™Yâ€™ indicates that the translation is current.
Summary foreign currency balances that are the result of foreign currency translation have TRANSLATED_FLAG set to NULL. All summary account balances have TEMPLATE_ID not NULL. The columns that end in ADB are not used. Also, the REVALUATION_STATUS column is not
GL_CODE_COMBINATIONS stores valid account combinations for
each Accounting Flexfield structure within your Oracle General Ledger
application. Associated with each account are certain codes and flags,
including whether the account is enabled, whether detail posting or
detail budgeting is allowed, and others.
Segment values are stored in the SEGMENT columns. Note that each
Accounting Flexfield structure may use different SEGMENT columns
within the table to store the flexfield value combination. Moreover, the SEGMENT columns that are used are not guaranteed to be in any order.
The Oracle Application Object Library table FND_ID_FLEX_SEGMENTS stores information about which column in this table is used for each segment of each Accounting Flexfield
structure. Summary accounts have SUMMARY_FLAG = â€™Yâ€™ and TEMPLATE_ID not NULL. Detail accounts have SUMMARY_FLAG = â€™Nâ€™ and TEMPLATE_ID NULL.