SAP Knowledge Base Article - Public

3778008 - Verification Repository Message Failure – Expired Batch with Expiry Date :: null

Symptom

EPCIS messages are displayed with Error or Failed status with Status Description: EPCIS message contains an expired batch(es) with an expiry date :: null.

Environment

SAP Traceability Hub.

Cause

The EPCIS message payload contains batch information where the expiry date is missing or not maintained (null value).

Specifically, the following attributes are either empty or not populated in the payload:

  • <DATEX> (Expiry Date)
  • <DATMF> (Date of Manufacture)

Due to the absence of valid expiration date information, the system interprets the batch as invalid or expired, resulting in message failure.

Resolution

To prevent EPCIS message failures, ensure that the required attributes are correctly maintained in the message payload.

Required Payload Validation:
1.<DATEX></DATEX>
2.<DATMF></DATMF>

Review the EPCIS message payload, Correct and update the payload with proper values.
Reprocess the failed messages after making the corrections.

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

Keywords

EPCIS message failed, EPCIS message contains an expired batch(es) with an expiry date :: null, SAP Traceability Hub,Verification Repository, US DSCSA Transaction Information Exchange. , KBA , IS-LS-TH , SAP Traceability Hub , Problem

Product

SAP Traceability Hub all versions