SAP Knowledge Base Article - Public

3793153 - EPCIS Messages Fail Due to Expired Batch and Missing DATEX/DATMF Values in SAP Traceability Hub

Symptom

  • EPCIS message processing fails.
  • Error message: "EPCIS message contains an expired batch(es) with an expiry date :: null."
  • Validation indicates missing or empty tag values for and in the EPCIS payload.

Environment

SAP Traceability Hub

Reproducing the Issue

Cause

The EPCIS message contains one or more expired batches for which the expiry date value is missing (null).

The required expiry date fields are not populated in the payload, causing message validation to fail during processing.

Resolution

  1. Ensure that valid values are provided for the following payload attributes:
    • <DATEX></DATEX>
    • <DATMF></DATMF>
  2. Populate both tags with valid date values as required by the integration specification.
  3. Correct the payload and resubmit the transaction or reprocess the failed message using Manage Message application.
  4. Verify that the message is processed successfully and no expiry date validation errors are reported.

See Also

Keywords

epcis, traceability hub, message failure, expired batch, expiry date null, datex, datmf, payload validation, missing attribute, verification repository, event processing, reprocess, xml tags, manufacturing date, expiry date , KBA , IS-LS-TH-NET-SCP , SAP Traceability Hub Message Exchange Issues SNR and EPCIS , IS-LS-TH , SAP Traceability Hub , Problem

Product

SAP Traceability Hub all versions