Results for “gl_plcy_sys”

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

Overview

GL_PLCY_SYS is an Oracle Process Manufacturing Financials (GMF) table that defines the fiscal policy sub-systems used by the EBS General Ledger integration. Within EBS 12.1.1 and 12.2.2, it acts as the configuration anchor that maps a given operating company (CO_CODE) to each transaction source code (TRANS_SOURCE_CODE) processed through the GMF-to-GL accounting pipeline. In effect, it establishes which transaction sources are governed by which fiscal policy master record and controls downstream posting behavior such as transaction counters and text-code assignment.

The ETRM heuristic Data Vault classification for this object is satellite-leaning. From a modeling perspective, this suggests GL_PLCY_SYS behaves as a descriptive satellite attached to the parent GL_PLCY_MST hub, since it carries its foreign key to that master, owns descriptive and audit attributes, and holds no independent business entity. The classification is a modeling suggestion only; in native EBS terms the table functions as a child detail of the policy master.

Key Information Stored

The primary key is defined by the unique index GL_PLCY_SYS_PK on the composite of CO_CODE and TRANS_SOURCE_CODE. This combination is the documented business-key candidate: it uniquely identifies one fiscal policy sub-system row per operating company per transaction source.

• CO_CODE — Operating company identifier; the leading PK column and the FK to GL_PLCY_MST.
• TRANS_SOURCE_CODE — The transaction source (e.g., inventory, purchasing, order entry) being governed by the fiscal policy; second PK column.
• TRANS_CNT — Transaction counter/sequence used to track processing activity for the source under the policy.
• TEXT_CODE — Descriptive code associated with the sub-system definition.
• DELETE_MARK — Soft-delete flag indicating logical removal without physical deletion.
• CREATION_DATE, CREATED_BY — Standard WHO audit columns recording row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent modification and session context.

No separate surrogate key column exists; the composite business key serves as the primary key.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include verifying which transaction sources are configured for a given company, reconciling GMF postings to GL, and tracing audit history. A representative query joins the child to its master:

• SELECT s.CO_CODE, s.TRANS_SOURCE_CODE, s.TRANS_CNT, s.TEXT_CODE, s.DELETE_MARK, m.* to enumerate sub-systems.
• FROM GMF.GL_PLCY_SYS s JOIN GMF.GL_PLCY_MST m ON s.CO_CODE = m.CO_CODE WHERE NVL(s.DELETE_MARK,'N') = 'N' to filter active rows and expose master policy attributes.
• Filtering on TRANS_SOURCE_CODE to confirm coverage of a specific source.
• Audit queries ordering by LAST_UPDATE_DATE / LAST_UPDATED_BY to trace configuration changes.
• Reconciliation extracts comparing TRANS_CNT against GL actuals to detect unposted activity.

Related Objects

• GL_PLCY_MST — The fiscal policy master; GL_PLCY_SYS.CO_CODE → GL_PLCY_MST.CO_CODE. This is the primary parent relationship.
• GL_PLCY_SYS_PK — The unique index enforcing the composite PK.
• GMF GL posting / accounting integration objects — Downstream processes that consume the fiscal policy sub-system mapping to route transactions by source.
• Standard WHO reference tables — FND_USER resolves CREATED_BY and LAST_UPDATED_BY identifiers.

Additional dependent objects are limited in the ETRM documentation; the FK to GL_PLCY_MST is the dominant documented relationship.