Search Results gl_auto_alloc_sets_pk1

Overview

GL_AUTO_ALLOC_SETS is a General Ledger configuration table in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2) that stores the definition header for autoallocation sets. An autoallocation set is the container that groups a sequence of individual allocation formulas so that they can be executed together as a batch. The set definition determines whether the member allocations run in step-down mode—where the output of one allocation becomes the input basis for the next—or in parallel mode, where each formula is calculated independently against the same source balances.

The table resides in the GL schema and holds 33 documented columns in the 12.2.2 ETRM record. Its primary key is GL_AUTO_ALLOC_SETS_PK1, defined on ALLOCATION_SET_ID, with a unique index GL_AUTO_ALLOC_SETS_U1 also on ALLOCATION_SET_ID. From a dimensional modeling perspective, the FK topology suggests a hub-leaning classification: the table is the durable identity anchor for an allocation set, referenced by transactional and historical child tables rather than itself accumulating changing descriptive payloads.

Key Information Stored

The most significant columns in the documented schema are:

• ALLOCATION_SET_ID — surrogate primary key; the internal identifier for the set.
• ALLOCATION_SET_NAME — the user-visible name of the set, used throughout the Allocation Entry forms.
• ALLOCATION_SET_TYPE_CODE — indicates whether the set executes as step-down or parallel allocation.
• SET_OF_BOOKS_ID_11I — the ledger (set of books) to which the set belongs.
• CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE — accounting flexfield and calendar context, denormalized for validation and reporting.
• ALLOCATION_CODE — a short code used to identify the set programmatically.
• DESCRIPTION — free-text explanation of the set's purpose.
• SECURITY_FLAG — governs definition access security.
• ORG_ID — the operating unit context for multi-org filtering.
• OWNER, CONTEXT, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield and descriptive-flexfield context columns plus ownership metadata.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical reporting and support scenarios include listing all sets for a ledger, identifying step-down versus parallel sets, and tracing which batches consumed a given set definition.

• Enumerate sets for a ledger:
  SELECT allocation_set_id, allocation_set_name, allocation_set_type_code FROM gl_auto_alloc_sets WHERE set_of_books_id_11i = :ledger_id;
• Count sets by execution mode to audit allocation design:
  SELECT allocation_set_type_code, COUNT(*) FROM gl_auto_alloc_sets GROUP BY allocation_set_type_code;
• Trace batch execution history per set by joining GL_AUTO_ALLOC_BATCHES on ALLOCATION_SET_ID.
• Reconcile definition changes against GL_AUTO_ALLOC_SET_HISTORY for audit trails.

Related Objects

• GL_SETS_OF_BOOKS — joined via GL_AUTO_ALLOC_SETS.SET_OF_BOOKS_ID; supplies ledger context.
• GL_AUTO_ALLOC_BATCHES — references GL_AUTO_ALLOC_SETS.ALLOCATION_SET_ID; records each batch run of the set.
• GL_AUTO_ALLOC_SET_HISTORY — references GL_AUTO_ALLOC_SETS.ALLOCATION_SET_ID; captures historical versions of the definition.
• GL_MGT_SEG_UPGRADE_H — referenced via CHART_OF_ACCOUNTS_ID per the FK metadata.
• GL_AUTO_ALLOC_FORMULAS / GL_AUTO_ALLOC_LINES — the member allocation formulas and their lines that constitute the set's contents.
• Allocation Entry and Generate Allocations concurrent programs — the standard forms and processes that read these definitions.