Do I need a new license file for the deployable package distributed for a new release?

No updated license file is currently needed.

If one is needed for a future release, Avanade will communicate deadlines and instructions through as well as informational pages.

How do I request Saturday delivery?

Saturday delivery is requested by adding an accessorial. Accessorials can be added manually or via accessorial assignment.

See for accessorial setup and assignment.

How is the container line item value populated?

The container line values for Ship requests are populated in the TMSProcessXML_Base D365 TMS class and come from the item master purchase price.

I do not see miscellaneous charges on sales order lines after confirming a shipment.

Make sure an apportionment engine is specified on the SCC engine (as shown in ).
Make sure to configure item weights; the AppWeight apportionment method requires item weights.
Look at the Apportionment TMS transaction (as shown in ). Often, errors displayed in the transaction can help clarify the issue.

There are no carriers/services in carrier/service drop-downs while configuring carriers in F&O.

Make sure your tenant API key is configured properly in the Ship module parameters.
Make sure the desired services are enabled within Supply Chain Cloud. That configuration is described in the guide.

Where are delivery address fields populated?

Delivery addresses for Ship requests are populated in the TMSSourceDocument_SalesTable and TMSAddressPhone base D365 TMS classes.

Where are the site/warehouse fields populated?

Site and Warehouse for Ship requests are populated in the TMSSourceDocument_SalesTable base D365 TMS class and come from the Sales Order Header.

I received the following error message:

During license Ship installation in F&O: "The certificate associated with this license ATO is not a trusted certificate."

Navigate to GoDaddy and download/install the “GoDaddy Certificate Chain - G2” certificates into your VM.

If this is a tier-2 machine (or production), put in a ticket with Microsoft to install the certificate bundle.

Error containing "Wrong Parameters."

Check the length of the Container ID; it should not be more than 20 characters.

Error during transmission: Document type "File" does not exist.

Supply Chain Cloud saves shipping labels as the document type "File" in D365.

You must have this document type configured in order manifest.

Organization administration > Document management > Document types

Function ATOShippableContainerTypeFinder_SourceOrderLine.findShippableContainerType has been incorrectly called.

Make sure the Shippable container directed by module parameter is set to "No shippable container type."

See for clarification.

I have account assignment records configured but am still receiving errors indicating the records cannot be found.

Make sure the account assignment criteria matches the data being used in the given scenario.
Make sure the account assignment records are enabled. Account assignment records that are not enabled are not considered during the account assignment process.

Rate shopping works, but manifesting fails, alerting "Missing or invalid shipper number" even though everything else is the same.

If you are using prepaid shipping terms, and DDP is enabled, a third-party account number is still required on the customer's account/sales order because DDP is stating that the end customer is responsible for duties and taxes.

Rate shopping does not need that value, but manifesting does.

Rating and routing returned exception "RAT0012" and note "SCC Error: The carrier of the order does not match the carrier of the current shipment."

Go to in D365 and check if the following fields are populated:

- Ship Carrier Code
- Ship Carrier Service Code

Rating and routing returned exception "RAT0012" and note "SCC Error: The carrier service requested is not enabled."

Enable the individual service in SCC.

Unsupported container shipping label type.

Make sure the label type F&SCM receives from the carrier is configured in your container packing policy > Close Container Profile Print.

If the carrier only supports PDF, make sure a PDF printer is included in the Close Container Profile Print section of the Container packing policy.

Upon ship confirmation: "TMSEngineSetupException: Assembly name not specified. Verify engine configuration."

Verify that an apportionment engine is specified in the SCC rate engine parameters.
Verify that the specified apportionment engine is set up properly in "Generic engines."

When shipping FedEx Smartpost with a <1 lb parcel.

Make sure the FedEx_SmartPostPresortedStandardAncillaryEndorsement SCC rating engine parameter is set to ADDRESS_CORRECTION or RETURN_SERVICE.

See for SCC rating engine setup and parameters.

Browser not supported