Skip to main content

Partial Picking configuration for Warehouse Management

Partial Picking configuration is set at two different areas within customising:

  • SPRO -> Logistics Execution -> Warehouse Management -> Master Data -> Define Control Parameters for Warehouse Number
  • SPRO -> Logistics Execution -> Warehouse Management -> Interfaces -> Shipping-> Define Shipping Control -> Shipping Control per Warehouse Number

The above configuration is utilised by the system in two different ways:

Define Control Parameters for Warehouse Number:
This configuration setting is only considered in multiple processing when the user creates picking instructions for a delivery group with WM reference via VL06P or a group of TR’s created via LT41.
If partial picking is not allowed, then the picking instructions created in background mode via LT42 will fail for the entire group if one or more line items is not completely fulfilled via a picking instruction, which will then require the user to step through each delivery in foreground mode to create the picking instructions.

Allowing partial picking will allow LT42 to run in background mode and create picking instructions for the available stock even if the available stock is less than the required amount. The picking instruction for the group will not fail if one or more line items is not completely fulfilled

Shipping Control per Warehouse Number:
This config setting is considered when the user creates picking instructions for a delivery via VL06P and follows the specified steps below:

  1. Execute VL06P.
  2. Select the required deliveries.
  3. Select Settings -> Subsequent Functions -> Background.
  4. Subsequent Functions -> Create Transfer Order.

Alternatively the user can create picking instructions in Background Mode from the initial screen of VL06P.
This setting is also a control parameter on function module L_TO_CREATE_DN.
This setting is not considered when picking instructions are created via multiple processing.

Comments

Popular posts from this blog

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...