OTMZOPTE - Optimization service errors

If an exception occurs in the Optimization service, a OTMZOPTE exception occurs. Learn about each OTMZOPTE error by its error code and message.

Table 1. OTMZOPTE - the Optimization service errors
Error code Error message
OTMZOPTE001 Invalid time format for cut-off.
OTMZOPTE002 Multiple lines containing the same SKU cannot supported SKUID <skuID>.

For example, Multiple lines containing same SKU are not supported, skuId ‘12035689'.
OTMZOPTE004 Capacity consumed value is not passed in the input to the Optimizer API.

For example, Capacity Consumed value is null or blank in input of Optimizer API for OrderID:
OTMZOPTE005 Standard capacity is not defined <Node ID>.

For example, Standard Capacity not defined 'Node102'.
OTMZOPTE006 Processing plan not defined.
OTMZOPTE007 Node balancing constants not defined <Node ID>

For example, Node balancing constants not defined 'Node36'.
OTMZOPTE008 Transit Matrix between origin zip <originZip> and destination zip <destZip3> missing/exception.

For example, Transit Matrix between origin zip '489' and destination zip '356' missing/exception.

Tip: While using CAS, check the zone configuration setup.
OTMZOPTE009 Rate card not defined for nodeType <Node ID>.

For example, Rate Card not defined for nodeType 'Store'.

Tip: While using CAS, check the transit rate setup.
OTMZOPTE010 Time zone not defined/Invalid for node <Node ID>.

For example, Time-zone not defined/Invalid for node 'Node36'.
OTMZOPTE011 SKU <SKU ID> exceeds weight limit.

For example, SKU 46448325 has weight 200.7 more than 150 lbs.

The weight of SKU 46448325 is 200.7 lbs. This amount exceeds the limit of 150 lbs.

The weight of an SKU is calculated as Maximum of SKU weight or [(sku length * sku width * sku height) / Dimensional Weight Factor of CMF].
Note: The default weight limit for the SKUs is 150 lbs. Contact IBM support to adjust or increase the weight limit. For more information, see Contacting IBM Support.
OTMZOPTE012 Carrier with sufficient weight limits were not found.

For example, Optimizer cannot find a carrier with sufficient weight limits.

OrderID: OrderType_28, Node: 37, Carrier: 4, ToZip: 36100, Weight: 1.0, Cost: 99999.0

Check the missing data in RC for the carriers.

Tip: While using CAS, check the transit rate setup.
OTMZOPTE014 The Optimization service order rejected because the order is large for optimization <Order ID>.

For example, Optimizer order rejected because order is large for optimization 'order123'.
OTMZOPTE015 The CarrierMode value <carrierMode> is invalid.

For example, CarrierMode value 'Mode16' is invalid.
OTMZOPTE016 Integer value <slaCode> does not map to a proper SLACode.

For example, Integer value '4' does not map to a proper SLACode.
OTMZOPTE017 Inv feature <dataFormat>: wrong date format.

For example, Inv Feature '2017-23-31': wrong date format.
OTMZOPTE018 Cap configuration missing for node <Node ID>.

For example, Cap Configuration Missing for Node 'Node123'.
OTMZOPTE019 Consumption for node <Node ID> missing.

For example, Consumption for node 'Node123' missing.
OTMZOPTE020 Unable to get SLA days <Node ID>.

For example, Unable to get SLA days 'Node123'.
OTMZOPTE021 Total Available Qty cannot be Zero/blank for assignment <AssignmentKey>.

For example, Total Available Qty can not be Zero/blank for assignment '2106::::2013589522'.
OTMZOPTE023 Derived Capacity not defined for node <Node ID>.
For example, Node derived Capacity not defined for Node 'Node123'.
Note: The terms Node Capacity Plan, Node Processing Plan, and Node Derived Capacity are used interchangeably in the Optimization service.
OTMZOPTE024 No OrderLines found for order <Order ID>.

For example, No OrderLines found for Order 'Order123'.
OTMZOPTE025 Unable to retrieve the current OTMZ runtime context.
OTMZOPTE026

Error occurred while validating zip code. Zip code format is null.

If the zip code is not properly formatted based on the country code that was assigned to the tenant, this error is thrown during the optimization call. For example, if the zip code was set to D@4 5AG and the tenant country code was set to US, this error would be thrown.
OTMZOPTE027

Error occurred while extracting zone information from the zip code.

If the fulfillment network feed contains nodes that reside outside of the country that was set for the tenant during onboarding, this error is thrown during the optimization call. For example, if the fulfillment network has nodes belonging to Canada, yet the tenant was onboarded with a US country code, this error would be thrown.
OTMZOPTE028 Error occurred while validating zone. Zone format is null.
OTMZOPTE029 Node Configuration Constants value for Node ID: %s is missing.

For example, Node Configuration Constants value for Node ID : Node123 is missing.
OTMZOPTE030 Could not find feasible carrier service for SLA code %s.

For example, Could not find feasible carrier service for SLA code 01.

Check reference data in NCA.
OTMZOPTE032 Could not find feasible carrier service for SLA %s, node %s and zip code %s.

For example, Could not find feasible carrier service for SLA 'Standard Ground', node '21' and zip code '56789'.

Check for missing data in NCA, TM and RC for given SLA, node and zip code.
OTMZOPTE042 The entire order was rejected. For more information about the order and reasons for rejection, search for the order in the Optimization service.
OTMZOPTE044 The OrderDate attribute is missing or blank in the input to the Optimizer API.
OTMZOPTE045 OrderNo attribute is missing in the input to the Optimizer API.
OTMZOPTE046 The LineId attribute is missing in the input to the Optimizer API.
OTMZOPTE047 The ItemID attribute is missing in the input to the Optimizer API.
OTMZOPTE048 The RequiredQty attribute is blank in the input to the Optimizer API.
OTMZOPTE049 The quantity attribute of assignment is missing or blank in the input to the Optimizer API.
OTMZOPTE055 Order lines are missing in the input for orderId: <Order ID>.