Results for “setup_step_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_LEDGER_CONFIG_DETAILS is a General Ledger configuration table in the GL schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. The table stores the detail lines that make up a ledger configuration: the primary ledger together with its associated secondary ledgers, legal entities, reporting currencies, and the individual setup steps required to complete each configuration. It functions as the transactional backbone of the Accounting Setup Manager, recording which accounting objects belong to a given configuration and the processing state of each associated setup task.

The table carries twelve documented columns and a single documented unique index, GL_LEDGER_CONFIG_DETAILS_U1, defined over CONFIGURATION_ID, OBJECT_ID, OBJECT_TYPE_CODE, and SETUP_STEP_CODE. Its foreign key relationship points to GL_LEDGER_CONFIGURATIONS via CONFIGURATION_ID, establishing the parent-child dependency between a configuration header and its detail rows. Under the heuristic Data Vault classification mined from the foreign key structure, this object is satellite-leaning: it holds descriptive and status attributes that hang off the GL_LEDGER_CONFIGURATIONS parent rather than acting as an independent hub or as a pure many-to-many link.

Key Information Stored

The principal columns in GL_LEDGER_CONFIG_DETAILS are:

• CONFIGURATION_ID — Foreign key to GL_LEDGER_CONFIGURATIONS; identifies the parent accounting configuration to which the detail row belongs and is the leading column of the unique index.
• OBJECT_ID — Identifier of the specific accounting object referenced by the row, such as a ledger, legal entity, or reporting currency definition. Combined with the configuration, object type, and setup step, it forms the business-key candidate.
• OBJECT_TYPE_CODE — Classifies the object referenced by OBJECT_ID, distinguishing primary ledgers, secondary ledgers, legal entities, and reporting currencies within a single configuration.
• OBJECT_NAME — Descriptive name of the associated object, denormalized for display in the configuration and setup user interfaces.
• SETUP_STEP_CODE — Identifies the particular configuration or setup step the row represents, allowing a single object to participate in multiple steps of the accounting setup flow.
• NEXT_ACTION_CODE — Indicates the next action required to advance the row through its setup lifecycle.
• STATUS_CODE — Current processing or completion status of the detail row, used to determine whether a setup step is complete, pending, or in error.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard Oracle EBS who-did-what and when tracking.

The surrogate/business key distinction is important: no single-column primary key is documented. Instead, GL_LEDGER_CONFIG_DETAILS_U1 serves as the business-key candidate, and CONFIGURATION_ID doubles as the parent foreign key.

Common Use Cases and Queries

Typical uses include auditing which secondary ledgers, legal entities, and reporting currencies are attached to each primary ledger configuration, and monitoring the status of accounting setup steps during implementation or after configuration changes.

A representative query joins the detail rows to their configuration header and filters by object type and status:

SELECT d.CONFIGURATION_ID, d.OBJECT_TYPE_CODE, d.OBJECT_NAME, d.SETUP_STEP_CODE, d.STATUS_CODE, d.NEXT_ACTION_CODE FROM gl.gl_ledger_config_details d WHERE d.CONFIGURATION_ID = :p_config_id ORDER BY d.SETUP_STEP_CODE;

Reporting extracts commonly aggregate by OBJECT_TYPE_CODE to count legal entities or reporting currencies per configuration, or filter on STATUS_CODE to surface incomplete setups. Because the table is a satellite of GL_LEDGER_CONFIGURATIONS, configuration-level reporting normally drives from the parent and joins downward.

Related Objects

• GL_LEDGER_CONFIGURATIONS — Parent table; join on GL_LEDGER_CONFIG_DETAILS.CONFIGURATION_ID = GL_LEDGER_CONFIGURATIONS.CONFIGURATION_ID. This is the only documented foreign key.
• GL_LEDGERS — Defines the primary and secondary ledgers referenced through OBJECT_ID when OBJECT_TYPE_CODE denotes a ledger.
• GL_LEGAL_ENTITIES — Legal entity definitions associated with configurations through the detail rows.
• GL_LEDGER_RELATIONSHIPS — Records primary-to-secondary ledger relationships established by completed configuration steps.
• GL_LEDGER_CONFIGURATIONS related setup and status objects in the GL schema are commonly queried alongside this table when reconciling Accounting Setup Manager output.