Search Results gl_acct_usg




Overview

The GL_ACCT_USG table is a core data object within the Oracle E-Business Suite module GMF (Process Manufacturing Financials). It serves as a repository for user-defined account usage codes, which are classification tags applied to general ledger accounts for specialized reporting and analytical purposes specific to process manufacturing operations. A critical distinction, as noted in the official documentation, is that this table and its associated functionality are designed for standalone GMF implementations. It is explicitly not utilized when GMF is integrated with Oracle Financials, where such classifications would be managed through the core GL (General Ledger) module's structures.

Key Information Stored

The primary data stored in this table is the account usage code itself, which acts as a unique identifier. The table's structure is defined by its primary key constraint, GL_ACCT_USG_PK, on the column ACCT_USAGE_CODE. While the provided metadata does not list additional columns, typical usage code tables in EBS often include descriptive fields such as a name (ACCT_USAGE_NAME), an enabled flag, a description, and audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY). The central purpose of each record is to define a distinct categorization, such as "Cost of Goods Sold," "Inventory Valuation," or "Production Overhead," that can be assigned to accounts for internal financial reporting within the process manufacturing context.

Common Use Cases and Queries

The primary use case is the generation of internal financial reports that group accounts by their manufacturing-related purpose, rather than by a standard chart of accounts segment. For instance, a report summarizing all accounts tagged for inventory valuation across multiple legal entities. Common queries involve selecting all defined usages or joining to the account master table. A fundamental query pattern is joining GL_ACCT_USG to its related account master table to list accounts by their usage.

  • Listing all defined account usage codes: SELECT acct_usage_code FROM gmf.gl_acct_usg ORDER BY 1;
  • Finding accounts assigned to a specific usage (via foreign key relationship): SELECT mst.* FROM gmf.gl_acct_mst mst WHERE mst.acct_usage_code = '&USAGE_CODE';

Related Objects

The most significant related object is the GL_ACCT_MST table, also in the GMF schema. A foreign key constraint exists from GL_ACCT_MST.ACCT_USAGE_CODE to GL_ACCT_USG.ACCT_USAGE_CODE, enforcing referential integrity. This relationship means that an account usage code must be defined in GL_ACCT_USG before it can be assigned to a general ledger account record in GL_ACCT_MST. This design ensures consistency in the classification of accounts for reporting. Other related objects would likely include GMF-specific reports, forms, and possibly value sets that reference this table to provide lists of valid account usages during data entry.