IBM Support

whbu030 generates ycs_manifest_ups_dtl record but no ycs_manifest_ups_hdr.

Troubleshooting


Problem

whbu030 generates ycs_manifest_ups_dtl record but no ycs_manifest_ups_hdr.

Symptom

Customer was seeing records for a particular manifest in YCS_MANIFEST_UPS_DTL, but not YCS_MANIFEST_UPS_HDR. Found that the same manifest number already existed in YCS_MANIFEST_UPS_HDR from about a year ago.

Resolving The Problem

Resolution 1:

Customer was seeing records for a particular manifest in YCS_MANIFEST_UPS_DTL, but not YCS_MANIFEST_UPS_HDR. Found that the same manifest number already existed in YCS_MANIFEST_UPS_HDR from about a year ago. Asked customer to:

1) purge table of closed manifests older than 6 months.

2) find the manifest in the SHIPMENT_MANIFEST table

3) set the MANIFEST_STATUS to '02' using a SQL update

4) reprocess using whbu030.

This resolved the issue.

Problem exists for more than one manifest, so customer will have to go through each manifest that was not sent, one by one, and follow the above steps. Customer confirmed that this issue is all set.

[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

NFX5602

Document Information

Modified date:
16 June 2018

UID

swg21558276