Search Results gl_sets_of_books_uk1

Overview

GL_SETS_OF_BOOKS is the foundational General Ledger configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of each set of books (known as a ledger in Release 12 terminology), which represents the financial reporting entity that combines a chart of accounts, an accounting calendar, a functional currency, and a subledger accounting method. Every accounting entry, journal batch, and subledger transaction in Oracle EBS ultimately resolves to a set of books through its SET_OF_BOOKS_ID, making this table the central anchor for financial data across the applications.

From a Data Vault modeling perspective, the heuristic FK analysis classifies GL_SETS_OF_BOOKS as hub-leaning. This suggests it behaves primarily as a hub entity that distributes its business key to a large number of dependent satellites and links. The table publishes SET_OF_BOOKS_ID as the surrogate identity and NAME as the business key, with dozens of downstream tables referencing it, consistent with a hub-and-link structure.

Key Information Stored

The table is uniquely identified by its surrogate primary key, SET_OF_BOOKS_ID, defined through the GL_SETS_OF_BOOKS_PK constraint. A business-key candidate is documented via the unique index GL_SETS_OF_BOOKS_UK1, which enforces uniqueness on NAME, the set of books (ledger) name. The most significant columns documented in the metadata include:

• CURRENCY_CODE — the functional currency, referencing FND_CURRENCIES. Determines the currency in which all accounting balances are maintained.
• PERIOD_SET_NAME — the accounting calendar period set, referencing GL_PERIOD_SETS. Defines the fiscal period structure.
• ACCOUNTED_PERIOD_TYPE — the period type used for accounting, referencing GL_PERIOD_TYPES.
• TRANSACTION_CALENDAR_ID — links the ledger to its transaction calendar in GL_TRANSACTION_CALENDAR.
• DAILY_TRANSLATION_RATE_TYPE — the default rate type for currency translation, referencing GL_DAILY_CONVERSION_TYPES.
• RET_EARN_CODE_COMBINATION_ID, NET_INCOME_CODE_COMBINATION_ID, CUM_TRANS_CODE_COMBINATION_ID, ROUNDING_CODE_COMBINATION_ID, and RES_ENCUMB_CODE_COMBINATION_ID — all foreign keys into GL_CODE_COMBINATIONS defining the Accounts for retained earnings, net income, cumulative translation adjustment, rounding, and encumbrance reserve.

Common Use Cases and Queries

The most common access pattern is resolving a SET_OF_BOOKS_ID to its name, currency, and chart of accounts. For example:

SELECT sob.set_of_books_id, sob.name, sob.currency_code, sob.period_set_name FROM gl_sets_of_books sob WHERE sob.set_of_books_id = :p_sob_id;

Reporting queries frequently join set of books to FND_CURRENCIES and GL_PERIOD_SETS to produce ledgers with their functional currency and calendar. In multi-org and multi-ledger environments, analysts join GL_SETS_OF_BOOKS to GL_MC_BOOK_ASSIGNMENTS using SET_OF_BOOKS_ID to map primary versus reporting ledgers. Migration and upgrade validation scripts count sets of books and compare their configuration attributes. Because the table is central, it is commonly used as the driving table in subledger reconciliation reports, where subledger transactions are grouped by SET_OF_BOOKS_ID.

Related Objects

The set of books hub is referenced by an extensive set of dependent tables. The most significant include:

• GL_SYSTEM_SETUP — holds ledger-level control options, joined on SET_OF_BOOKS_ID.
• GL_CODE_COMBINATIONS — the chart of accounts, referenced by the several code combination columns above.
• GL_PERIOD_SETS and GL_PERIOD_TYPES — define the accounting calendar structure.
• GL_MC_BOOK_ASSIGNMENTS, GL_MC_CONVERSION_RULES, and GL_MC_REPORTING_OPTIONS — manage multiple reporting currencies, referencing PRIMARY_SET_OF_BOOKS_ID and REPORTING_SET_OF_BOOKS_ID.
• AP_CHECK_TRANSMISSIONS and AP_INVOICE_TRANSMISSIONS — subledger transmissions keyed by SET_OF_BOOKS_ID.
• PO_DISTRIBUTIONS_ALL and RCV_RECEIVING_SUB_LEDGER — procurement and receiving accounting linked by SET_OF_BOOKS_ID.
• CE_SYSTEM_PARAMETERS_ALL — cash management setup referencing the ledger.

These relationships confirm the table's role as the enterprise-wide anchor for financial configuration and accounting transaction data.