Results for “gl_acct_val”

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

Overview

The GL_ACCT_VAL table, owned by the GMF schema (Process Manufacturing Financials), is an Oracle E-Business Suite container that assigns validation codes to general ledger accounts. In the Process Manufacturing environment, accounts must be auto-generated only when their Accounting unit carries a matching validation code. This table therefore enforces the binding between an account and the validation codes that govern its auto-generation. An important restriction documented in the ETRM metadata is that this table is not used with an Oracle Financials integrated setup; its scope is confined to the Process Manufacturing (GMF) application boundary.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is link. This is a modeling suggestion rather than a physical fact: the table sits at the intersection of Account (GL_ACCT_MST), Validation Code (GL_VALN_CDS), and Text (GL_TEXT_HDR) reference data, and its natural role is to record the association among those entities rather than to serve as an independent hub or a descriptive satellite.

Key Information Stored

The documented physical schema for ETRM 12.2.2 comprises twelve columns. The most significant are:

• CO_CODE — the company (accounting) identifier, and part of the composite primary key. It joins to GL_ACCT_MST.
• ACCT_NO — the account number associated with the validation assignment. Together with CO_CODE it identifies the account in GL_ACCT_MST.
• VALIDATION_CODE — the validation code assigned to the account; joins to GL_VALN_CDS.
• TEXT_CODE — reference to a text header record via GL_TEXT_HDR, used to attach descriptive text to the assignment.
• INCLUDE_FLAG — a control flag indicating whether the record participates in downstream validation processing.
• TRANS_CNT — a transaction/count accumulator used for process manufacturing transactional tracking.
• DELETE_MARK — soft-delete indicator; a value of 1 marks the row as logically removed.
• CREATION_DATE, CREATED_BY — audit columns recording row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns capturing the most recent modification and login session.

The surrogate primary key constraint is GL_ACCT_VAL_PK, defined on (CO_CODE, ACCT_NO, VALIDATION_CODE). Because this composite uniquely identifies each row and is the same set of columns exposed through the unique index, it also serves as the business-key candidate for the link. Note that no separate single-column surrogate identifier exists in the documented schema; the primary key is entirely business-derived.

Common Use Cases and Queries

Typical uses include validating that an account may be auto-generated for a given accounting unit, reconciling validation code assignments, and auditing changes for period-end control. A representative join retrieves accounts with their assigned validation codes:

SELECT a.CO_CODE, a.ACCT_NO, v.VALIDATION_CODE, a.INCLUDE_FLAG
FROM   GMF.GL_ACCT_VAL a, GMF.GL_VALN_CDS v
WHERE  a.VALIDATION_CODE = v.VALIDATION_CODE
AND    a.DELETE_MARK = 0;

To trace the descriptive text attached to an assignment, join to GL_TEXT_HDR on TEXT_CODE. Reporting queries frequently filter on DELETE_MARK to exclude logically deleted rows and on INCLUDE_FLAG to isolate active validation assignments. Auditing queries aggregate by LAST_UPDATED_BY and LAST_UPDATE_DATE to establish change trails. Because this table is documented as unused in Oracle Financials integrated setups, any extraction targeting integrated environments should confirm that GMF validation logic is actually enabled before relying on these rows.

Related Objects

The following objects are the most significant dependencies, derived from the documented foreign keys:

• GL_ACCT_MST — the account master; joined via CO_CODE (and ACCT_NO) from GL_ACCT_VAL.
• GL_VALN_CDS — the validation code definitions; joined via VALIDATION_CODE.
• GL_TEXT_HDR — text header records; joined via TEXT_CODE.

In addition to these foreign-key targets, reporting and integration logic in the GMF module typically traverses from GL_ACCT_VAL toward the accounting unit and account generation routines that consume the validation code assignments. Queries should always respect the GMF schema ownership and the DELETE_MARK soft-delete convention when producing authoritative results.