2-Step picking in WM

The two-step picking process is controlled at the material level. In the first step of this process, a single transfer order is created for a group of outbound deliveries or transfer requirements. Using this picking transfer order, you pick the total quantity of all of the required materials together.

In the second step, transfer orders are created to divide the removed quantity among the outbound deliveries or transfer requirements contained in the group.

The system decides whether a material is relevant for two-step picking on the basis of the two-step picking indicator in the Warehouse Management 1 view. Only materials with this indicator are included in the process. All others are picked in one step.

The two-step picking procedure divides the stock removal process into two steps: a withdrawal step and a distribution step. First, the total quantity of a material is removed from storage for a group of outbound deliveries and is stored temporarily  in a storage type set up for this purpose (storage type 200 in standard SAP). The material quantity is then distributed among the individual outbound deliveries and shipments in the goods issue area. Movement type 850 (“removal 2-step picking”) is also preconfigured in the standard SAP, and storage type 200 is assigned to it as the destination storage type. The storage bin search for this storage type is dynamic, which means that the system generates storage bins for putaway in relationship to the activity. Once the activity is complete, the system deletes the dynamic storage bins. However, in contrast to the one-step putaway and picking processes, the creation of the dynamic storage bin is not controlled by a requirement type but rather by a special storage bin search strategy. Strategy R (“dynamic coordinate reference number”), which is assigned to storage type 200 in a standard system, ensures that the number of the outbound delivery group is used as the storage bin coordinate during putaway. This means that in Warehouse Management, you can always see which specific group of outbound deliveries the picked quantity
belongs to.

Therefore, in order to use two-step picking, you have to consolidate outbound deliveries into groups. The outbound delivery monitor (VL06O) is the most suitable transaction for doing this. It offers a wide range of selection criteria for selecting outbound deliveries for processing as a group.

You can also form groups of outbound deliveries by grouping document numbers manually using transaction VG01.

In the outbound delivery monitor, select all of the deliveries that you want to group together and choose Subsequent Functions -> Group -> Create with WM reference. You can use a group formed in this way for one-step collective
processing as well. Generally, two-step picking is only possible if, during outbound delivery creation, the system has already recognized the relevance of a document item for the two-step process. If a material is flagged as being relevant for two-step picking in the WM1 view, the document item is included in this process. All material items that are not flagged are picked using the one-step method, which means that the system does not consider them in the withdrawal
step of the two-step procedure. However, you can change the relevance of a material for individual activities in a separate transaction (LT72) once the group has been formed. The settings for two-step picking for outbound deliveries are in Customizing forWarehouse Management under Logistics Execution ->Warehouse Management -> Interfaces -> Shipping -> 2-step Picking.

You can use user exit MWM2S001 to postpone the decision as to the relevance for two-step picking until after the groups have been formed, and make the decision dependent on non-material-related criteria.

Finding a Release Note in SAP

 Release notes describe the new functions and changes in each SAP release. Using the Help menu, you can display release notes for any SAP application and release. You can also search for release notes using keywords and attributes.

Whenever you receive a new SAP release, you should review the release notes. The release notes describe new functions that may affect the task you perform in the system. They also describe how to change Customizing and installation parameters before upgrading from one SAP release to another.

You can find a release note directly in your SAP system by executing T. Code SE61

Select Document Class as “Release Notes”. This field comes in display mode, but accepts your selection from F4 entries.

Then enter the release note in the field below for example “MM_PUR_40A_WIA” and execute.

 You can display release notes in the SAP Library or from within the SAP System.

 

To display release notes in the SAP System, proceed as follows:

 

  1. From the menu, choose Help ® Release notes.

The Find Release Notes screen appears.

 

  • For a list of all release notes, choose Complete list 3.0/3.1 or Complete list from 4.0.
  • Highlight the release notes for the SAP version you want to see, and choose Choose.A hierarchical list of the available release notes appears, with plus signs [+] to the left of every item that has sublists.
  • Display one of the release note sublists by double-clicking it.The sublist appears, containing release notes, more sublists, or both. You can identify a set of release notes by the fact that no plus or minus sign appears to the left of it.
  • Repeat step 3 until you see the desired release notes.
  • Double-click the release notes you want to display.

 

The release notes appear. To print the selected release notes, choose Print.

 Searching for Release Notes

You can search for release notes by keyword or by attribute.

A keyword is a term associated with a release note, such as “Purchasing” for release notes in purchasing.

An attribute refers to the type of information the release note contains. You can narrow the search for release notes by choosing the attributes of the release notes you want to display. For example, a release note has the attribute Changes to Customizing parameters if the new function requires a change in your system’s Customizing parameters. Thus, if you want to display all release notes requiring a change to Customizing, you can list all release notes with this attribute.

To search for release notes:

  1. From the menu bar, choose Help ® Release notes.
  • To search by keyword, choose Full text search.
  • To search for release notes that contain only a certain type of information, choose Attribute search.
  • Enter your search criteria (keywords or attributes).
  • Choose Find.

The system displays any release notes that match your search criteria.

 

 

Transaction for Held PO’s in SAP

You can get the list of Held POs in SAP using transaction ME80FN. Search for the field “Incompleteness” in the Header section of the dynamic selection and select “H  – Document on Hold”. You can also execute ME2N and look for the field “Incomplete” where you need to enter “X – Yes”. Same is the case with ME81N but this you need to execute per currency.

Contract / Scheduling Agreement upload is taking a lot of time

When you call function module BAPI_SAG_CHANGE and/or BAPI_CONTRACT_CHANGE for a huge amount of documents that itself have several items you will observe a very high memory consumption in class CL_MASTER_CONDITONS_MM. This causes the system to be very very slow and if the scheduling agreement or contracts have thousands of line items, the performance needs to be improved.

This is because the destructor for class CL_MASTER_CONDITIONS_MM is not getting called for agreement items.

Please install SAP Note 1612649 to improve the performance.