Results for “shipper_code”

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

Overview

OP_SHIP_MST is the carrier (shipper) master table within the Oracle E-Business Suite Process Manufacturing Logistics module, owned by the GML schema. It stores the definitive registry of shipper codes used throughout Oracle Process Manufacturing (OPM) and, through shared foreign key references, in Oracle Purchasing as well. Every shipment, purchase order, receipt, return, bill of lading, and release schedule that needs to identify a carrier resolves that carrier through a SHIPPER_CODE value originating in this table, making OP_SHIP_MST a foundational reference or lookup entity rather than a transactional one. In practice it functions as a controlled vocabulary of transportation providers, tightly integrated with address and descriptive text data.

Applying a heuristic Data Vault classification to the documented foreign key structure, OP_SHIP_MST is best modeled as a hub. It carries two independent unique business keys (SHIPPER_CODE and OF_SHIPPER_CODE) and serves as the anchor referenced by a broad set of transactional and dependent objects, which is characteristic of a hub surrounded by link and satellite structures in a Data Vault design. This classification is a modeling suggestion derived from the FK topology, not an Oracle-imposed designation.

Key Information Stored

The table is documented with twelve columns. The most operationally significant are:

• SHIPPER_CODE — the primary business identifier for the carrier. It is backed by the unique index OP_SHIP_MST_PK and is the column referenced by virtually every downstream foreign key.
• OF_SHIPPER_CODE — a secondary unique identifier, protected by unique index OP_SHIP_MST01, commonly associated with Oracle Flow Manufacturing / outside processing shipper usage.
• SHIPPER_NAME — the human-readable carrier name used in reports, pick tickets, and shipping documents.
• ADDR_ID — foreign key to SY_ADDR_MST, supplying the carrier's address details from the shared address repository.
• TEXT_CODE — foreign key to OP_TEXT_HDR, linking the carrier to long-form descriptive or instructional text.
• DELETE_MARK — the standard OPM soft-delete / logical-deletion flag.
• TRANS_CNT — an optimistic-locking transaction counter used to detect concurrent updates.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle WHO-column audit trail capturing record creation and modification metadata.

The surrogate primary key is OP_SHIP_MST_PK on SHIPPER_CODE, while OF_SHIPPER_CODE is the alternate business-key candidate. Both unique indexes exist on natural business identifiers rather than a synthetic sequence, which is typical of OPM master data.

Common Use Cases and Queries

Because OP_SHIP_MST is a lookup hub, the most frequent access pattern is a join from a transactional table to resolve a carrier name or address for reporting. A typical inventory of active carriers excludes soft-deleted rows:

• SELECT SHIPPER_CODE, SHIPPER_NAME, ADDR_ID FROM GML.OP_SHIP_MST WHERE DELETE_MARK = 0;
• Joining order headers to carriers for shipment reporting: SELECT h.ORDER_NO, s.SHIPPER_NAME FROM GML.OP_ORDR_HDR h JOIN GML.OP_SHIP_MST s ON h.SHIPPER_CODE = s.SHIPPER_CODE;
• References from Purchasing receipt data: SELECT r.RECEIPT_NUM, s.SHIPPER_NAME FROM PO_RECV_HDR r JOIN OP_SHIP_MST s ON r.SHIPPER_CODE = s.SHIPPER_CODE;
• Identifying a preferred carrier for a ship method via OP_SHIP_MTH.PREFERRED_SHIPPER.
• Referential integrity audits detecting shipments whose SHIPPER_CODE no longer exists in the master.

These patterns support transportation spend analysis, carrier performance dashboards, and open-order delivery tracking.

Related Objects

OP_SHIP_MST participates in a dense web of relationships. It references two parent objects and is referenced by many dependents via the SHIPPER_CODE column:

• SY_ADDR_MST — joined on OP_SHIP_MST.ADDR_ID for carrier address data.
• OP_TEXT_HDR — joined on OP_SHIP_MST.TEXT_CODE for descriptive text.
• OP_ORDR_HDR / OP_ORDR_DTL — process order headers and details carry SHIPPER_CODE.
• OP_BILL_LAD — bills of lading reference the shipper directly.
• OP_SHIP_MTH — shipping methods reference a PREFERRED_SHIPPER value.
• PO_ORDR_HDR / PO_ORDR_DTL — purchasing orders and lines carry SHIPPER_CODE.
• PO_RECV_HDR / PO_RECV_DTL — receipts designate the delivering carrier.
• PO_RTRN_HDR — return documents reference the carrier for reverse logistics.
• OP_RELS_SCH, PO_RELS_SCH, PO_BPOS_HDR, PO_BPOS_DTL, OP_PRSL_HDR, OP_PRSL_DTL, OP_CUST_SHP — scheduling, blanket order, proposal, and customer shipment objects that resolve carriers through this master.

Maintenance of shipper codes is performed through the OPM Logistics setup or the Oracle Transportation / Order Management configuration flows that populate this table; direct DML is generally discouraged in favor of supported setup APIs.