Search Results carrier




The GML.OP_SHIP_MST table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical data structure within the Global Trade Management (GTM) or Logistics modules, specifically related to shipment management. This table stores master shipment records, which serve as the foundation for tracking and managing logistics operations, including freight, carrier assignments, and shipment routing. Below is a detailed breakdown of its purpose, structure, and integration within Oracle EBS. ### **Purpose and Functional Overview** The GML.OP_SHIP_MST table acts as the primary repository for shipment header information. It captures essential attributes such as shipment IDs, dates, statuses, and associated business entities (e.g., carriers, customers, or suppliers). This table integrates with other EBS modules like Order Management (OM), Inventory (INV), and Purchasing (PO) to ensure end-to-end visibility of goods movement. Key functionalities supported by this table include: - **Shipment Creation & Tracking**: Stores metadata for each shipment, including origin, destination, and transit details. - **Carrier & Freight Management**: Links to carrier contracts, freight terms, and transportation modes. - **Compliance & Documentation**: Supports trade compliance by storing export/import references and regulatory data. ### **Key Columns and Data Model** The table's schema typically includes the following columns (specific implementations may vary): - SHIP_ID: Primary key, uniquely identifying each shipment. - SHIP_NUM: User-friendly shipment number for reporting and tracking. - STATUS: Indicates workflow stages (e.g., "DRAFT," "IN_TRANSIT," "DELIVERED"). - ORIGIN_LOCATION_ID / DEST_LOCATION_ID: References to HR_LOCATIONS or WSH_LOCATIONS for geospatial data. - CARRIER_ID: Foreign key to WSH_CARRIERS or PO_VENDORS for carrier details. - SHIP_DATE / DELIVERY_DATE: Timestamps for logistics planning. - CREATED_BY / LAST_UPDATE_DATE: Standard Oracle audit columns. ### **Integration with Oracle EBS Modules** 1. **Order Management (OM)**: Shipments in OP_SHIP_MST may link to sales orders via WSH_DELIVERY_DETAILS, enabling order-to-shipment reconciliation. 2. **Inventory (INV)**: Ties to MTL_SHIPMENTS for material movement records. 3. **Purchasing (PO)**: References purchase orders or ASNs (Advance Shipment Notices) for inbound logistics. 4. **Trade Management (GTM)**: Integrates with compliance tables like GML_GTM_DOCS for export/import documentation. ### **Customization and Extensions** In implementations requiring enhanced logistics features, OP_SHIP_MST may be extended via: - **Descriptive Flexfields (DFFs)**: Adding custom attributes (e.g., "Customs_Entry_Number"). - **API Hooks**: Using Oracle's WSH_SHIPMENTS_PUB API for programmatic updates. - **Workflow Extensions**: Triggering notifications or validations via Oracle Workflow. ### **Performance Considerations** For large-scale deployments, indexing strategies on SHIP_ID, SHIP_NUM, and status columns are critical. Partitioning by date ranges may improve query performance for historical data. ### **Conclusion** The GML.OP_SHIP_MST table is a cornerstone of Oracle EBS's logistics framework, enabling robust shipment lifecycle management. Its design ensures interoperability with core modules while supporting compliance and operational reporting. Implementers should leverage its schema and integration points to optimize supply chain workflows in EBS 12.1.1 or 12.2.2 environments.