Results for “gl_acct_cls”
26 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
GMF.GL_ACCT_CLS is a reference table within the Oracle Process Manufacturing Financials (GMF) module that stores user-defined account classes. Account classes are classification codes applied to accounting entities to support reporting and grouping; they carry no posting or balance-generation logic. The object is documented as VALID in both Oracle E-Business Suite 12.1.1 and 12.2.2 and contains 10 physical columns under the GMF schema. Notably, the ETRM documentation states that this table is not used under Oracle Financials Integrated setup; it therefore matters only to environments where GMF maintains its own subledger accounting rather than deferring to the Financials application suite.
From a Data Vault modeling perspective, the mined foreign-key structure classifies GL_ACCT_CLS as hub-leaning: it holds a single natural business key with no downward FK dependencies of its own, and it is referenced by GL_ACCT_MST. This suggests treating ACCT_CLASS_CODE as a hub key with the descriptive attributes carried in an associated satellite.
Key Information Stored
The table is anchored by the unique index GL_ACCT_CLS_PK on ACCT_CLASS_CODE, which functions both as the primary key and as the business-key candidate. The principal descriptive column is ACCT_CLASS_DESC, which holds the user-facing name of the account class used in reports and list-of-values prompts. TEXT_CODE provides an additional short code or tag used for lookup and display flexibility, while TRANS_CNT stores a transaction-use counter consistent with GMF reference-table conventions.
The remaining columns are standard Oracle EBS audit and lifecycle attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture who created and last modified each row and when, supporting audit trails and concurrent-program attribution. DELETE_MARK implements the soft-delete flag typical of GMF tables, allowing rows to be logically retired without physical removal so that historical account assignments remain resolvable.
Common Use Cases and Queries
The primary use case is populating and validating account-classification prompts and driving reporting groupings. A typical lookup joins the classification to the master account table:
SELECT c.acct_class_code, c.acct_class_desc FROM gmf.gl_acct_cls c WHERE c.delete_mark = 0 ORDER BY c.acct_class_code;SELECT m.acct_class_code, c.acct_class_desc, COUNT(*) FROM gmf.gl_acct_mst m JOIN gmf.gl_acct_cls c ON c.acct_class_code = m.acct_class_code GROUP BY m.acct_class_code, c.acct_class_desc;- Audit trail extraction:
SELECT acct_class_code, created_by, creation_date, last_updated_by, last_update_date FROM gmf.gl_acct_cls WHERE last_update_date >= :p_since;
These patterns support configuration validation (identifying orphaned or unused classes), data-conversion reconciliation when migrating account masters, and report parameter lists where the description, not the code, must be presented to the user.
Related Objects
The documented relationship surface is narrow but precise:
- GMF.GL_ACCT_MST — the principal dependent table. Its column ACCT_CLASS_CODE carries a foreign key to GL_ACCT_CLS.ACCT_CLASS_CODE, making GL_ACCT_MST the child in the relationship and the object most affected by any change to GL_ACCT_CLS rows.
- GL_ACCT_CLS_PK — the unique index on ACCT_CLASS_CODE that enforces key integrity and serves as the join anchor for GL_ACCT_MST.
Because GL_ACCT_CLS is a leaf-level reference table with no outgoing foreign keys, no further parent dependencies are documented. Any reporting view or concurrent program that resolves account descriptions through GL_ACCT_MST will transitively depend on this table, so changes to account-class values should be assessed against downstream GL reporting extracts and any GMF financial inquiry screens that display the class description.
-
User-defined Account classes. These classes are used to classify accounts and are used for reporting purposes only. Note that this table is not used under Oracle Financials Integrated setup.
-
User-defined Account classes. These classes are used to classify accounts and are used for reporting purposes only. Note that this table is not used under Oracle Financials Integrated setup.
-
TABLE: GMF.GL_ACCT_CLS 12.2.2
-
TABLE: GMF.GL_ACCT_CLS 12.1.1
-
SYNONYM: APPS.GL_ACCT_CLS 12.1.1
-
SYNONYM: APPS.GL_ACCT_CLS 12.2.2
-
VIEW: GMF.GL_ACCT_CLS# 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
VIEW: GMF.GL_ACCT_CLS# 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
Contains the Company specific Chart of Accounts. Note that in the Oracle Financials integrated setup this table is populated with Oracle Financials Accounts while entering the Account Mapping information.
-
Contains the Company specific Chart of Accounts. Note that in the Oracle Financials integrated setup this table is populated with Oracle Financials Accounts while entering the Account Mapping information.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - GMF Tables and Views 12.2.2
Defines Third-Party software which has a supported interface to OPM.
-
eTRM - GMF Tables and Views 12.1.1
Defines Third-Party software which has a supported interface to OPM.
-
eTRM - GMF Tables and Views 12.2.2
Defines Third-Party software which has a supported interface to OPM.
-
eTRM - GMF Tables and Views 12.1.1
Defines Third-Party software which has a supported interface to OPM.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1