February 14, 2026

Yard Management

 

A warehouse usually has - Parking Yard and Dock Doors. Yard will have Rows and Each Row has some defined number of slots. Container will first be placed in the Yard slot. Users at warehouse will pull the container from Yard Slot to Door for unloading. Usually, responsibility of the carrier is to bring the container from port to yard. To move a container from Port to Yard – we can have a custom container ranking algorithm based on certain parameters (like PO priority, delivery dates, etc.)  to give ranking to containers. Users at warehouse can use this rank to identify what containers they need to pull to the door at the earliest.

Once the shipment/container is in the yard slot, next step is to assign shipment to a door where loading/unloading happens. This step is called scheduling an appointment. Door will have time slots (30 min slot etc.) for loading or unloading activity that can be configured on the location resource.

Depending on the requirement, the Drayage carrier should be notified once the appointment is made in the system for a specific container. This is usually done by sending a tender offer EDI 204 file with expected delivery time and other details like Yard/Door No. Fpr example, EDI 204 can be triggered based on status update events from Ocean carrier like ‘Available for Delivery’ etc.

Below are the OTM location resource level configurations to define the yard:


Once location resource level yard is defined, you can use custom logic to select shipments that are eligible to be displayed in the yard using business rules. For example, shipments/containers that are unloaded at destination port can be made visible in the yard. In this example, yard can be virtual yard just to give warehouse users visibility on what containers they can expect in coming days.Also, high priority shipments can be assigned to first rows and slots so that warehouse users can pull shipments for appointment scheduling from left to right and bottom down approach on the yard manager screen.

Using all this custom logic, insert entries in Yard table as shown below:


Once shipments are inserted into yard table, we can see them in UI with below navigation:

Operational Planning > Appointment Management > Dock and Yard Managers > Query location > Actions > Manage Yard


In the above screen, display text on shipments can be configured using glog property below (second one):



August 22, 2020

Basic OTM Configurations - 01 - Domain, Items, Locations, and Equipment

Note: Below configurations are shown from 6.3.7 version of the OTM app. These posts are numbered to cover a typical end to end transaction flow that happens in OTM at a very high level. 

Basic OTM Configurations - 01 - Domain, Items, Locations, and Equipment
https://www.oracle-otm.com/2020/08/basic-otm-configurations-01-domain.html

Basic OTM Configurations - 02 - Itinerary
https://www.oracle-otm.com/2020/08/basic-otm-configurations-02-itinerary.html

Basic OTM Configurations - 03 - Service Provider and Rates
https://www.oracle-otm.com/2020/08/basic-otm-configurations-03-service.html

Basic OTM Configurations - 04 - Business Numbers, Planning Parameter
https://www.oracle-otm.com/2020/08/basic-otm-configurations-04-business.html

Basic OTM Configurations - 05 - Bulk Plan
https://www.oracle-otm.com/2020/08/basic-otm-configurations-05-bulk-plan.html

Basic OTM Configurations - 06 - Tender process
https://www.oracle-otm.com/2020/08/basic-otm-configurations-06-tender.html

Basic OTM Configurations - 07 - Invoicing
https://www.oracle-otm.com/2020/08/basic-otm-configurations-07-invoicing.html

Basic OTM Configurations - 08 - Voucher Allocation
https://www.oracle-otm.com/2020/08/basic-otm-configurations-08-voucher.html

Below is a typical OTM end to end flow in it's most simple/vanilla usage. Readers can explore more on each of the below topics and use this as starting point to understand basic OTM configurations using OTM Help documentation.

Business Scenario:

There is Toys Corporation (TCRP) with one DC/Warehouse and three stores in 3 different cities. DC distributes items – Item A, Item B and Item C to three locations (store locations). TCRP has contract with two carriers (SGTM, PNDP) to support their logistics needs and these carriers use their 20 foot, 40 foot or 50 foot equipments. As specified below each carrier supports specific itineraries/legs for TCRP.

TCRP wants to optimize their transport costs using "bulk planning" feature of OTM app and settle invoices for the transport services provied by these carriers.

Below is a draft overview of what we are trying to implement:

We can map above locations to real time locations as below:

  • DC/Warehouse location in Indianapolis, IN, 46202
  • Loc_A in Nashville, TN, 37203
  • Loc_B in Charlotte, NC, 28078
  • Loc_C in Atlanta, GA, 30303



Domain:

Create a new domain TCRP to store the configurations and transaction data related to this business scenario. 

Config and Admin > Domain Management > Add Domain


 

 Login to this new domain with default ADMIN user and CHANGEME as password:

Once you login, you will see: 
Items:

Define three items ITEMA01, 02, 03
Order Management > Material Management > Item:
 
Item Dimensions:
Item Weight = 2 LB. 

Other item dimensions are updated as below:

 

Locations:

First, let's create for required locations as shown below:
Shipment Management > Location Manager

Create Warehouse/DC location: DC_TCRP with below details:




 

Create other 3 store locations with role as ship from/to:
 


Equipment 
 
Define equipment groups  – 20_FT, 40_FT, 53_FT with below data:
Shipment Management > Equipment Management > Equipment Groups:

Define Equipment Group Profiles with below data:
Shipment Management > Equipment Management > Equipment Group Profile: