Results for “acct_usage_code”

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

Overview

GL_ACCT_USG is a reference table owned by the GMF schema (Process Manufacturing Financials) in Oracle EBS 12.1.1 and 12.2.2. It stores user-defined Account Usage codes that are consumed for reporting purposes within Oracle Process Manufacturing. Per the documented description, these codes are informational only; the table is explicitly noted as not used with the Oracle Financials integrated setup. Its documented status is VALID, and its role in the EBS data model is that of a small, stable lookup/code table that classifies accounts by usage category rather than driving subledger or GL posting logic.

From a Data Vault modeling perspective, the mined FK structure classifies GL_ACCT_USG as hub-leaning. This is a modeling suggestion: the table behaves like a hub, anchored on a single business code (ACCT_USAGE_CODE) that uniquely identifies each usage definition, with descriptive and audit attributes attached. It is not a transactional link and is not a satellite of another hub; it is the parent side of a relationship.

Key Information Stored

The documented physical schema in ETRM 12.2.2 contains 10 columns. The most significant are:

• ACCT_USAGE_CODE — the primary key column and the single unique index (GL_ACCT_USG_PK). This is the business-key candidate: the human-readable code used to identify an account usage.
• ACCT_USAGE_DESC — the descriptive text explaining the meaning of the usage code, which is what users see on reports and in setup forms.
• TEXT_CODE — an additional coding attribute associated with the usage definition.
• TRANS_CNT — a transaction/counter column, typically used for concurrency or tracking against the record.
• DELETE_MARK — the standard OPM soft-delete flag. Rows are logically deactivated rather than physically removed, so any query must filter on this column.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN record who created and most recently modified each row.

Note the distinction: ACCT_USAGE_CODE is both the physical primary key (via GL_ACCT_USG_PK) and the only documented unique business-key candidate. There is no separate surrogate numeric key documented in the metadata; the code itself serves as the identifier.

Common Use Cases and Queries

The typical use case is reporting and validation: confirming which usage codes are defined and currently active before assigning them to accounts. A standard lookup query follows the OPM conventions of filtering the soft-delete flag:

• SELECT acct_usage_code, acct_usage_desc FROM gl_acct_usg WHERE delete_mark = 0 ORDER BY acct_usage_code;
• Validation pattern before inserting into GL_ACCT_MST: SELECT COUNT(*) FROM gl_acct_usg WHERE acct_usage_code = :code AND delete_mark = 0;
• Reporting pattern joining accounts to their usage description: SELECT m.account, u.acct_usage_desc FROM gl_acct_mst m, gl_acct_usg u WHERE m.acct_usage_code = u.acct_usage_code AND u.delete_mark = 0;

Because the table is disclosure-only and not integrated with Oracle Financials, it should not be used for GL balance derivation, posting rules, or subledger accounting logic.

Related Objects

• GL_ACCT_MST — the principal dependent table. It carries a foreign key on ACCT_USAGE_CODE referencing GL_ACCT_USG (GL_ACCT_MST.ACCT_USAGE_CODE → GL_ACCT_USG.ACCT_USAGE_CODE). This is the one documented inbound relationship and defines the join used in nearly all reporting.

No other tables, views, or public APIs are documented in the ETRM metadata as referencing GL_ACCT_USG. Any additional dependencies should be confirmed against the live 12.1.1/12.2.2 data dictionary before being relied upon.