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

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).
4 comments
Read more

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.
Post a Comment
Read more

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...
1 comment
Read more