Supply Chain Management Blog Posts by Members
Learn about SAP SCM software from firsthand experiences of community members. Share your own post and join the conversation about supply chain management.
cancel
Showing results for 
Search instead for 
Did you mean: 
28,275

SUBJECT:

Steps to replicate and resolve the queue failure with error message “There are no delivery documents for these selection criteria”

Stock Transfer Order:

A Stock Transfer Order (STO) is a document or request used in inventory management and logistics to transfer goods or stock from one location to another within the same organization or between different branches or warehouses. It helps manage and track the movement of inventory to ensure that the right quantities are available at the right locations when needed.

Inbound delivery:

An inbound delivery is a logistics term referring to the process and documentation involved in receiving goods from suppliers or vendors into a warehouse or distribution center. It is a critical component of the supply chain, focusing on the receipt of inventory and its subsequent integration into the warehouse management system.

Outbound delivery:

An outbound delivery refers to the process and documentation involved in dispatching goods from a warehouse or distribution center to customers, other warehouses, or locations within the supply chain. It encompasses all activities related to preparing, packing, and shipping items out of a facility.

Reference Document Categories:

Reference Document Categories are classifications used within information management and enterprise systems, such as ERP (Enterprise Resource Planning) and document management systems, to organize and categorize various types of documents and records. These categories help streamline document management, retrieval, and processing by providing a structured way to classify and manage different types of documents related to business processes.

ASN:

Advance Shipping Notification, is a crucial document in the logistics and supply chain management processes. It is sent by a supplier or shipper to inform the recipient (such as a warehouse or customer) of the upcoming shipment and provide details about the contents and expected arrival.

BOL:

Bill of Lading (BOL) is a crucial document in the transportation and shipping industry that serves multiple purposes, including acting as a contract of carriage, a receipt of goods, and a document of title. It is used to facilitate the shipping process and ensure that goods are transported from the sender to the recipient as agreed.

Steps to replicate and resolve the queue failure with error message “There are no delivery documents for these selection criteria”

The Reference document categories configuration has the ASN and BOL inactive options check marked.

PrasannaG_0-1724395234390.png

 

Scenario:

Stock transfer order is created using the Transaction code ME21N

PrasannaG_1-1724395270892.png

Advance return delivery created using transaction code VL31N

PrasannaG_2-1724395285209.png

 

Complete Picking and Goods Issue in S4

PrasannaG_3-1724395300610.png

Inbound delivery created Automatically in S4

The external id populates Automatically with Outbound delivery number.

PrasannaG_4-1724395314539.png

 

Completed Goods receipt and Putaway against IBD in EWM

 PrasannaG_5-1724395323992.png

PrasannaG_6-1724395337291.png

PrasannaG_7-1724395342676.png

The external id changed to empty with no Outbound delivery number and therefore the queue DLWSDEPCLNT1200400057211 is stuck with the error message “There are no delivery documents for these selection criteria.”

PrasannaG_8-1724395357243.png

PrasannaG_9-1724395368273.png

 

PrasannaG_10-1724395377711.png

After configuration change by unchecking Inactive for ASN and BOL:

 PrasannaG_11-1724395417768.png

I have reset the queue, but the error persists.

 PrasannaG_12-1724395431829.png

 

PrasannaG_13-1724395439078.png
 
Result: Reprocessing the queue does not work as the entry in LIKP-LIFEX is still missing and the absence of outbound delivery in the external id field of the inbound delivery.

For the queue to be successfully reprocessed the field LIFEX (External Field) of the Inbound delivery should be filled with Outbound delivery number in LIKP table but whereas the new deliveries created after the above configuration maintained will no longer face the error. 


Retested Scenario after the configuration is changed:

Stock transfer order created using the transaction code ME21N

PrasannaG_14-1724395470335.png

Return delivery created using the transaction code VL31N 

PrasannaG_15-1724395488433.png

Inbound delivery created Automatically in S4

PrasannaG_16-1724395514937.png

 

The external id populates Automatically with Outbound delivery number.

PrasannaG_18-1724395608567.png

Completed Goods Receipt and Put away against IBD in EWM

PrasannaG_19-1724395624510.png

 

PrasannaG_20-1724395638099.png

 

PrasannaG_21-1724395642561.png

The external id still populates Outbound delivery number after Goods Receipt completed.

 PrasannaG_22-1724395660027.png

 

PrasannaG_23-1724395668787.png

 

PrasannaG_24-1724395673091.png

No queue error occurred.

The scenario is processed successfully.

Conclusion:

Steps to replicate and resolve the queue failure with error message “There are no delivery documents for these selection criteria” is provided.



Labels in this area