This chapter covers the following topics:
Oracle Yard Management (YMS) is designed to oversee the movement of equipment in the yard of a manufacturing facility, warehouse, or distribution center. YMS provides real-time information on the location of equipment in the yard and allows yard employees to move equipment from parking to docks to fill orders in an efficient manner. Oracle Shipping Execution is integrated with YMS for outbound activities such as loading equipment and ship confirmation.
To support this integration, Shipping Execution provides the following:
YMS entities in Shipping Transactions window
YMS entities in Quick Ship window
APIs to support the applicable outbound activities
YMS Related Actions in Shipping Transactions window
See: Oracle Yard Management Process Guide and My Oracle Support Note 1672903.1 - Oracle Yard Management, Deployment Steps For ADF Components.
Shipping Transactions window enables the following to support Oracle Warehouse Management (WMS) and non-WMS inventory organizations:
Stores the equipment number at delivery detail level.
Supports multiple deliveries for equipment.
Supports multiple trips for equipment (Oracle Transportation Management (OTM) and non OTM trips).
Supports multiple equipments for one delivery.
Supports multiple equipments for one trip (non OTM trips).
Flexibility to relieve inventory at ship confirm or yard check-out that you can achieve by defining a business process on when to run Interface Trip Stop (ITS) / Inventory Interface.
Once the pick-up stop is closed, ITS runs or you can schedule it to run which relieves inventory and interfaces the shipment to OM and AR.
The application stamps the time of actual ship confirm on the shipment records and ITS honors it as the shipment date and time.
For issues related to incorrect shipments, you can create an RMA to receive the shipments back into inventory.
Shipping Execution validates only the shipments created by Oracle Transportation Management (OTM) – One equipment per OTM batch/shipment/trip.
For OTM planning eligible deliveries in OTM enabled organizations, whenever a delivery has contents that are loaded into a equipment and if the delivery is not already assigned to a trip, the application stops you from performing the load action. It prompts you to mark such deliveries to 'Ignore for planning' and then perform this action. You cannot mark this delivery, which is loaded to equipment, as 'Include for Planning'.
Whenever delivery(s) is sent to OTM for planning and OTM sends the equipment type, Shipping Execution enforces loading of the details/delivery/trip in only one equipment instance of the equipment type sent by OTM. If you want to load the details/delivery/trip into a different equipment type, then you have to unassign the delivery from trip and the application marks the delivery as Ignore for Planning automatically.
Note: Whenever a delivery is sent to OTM for planning and OTM sends the equipment type, Shipping Execution enforces the loading of the details/delivery/trip in only one equipment instance of the equipment type sent by OTM. If you want to load the details/delivery/trip into a different equipment type, then you need to change the vehicle details on the Trips tab of the Shipping Transaction window or you can remove the vehicle details from this tab.
Shipping Execution prevents pack and unpack transactions for details already assigned to equipment.
Validates close pick stop if at-least one delivery is not loaded to equipment.
Validates the following during ship confirm:
Prevents ship confirm if a delivery is partially loaded to equipment.
Availability of an implicit yard checkout at ship confirm.
Note: You need to add subscription to the existing business event “oracle.apps.wsh.delivery.gen.shipconfirmed" and in that subscription you could call out your custom pl/sql API. In this custom pl/sql api, you need to call YMS Public API - YMS_TRANSACTION_PUB.checkout.
Allows backorder for only unloaded equipment.
For OTM enabled organizations, under the Trips tab, if the vehicle related information is not populated, then Shipping Execution populates this information as soon as any of the content of the trip is loaded into the equipment.
The Search Results for lines/LPNs display the following YMS entities:
Equipment Number
Dock Door information
Equipment Status (like 'In Yard')
SCAC Code
This integration uses the following:
Public APIs to support load and unload of equipments from Oracle Shipping Execution entities such as Lines/LPNs, Deliveries, Stops and Trips.
Private API to calculate the equipment content cost. This API accepts a delivery and equipment as inputs and computes the current cost of all its contents assigned in that equipment.
Private API to determine the delivery checkout status. This API accepts one or more deliveries as input and checks whether the associated pickup stop(s) are closed or not. If the stop(s) are not closed during checkout, then it raises an error.
Calling the private YMS Document Content API in the shipping processes. Whenever there is an assignment of lines/LPNs to a delivery or unassignment from a delivery (involving an inventory organization having an associated yard organization), then the Call YMS Document Content API reflects these changes. This API reflects the changes done during load and unload of equipments as well.
The following actions are available for all organizations which have an associated YMS organization:
Search for Deliveries using YMS Entities
View YMS Entities in Search Results
Load To Dock Door
Unload to Dock Door
View Equipment Details and Update Seal Information
Ensure Contents of Trips are Loaded into Specific Equipment
You can now search for deliveries using the following folder-enabled criteria at line and LPN level in the Shipping Transactions window:
Equipment Number
Dock Door
In Yard – Tied to the status and available only if the organization has an associated yard.
SCAC Code
Loaded To Dock Door
The Search Results in the Shipping Transaction window displays the following yard objects in the Lines/LPNs tab:
Equipment Number
Equipment Status (like 'In Yard')
SCAC Code
Dock Door information
The Load to Dock Door action enables you to choose equipment and load one or more (multi-select) shipping entities to that equipment. This action is available from Lines/LPNs, Delivery, Path by Stop, and Path by Trip tabs. Only Staged details are eligible for loading to equipment. The application loads the packed delivery details together.
You can complete this action using the following navigation:
Query Staged lines > Select deliveries for which you want to load equipment > Select Load From Dock Door action > Click Go
The Unload to Dock Door action enables you to unload one or more (multi-select) shipping entities from the equipment that they are currently loaded into. This action is available from Lines/LPNs, Delivery, Path by Stop, and Path by Trip tabs. Only Staged details are eligible for unloading from the equipment. The application unloads the packed delivery details together.
You can complete this action using the following navigation:
Query Staged lines > Select deliveries with equipment loaded previously > Select Unload From Dock Door action > Click Go
Oracle Shipping Execution enables you to navigate to the Equipment Details page in Oracle Yard Management to search equipment by dock door, equipment number, SCAC, and update the seal number for the equipment. You cannot perform this action when you select multiple details and is enabled if the delivery detail is loaded into the equipment.
You can complete this action using the following navigation:
Query Staged lines > Under Lines/LPNs tab, select deliveries with equipment loaded previously > choose Tools menu > choose Equipment Details
Oracle Shipping Execution enables you to ensure that contents are loaded into specific equipment. Under the Path by Trip tab, if the following fields are populated, then you can load the contents into the same vehicle mentioned. These fields are editable if none of the contents are loaded in the equipment. However, if the contents are partially or fully loaded into the equipment, then these fields are read only:
Vehicle Org Code
Vehicle Item Name
Vehicle Number
Vehicle Number Prefix