Results for “contiguity_ind”

8 results




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

Overview

IC_PLNT_INV is a GMI (Process Manufacturing Inventory) base table owned by the GMI schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores production rules defined at the item and plant (organization) level. These rules drive MRP planning behavior and provide the supply defaults consumed during Production Batch creation. In practical terms, the table answers the question: for a given item in a given plant, how should the system plan, size, and schedule replenishment or production?

The documented ETRM metadata assigns IC_PLNT_INV a heuristic Data Vault classification of link. This classification is mined from the foreign key structure and should be treated as a modeling suggestion rather than a definitive declaration. The link interpretation is consistent with the table's role: its unique business key is the combination of ITEM_ID and ORGN_CODE, joining the item dimension to the organization dimension, with the remaining columns carrying rule attributes.

The table is registered as VALID and contains 52 documented columns, most of which are reserved for descriptive flexfield storage (ATTRIBUTE1 through ATTRIBUTE30 plus ATTRIBUTE_CATEGORY).

Key Information Stored

The table uses two documented unique indexes. IC_PLNT_INV_PK is the surrogate primary key on PLNTINV_ID, a system-generated identifier. IC_PLNT_INV_U1 is the business-key candidate on the natural combination of ITEM_ID and ORGN_CODE, which enforces one production rule set per item per plant.

The most significant columns fall into three groups:

Common Use Cases and Queries

Typical use cases include validating that production rules exist before batch creation, auditing lead time settings across plants, and feeding planning reports with rule values. A standard lookup retrieves the rule for a single item and plant:

  • SELECT * FROM gmi.ic_plnt_inv WHERE item_id = :p_item AND orgn_code = :p_orgn AND delete_mark = 0;

For cross-plant analysis, join to the item master to resolve identifiers and descriptions, then aggregate by ORGN_CODE to compare STD_QTY or lead time settings. A typical pattern joins IC_PLNT_INV to IC_ITEM_MST on ITEM_ID to obtain the item number, and to SY_ORGN_MST on ORGN_CODE to obtain the plant description. Reporting use cases include exception reports for items with missing or expired reschedule periods, and time-fence compliance reports for items where INNER_TIMEFENCE is populated.

Because DELETE_MARK is a documented soft-delete indicator, application-oriented queries should filter on it to exclude logically deleted rows. Reporting queries should also account for the large number of flexfield attributes by selecting only the needed columns.

Related Objects

The documented foreign keys define the core join paths:

  • IC_ITEM_MST — joined on IC_PLNT_INV.ITEM_ID = IC_ITEM_MST.ITEM_ID; the primary item master reference.
  • IC_ITEM_MST_B — joined on IC_PLNT_INV.ITEM_ID = IC_ITEM_MST_B.ITEM_ID; the companion item master table.
  • SY_ORGN_MST — joined on IC_PLNT_INV.ORGN_CODE = SY_ORGN_MST.ORGN_CODE; provides the plant or organization definition.
  • SY_ORGN_MST_B — joined on IC_PLNT_INV.ORGN_CODE = SY_ORGN_MST_B.ORGN_CODE; the companion organization table.
  • IC_TEXT_HDR — joined on IC_PLNT_INV.TEXT_CODE = IC_TEXT_HDR.TEXT_CODE; supplies free-form text associated with the rule set.

In addition to these FK relationships, the table interacts functionally with GMI production batch creation logic and MRP planning processes, which read the rule values to derive supply defaults and scheduling parameters.