Troubleshooting
Problem
In a few instances, when you are trying to add a container to the manifest(addContainerToManifest API), the error 'Manifest is in Closure Requested Status' may be encountered
Cause
When you are trying to add a container to the manifest, but there is already a manifest for this carrier Service in 'Closure Requested' Status, you will see the error reported
This is working as expected.
Diagnosing The Problem
The clause used to check for existing manifest before opening a new one is :
WHERE SHIPNODE_KEY = <> AND SCAC =<> AND SHIPPER_ACCOUNT_NO = <> AND MANIFEST_CLOSED_FLAG = 'N' AND ( MANIFEST_STATUS IN ( '1100' , '1300' , '1200' ) ) AND MANIFEST_DATE >= <> AND MANIFEST_DATE <= <>
When manifest is in 'Closure Requested' Status, we treat it as Open and NOT closed. This is to prevent creation of multiple manifests for the same carrier. If multiple manifests are created and one of them moves to Closure Failed status, it will result in two manifests causing confusion.
Resolving The Problem
One instance where the error is thrown is the following-
If you are running closeManifest API in yfs.closemanifest.online=Y , the API is probably still running, trying to confirm all Shipments before closing the Manifest. The manifest eventually closes and you will be able to add the container to a new manifest. You can attempt running closeManifest again after a few seconds.
If yfs.closemanifest.online=N , then the same is being performed by the CLOSE MANIFEST agent and the user will have to wait for the agent to process the Manifest
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22000302