on 03-20-2013 10:43 PM
Hi All,
We are using the FEFO strategy for Stock Removal. In case of PGI against the Deliveries , we want systemm should first check with FEFO. If for the same material , same batch numbers(having same SLED) found in different palletes then System should first check the pallet quantity accordingly Delivery quantity & picking shall be done .
Now when we are creating TO in foreground , we can manually select the pallete , but if the TO is creating in background, we want the functionality to search for the full quantity pallet & pick that one instead of using broken pallets .
Awaiting your valuable comments
Regards,
Satpal
Hi,
"System should first check the pallet quantity accordingly Delivery quantity & picking shall be done"
So you want a best fit? According the delivery find a pallet? No standard strategy supports this. If you build it, they will come...
Best regards
Juergen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Satpal,
You can enter only one stock removal strategy for a particular storage type. You mentioned that FEFO ( SLED based) stock removal strategy is being used.
You must work with ABAP to find user exits to enhance the stock removal strategy FEFO to include the feature of checking for full pallets first and then look for broken pallets.
Pls find below SAP help on SPRO
In the Warehouse Management system you can develop your own stock removal strategy using an SAP user exit.
You can also use the existing checks and updates from the stock removal strategy FIFO by combining the standard strategy with your own stock removal strategy.
Standard settings
For the area of Warehouse Management (stock removal strategy), the following user exits are available:
MWMTO004 "Own stock removal strategy" (FIFO strategy)
MWMTO013 "Own stock removal strategy" (stringent FIFO strategy)
Further user exits of the Warehouse Management system are listed in the chapter "Tools - Develop user exits for Warehouse Management".
Activities
Further notes
User exits, in contrast to modifications, are not affected by SAP releases because they are not written in SAP original code but in a name area that is reserved for customers.
The general procedure for creating user exits is described in the user exit transaction under the menu path "Utilities - Online manual".
Each user exit is documented. You will find additional documentation by pressing the pushbutton "SAP doc." in the user exit transaction.
Re
SRI
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.