Search Results po_vgld_cls

Overview

The GL_ACCT_MAP table is a core data object within the Process Manufacturing Financials (GMF) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the central repository for General Ledger (GL) account mapping rules, which are critical for the automated determination of accounting flexfield combinations during transactional processing. The table stores predefined mappings that link specific business entities and attributes—such as items, resources, warehouses, and customers—to specific GL accounts. These mappings are defined based on a combination of company (legal entity), account title type, and other key attributes that have a priority greater than zero in the related GL_ACCT_HRC table, ensuring a structured and hierarchical approach to account derivation.

Key Information Stored

The table's primary function is to associate transactional attributes with a specific GL account identifier (ACCT_ID). While the full column list is not detailed in the provided excerpt, the foreign key relationships reveal the critical dimensions used for mapping. The core identifier columns include CO_CODE (company), ACCT_TTL_TYPE (account title type), and ACCT_ID (the target GL account). The extensive list of foreign keys indicates the table stores numerous attribute columns to facilitate precise mapping, such as ITEM_ID, RESOURCES, WHSE_CODE, ROUTING_ID, CUST_ID, VENDOR_ID, ORGN_CODE, COST_ANALYSIS_CODE, and various GL class codes (e.g., ICGL_CLASS, CUSTGL_CLASS). This structure allows the system to select the correct accounting flexfield based on the specific context of a manufacturing, inventory, or purchasing transaction.

Common Use Cases and Queries

The primary use case is the real-time derivation of accounts for journal entry generation. For instance, when a costed production batch is completed, the GMF costing engine references GL_ACCT_MAP using the item, resource, organization, and other transaction line details to post the appropriate inventory and cost of goods sold accounting. A common reporting need is to audit or review the mapping rules for a specific account title or company. A sample query pattern would be:

SELECT gam.co_code, gam.acct_ttl_type, gl_flexfields_pkg.get_description_sql(gam.acct_id) account_desc,
iim.item_no, crs.resource_code, icw.whse_code
FROM gmf.gl_acct_map gam,
ic_item_mst iim,
cr_rsrc_mst crs,
ic_whse_mst icw
WHERE gam.item_id = iim.item_id (+)
AND gam.resources = crs.resource_id (+)
AND gam.whse_code = icw.whse_code (+)
AND gam.co_code = :p_company
ORDER BY gam.acct_ttl_type;

Related Objects

GL_ACCT_MAP has a dense network of foreign key relationships, highlighting its integrative role. Key related objects include:

• GL_ACCT_MST and GL_ACCT_TTL: Joined via ACCT_ID and ACCT_TTL_TYPE, these define the target account and account title classification.
• GL_PLCY_MST: Joined via CO_CODE, defining the company policy.
• Master Data Tables: The table links to numerous foundational masters, including IC_ITEM_MST (ITEM_ID), CR_RSRC_MST (RESOURCES), IC_WHSE_MST (WHSE_CODE), OP_CUST_MST (CUST_ID), PO_VEND_MST (VENDOR_ID), and SY_ORGN_MST (ORGN_CODE).
• Process Manufacturing Objects: Links to GMD_ROUTINGS_B / FM_ROUT_HDR (ROUTING_ID) and CM_CMPT_MST (COST_CMPNTCLS_ID) for costing and routing integration.
• Class Code Tables: References like IC_GLED_CLS (ICGL_CLASS), OP_CGLD_CLS (CUSTGL_CLASS), and PO_VGLD_CLS (VENDGL_CLASS) provide additional grouping attributes for mapping.