glog.settlement Properties

glog.settlement.allocation.metric.directDistance.checkForOrderPickupAndDropoffStopsOnlyOnShipment

6.4.2

If set to true, while calculating DIRECT DISTANCE metric for an order, OTM checks if the order has a pickup stop and drop off stop on the corresponding shipment.

This is useful in a multi-stop shipment, when an order is actually picked up or dropped off in intermediary locations, which are not the order source and destination locations.

For example, following are two order releases on a multi-stop shipment:

• OR1 --> A ------------------- E
• OR2 --> A ------------- D

There are three shipments as shown below:

                      (OR1,OR2)

• S1 --> A ----------- B  

• S2 -->   B ---------- C -------- D

• S3 -->                    C ------------- E

In the above example, to get the DIRECT DISTANCE metric of OR1 on shipment S2 with property set to false, OTM calculates the distance traveled between A to E.

When this property is set to true, OTM calculates the distance between B to C.

Default: False

This property controls whether to use existing distance or calculate the distance between the shipment stops of the shipment while allocating.

If set to true,  the existing distance will be used. 

If set to false, the system will calculate the distance between the shipment stops of the shipment.

Default: true 

glog.settlement.allocation.mergeLikeAllocatedCosts

6.2

If set to true, the resulting allocated costs will be merged if possible.

If false, no attempt will be made to merge them.

glog.settlement.allocation.singleCurrency

Configures whether allocated results are in the currency of the original cost line (shipment cost, voucher line, bill line item) or converted to the currency of the header.

The default is FALSE (currency of each cost line).

glog.settlement.allocation.useLineDescription

Configures whether or not Oracle Transportation Management considers the Invoice Line Item Description as criteria for rolling up costs during voucher and bill allocation. Oracle Transportation Management does this today, but assumes Description contains a Cost Type (B, A, O, S, D, etc.). By default, Oracle Transportation Management will allocate using a constrained Cost Type field. You can enable Description as a distinguishing factor if desired.

glog.settlement.claim.lines.createLines.UsingOneShipUnitAtATime

22A

When an order release has multiple ship units and you use the option "Select Order Releases" to create claim lines, duplicate claim lines will be created. When set to true, the application will not create duplicate claim lines.

Default: true

glog.settlement.invoice.GenerateInvoiceNumberOnCreate

This property is used in conjunction with the Generate Invoice/Bill Number action in the Invoice and Bill Managers. The default is TRUE, which means the invoice number is generated when an invoice or bill is created. If you wish to generate invoice numbers at another time, this property should be set to FALSE. It is then up to you to either run the generate invoice number action manually or set up an agent to do it.

glog.settlement.invoice.NegativeAdjustedCostMakesCreditNote

When you run the Invoice Adjusted Costs action from the shipment (which adjusts the invoice to match the shipment), if it ends up creating a new invoice, this property tells it to make any negative adjustments a credit note.

glog.settlement.invoice.disableParentInvoiceRecalcOnStatusChange

21C

This property will determine whether a status change to a child invoice will trigger a recalculation of its related parent invoice. If the property is set to true, it will disable triggering of recalculation on status change. If false, it will enable triggering of recalculation.

Default: true

glog.settlement.invoice.registerShipmentInvoiceCostFieldsSync

21C

This property will determine whether changes to the invoice cost fields will trigger a recalculation of its matched shipment. If set to true, it will enable triggering of recalculation. If false, it will disable triggering of recalculation.

Default: true