Import Shipping Method

The Shipping Method attribute is a combination of three attributes. You use different attributes depending on the technology you use to import.

Sales Orders for Order Hub Resource in REST API	SourceSalesOrderImportTemplate Through File-Based Data Import
ShippingCarrierId	Shipping Carrier Code
ShippingMode	Shipping Mode
ShippingServiceLevel	Shipping Service Level

If you import a shipping method through REST API or FBDI, you must make sure the method is valid.

• If you include a value for one of the three attributes, then you must include a value for all of them. For example, if you include a value for ShippingCarrierId, then you must include a value for ShippingMode and ShippingServiceLevel.

• The WSH_MODE_OF_TRANSPORT lookup type must contain the value you import for ShippingMode.

• The WSH_SERVICE_LEVELS lookup type must contain the value you import for ShippingServiceLevel.

For details and examples, go to REST API for Oracle Supply Chain Management Cloud, expand Order Management, then click Sales Orders for Order Hub.

The combination of ShippingCarrierId, ShippingMode, and ShippingServiceLevel must be valid with each other. Here's an easy way to identify valid combinations that you can import.

1. Go to the Order Management work area, then create a sales order.

2. In the Order Lines area, click Shipment Details.

3. On the Shipment Details tab, in the Shipping Method attribute, click down arrow > Search.

4. In the Select Shipping Method dialog, leave the attributes in the Search area empty and click Search.

5. Select a set of values from the search results and use them in your REST API payload or FBDI template.

   Here are some example results.

   Shipping Method	Carrier	Mode of Transport	Service Level
   Airborne Parcel Express	Airborne	Parcel	Express
   Airborne Parcel 2nd day air	Airborne	Parcel	2nd day air
   Airborne Parcel Standard	Airborne	Parcel	Standard
   Big Rigs Truckload Ground	Big Rigs	Truckload	Ground
   Nautilus Rail Standard	Nautilus	Rail	Standard
   Nautilus Ocean Standard	Nautilus	Ocean	Standard

   Here are some examples of combinations that aren't valid.

   Shipping Method	Description
   Nautilus Standard	Standard isn't a mode of transport.
   Airborne Express Parcel	Express isn't a mode of transport. Its a service. Parcel isn't a service. Its a mode of transport.

Identify Lookup Values You Can Use

1. In the Setup and Maintenance work area, go to the task.

   • Offering: Manufacturing and Supply Chain Materials Management

   • Functional Area: Carriers and Transit Times

   • Task: Manage Carriers Lookups

2. Identify the modes of transport you can use.

   • On the Manage Carriers Lookups page, search Lookup Type for WSH_MODE_OF_TRANSPORT.

   • In the search results, examine the values in the Lookup Meaning column.

     Example results include Air, Less than Truckload, Ocean, Parcel, Rail, Truckload, and so on. Set the ShippingMode attribute in your import payload to one of these values.

     If you don't see the lookup code you need, then click Actions > New in the Lookup Codes area, and add it.

3. Identify the service levels you can use.

   • On the Manage Carriers Lookups page, search Lookup Type for WSH_SERVICE_LEVELS.

   • In the search results, examine the values in the Lookup Meaning column.

     Example results include Door-to-door, Express, FedEx 2day, and so on. Set the ShippingServiceLevel attribute in your import payload to one of these values.

     If you don't see the lookup code you need, then click Actions > New in the Lookup Codes area, and add it.

Troubleshoot

If you import a shipping method that isn't valid, then the communication with Global Order Promising might fail. You will notice when the Order Entry Specialist attempts to submit a sales order but receives an error, similar to:

You can't submit the sales order because the combination of the mode of transport, service level, and carrier that determines the shipping method on the order header isn't valid.

Here are some solutions you can try.

Trouble	Shoot
The DOO_VALIDATE_ORDER_SHIP_METHOD processing constraint or DOO_VALIDATE_FULFILL_LINE_SHIP_METHOD constraint examined the shipping method and found that it isn't valid.	Reimport the shipping method with the correct values.
The mapping in MSC_XREF_MAPPING isn't valid. The msc_xref_mapping entity in the Order Orchestration and Planning Data Repository maps values for the shipping method. For example, assume you see Airborne Parcel 2nd day air in the Order Management work area, but msc_xref_mapping maps the alphanumeric value to a numeric value, so the repository stores only the numeric value. Map Airborne to 32510 and store 32510 in the carrier_id column of the repository. Map Parcel to 39 and store 39 in the ship_mode_of_transport column of the repository. Map 2nd day air to 821 and store 821 in the ship_class_of_service column of the repository. Assume you create a pretransformation rule or an order management extension that transforms the carrier ID to -999 before or during order submit. msc_xref_mapping doesn't map -999, so the carrier isn't valid and Order Management will display an error.	Make sure msc_xref_mapping correctly maps your values. Make sure your set ups don't modify the mappings that msc_xref_mapping references.