3790045 - Error - The Content Model Does Not Allow Element <Q{}lotNumber> To Appear As The First Child

Symptom

EPCIS messages are displayed with Error or Failed status with Error Description:
The content model does not allow element <Q{}lotNumber> to appear as the first child. Expected <Q{}extension> or nothing. There is an <xs:any> wildcard, but it does not match: The name is in one of the disallowed namespaces for the wildcard

Environment

SAP Traceability Hub

Cause

This issue occurs when the EPCIS message payload contains an invalid <ilmd> (Instance/Lot Master Data) structure.
Custom elements such as <lotNumber> are maintained directly under the <ilmd> element without a valid namespace definition.
As a result, XML schema validation fails because the payload structure does not comply with the expected EPCIS schema requirements.

Resolution

Ensure that the required XML structure and namespaces are correctly maintained in the message payload.

Required Payload Validation:
• Review the <ilmd> section of the EPCIS message payload.
• Ensure that custom elements are defined using valid namespaces.
• Do not place custom elements directly under the <ilmd> element.
• Reprocess the failed messages after making the corrections.

Example of Valid Namespace for a Custom Element:

<ABCcompany:lotNumber>LOT12345</ABCcompany:lotNumber>

</ilmd>

If the issue persists, create a support ticket under component IS-LS-TH at https://support.sap.com

Keywords

DisallowedNamespaces, ILMD, Instance/Lot Master Data, lotNumber, Namespace Validation, xs:any wildcard, SAP Traceability Hub, US DSCSA Transaction Information Exchange, Payload Structure , KBA , IS-LS-TH , SAP Traceability Hub , Problem

Product

SAP Traceability Hub all versions