Skip to main content

Batch Management - SD

This functionality is used by SD, MM, PP, WM Module and can be handled at client , Plant and Material Level.

Configuration

Condition technique

Condition table ------> All possible combinations of deriving batch will be created in the form of condition table

Access sequence  -----> Assignment of Condition table will be done

Strategy type ----> Assignment of Access sequence will be done and besides it

In this selection class and the sort sequence will be assigned

Controls Classification of batches, sort sequence and Batch split

Batch search Procedure  -----> Assignment of strategy type for Procedure will be done

Sales area and document type ----> Assign Batch search Procedure

Automatic batch determination need to be activated at Sales order and Delivery Item category level.

If batch is determined at sales order level then this will be copied over to Delivery.

Ideally it's better to determine batch at delivery level.

Create a material which is Batch Managed or if batch material already exist then we can consider it as well

Master Data

Batch Search strategy ----> Here condition records will be maintained against the required combination

If business doesn't require batch to be determined based on the selection class then selection field need to be maintained with appropriate parameter

Comments

Popular posts from this blog

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.

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...

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...