Results for “ic_text_hdr”

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

Overview

PS_PLNG_CLS is a Process Manufacturing Process Planning (GMP) reference table that stores planning class definitions. A planning class is an attribute assigned to items and operation classes to influence how master production scheduling, material requirements planning, and capacity planning treat those entities. In Oracle EBS 12.1.1 and 12.2.2, PS_PLNG_CLS functions as a low-volume configuration or lookup table within the GMP schema, populated during implementation and referenced at planning run time.

Under the heuristic Data Vault classification derived from its foreign key structure, PS_PLNG_CLS is satellite-leaning. Modeling guidance suggests treating it as a descriptive satellite attached to the item and operation-planning hubs, with its foreign keys to IC_TEXT_HDR and SY_UOMS_MST providing additional descriptive context rather than structural relationships. Note that the ETRM metadata records this table as "Not implemented in this database," indicating that it exists in the product schema definition but may be unpopulated or absent in a given instance; the same is true of IC_TEXT_HDR, which the user searched for in connection with this object.

Key Information Stored

The table is narrow by design, and the following columns are the significant ones documented in the ETRM metadata:

• PLANNING_CLASS — The primary key column and the business-key candidate. It is the single column comprising PS_PLNG_CLS_PK and uniquely identifies each planning class definition. This value is the same code propagated to IC_ITEM_MST.PLANNING_CLASS and PS_OPER_PCL.PLANNING_CLASS.
• TEXT_CODE — Foreign key to IC_TEXT_HDR. Links the planning class to a text header record, allowing extended descriptive or instructional text to be attached to the class without storing it in PS_PLNG_CLS itself. This is the join path relevant to the "ic_text_hdr" search.
• REPORTING_UOM — Foreign key to SY_UOMS_MST. Defines the unit of measure used when planning results for items in this class are reported or aggregated, ensuring consistent UOM presentation across planning output.

Because the table is a definition table rather than a transaction table, there is no documented surrogate key separate from the natural business key; PLANNING_CLASS serves both roles. Additional descriptive attributes may exist in the physical table but are not documented in the ETRM excerpt and should be confirmed against the deployed schema.

Common Use Cases and Queries

Typical uses center on validating and reporting planning class assignments and resolving the associated text and UOM context.

• Listing all defined planning classes with their reporting UOM:
  SELECT p.PLANNING_CLASS, p.REPORTING_UOM, u.UNIT_OF_MEASURE
FROM PS_PLNG_CLS p, SY_UOMS_MST u
WHERE p.REPORTING_UOM = u.UOM_CODE;
• Retrieving the descriptive text attached to each planning class through the IC_TEXT_HDR relationship:
  SELECT p.PLANNING_CLASS, t.TEXT_CODE, t.TEXT
FROM PS_PLNG_CLS p, IC_TEXT_HDR t
WHERE p.TEXT_CODE = t.TEXT_CODE;
• Identifying items assigned to each planning class for planning setup audits:
  SELECT i.ITEM_ID, i.PLANNING_CLASS
FROM IC_ITEM_MST i, PS_PLNG_CLS p
WHERE i.PLANNING_CLASS = p.PLANNING_CLASS;
• Reviewing which operation planning classes consume each definition:
  SELECT o.PLANNING_CLASS, o.OPERATION_CLASS
FROM PS_OPER_PCL o, PS_PLNG_CLS p
WHERE o.PLANNING_CLASS = p.PLANNING_CLASS;

These queries support implementation verification, data migration checks, and reporting on planning configuration before an MRP or MPS run.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

• IC_TEXT_HDR — Referenced by PS_PLNG_CLS.TEXT_CODE; supplies descriptive text for a planning class.
• SY_UOMS_MST — Referenced by PS_PLNG_CLS.REPORTING_UOM; supplies the unit of measure definition.
• IC_ITEM_MST — References PS_PLNG_CLS via IC_ITEM_MST.PLANNING_CLASS; the master item table where planning classes are assigned to items.
• PS_OPER_PCL — References PS_PLNG_CLS via PS_OPER_PCL.PLANNING_CLASS; operation planning class assignments that depend on these definitions.
• PS_PLNG_CLS_PK — The primary key constraint enforcing uniqueness of PLANNING_CLASS.

Together these objects form the configuration backbone for GMP planning behavior at the item and operation level, with PS_PLNG_CLS acting as the central definition point.