Results for “gl_acct_map”

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

Overview

GL_ACCT_MAP is a Process Manufacturing Financials (GMF) table that stores General Ledger account mapping definitions used by Oracle Process Manufacturing to derive the correct GL account combination during accounting distribution. The table holds mapping rules that are qualified by company, account title, and any optional attributes whose priority is greater than zero in the gl_acct_hrc table. These optional attributes allow a single account title to be resolved to different GL accounts depending on dimensions such as item, warehouse, vendor, customer, organization, resource, routing, cost component class, or tax authority. The object resides in the GMF schema and is documented as valid within Oracle EBS 12.1.1 and 12.2.2, containing 68 columns in the ETRM 12.2.2 physical schema.

From a Data Vault modeling perspective, the mined classification for this table is a link. This is a reasonable suggestion because GL_ACCT_MAP primarily associates many independent business entities — company, account, item, vendor, customer, organization, warehouse, and others — through foreign keys. It can therefore be modeled as a link table connecting these hubs, with the descriptive columns treated as link attributes or as a dependent satellite.

Key Information Stored

The documented structure includes a small set of key drivers and a large number of optional context columns. The most important columns are:

• CO_CODE — Company code, referencing GL_PLCY_MST; the primary scoping attribute for a mapping rule.
• ACCT_TTL_TYPE — Account title type, referencing GL_ACCT_TTL; identifies the type of account title being mapped.
• ACCT_ID — The target GL account, referencing GL_ACCT_MST.
• ORGN_CODE — Organization code, referencing SY_ORGN_MST.
• WHSE_CODE — Warehouse code, referencing IC_WHSE_MST.
• ITEM_ID — Item identifier, referencing IC_ITEM_MST.
• VENDOR_ID — Vendor identifier, referencing PO_VEND_MST.
• CUST_ID (and OPM_CUST_ID) — Customer identifier, referencing OP_CUST_MST.
• RESOURCES — Resource identifier, referencing CR_RSRC_MST.
• ROUTING_ID — Routing identifier, referencing GMD_ROUTINGS_B / FM_ROUT_HDR.
• COST_CMPNTCLS_ID — Cost component class, referencing CM_CMPT_MST.
• CURRENCY_CODE — Currency, referencing GL_CURR_MST.
• REASON_CODE — Reason code, referencing SY_REAS_CDS.
• GL_CATEGORY_ID / GL_BUSINESS_CLASS_CAT_ID / GL_PRODUCT_LINE_CAT_ID — Category identifiers used for GL classification.
• ORDER_TYPE, LINE_TYPE, SOURCE_TYPE, MIGRATED_IND — Context and control attributes.

No explicit surrogate primary key is declared in the documented metadata; the natural business key is effectively the combination of CO_CODE, ACCT_TTL_TYPE, and the qualifying attribute columns. Administrative columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, DELETE_MARK, and thirty ATTRIBUTE1–30 columns with ATTRIBUTE_CATEGORY. TRANS_CNT and TEXT_CODE provide technical controls.

Common Use Cases and Queries

Typical usage centers on resolving the GL account for a given accounting event and on auditing mapping completeness. A representative query joining the company, account title, and target account might resemble:

• Resolve a company/account-title mapping: SELECT ACCT_ID, CURRENCY_CODE, ITEM_ID FROM GMF.GL_ACCT_MAP WHERE CO_CODE = :co AND ACCT_TTL_TYPE = :ttl AND DELETE_MARK = 0;
• Inspect attribute-qualified rules for a specific item or vendor: filter on ITEM_ID or VENDOR_ID in addition to the company and account title.
• Audit unmapped accounts: compare GL_ACCT_TTL against GL_ACCT_MAP to find account titles with no mapping for a given company.
• Report by cost component, resource, or routing to verify manufacturing account determination for process batches.
• Reconciliation reporting across source document types using SOURCE_TYPE, ORDER_TYPE, and LINE_TYPE.

Because many dimensions are optional, effective queries should always include the company and account title as the minimal predicate and apply DELETE_MARK = 0 to exclude logically deleted rows.

Related Objects

The FK metadata identifies the principal related objects and join columns:

• GL_PLCY_MST — joined on GL_ACCT_MAP.CO_CODE.
• GL_ACCT_TTL — joined on GL_ACCT_MAP.ACCT_TTL_TYPE.
• GL_ACCT_MST — joined on GL_ACCT_MAP.ACCT_ID.
• IC_ITEM_MST — joined on GL_ACCT_MAP.ITEM_ID.
• PO_VEND_MST / OP_CUST_MST — joined on VENDOR_ID and CUST_ID respectively.
• IC_WHSE_MST / SY_ORGN_MST — joined on WHSE_CODE and ORGN_CODE.
• CR_RSRC_MST / CM_CMPT_MST / GMD_ROUTINGS_B — joined on RESOURCES, COST_CMPNTCLS_ID, and ROUTING_ID.
• GL_CURR_MST / SY_REAS_CDS / TX_TAXA_MST — joined on CURRENCY_CODE, REASON_CODE, and TAXAUTH_ID.

These relationships confirm that GL_ACCT_MAP functions as a central link between GL configuration and the operational master data that drives process manufacturing account determination.