Results for “gl_accu_mst_u1”

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

Overview

GL_ACCU_MST is a Process Manufacturing Financials (GMF) master table that stores user-defined Accounting Units. Accounting Units represent organizational divisions of a company — cost centers, departments, and divisions — that participate in the composition of an Account key. In the Oracle EBS 12.1.1 and 12.2.2 environments, this table acts as the authoritative registry of accounting unit definitions owned by the GMF schema and consumed across both Process Manufacturing and Oracle Financials integration points.

The object resides in the GMF schema and carries VALID status in the ETRM 12.2.2 documented schema with 14 columns. From a Data Vault modeling perspective, the heuristic classification derived from its foreign key topology is a hub: GL_ACCU_MST holds a stable business concept (the accounting unit) keyed by a surrogate identifier, with descriptive and transactional attributes attached. This classification is a modeling suggestion rather than a documented constraint.

Key Information Stored

The table is anchored by the surrogate primary key ACCTG_UNIT_ID through the GL_ACCU_MST_PK constraint. A second unique index, GL_ACCU_MST_U1, defines the business-key candidate (CO_CODE, ACCTG_UNIT_NO), which together uniquely identify an accounting unit within a company/ledger context.

• ACCTG_UNIT_ID — Surrogate primary key; the numeric identifier referenced by dependent transactional and mapping tables.
• ACCTG_UNIT_NO — Business-facing accounting unit number; part of the unique business key U1.
• CO_CODE — Company code; part of the business key and a foreign key to GL_PLCY_MST.
• ACCTG_UNIT_DESC — Descriptive name of the accounting unit (e.g., cost center or division label).
• START_DATE / END_DATE — Effective date range governing when the accounting unit is active.
• DELETE_MARK — Soft-delete / logical deletion indicator.
• TRANS_CNT — Transaction control/counter column used for concurrency or propagation logic.
• TEXT_CODE — User-defined classification or free-text code for the unit.
• CREATION_DATE, CREATED_BY — Audit columns capturing record creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit columns capturing the most recent modification and its responsible user session.

Common Use Cases and Queries

Typical uses include validating accounting unit definitions, driving account key derivation, and enriching financial reporting extracts with organizational context.

• Retrieving all active accounting units for a company:

  SELECT acctg_unit_id, acctg_unit_no, acctg_unit_desc
  FROM   gl_accu_mst
  WHERE  co_code = :p_co_code
  AND    delete_mark = 0
  AND    SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

• Joining to subordinate ledger or mapping tables to trace where a unit is used, e.g., linking GL_ACCU_MST.ACCTG_UNIT_ID to GL_ACCU_MAP.ACCTG_UNIT_ID or GL_SUBR_LED.ACCTG_UNIT_ID.
• Reporting hierarchies of accounting units per company for cost center and department analysis.

Related Objects

GL_ACCU_MST participates in a dense foreign key network across GMF and Oracle Financials integration objects.

• GL_PLCY_MST — Referenced via GL_ACCU_MST.CO_CODE; defines company/accounting policy context.
• GL_ACCT_KEY — References CO_CODE and ACCTG_UNIT_NO; composes account keys from accounting units.
• GL_ACCU_MAP — References ACCTG_UNIT_ID; maps accounting units to other structures.
• GL_ACCU_VAL — References CO_CODE and ACCTG_UNIT_NO; holds valid values for accounting units.
• GL_SUBR_LED and GL_SUBR_TST — Both reference ACCTG_UNIT_ID for subledger and test ledger postings.
• PO_DIST_DTL — References ACCTG_UNIT_ID, tying purchasing distribution lines to accounting units.
• IC_ADJS_JNL — References ACCTG_UNIT_ID for intercompany adjustment journal entries.