Skip to main content

Sage X3 - [ERROR] ASN Missing Package and Item Level Data (DLL 8.17.XX.XXX)

Troubleshooting guide for Sage X3 V12 customers on DLL 8.17 where Advance Ship Notices import with 0 transactions due to the XX4STC parameter being disabled for the TMEDI user.

Written by Doug Heckman

Product: Sage X3

Article Link: https://help.truecommerce.com/en/articles/18247450-sage-x3-error-asn-missing-package-and-item-level-data-dll-8-17-xx-xxx

This article applies to Sage X3 Version 12 (V12) customers using a Dynamic Link Library (DLL) version that begins with 8.17 (e.g., 8.17.XX.XXX).

Issue: When performing an integrated search in TrueCommerce Foundry that returns results for an Advance Ship Notice (856) from Sage X3, clicking Import results in 0 transactions successfully imported — even when the Import Document Type is set and active under the Trading Partner menu. Reviewing the log shows the web service read is returning results, but the Dynamic Link Library (DLL) is not building out the XML, and the web service read result contains no User Defined Fields (UDFs).

Reason: The TrueCommerce Electronic Data Interchange (EDI) parameter XX4STC in Sage X3 is set to No for the TMEDI user. When this parameter is disabled, the DLL cannot attach the required UDF data to the XML output, causing the Advance Ship Notice (856) to import with no package or item level data.

Solution - Enable the XX4STC Parameter

To resolve this issue, the XX4STC parameter must be set to Yes for the TMEDI user in Sage X3 as a Super Administrator. After updating the parameter, web services must be republished and the Advance Ship Notice re-imported.

Step 1 — Verify the Log and Web Service Read Result

Before making changes, confirm you are experiencing this specific scenario:

  • An integrated search in TrueCommerce Foundry returns results for an Advance Ship Notice (856) from Sage X3

  • Clicking Import results in 0 transactions successfully imported

  • The Import Document Type under the Trading Partner menu is set and active

  • The log shows the web service read is returning results

  • The web service read result contains no User Defined Fields (UDFs)

  • The Dynamic Link Library (DLL) is not building out the XML

If the log shows the DLL did build out the XML, verify instead that the delivery in Sage X3 is packed, and that the Import Document Type is set and active.

Below is an example of what the log will look like when XX4STC is set to No.

Step 2 — Set XX4STC to Yes in Sage X3

Log into Sage X3 as a Super Administrator and update the XX4STC parameter for the TMEDI user:

Navigate: All → Setup → Users

Select: User TMEDI from the list on the left

Select: Parameters tab

Locate: Chapter "Sales" → Group "XX4S" → Description "TrueCommerce"

Select: Menu icon at the start of that row → Detail

Set: Parameter XX4STC (TrueCommerce EDI) to YES

Step 3 — Republish Web Services

Once XX4STC has been set to Yes, web services must be republished in Sage X3 for the change to take effect.

Republishing web services is a Sage X3 administration task. Contact your Sage X3 system administrator if you do not have access to perform this step.

Step 4 — Re-Import the Advance Ship Notice

After republishing web services, return to TrueCommerce Foundry and attempt to re-import the Advance Ship Notice (856) to verify that package and item level data is now populating correctly.

Navigate: TrueCommerce Foundry → Integrated Search

Search: Advance Ship Notice (856)

Select: Import

Review: Log and transaction results to confirm data is present

rev 11/05/26

Related Articles
Did this answer your question?