Search Results op_ship_mst
Overview
The OP_SHIP_MST table is a master data table within the Oracle E-Business Suite (EBS) Process Manufacturing Logistics (GML) module. It serves as the central repository for defining and maintaining carrier or shipper codes. These codes represent the third-party logistics providers or transportation companies used to ship goods. The table is fundamental to the logistics and order fulfillment processes, enabling the system to associate shipments, purchase orders, sales orders, and related documents with specific carriers. Its integrity is enforced by primary and foreign key relationships with numerous transactional tables across the Order Management and Purchasing suites.
Key Information Stored
While the provided ETRM excerpt does not list all columns, the primary keys and foreign key relationships indicate the core data elements. The table's primary identifier is the SHIPPER_CODE (also referenced as OF_SHIPPER_CODE in one key definition). This column stores the unique code for the carrier. Another critical column is ADDR_ID, which creates a foreign key relationship to the SY_ADDR_MST table, linking the shipper record to a specific address in the system's address book. The TEXT_CODE column links to the OP_TEXT_HDR table, allowing for descriptive text or notes to be associated with the shipper record. This structure allows the table to store the essential identification and reference data required for logistics operations.
Common Use Cases and Queries
This table is primarily referenced for master data maintenance, transaction processing, and reporting. Common operational scenarios include setting up new carriers, assigning default or preferred shippers to customers or items, and validating shipper codes during order entry. For reporting, it is frequently joined to transactional data to analyze carrier performance or shipping costs. A typical query pattern involves joining OP_SHIP_MST to order or purchase order headers to retrieve carrier details for a shipment.
- Sample Query to List Active Shippers with Address:
SELECT s.shipper_code, a.addr_line1 FROM gml.op_ship_mst s, sy.sy_addr_mst a WHERE s.addr_id = a.addr_id; - Use Case in Transaction Validation: When creating a sales order shipment (OP_SHIP_MTH), the system validates the entered SHIPPER_CODE against the OP_SHIP_MST table to ensure it is a valid, predefined carrier.
Related Objects
As indicated by the extensive foreign key list, OP_SHIP_MST is a cornerstone table with dependencies across multiple modules. Key related objects include transactional headers and details in Order Management (OP_ORDR_HDR, OP_ORDR_DTL, OP_SHIP_MTH), Purchasing (PO_ORDR_HDR, PO_RECV_HDR), and Process Manufacturing logistics (OP_BILL_LAD, OP_RELS_SCH). It also relates to master data tables for addresses (SY_ADDR_MST) and descriptive text (OP_TEXT_HDR). This wide integration underscores its critical role in ensuring data consistency for shipper information throughout the supply chain execution processes in EBS.
-
Table: OP_SHIP_MST
12.1.1
owner:GML, object_type:TABLE, fnd_design_data:GML.OP_SHIP_MST, object_name:OP_SHIP_MST, status:VALID, product: GML - Process Manufacturing Logistics , description: Carrier (shipper) codes . , implementation_dba_data: GML.OP_SHIP_MST ,
-
Table: OP_SHIP_MST
12.2.2
owner:GML, object_type:TABLE, fnd_design_data:GML.OP_SHIP_MST, object_name:OP_SHIP_MST, status:VALID, product: GML - Process Manufacturing Logistics , description: Carrier (shipper) codes . , implementation_dba_data: GML.OP_SHIP_MST ,
-
APPS.GML_PO_INTERFACE dependencies on OP_SHIP_MST
12.1.1
-
APPS.GML_VALIDATE_PO dependencies on OP_SHIP_MST
12.2.2
-
APPS.GMF_GLSYNCH dependencies on OP_SHIP_MST
12.2.2
-
APPS.GML_VALIDATE_PO dependencies on OP_SHIP_MST
12.1.1
-
APPS.GML_PO_INTERFACE dependencies on OP_SHIP_MST
12.2.2
-
APPS.GML_VALIDATE_PO dependencies on OP_SHIP_MST
12.2.2
-
APPS.GML_VALIDATE_PO dependencies on OP_SHIP_MST
12.1.1
-
APPS.GMF_GET_OPM_CODE dependencies on OP_SHIP_MST
12.1.1
-
APPS.GMI_ICR03_XMLP_PKG dependencies on OP_SHIP_MST
12.2.2
-
APPS.GMF_GET_OPM_CODE dependencies on OP_SHIP_MST
12.2.2
-
APPS.GMI_ICR03_XMLP_PKG dependencies on OP_SHIP_MST
12.1.1
-
APPS.GMF_GLSYNCH dependencies on OP_SHIP_MST
12.1.1
-
APPS.GMI_ICR03_XMLP_PKG dependencies on PO_VEND_MST
12.1.1
-
APPS.GMI_ICR03_XMLP_PKG dependencies on PO_RECV_HDR
12.1.1
-
APPS.GMI_ICR03_XMLP_PKG dependencies on OP_BILL_LAD
12.1.1
-
APPS.GMI_ICR03_XMLP_PKG dependencies on OP_BILL_LAD
12.2.2
-
APPS.GMI_ICR03_XMLP_PKG dependencies on OP_ORDR_DTL
12.1.1
-
APPS.GMI_ICR03_XMLP_PKG dependencies on OP_ORDR_DTL
12.2.2
-
APPS.GMI_ICR03_XMLP_PKG dependencies on PO_VEND_MST
12.2.2
-
APPS.GMI_ICR03_XMLP_PKG dependencies on OP_CUST_MST
12.1.1
-
APPS.GMI_ICR03_XMLP_PKG dependencies on OP_CUST_MST
12.2.2
-
APPS.GMI_ICR03_XMLP_PKG SQL Statements
12.2.2
-
APPS.GMI_ICR03_XMLP_PKG dependencies on OP_ORDR_HDR
12.2.2
-
APPS.GMI_ICR03_XMLP_PKG dependencies on PO_RECV_HDR
12.2.2
-
APPS.GMI_ICR03_XMLP_PKG dependencies on OP_ORDR_HDR
12.1.1
-
APPS.GMI_ICR03_XMLP_PKG dependencies on PO_ORDR_DTL
12.1.1
-
APPS.GMI_ICR03_XMLP_PKG dependencies on PO_ORDR_HDR
12.1.1
-
APPS.GMI_ICR03_XMLP_PKG dependencies on PO_ORDR_HDR
12.2.2
-
APPS.GMI_ICR03_XMLP_PKG dependencies on PO_RECV_DTL
12.1.1
-
APPS.GMI_ICR03_XMLP_PKG dependencies on PO_ORDR_DTL
12.2.2
-
APPS.GMI_ICR03_XMLP_PKG dependencies on PO_RECV_DTL
12.2.2
-
VIEW: GML.OP_SHIP_MST#
12.2.2
owner:GML, object_type:VIEW, object_name:OP_SHIP_MST#, status:VALID,
-
APPS.GMI_ICR03_XMLP_PKG SQL Statements
12.1.1
-
SYNONYM: APPS.OP_SHIP_MST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:OP_SHIP_MST, status:VALID,
-
VIEW: GML.OP_SHIP_MST#
12.2.2
-
SYNONYM: APPS.OP_SHIP_MST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:OP_SHIP_MST, status:VALID,
-
PACKAGE BODY: APPS.GMI_ICR03_XMLP_PKG
12.1.1
-
PACKAGE BODY: APPS.GMI_ICR03_XMLP_PKG
12.2.2
-
TABLE: GML.OP_SHIP_MST
12.2.2
owner:GML, object_type:TABLE, fnd_design_data:GML.OP_SHIP_MST, object_name:OP_SHIP_MST, status:VALID,
-
TABLE: GML.OP_SHIP_MST
12.1.1
owner:GML, object_type:TABLE, fnd_design_data:GML.OP_SHIP_MST, object_name:OP_SHIP_MST, status:VALID,
-
PACKAGE BODY: APPS.GML_VALIDATE_PO
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:GML_VALIDATE_PO, status:VALID,
-
Table: OP_SHIP_MTH
12.2.2
owner:GML, object_type:TABLE, fnd_design_data:GML.OP_SHIP_MTH, object_name:OP_SHIP_MTH, status:VALID, product: GML - Process Manufacturing Logistics , description: Shipping method codes. , implementation_dba_data: GML.OP_SHIP_MTH ,
-
APPS.GML_PO_INTERFACE dependencies on OP_FOBC_MST
12.2.2
-
APPS.GML_PO_INTERFACE dependencies on OP_FOBC_MST
12.1.1
-
Table: PO_RTRN_HDR
12.1.1
owner:GML, object_type:TABLE, fnd_design_data:GML.PO_RTRN_HDR, object_name:PO_RTRN_HDR, status:VALID, product: GML - Process Manufacturing Logistics , description: Return header. , implementation_dba_data: GML.PO_RTRN_HDR ,
-
Table: PO_RTRN_HDR
12.2.2
owner:GML, object_type:TABLE, fnd_design_data:GML.PO_RTRN_HDR, object_name:PO_RTRN_HDR, status:VALID, product: GML - Process Manufacturing Logistics , description: Return header. , implementation_dba_data: GML.PO_RTRN_HDR ,
-
Table: OP_RELS_SCH
12.1.1
owner:GML, object_type:TABLE, fnd_design_data:GML.OP_RELS_SCH, object_name:OP_RELS_SCH, status:VALID, product: GML - Process Manufacturing Logistics , description: Blanket Sales Order Release Schedules. , implementation_dba_data: GML.OP_RELS_SCH ,
-
Table: OP_RELS_SCH
12.2.2
owner:GML, object_type:TABLE, fnd_design_data:GML.OP_RELS_SCH, object_name:OP_RELS_SCH, status:VALID, product: GML - Process Manufacturing Logistics , description: Blanket Sales Order Release Schedules. , implementation_dba_data: GML.OP_RELS_SCH ,