Results for “gl_temporary_combinations”

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

Overview

GL_TEMPORARY_COMBINATIONS is a General Ledger staging table that stores newly created account combinations prior to, or in parallel with, their validation and propagation into the definitive GL_CODE_COMBINATIONS table. It is populated primarily by concurrent processes such as summary account template generation and mass allocation creation, which need to enumerate candidate segment combinations before committing them to the chart of accounts. The table carries a REQUEST_ID foreign key to FND_CONCURRENT_REQUESTS, confirming that rows are scoped to a specific concurrent program run, and a TEMPLATE_ID foreign key to GL_SUMMARY_TEMPLATES, tying each staged combination to the summary template that generated it. An additional relationship exists from CHART_OF_ACCOUNTS_ID to GL_MGT_SEG_UPGRADE_H, indicating use during chart of accounts structure upgrade and re-mapping activity.

Under a heuristic Data Vault classification, the table behaves as a link, since its dominant purpose is to record associations between a concurrent request, a summary template, a chart of accounts, and a prospective code combination rather than to serve as a durable descriptive hub. It is transient by nature; rows are typically consumed and cleared once validation completes.

Key Information Stored

The table comprises 52 documented columns. The most operationally significant are listed below.

• REQUEST_ID — identifies the concurrent request that produced the staged rows; joins to FND_CONCURRENT_REQUESTS.
• TEMPLATE_ID — references the GL_SUMMARY_TEMPLATES definition responsible for generating the combination.
• CHART_OF_ACCOUNTS_ID — identifies the target chart of accounts structure; related to GL_MGT_SEG_UPGRADE_H.
• CODE_COMBINATION_ID — the identifier assigned once the combination is created in GL_CODE_COMBINATIONS.
• SEGMENT1 through SEGMENT30 — the individual accounting flexfield segment values that together form the prospective account combination.
• ACCOUNT_TYPE — classifies the combination (for example asset, liability, expense, or summary).
• DESCRIPTION — free-form text associated with the new combination.
• ALLOCATION_CREATE_FLAG — indicates whether the row was produced by an allocation creation process.
• START_DATE_ACTIVE / END_DATE_ACTIVE — define the effective active period of the combination.
• ATTRIBUTE1 through ATTRIBUTE10, plus CONTEXT — descriptive flexfield context and attribute values.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — standard audit columns.

The metadata does not document a single-column surrogate primary key or unique index; the practical business key is the tuple of segment values (SEGMENT1–SEGMENT30) combined with CHART_OF_ACCOUNTS_ID for a given REQUEST_ID.

Common Use Cases and Queries

Typical usage centers on auditing which candidate combinations a concurrent process attempted to create, and reconciling those against the final GL_CODE_COMBINATIONS entries. A common pattern joins the staging table to the concurrent request and summary template:

• List staged combinations for a request: SELECT segment1, segment2, segment3, code_combination_id FROM gl_temporary_combinations WHERE request_id = :req_id;
• Join to template metadata: SELECT t.segment1, t.segment2, s.name FROM gl_temporary_combinations t, gl_summary_templates s WHERE t.template_id = s.template_id;
• Monitor producing programs: SELECT r.concurrent_program_id, r.phase_code FROM fnd_concurrent_requests r, gl_temporary_combinations t WHERE r.request_id = t.request_id GROUP BY r.concurrent_program_id, r.phase_code;
• Reconcile staged versus confirmed combinations by matching on CODE_COMBINATION_ID or segment values.

Related Objects

• GL_CODE_COMBINATIONS — the definitive chart of accounts; receives validated staged combinations.
• GL_SUMMARY_TEMPLATES — joined via TEMPLATE_ID; drives summary account generation.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID; provides program run context.
• GL_MGT_SEG_UPGRADE_H — related through CHART_OF_ACCOUNTS_ID during structure upgrades.
• GL_ACCOUNT_HIERARCHIES / GL_SUMMARY_ACCOUNTS — downstream consumers of generated combinations.
• FND_FLEX_VALUES / FND_FLEX_VALUES_VL — validate individual segment values before promotion.