glog.shipment Properties

glog.shipment.createBMRefnum

Indicates whether the Bill of Lading (BM) reference number is created automatically when a shipment is created. If False, it is not created.

Default: True

glog.shipment.event.checkServiceProvider

If enabled, this checks shipment status processing and prevents processing of shipment status events with a service provider different than that on the shipment.

Default: False

glog.shipment.event.checkstatus

You can add a shipment status regardless of whether the shipment has a status of Secured Resources and Enroute_Enroute. You bypass checking the status to add the shipment status.

• True - enables adding an event to a shipment only if it has an enroute status and a secured resources status in its shipment status history.
• False - (default) enables adding the event. Still there may be things that cannot happen in Oracle Transportation Management considering the status of the shipment. For example, an agent cannot perform the action Recalc Estimated Stop Times since the status of the shipment is incompatible with this action.

Note: This property is used if Match Shipment or Legacy Shipment Matching tracking event agent actions are used so if the tracking event entered is for a shipment, then this property applies.

glog.shipment.event.publishNonTrackingEvents

Determines if Oracle Transportation Management should publish shipment status events, where the event's attribute IS_TRACKING has the value 'N'.

Default: true

glog.shipment.event.tracking.validate

Validation control for a shipment status event for tracking.

Note: This is all based on the glog.integration.validation.shipmentstatusinterface property.

• NONE - all event groups classified will be published.
• VALID - all event groups which pass the validation criteria are published
• TRACKING - (default) publish all event groups only if the Tracking Event Group passes validation
• ALL - publish all event groups only if ALL Event Groups pass validation

glog.shipment_overview.buy_shipment.DefaultFinder SetGid

5.5 CU3

Used when editing the cust-screenable elements. Also used when using the Add button to the Order Releases or Order Movements list in View Shipment Overview.

glog.shipment_overview.max_order_movements

5.5 CU3

Determines how many order movements display on the View Shipment Overview page.

Default: 10

glog.shipment_overview.max_order_releases

5.5 CU3

Determines how many order releases display on the View Shipment Overview page.

Default: 10

glog.shipment_overview.order_movement.DefaultFinder SetGid

5.5 CU3

Used when editing the cust-screenable elements. Also used when using the Add button to the Order Releases or Order Movements list in View Shipment Overview.

glog.shipment_overview.order_release.DefaultFinder SetGid

5.5 CU3

Used when editing the cust-screenable elements. Also used when using the Add button to the Order Releases or Order Movements list in View Shipment Overview.

glog.shipment_overview.sell_shipment.DefaultFinder SetGid

5.5 CU3

Used when editing the cust-screenable elements. Also used when using the Add button to the Order Releases or Order Movements list in View Shipment Overview.

glog.shipment.tarifffields.active

6.3

When set to true, tariff fields are NOT automatically copied from a rate offering to a shipment.

Default: false

glog.shipment.viewevents.sortorder

Controls in what order the shipment events are shown in the shipment events history page. This property name is misleading. If the value of the property is 'event_date' (default) then the events are shown ordered in a Descending fashion and ordered by the event date. It the value of the property is NOT 'event_date', then the events are shown still ordered by the event date, but in an Ascending fashion. And technically the value of the property, if it is not 'event_date', could be anything.

Default: 'event_date'