cancel
Showing results for 
Search instead for 
Did you mean: 

Shipment idoc getting stuck in Status 52

Former Member
0 Kudos

We are working with Shipments.

For Shipment documents, the shipment completion is getting set through incoming Idoc of basic type SHPMNT04, Message Type SHPMT. This idoc sets the shipment status to complete and also as per activity profile assigned to u201CShipment Completionu201D, PGI of the deliveries in shipment is taking place.

We have issues in Production where Idoc is getting stuck in Status 52 with Message # VW 229 u2013 Delivery XXX in Shipment could not be posted for GI.

This is happening for no apparent reason. We have checked the deliveries and deliveries are complete in all respects. In case there is any issue with deliveries, we get more concrete messages like No picking done, batches missing, etc.

Above is happening through batch job. We have tried to replicate the same in Quality systems; but are not able to do so after repeated attempts.

If anyone would have encountered a similar issue earlier and is aware of same, would request you to revert.

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member182609
Active Contributor
0 Kudos

we have faced the similar prob like Idoc stuck 52 and it will not do PGI for the deliveries (The reason could article locs or delivery data lock...etx).For these we need to do shipment completion manually then do PGI .

We pimplemented solution for shipment idocs ,we separated the Delivery PGI job.It will crete shipment first then batchjob (VL06O) will pick these shipment deliveries to do PGI.Now our idocs are successfully posting to 53.