Results for “ic_ship_cls”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IC_SHIP_CLS is a Process Manufacturing Inventory (GMI/OPM) setup table that stores the item shipping class definition used throughout Oracle Process Manufacturing. A shipping class is a short code assigned to items and warehouse inventory records that groups products by how they are shipped, handled, or staged — for example, ambient versus refrigerated goods, hazardous versus non-hazardous materials, or bulk versus packaged items. Because the class is carried on both the item master and the warehouse inventory record, it acts as a single reusable reference point for logistics rules, picking and put-away logic, and customer shipment defaulting across the OPM inventory and order fulfillment modules.
The table is not implemented in every database instance; it is created only where the OPM Inventory schema has been installed. Under a heuristic Data Vault classification mined from the foreign key structure, IC_SHIP_CLS resolves as hub-leaning: its primary key ICSHIP_CLASS is a stable, unique business code, and the table is referenced by multiple downstream entities while itself referencing only a text/lookup header. This suggests modeling it as a hub keyed on the shipping class code, with dependent descriptive attributes held in a satellite and its relationship to IC_TEXT_HDR treated as a reference to a shared code table rather than an independent business transaction.
Key Information Stored
The documented metadata identifies ICSHIP_CLASS as the primary key column, enforced through the constraint IC_SHIP_CLS_PK. This column holds the business shipping class code itself — typically a short alphanumeric value such as a two- to four-character identifier — and is the value propagated to child records. It is the natural business key rather than a system-generated surrogate, so the same value appears as SHIP_CLASS on inventory items and warehouse inventory rows and as ICSHIP_CLASS on customer shipment lines.
- ICSHIP_CLASS — the unique shipping class code (primary key / business key candidate).
- TEXT_CODE — foreign key to IC_TEXT_HDR, linking the class to a descriptive text block for instructions, handling notes, or documentation attached to the class.
- Descriptive attributes — the remaining columns hold the class name, description, and associated operational attributes that define how items carrying the class are shipped and stored. These are not itemized in the supplied excerpt; the excerpt documents only the key and the foreign key columns.
The principal distinguishing point is that ICSHIP_CLASS is both the primary key and the only documented unique identifier, while TEXT_CODE is a non-unique foreign key to IC_TEXT_HDR and carries no independent uniqueness.
Common Use Cases and Queries
Typical uses are setup validation, shipping class assignment auditing, and lookup-driven reporting. A representative pattern joins items and inventory to their class in a single pass:
- Assign class to items:
SELECT i.ITEM, i.SHIP_CLASS, s.TEXT_CODE FROM IC_ITEM_MST i, IC_SHIP_CLS s WHERE i.SHIP_CLASS = s.ICSHIP_CLASS; - Find items lacking a class:
SELECT ITEM FROM IC_ITEM_MST WHERE SHIP_CLASS IS NULL; - Inventory grouped by class:
SELECT w.SHIP_CLASS, COUNT(*) FROM IC_WHSE_INV w GROUP BY w.SHIP_CLASS; - Retrieve handling text: join IC_SHIP_CLS to IC_TEXT_HDR on
TEXT_CODEto display shipping instructions for a class. - Shipment defaulting: trace
OP_CUST_SHP.ICSHIP_CLASSback to the class definition to confirm default shipping behavior on customer shipments.
Reporting generally uses the class as a grouping dimension for inventory valuation summaries, warehousing capacity analysis, and outbound shipment profiling, because it is a low-cardinality attribute that partitions products into manageable logistical buckets.
Related Objects
- IC_ITEM_MST — references IC_SHIP_CLS via
SHIP_CLASS; the item master assigns a default class to each item. - IC_WHSE_INV — references IC_SHIP_CLS via
SHIP_CLASS; carries the class on warehouse inventory balances. - OP_CUST_SHP — references IC_SHIP_CLS via
ICSHIP_CLASS; holds the class on customer shipment records. - IC_TEXT_HDR — referenced by IC_SHIP_CLS through
TEXT_CODE; supplies attached descriptive text. - IC_SHIP_CLS_PK — the primary key constraint that enforces uniqueness of the shipping class code and is the object most commonly encountered when searching the dictionary for this table.
-
SYNONYM: APPS.IC_SHIP_CLS 12.1.1
-
SYNONYM: APPS.IC_SHIP_CLS 12.2.2
-
Table: IC_SHIP_CLS 12.1.1
This table contains the item shipping class definition for use throughout OPM.
Not implemented in this database·Explore GMI module →
-
Table: IC_SHIP_CLS 12.2.2
This table contains the item shipping class definition for use throughout OPM.
Not implemented in this database·Explore GMI module →
-
VIEW: APPS.IC_SHIP_CLS_DFV 12.1.1
-
VIEW: APPS.IC_SHIP_CLS_DFV 12.2.2
-
Preferred shippers (carriers) and ship methods for customers.
-
VIEW: APPS.IC_SHIP_CLS_VW 12.2.2
-
VIEW: APPS.IC_SHIP_CLS_VW 12.1.1
-
PACKAGE BODY: APPS.GMIVITM 12.1.1
-
Preferred shippers (carriers) and ship methods for customers.
-
PACKAGE: APPS.GMIVITM 12.1.1
-
VIEW: APPS.IC_SHIP_CLS_DFV 12.1.1
-
VIEW: APPS.IC_SHIP_CLS_DFV 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
PACKAGE: APPS.GMIVITM 12.2.2
-
PACKAGE BODY: APPS.GMIVITM 12.2.2
-
Table: IC_ITEM_MST 12.2.2
This is the Item definition table. It contains all information relating to an item, such as lot/sublot control, unit of measure information, and all class and type designations.
Not implemented in this database·Explore GMI module →
-
Table: IC_ITEM_MST 12.1.1
This is the Item definition table. It contains all information relating to an item, such as lot/sublot control, unit of measure information, and all class and type designations.
Not implemented in this database·Explore GMI module →
-
APPS.GMIVITM SQL Statements 12.1.1
-
APPS.GMIVITM SQL Statements 12.2.2
-
TABLE: GML.OP_CUST_SHP 12.2.2
-
TABLE: GML.OP_CUST_SHP 12.1.1
-
Warehouse rules
-
Warehouse rules
-
PACKAGE BODY: APPS.GMIVITM 12.1.1
-
eTRM - GMI Tables and Views 12.1.1
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
PACKAGE BODY: APPS.GMIVITM 12.2.2
-
eTRM - GMI Tables and Views 12.2.2
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
eTRM - GML Tables and Views 12.1.1
Tax reporting classes.
-
eTRM - GML Tables and Views 12.2.2
Tax reporting classes.
-
eTRM - GMI Tables and Views 12.1.1
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
eTRM - GMI Tables and Views 12.2.2
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
12.2.2 DBA Data 12.2.2
-
eTRM - GML Tables and Views 12.2.2
Tax reporting classes.
-
12.1.1 DBA Data 12.1.1
-
eTRM - GML Tables and Views 12.1.1
Tax reporting classes.