Results for “co_code”

50+ results




Overview
Explore in AI Chat

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

Overview

GL_PLCY_LGR is a table owned by the GMF schema within Oracle E-Business Suite, associated with the Process Manufacturing Financials product family. The ETRM documentation describes its purpose succinctly as "Company ledgers." In practical terms, the table serves as a cross-reference or association object that binds an operating company (identified by CO_CODE) to a ledger (identified by LEDGER_CODE), allowing the Process Manufacturing Financials module to determine which accounting ledgers apply to which companies within the enterprise structure.

Because the table's primary key is a composite of two foreign-key columns drawn from two distinct master tables, a Data Vault modeling heuristic classifies GL_PLCY_LGR as a link table. This is a modeling suggestion rather than a contractual designation: the object functions as a relationship carrier between independent business entities (companies and ledgers) rather than as a descriptive hub or an attribute-bearing satellite. The table holds relatively little descriptive payload beyond its association semantics, which reinforces the link interpretation.

Key Information Stored

The documented physical schema for GL_PLCY_LGR in ETRM 12.2.2 contains ten columns. The following are the most significant:

  • CO_CODE — The company code. Part of the composite primary key and a foreign key to GL_PLCY_MST. It identifies the operating company or policy entity to which the ledger association applies.
  • LEDGER_CODE — The ledger code. The second component of the composite primary key and a foreign key to GL_LDGR_MST. It identifies the specific general ledger associated with the company.
  • TRANS_CNT — A transaction counter column, typically used to track the number of transactions or to support concurrency and audit tracking within process manufacturing financial flows.
  • TEXT_CODE — A code field referencing descriptive text, commonly used to store supplemental or user-defined context tied to the company-ledger relationship.
  • DELETE_MARK — The standard Oracle EBS soft-delete flag. Records are logically removed by setting this indicator rather than being physically deleted, preserving referential integrity.

The remaining columns are standard Oracle EBS audit and concurrency attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The unique index GL_PLCY_LGR_PK on (CO_CODE, LEDGER_CODE) constitutes the business-key candidate, meaning a given company-ledger pairing may appear only once. There is no separate single-column surrogate key documented; the composite of the two business columns serves both as the primary key and as the natural business identifier.

Common Use Cases and Queries

The most frequent use of this table is resolving which ledgers are valid for a given company. A typical query retrieves all ledgers associated with a company code:

SELECT l.CO_CODE, l.LEDGER_CODE FROM GMF.GL_PLCY_LGR l WHERE l.CO_CODE = :company AND NVL(l.DELETE_MARK,0) = 0;

The inverse lookup — identifying all companies tied to a particular ledger — follows the same pattern using LEDGER_CODE. Joining to GL_PLCY_MST and GL_LDGR_MST produces a human-readable report of company names and ledger names, which is useful for security validation, ledger assignment audits, and confirming that process manufacturing transactions will post to the correct ledger. Because the table acts as a link, reconciliation reporting frequently joins it against transaction and accounting entry tables to verify that vouchers were generated for a valid company-ledger combination.

Related Objects

  • GL_PLCY_MST — The company master. Joined on GL_PLCY_LGR.CO_CODE = GL_PLCY_MST.CO_CODE.
  • GL_LDGR_MST — The ledger master. Joined on GL_PLCY_LGR.LEDGER_CODE = GL_LDGR_MST.LEDGER_CODE.
  • GL_PLCY_LGR_PK — The unique index enforcing the composite business key (CO_CODE, LEDGER_CODE).
  • GL_JE_HEADERS / GL_JE_LINES — General ledger journal objects that indirectly depend on valid company-ledger pairings.

These relationships establish GL_PLCY_LGR as a compact but structurally important link table within the GMF financials schema.