Search Results gl_ledg_map




Overview
Explore in AI Chat

Overview

The GL_LEDG_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. Its primary function is to manage the mapping relationship between operational entities and financial ledgers. This mapping is critical for ensuring that manufacturing and inventory transactions, which originate at the organization level, are correctly posted to the appropriate General Ledger. By defining the link between a specific company code (CO_CODE) and organization (ORGN_CODE) to a specific ledger (LEDGER_CODE), this table enables the seamless flow of financial data from operational modules into the centralized GL, maintaining financial integrity and supporting accurate financial reporting.

Key Information Stored

The table's structure centers on establishing a unique mapping key and its associated ledger reference. The primary identifier is the LEDG_MAP_ID. The core mapping logic is defined by the combination of CO_CODE (Company Code) and ORGN_CODE (Organization Code), which together form a unique key (GL_LEDG_MAP_U1). This pair is then mapped to a specific LEDGER_CODE. The table also includes standard WHO columns for tracking creation and last update details, such as CREATED_BY and LAST_UPDATE_DATE. The foreign key constraints explicitly detail its relationships: LEDGER_CODE references GL_LDGR_MST, CO_CODE references GL_PLCY_MST, and ORGN_CODE references SY_ORGN_MST_B and SY_ORGN_MST, highlighting its integration with foundational master data for ledgers, accounting policies, and organizations.

Common Use Cases and Queries

The primary use case is to determine the correct General Ledger for posting transactions from a given manufacturing or inventory organization within a specific company. This is essential during period-end closing, cost accounting, and financial reconciliation processes. A common query retrieves the ledger for a specific organization to validate or drive interface posting. For example: SELECT ledger_code FROM gmf.gl_ledg_map WHERE co_code = :p_co_code AND orgn_code = :p_orgn_code; Another typical reporting use case involves listing all organization-to-ledger mappings for audit or setup verification: SELECT glmap.orgn_code, orgmst.orgn_name, glmap.co_code, glmap.ledger_code, ldgr.ledger_name FROM gmf.gl_ledg_map glmap JOIN sy_orgn_mst orgmst ON glmap.orgn_code = orgmst.orgn_code JOIN gl_ldgr_mst ldgr ON glmap.ledger_code = ldgr.ledger_code ORDER BY glmap.co_code, glmap.orgn_code; This table is often accessed by GMF-specific programs and interfaces that prepare journal entries for the General Ledger.

Related Objects

GL_LEDG_MAP is intrinsically linked to several key master data tables via foreign key constraints, forming a central hub in the GMF-to-GL data architecture. Its primary relationships are:

  • GL_LDGR_MST: Provides the ledger master information for the mapped LEDGER_CODE.
  • GL_PLCY_MST: Provides the accounting policy and company master information for the mapped CO_CODE.
  • SY_ORGN_MST_B / SY_ORGN_MST: Provide the organization master details for the mapped ORGN_CODE.
Given its role, it is also a likely reference point for various GMF transaction tables and subledger accounting setup tables within the Process Manufacturing suite, which rely on this mapping to determine the correct financial context for transactional data.