Results for “gl_plcy_seg”

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

Overview

GL_PLCY_SEG is a table owned by the GMF schema (Process Manufacturing Financials) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores segments for account key segregation and holds the Chart of Accounts configuration used by Oracle Process Manufacturing. Specifically, the table defines how the accounting key is decomposed into individual segments — each row represents one segment of an account structure, together with its type, length, and the source reference used by GMF costing and financials.

Its role is to describe segment-level policy metadata linked to a company code, making it a foundational configuration object for account key generation. Under the heuristic Data Vault classification derived from the foreign-key structure, GL_PLCY_SEG is treated as satellite-leaning. This suggests that a data warehouse model would best represent it as an entity (satellite) dependent on parent entities such as GL_PLCY_MST and CSF_TDS_SEGMENTS, rather than as an independent hub or an associative link.

Key Information Stored

The physical schema documented for ETRM 12.2.2 contains 16 columns. The most important are listed below.

• CO_CODE — Company code; part of the composite primary key and a foreign key to GL_PLCY_MST.
• SEGMENT_NO — Segment sequence/number; the second component of the composite primary key.
• SEGMENT_ID — Identifier of the segment; documented as a foreign key to CSF_TDS_SEGMENTS.
• TYPE — Segment type (e.g., the category or nature of the account segment).
• LENGTH — Length of the segment value.
• SHORT_NAME — Short descriptive name for the segment.
• LONG_NAME — Long descriptive name for the segment.
• SEGMENT_REF — Reference used to derive or qualify the segment.
• TEXT_CODE — Associated text/code value for the segment.
• DELETE_MARK — Deletion/soft-delete indicator.
• TRANS_CNT — Transaction count or usage counter.
• CREATION_DATE, CREATED_BY — Standard audit columns recording initial creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent change.

The surrogate primary key is GL_PLCY_SEG_PK, defined on (CO_CODE, SEGMENT_NO). Because this same composite key is documented as the unique index, GL_PLCY_SEG_PK also serves as the business-key candidate, ensuring that each company/segment-number pairing is unique.

Common Use Cases and Queries

Typical use cases include validating the account key structure for a company before running costing, reconciling GMF segment definitions against the general ledger configuration, and reporting on segment type and length for chart-of-accounts maintenance.

A representative query retrieves all segment definitions for a company:

• SELECT CO_CODE, SEGMENT_NO, SEGMENT_ID, TYPE, LENGTH, SHORT_NAME, LONG_NAME FROM GMF.GL_PLCY_SEG WHERE CO_CODE = :co_code ORDER BY SEGMENT_NO;

A second pattern joins the parent master to validate active segments:

• SELECT s.CO_CODE, s.SEGMENT_NO, s.SHORT_NAME FROM GMF.GL_PLCY_SEG s, GMF.GL_PLCY_MST m WHERE s.CO_CODE = m.CO_CODE AND s.DELETE_MARK = 0;

These queries support configuration review, segment mapping audits, and diagnostics when an account key fails to generate in process manufacturing.

Related Objects

The following objects are the most significant with respect to GL_PLCY_SEG, based on the documented fee/foreign key relationships.

• GL_PLCY_MST — Parent master table; related via GL_PLCY_SEG.CO_CODE = GL_PLCY_MST.CO_CODE.
• CSF_TDS_SEGMENTS — Segment definition source; related via GL_PLCY_SEG.SEGMENT_ID = CSF_TDS_SEGMENTS.SEGMENT_ID.
• GL_PLCY_SEG_PK — The primary key/unique index enforcing (CO_CODE, SEGMENT_NO).

Additional dependencies in GMF costing, account key generation, and GL interface routines reference the segment IDs established here, making GL_PLCY_SEG a key configuration dependency for Process Manufacturing Financials.