Re : Reservation stock in warehouse management

Hi
I am transfering warehouse stock to production; I am using LT01 and LT12 for pick and confirm the material transfer from warehouse to production. after doing confirmation using co15 the bin stock ir removed(LS24). But the reserved stock in MMBE is not removed.
How to remove reserved stock
while not using LT01 and LT12 the werehouse stock is not removed. Bot stock in MMBE is removed.
How to solve this.
Thanks
Anto

Hi,
Reservations which you see in MMBE are created against either a Production Order / Cost Center reservations.
In you case you are transferring the Material from the Warehouse to Production Storage location, Logically if your production order reservation is existing agisnt the Production Storgae location system should remove the reservation on confirmation of the order (with backflush option used ).
I suggest you to run the MRP for the material in MD03 and check as the Goods Issue is completed for the order reservation should be removed.
Hope this will help you.
regards
radhak mk

Similar Messages

In warehouse management how to post stock in the warehouse by using physica

hi
in warehouse management how to post stock in the warehouse by using physical inventory method
can anyone tell me the process in detail
thanksin advance.

HI ,
In Ware house management you can block the stock for Physical Inventory purpose. You cannot post the stock to the warehouse using Physical Invenory.
If there is a count going on so the concerned Warehouse bin is to be blocked during Inventory so that no further goods movement is possible during that period.
Once the Physical Inventory ids done the block can be released so that the movement can again happen.
The Inventory mangement initiates the transfer requirement. This transfer requirement is used for creating the transfer orders. The transfer order confirmation is done then which actually places the stock in the concerned bin mentioned in the order.
The stock in WM can be checked in LX24/ LX26 which is same as theat of MMBE of MM.
Hope this helps.
Regards,
Prasanna
Award pls if helpful.

Stock posting for warehouse managed plant

Dear All,
Our plant is warehouse managed.
I am unable to post the stock using 561 or 501 Movement types.
How to post the stock if the plant is warehouse managed?
Is there any spcial indicators available?
Kindly suggest?
Mullairaja

Hi,
I think, my question is not phrased well.
My question is, if the plant is warehouse managed, do we need to use different movement types to post the stock?
Because, I was unable to post the stock using the movement types 561 or 501.
Please clarify.
Regards,
Mullairaja

User Exit for putting own stock placement logic in WM (Warehouse Managment)

Hi Techi's,
I have got one requirment for stock placement in Warehouse Managment as below:
If client uses the standared strategy for putting stock in Storage Bin as "Addition to Stock" Then the self life of the coming material is being replaced by the existing material's seft life.
If they use the "Next Empty Bin" strategy than the obove issue is not coming but system always searches for the full empty bin only thus wastage of the existing bin's which already has some space.
Now what my client wants is to use the "Next Empty Bin Strategy" so that self life is not being overwritten but along with system should not search the complete empty bin for placing the stock rather it should search the bin's which already has some space then later move to the empty bin's.
For good reciept they are using MB01.
In summary its a mixture of "Addition to Stock and Next Empty Bin" Strategy.
Please suggest me the Exit for this if available or tell me the code if already has implemented it. Friends its going very hot.
Please please help me.
Thanks in Advance.
-=Maddu=-

Hi Maddu,
If I undertstand it correctly,
System should search for the available Bin Capacity, and if there is space available the next incoming stock also need to be placed in the same Bin (system should suggest the Bin).
Now, let us consider the Physical process involved. Let us say, System suggested Bin A1001 and stock of Material A 500 Qty has been placed in some part of the Bin. Now, next time for the same material while incoming, system let us assume for time being suggested A1001 Bin due to available capacity. The operator should place the stock in the same bin, right. Assume that you have two quants in the Bin so that in system Shelf life date (GR Date) is different for these two different receipts. However, while Issuing even if system suggested Bin based on Shelf Life date, how the Operator will physically identify between the above two stocks. Hence, there should be physically some more identification parameters.
Under this case, either you can have Batch Management, (two have multiple quants) or Storage Unit Management. In this way, system will suggest the Identifier based on GR Date or Shelf life Exp date, also physically some labels placed to identify the different stocks in the same Bin.
I hope, it clarifies your doubt.
Last but not the least, user Exit will not solve your purpose.. instead operation process change involved along with Batch Identifier or Storage Unit Identifier.
Please reward points, if it helps.
Thanks & Regards,
Ramkumar

Decentralize warehouse management

Dear Friends,
This is the question related to warehouse management system.
My requirement is that we are going to set decentralize management. Presently we are having CWM in our present system. At another place there is local ERP , we want to replace it and need to go for decentralise WM there.
Then this decentralised WMS and my present WM willl communicate with each other.
Could you please let me know what will be it process ? Transaction cycles ? and its configuration?
Regrads,
Mahesh

Dear All ,
I got some information I am sharing with you and closing this ticket.
1) Process :
rocesses Between the SAP System as ERP System and as WM System
Purpose The variant for the SAP System as an enterprise resource planning (ERP) system and as a Warehouse Management (WM) system describes the link-up of an external warehouse management system to an SAP System. The stand-alone system that executes all warehouse management functions is an SAP System. Prerequisites Two systems are involved in this scenario. The first system is an ERP system that performs inventory management, purchasing and sales tasks and distributes existing master data and movement data to the Warehouse Management system (WMS). The second system is a WMS that performs warehouse management tasks such as putaway/picking and goods receipt/goods issue and is responsible for carrying out the physical material transfers. Process and Data Flow General inventory postings: If the decentralized scenario is used, inventory postings are not directly processed in Inventory Management (IM). If a goods movement is created in IM, the system generates inbound or outbound deliveries and distributes them to the WMS. In the WMS, the goods are put away or picked based on the existing delivery. As a result of the goods movement posting in the WMS delivery, the system sends the completion verification to the ERP system and then uses the delivery to post the actual goods receipt or goods issue in inventory management. Deliveries with a purchase order or a sales order as a source document are handled in the same way. Goods receipts based on purchase orders: You use the ERP system to create purchase orders and send them to the vendors. To give notification of the delivery that is due, the vendor returns a shipping notification that is recorded in the ERP system as an inbound delivery. The inbound delivery is distributed to the WMS using a Business Application Programming Interface (BAPI). In the WM system, the inbound delivery is a request to put away or pick goods. When the vendor physically delivers the goods, a transfer order is generated in the WMS which is used to place the goods into stock. After the transfer order is confirmed, goods receipt is posted for the inbound delivery. This clears the interim storage bin. As a result, the completion confirmation is sent to the ERP system and the goods receipt is processed in inventory management. An inbound delivery based on a purchase order can be created in different ways, depending on the confirmation control key in purchasing. If the vendor usually sends a shipping notification, the inbound delivery is created when the shipping notification is recorded in the system. In all other cases, you have the option of creating inbound deliveries automatically using collective processing. Process for goods receipts based on a purchase order: Creating the purchase order in the ERP system Generating the inbound delivery (automatically/manually) Distributing the inbound delivery from the ERP system to the WM system using BAPI method "InboundDelivery.SaveReplica" (this process is automatically executed in the background) Physically receiving the goods into the warehouse (WMS) Creating the transfer order Putting the goods away Confirming the transfer order Posting goods receipt for the inbound delivery (as a result, a completion verification is sent to the ERP system using BAPI method "InboundDelivery.ConfirmDecentral") Goods receipt for the inbound delivery is automatically posted in the ERP system (in inventory management) when the verification is recorded. Quality management in decentralized WMS using handling units (HUs) Quality management is also available in the goods receipt process in the decentralized warehouse. In this scenario, the quality management function is in the central system. If there are handling units in the inbound delivery for which an inspection lot has been created, the inspection lot number is copied into the decentralized WMS and stored in the quants there. The inspection lot does not exist in the decentralized system. You make the usage decision for the inspection lot in the central system, which triggers the system to create a posting change delivery and distribute it to the decentralized system. Then, the stock that belongs to this inspection lot is found in the warehouse and the corresponding posting change is made. From this point on, the procedure is the same as that of a posting change (see below). Other goods receipts: All other goods receipts are recorded in the ERP system. When the document is saved, the system creates an inbound delivery and sends it to the WM system using a BAPI. The inbound delivery is then processed in the WM system as described above. When the verification for the inbound delivery is sent to the ERP system, the goods receipt posting is automatically initiated in inventory management. Stock transfers: A stock transfer usually involves two storage locations (plants): the issuing storage location for picking and the receiving storage location for putaway. If the stock transfer is recorded in the ERP system as a two-step procedure and if one of the storage locations involved is a WMS-relevant storage location, the system creates a delivery for this posting and sends it to the WMS. Both storage locations involved are copied into the delivery to allow the actual posting to be executed after the verification is received from the WMS. One-step stock transfers using a WMS-relevant storage location are only possible if a storage location that is not WM-relevant is involved in the posting change. Process for stock transfers: Entering the goods movement in the system Automatically creating the delivery Distributing the delivery from the ERP system to the WM system using BAPI method "InboundDelivery.SaveReplica" (this process is automatically executed in the background) Physically receiving the goods into the warehouse or removing the goods from the warehouse (WMS). Creating the transfer order Putting away or picking the goods Confirming the transfer order Posting goods receipt for the inbound delivery (as a result, a completion verification is sent to the ERP system using BAPI method "InboundDelivery.ConfirmDecentral") or posting goods issue for the outbound delivery (as a result, a completion verification is sent to the ERP system using BAPI method "OutboundDelivery.ConfirmDecentral"). Goods receipt for the inbound delivery or goods issue for the outbound delivery is automatically posted in the ERP system (in inventory management) when the verification is recorded. When the goods receipt or goods issue is posted in the ERP system, the stock transfer is simultaneously posted in inventory management. Goods issues based on sales orders: The system uses sales orders to generate deliveries in the ERP system. The deliveries are then sent to the WMS. You use the WMS to create the transfer order, pick the goods and confirm the transfer order. When goods issue is posted, the picking quantities are passed on to the delivery of the ERP system. Process for goods issues based on deliveries: Creating the sales order Creating the outbound delivery Distributing the delivery to the WMS Creating the transfer order for outbound delivery Physically picking the goods in the warehouse Confirming the transfer order Printing the shipping documents, if appropriate Posting goods issue for the outbound delivery (as a result, a completion verification is sent to the ERP system using BAPI method "OutboundDelivery.ConfirmDecentral") Goods issue for the outbound delivery is automatically posted in the ERP system (in inventory management) when the completion confirmation is recorded. Posting changes You can also initiate transfer postings in the central system, in which case the stock change will be compared with the stock in the decentralized system and adjusted, if necessary. If you use inventory management to make posting changes in the central system, the system first generates a delivery. This delivery is technically a request for the decentralized system to make a transfer posting for the stock involved. The central system does not create material documents or make any changes in stock at this point. The delivery is transmitted to the decentralized system and, as of this point, can only be changed there. You can make settings in the decentralized system so that the system automatically creates a transfer order that corresponds to this delivery that does not require confirmation. You can also set the system to make the appropriate transfer posting in the WM stock automatically at the end of the process. The transfer posting in the decentralized system simultaneously verifies the appropriate quantities to the central system. When the central system receives this verification, it automatically makes the stock change and creates a material document. You can display the material document in the delivery’s document flow. Production supply If the decentralized warehouse is also responsible for production supply, the following two methods of material staging are available in the system: Production staging by switching storage locations Production stock is managed in a storage location that is located somewhere other than in the decentralized warehouse. In this case, the production storage location is not managed in the decentralized warehouse. If you switch the storage location in the central system, the system generates a delivery, for which you can then pick and post goods issue in the decentralized system. At this point, the stock that has been staged using this method can be used in a manufacturing order in the central system. Goods issue posting for a manufacturing order In this scenario, the raw materials are taken directly from the decentralized warehouse’s storage location and used in the manufacturing order. If goods issue is posted for the manufacturing order in the central system, the system creates a delivery that is sent to the decentralized system. The rest of the process is the same as regular goods issue processing. Note the following distinctions with regard to reservations: Delivery does not trigger request generation If the goods issue posting that generates the delivery refers to a reservation, the reservation number is copied into the delivery. In this case, the delivery does not check for availability and no requirements are generated, since that was already done in the manufacturing order. The reservation is canceled when the actual goods issue posting is made. Changes disappear after the delivery is distributed Keep in mind that if the reservation is changed in the meantime (if the production quantity has changed, for example), this change will not affect the delivery. Similarly, a change in the delivery will not result in a change in the reservation. The WM/PP interface, which you can use for production supply in an integrated system, is not supported for decentralized warehouse processing. This function is not available decentrally because the WM/PP interface is based on the assumption that WM and PP are running in the same system, which is not the case in a decentralized system. Goods receipt for a manufacturing order You can process goods receipts from manufacturing orders in the decentralized WM system. For goods receipt postings, the central system first creates an inbound delivery for the manufacturing order and distributes it to the decentralized system. In the decentralized system, the inbound delivery serves as a basis for putaway in WM. You can correct quantity differences here. Once you have confirmed the putaway transfer orders, goods receipt is posted in the decentralized system. The decentralized system then reports the quantity that was posted back to the central system. This verification automatically makes the actual goods receipt posting for the manufacturing order, along with the material document, in the central system.
2) Config we will get from Google also we will get standard idocs for ib and out bound.
Regards,
Mahesh

Warehouse management business process

Hello Sap Consultants,
I have configured the Warehouse management into our system. I have created a purchase order for a material for which the WM is activated in material master. Please tell me the process to carried out with respect to warehouse management while goods receipt, goods issue, transfer posting, Physical inventory, stock transfer etc.
Thanks & Regards,
Aaditya.

Hi,
Please see the very first thread of this Forum for more Inputs.
and Check the book MMWM.pdf from http://www.easymarketplace.de/online-pdfs.php, as well you can see the http://www.sap-img.com/sap-wm.htm.
As well you can see
http://wiki.sdn.sap.com/wiki/display/ERPLO/ERP+WM
It worked for lots of consultant's
Regards,
Ninad Kshirsagar

Inserting Totals on the Stock in Warehouse report

Hi all
I want to knwo what code or formula must I use to total the stock in warehouse report .
This report must print each warehouse report on separate papers.
Thanks

Hi All
Managed to sort out the totaling had to insert formula ColSUm

Steps to Add stock in Warehouse bins

Gurus,
Please give me the transaction and steps to add Stock in Warehouse Bins without reference to Inventory management......
We dont user Inventory management. We only use Warehouse Management in our company. So How do I update the initial stock entry in the respective bins...Please provide me the steps....
Thanks in Advance

still not totally clear if you have a stand alone WM or only a decentralized WM,
If you have decentralized Warehouse Management, all your business transactions, including inventory management of quantities, are executed in the ERP system, while all the processes required for the physical and logical goods movements run in the decentralized WMS.
The leading ERP system communicates planned goods movements to the decentralized Warehouse Management system (WMS) through deliveries (BAPI method)
for details look here:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/57/803c35975f0054e10000009b38f839/frameset.htm
dont miss the the menu on the left to navigate to stock transfer ,goods receipt etc.

Oracle Warehouse Management System system implementaion concepts.

Hello, we are using an old version of Oracle Warehouse Management System(back in Retek time). Anyways I think the concepts remaon the same. Can someone please point me to some implementation details document please. Hoping for docs that explain, for example how the concentric putaway logic is implemented in the system. That is, the inner workings of the system. I had an issue report for a bug(4896266) that explains the old logic Oracle used and the new logic they are pursuing for concentric putaway. It was clearly explained. I am unable to attach the doc, but hoping for that kind of docs or a place where to find them.

Hi,
Ah I see. I'm afraid it's highly unlikely that sort of documentation is available; I've certainly never found anything that useful. I've often had to resort to going through the PL/SQL of various packages to gain an understanding of what the system is doing. Obviously that's a terrible substitute to proper documentation.
I suppose if you were desperate you could take a look at the operations guide for a more recent version and use this as a starting point for further investigation?...
I've just had a quick search of the v13 RDM docs and it has the following to say:
Directed Movement
When merchandise is putaway, RWMS uses the product location attributes and configurable putaway plan to suggest the location that best conserves space in the reserve locations, or it inquires opportunities such as zone, location type, and status (for example, Different SKU, Same SKU, Empty Loc). The number of storage preferences associated with a particular plan is virtually unlimited, providing significant control over the storage strategy for the overall facility. Inventory Control uses three putaway methods: cube, capacity, and unit.
Cube – Dimension derived from the length, width, and height
Capacity – Capacity measured in units
Unit – Capacity in number of units
All merchandise in the DC is system-directed whether it is for putaway, processing, or picking goods.
Concentric Putaway allows for putaway plan creation that suggests reserve storage locations closest to an item picking location. This is done using XYZ coordinates to measure the distance of storage locations from the pick face. This functionality is controlled for each item within a putaway plan.
Thanks,
Dave

Movement type to scrap the Restricted stock from warehouse

Hi,
Kindly advise the movement type to scrap the Restricted stock from warehouse.
Thank you.

hi
what do u mean by restricted stock
i thnk it is BLOCKED stock
please clerify that
u cant see any restricted stock in MMBe
it is GR blocked stock and blocked stock or reserved stock
hope it clears
regards
kunal

Movement types--warehouse management

WM movement type 561 not allowed for warehouse number ......this is the error i am getting while trying to create material stock.....what is the solution for this error plsss assist
thanking you
Maddy

Hi Maddy,
When you are using a Ware house management then all the movement types to be used has to be configure.
Please configure the Movement type 561 for your warehouse in spro > logistics execution > warehouse management > activities > define movement types.
I hope this will resolve your issue.
Reward points if this information is useful
Regards
Sanjay

Lean warehouse Management

Hi!
I want to use lean warehouse management for creating TO. kinldly help me out to know the settings of lean warehouse management with fixed storage bin and also for
2. Wave pick settings
With Regards
Bhikshapathi

dear vonnala
Lean Warehouse Management: Configuration Guide
Purpose
The purpose of this document is to describe the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation.
The Configuration Guide describes how to set up the configuration of a Building Block manually, without the support of automated configuration tools.
Preparation
1.1 Prerequisites
The following building blocks form the basis for all my SAP All-in-One Automotive, High Tech and Industrial Machinery and Components solutions. You only have to install these building blocks once.
Building Blocks Comment
Baseline Building Blocks (Layer 0)
J00 - Essential Information
J02 - Organizational Structure
J03 - Financial Accounting
J08 - Controlling
J05 - Materials Management
J04 - Sales and Distribution
Baseline Building Blocks (Layer 1)
J06 - Production Planning and Controlling
J07 Quality Management
J18 - Product Cost Controlling
J19 Batch Management
J20 - Cost Object Controlling Make-to-Order
J21 - Cost Object Controlling Make-to-Stock
J17 - Profitability Analysis
J14 - Human Capital Management
J09 - Travel Management
Industry generic Building Blocks
E04 - Supplement Settings
E05 - Master Data HT / IM&C
Configuration
1.2 Lean WM Basic Settings
1.2.1 Defining Defining ControlControl Parameters and Number Ranges for the Warehouse Number Parameters for the Warehouse Number
Use
A warehouse number is an organizational unit in Logistics, which organizes the company from the perspective of Warehouse Management.
In the Warehouse Management System, you can define a variety of control parameters at warehouse number level.
Procedure
1. Access the activity using one of the following navigation options:
 Picking  Shipping  Logistic Execution IMG Menu IMG   Define control parameters and number ranges for the warehouse numberLean WM Define control parameters and number ranges for warehouse no.(double click)
Transaction Code SM30
2. Find the Field Name and input the relative value into the field.
Table V_T3002
Field name Value R/O/C Description
Whse number L01 R
Warehouse no. description Lean WM BP01 R
Weight unit KG R
Volume unit
Default UoM K R
Time unit/performance data
Lean WM active X R
Link to subsystem active
Performance data
Transfer order 01 R
Group number 01 R
1.2.2 Defining Storage Type
Use
A warehouse number is subdivided into a variety of storage types. A storage type is defined by its physical or organizational features (for example, high rack storage area, bulk storage, and goods receipt areas).
A storage type has a short description rather than an address.
Before you can implement Lean WM, you must configure the following settings:
1. Assign a (newly defined) storage location to a warehouse number.(This step is defined by step 3.12 Control Plant / Storage Location / Warehouse Number Assignment
2. You should set up at least three storage types:
a storage type (that will be used as a source storage type) with one or several fixed storage bins
a goods issue area (as destination storage type) for deliveries
an interim storage area for differences
Procedure
1. Access the activity using one of the following navigation options:
IMG Define Storage Lean WM  Picking  Shipping  Logistic Execution Menu IMG type
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T3012
Data record 1:
Field name Value Sub-screen
Whse number L01
Warehouse no. description Lean WM BP01
Storage type 001
Storage type name Fixed bin storage
Stock plcmt requires confirmation for putaway control
Unit of measure type srch
Stock rmvl requires confirmation for picking control
Unit of measure type srch
Data record 2:
Field name Value Sub-screen
Whse number L01
Warehouse no. description Lean WM BP01
Storage type 916
Storage type name Shipping area deliveries
Stock plcmt requires confirmation for putaway control
Unit of measure type srch
Stock rmvl requires confirmation for picking control
Unit of measure type srch
Data record 3:
Field name Value Sub-screen
Whse number L01
Warehouse no. description Lean WM BP01
Storage type 999
Storage type name Differences
Stock plcmt requires confirmation for putaway control
Unit of measure type srch
Stock rmvl requires confirmation for picking control
Unit of measure type srch
Data record 4:
Field name Value Sub-screen
Whse number L01
Warehouse no. description Lean WM BP01
Storage type 902
Storage type name IN-ZONE
Stock plcmt requires confirmation for putaway control
Unit of measure type srch
Stock rmvl requires confirmation for picking control
Unit of measure type srch
1.2.3 Defining Doors
Use
In a WM-managed warehouse, you can define dock doors (also known as doors or gates). A door is a location where the goods either arrive in the warehouse or leave it.
You can assign different functions to a dock door, for example:
Goods receipt
Goods issue
Other transactions such as cross-docking and flow-through
Procedure
1. Access the activity using one of the following navigation options:
 Picking  Shipping  Logistic Execution IMG Menu IMG Define DoorsLean WM
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T30B
Field name Value R/O/C Description
Whse no. L01 R Warehouse number
Door A01 R Door for warehouse number
Text for door Door A01 R Text for door
Staging area
Matl stag. area txt
GI indic. X R Goods issue indicator
GR ind X R Goods receipt indicator
CD ind Cross-docking indicator
FT ind Flow-through indicator
1.2.4 Defining Material Staging Areas
Use
A staging area is an interim storage area for goods that have been received from goods receipt and afterwards need to be transferred into the warehouse.
It is also an interim storage area for goods that were picked in a warehouse and are to be loaded for goods issue through loading ramps or doors.
You can assign different functions to a staging area:
Goods issue
Goods receipt
Procedure
1. Access the activity using one of the following navigation options:
 Lean WM  Picking  Shipping  Logistic Execution IMG Menu IMG Define Material Staging Area
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T30C
Field name Value R/O/C Description
Whse no. L01 R
Staging area A01-01 R
Matl stag. area txt Zone 1 R
Door A01 R Door for warehouse number
Text for door Door A01 R
GI ind X R Goods issue indicator
GR ind X R Goods receipt indicator
CD ind Cross-docking indicator
FT ind Flow-through indicator
HU ind Handling unit indicator
1.2.5 Defining Picking Area
Use
A picking area is an object within a storage type that groups together storage bins for purposes of stock removal.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG Define Picking Lean WM  Picking  Shipping Logistic Execution Area
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T30A2
Data record 1:
Field name Value R/O/C Description
WhN L01 R Warehouse number
STy (storage type) 001 R
PAr (Picking area) 001 R
Picking area name Picking area 1 R
Data record 2:
Field name Value R/O/C Description
WhN L01 R Warehouse number
STy (storage type) 001 R
PAr (Picking area) 002 R
Picking area name Picking area 2 R
1.2.6 Defining Transfer Type
Use
In Lean WM, the transfer type "A" (stock removal) is required for movement type control.
Procedure
1. Access the activity using one of the following navigation options:
 Picking  Shipping  Logistic Execution IMG Menu IMG   Define Transfer TypeLean WM
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T333A2
Field name Value R/O/C Description
WhN L01 R Warehouse number
Transfer type A R
Text f. shipment type Pick R
1.2.7 Defining Movement Types
Use
The SAP R/3 System uses movement type to process movements in Inventory Management (for example, goods receipt for a purchase order or goods issue to a cost center). When the system recognizes a movement as being relevant for Warehouse Management, it assigns this movement to a WM movement type by means of a table.
The movement type for the Warehouse Management System provides the information required for stock removals or picking:
Interim storage bin
Fixed bin coordinate
Control indicator for processing, confirming, and printing transfer orders
Confirmation info
Procedure
1. Access the activity using one of the following navigation options:
 Lean WM  Picking  Shipping  Logistic Execution IMG Menu IMG Define Movement Type
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T3332
Data record 1:
Field name Value R/O/C Description
Warehouse number L01 R
Warehouse no. description Lean WM R
Movement type 255 R
Movement type description Goods Issue general R
Src 001 R
Src Stor. Bin
Dest 916 R
Dest Stor. Bin
Transfer type A R
Text for transfer type TRATX Pick R
TO creation screen 2 R
Scr. TO confirmation 2 R
Manual TO creation not allowed
Transfer priority
Print code
TO item can be confirmed immed.
Propose confirmation
Data record 2:
Field name Value R/O/C Description
Warehouse number L01 R
Warehouse no. description Lean WM R
Movement type 601 R
Movement type description Picking by delivery note R
Src 001 R
Src Stor. bin
Dest 916 R
Dest Stor. bin
Transfer type A R
Text for transfer type TRATX Pick R
TO creation screen 2 R
Scr. TO confirmation 2 R
Manual TO creation not allowed X R
Transfer priority
Print code 02 R
TO item can be confirmed immed. X R
Propose confirmation
1.2.8 Defining Difference Indicator
Use
Using the difference indicator, you can classify your differences. This indicator is used in Lean WM for evaluation purposes only.
Procedure
1. Access the activity using one of the following navigation options:
LogisticIMG Menu IMG   Define Difference Lean WM  Picking  Shipping Execution Indicator
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T3362
Field name Value R/O/C Description
WhN L01 R Warehouse number
DiffInd (difference indicator) X R
Description of difference indicator Stock difference R
Stor.ty.differences 999 R
Diff.bin
TO X R
Source bin
1.2.9 Control Plant / Storage Location / Warehouse Number Assignment
1.2.9.1 Assigning Warehouse No. to Plant-Storage Locations
Use
By doing so, system can recognize which storage locations in Materials Management are controlled by the Warehouse Management system (LE-WM); you must assign the plants and the storage location to the warehouse number.
Procedure
1. Access the activity using one of the following navigation options:
Assignment Enterprise Structure IMG Menu IMG Assign warehouse No. To plant/storageLogistic Execution Location
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T320
Field name Value R/O/C Description
Plant BP01 R
SLoc 0005 R
WhN L01 R
1.2.9.2 Control Plant / Storage Location / Warehouse Number Assignment
Use
You can control for each combination of plant, storage location, and warehouse number whether Lean WM or standard management of bin inventory is to be selected.
If you are using Lean WM, you can also specify a picking storage type that is used for creating transfer orders.
Procedure
1. Access the activity using one of the following navigation options:
 Logistic Execution IMG Menu IMG   Control Plant / Storage Location / Warehouse Lean WM  Picking Shipping Number Assignment
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_T3202
Field name Value R/O/C Description
Plnt BP01 R
Stor. loc. 0005 R
WhNo (Whse number) L01 R
Degree of activation Warehouse Mgmt 1 R
Stor.type for picking in Lean WM 001 R
1.2.10
1.2.11 Assigning Picking Location
Use
Assign the picking locations to the combinations of shipping point and storage condition for every plant.
Procedure
1. Access the activity using one of the following navigation options:
 Shipping  Logistic Execution IMG Menu IMG   Assign Picking Location Determine Picking Location Picking
Transaction Code SM30
2. Find the Field Name and input the relative value into the field
Table V_TVKOL
Field name Value Description
ShPt BP01 Plant
Plnt BP01 Shipping point/receiving pt
SC K1 Storage conditions
SLoc 0005 Storage location
1.3 Print Control for Warehouse
Use
Print control defines the following:
Which slips are to be printed for the movements (that is, for the transfer orders) within the Warehouse Management System
How these slips are to be printed (that is, which forms are to be used, how many copies are to be printed)
On which printer a slip is to be printed automatically
And print control manages the print operations of the warehouse. This flexibility involves a certain degree of complexity with regard to the parameterization.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG   Define Print Lean WM  Picking  Shipping Logistic Execution control
Transaction Code OMLV
2. Choose the following button and check the contents
(Here only the contents of the warehouse no. L01 are listed):
2.1 Spool code
Data Record 1
Field name Value R/O/C Description
WhN L01 R Warehouse number
Spool 01 R Spool request name
Copies 1 R Number of copies
Title LVS1 R Spool control data
Print_immed. X R Print immediately
Delete_after_print X R Release after output
NewSplReq__ New spool request
Data Record 2
Field name Value R/O/C Description
WhN L01 R Warehouse number
Spool 02 R Spool request name
Copies 1 R Number of copies
Title LVS2 R Spool control data
Print_immed. Print immediately
Delete_after_print X R Release after output
NewSplReq__ New spool request
2.2 sort profile/collective process
Field name Rec1 Rec2 Rec3 Rec4 Rec5 Rec6 Rec7 Rec8 Rec9
WhNo_(Whse_number) L01 L01 L01 L01 L01 L01 L01 L01 L01
Sort_profile 1 2 3 4 5 6 7 8 9
1st_sort_criterion SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI SPOOI
Sort_descending_order (1st_sort_criter.)
Control_break_1st_sort_criterion
2nd_sort_criterion LDESI LDESI LDESI LDESI LDESI LDESI LDESI LDESI LDESI
Sortdescending_order (2nd_sort_crit.)
Control_break_2nd_sort_criterion X
3rd_sort_criterion REFNR REFNR REFNR REFNR FORMI FORMI FORMI FORMI REFNR
Sortdescending_order (3rd_sort_crit.)
Control_break_3rd_sort_criterion X X X X
4th_sort_criterion FORMI FORMI FORMI FORMI LGNUM LGNUM LGNUM LGNUM FORMI
Sortdescending_order (4th_sort_crit.)
Control_break_4th_sort_criterion X X X X
5th_sort_criterion LGNUM LGNUM LGNUM LGNUM VLTYP VLTYP VLTYP VLTYP LGNUM
Sortdescending_order (5th_sort_crit.)
Control_break_5th_sort_criterion
6th_sort_criterion VLTYP NLTYP VLTYP TANUM VLPLA NLPLA WERKS TAPOS NLTYP
Sortdescending_order (6th_sort_crit.)
Control_break_6th_sort_criterion X X X X
7th_sort_criterion VLPLA NLPLA WERKS TAPOS
TANUM TANUM LGORT KOBER
Sortdescending_order_ (7th_sort_crit.)
Control_break_7th_sort_criterion X
8th_sort_criterion TANUM TANUM LGORT TAPOS TAPOS MATNR VLPLA
Sortdescending_order (8th_sort_crit.)
Control_break_8th_sort_criterion
9th_sort_criterion TAPOS TAPOS MATNR CHARG TANUM
Sortdescending_order (9th_sort_crit.)
Control_break_9th_sort_criterion
10th_sort_criterion CHARG BESTQ
TAPOS
Sortdescending_order_ (10th_sort_crit.)
Control_break_10th_sort_criterion
11th_sort_criterion BESTQ SOBKZ
Sortdescending_order_ (11th_sort_crit.)
Control_break_11th_sort_criterion
12th_sort_criterion SOBKZ LSONR
Sortdescending_order_ (12th_sort_crit.)
Control_break_12th_sort_criterion
13th_sort_criterion LSONR VLTYP
Sortdescending_order_ (13th_sort_crit.)
Control_break_13th_sort_criterion
14th_sort_criterion VLTYP
Sortdescending_order_ (14th_sort_crit.)
Control_break_14th_sort_criterion
15th_sort_criterion
Sortdescending_order_ (15th_sort_crit.)
Control_break_15th_sort_criterion
2.3 print code
Field name Rec1 Rec2 Rec3 Rec4 Rec5 Rec6 Rec7
WNo___(Warehouse_number) L01 L01 L01 L01 L01 L01 L01
PrCd__(Print_code) 01 02 03 11 12 21 22
Print_code_description
Find_shipping_data____
Determine_production_data_
Form_ LVSTAEINZEL LVSTALISTE LVSTOSOLO LVSTAEINZEL LVSTALISTE LVSKOMMIL1
LVSKOMMIL2
PTm_(Time_of_printing)________
Sort_profile 1 1 1 4 1 1
Combined_print x x x x
Spool_data 02 02 01 02 02 02 02
Label_form LVSLABELS
Label_spool_code 01
Quantity_of_labels_(Indicator) 2
2.4 assign printer to storage type (LP01 to 001 only)
Field name Rec1 Rec2 Rec3
WhNo_(Whse_number) L01 L01 L01
STy__(storage_type) 001 916 999
Storage_type_description Fixed bin storage Shipping area deliveries Differences
Printer
2.5 assign print code to movement type
Field name Rec1 Rec2 Rec3
WhNo_(Whse_number) L01 L01 L01
MvT__(WM_movement_type) 101 255 601
Movement_type_description Goods receipt for pur.or.
Picking by delivery note
PrCd__(Print_code) 01 02
2.6 assign print report to warehouse No.
Field name Rec1
WhNo_(Whse_number) L01
Warehouse_number_descrip. Lean WM Plant BP01
Print_report RLVSDR40
2.7 print control multi-processing
Field name Rec1
WhN L01
Ref.ty. L
Status 2
Print_prog. RLKOMM40
PrCd 21
Printer LP01
1.4 Manual Activity
1.4.1 Maintaining Number Range Intervals for Transfer Order
Use
Maintain number range intervals for transfer order
Procedure
In this step, you define that, the Number range for Transfer order as 01 and Group number as 01, now you should tell the system how the number range would like for 01 as transfer order and 01 for the group number, for both number range, you may define you own number range, the following information just for reference:
Access the activity using one of the following navigation options:
 Logistic Execution IMG Menu IMG   Define control parameters and number ranges for Lean WM  Picking Shipping   Maintain number range intervals for transfer ordersthe warehouse number (double click)
Transaction Code LN02
Check if the internal number range 01 (0000000001-1000000000) has been defined
Once you have defined your number ranges, it is extremely difficult to change them afterwards when the objects concerned are filled with data.
Bear in mind that you will be entering data on a long-term basis. Create your number range intervals accordingly.
1.4.2 Maintaining Number Range Intervals for Reference Numbers
Use
Reference number range has the following meanings:
This number identifies a number range to be used for the assignment of sequential numbers for WM reference numbers. Reference numbers are used to create or print a group of transfer orders at one time.
A sequential number generated by the system for the purpose of multiple processing of transfer requirements and delivery notes.
The reference number can also be used to print the resulting transfer orders at a later time.
Procedure
In this step, you define that, the Number range for Transfer order as 01 and Group number as 01, now you should tell the system how the number range would like for 01 as transfer order and 01 for the group number, for both number range, you may define you own number range, the following information just for reference:
Access the activity using one of the following navigation options:
IMG Menu IMG Define control parameters Lean WM  Picking  Shipping Logistic Execution   Maintain number range intervals forand number ranges for the warehouse number Reference Numbers( double click)
Transaction Code LN06
Check if the internal number range 01 (5000000000 - 5999999999) has been defined
Once you have defined your number ranges, it is extremely difficult to change them afterwards when the objects concerned are filled with data.
Bear in mind that you will be entering data on a long-term basis. Create your number range intervals accordingly.
rewards if it helps
siva

Configuration of warehouse management

Dear All,
     Can anybody tell me step by step detail configurations of Warehouse management in SAP R/3 system ??
                                                                                with regards,
                                                                                RANA

Hi,
It's very tough to explain you step to step config process of WM. Following are the main configuration steps that are required for any new ware house implementation.
Please explore all the following steps, that will help you in configuring the ware house.
     Configuration
1     Define, copy, delete, check warehouse number (SPRO)
2     Assign warehouse number to plant/storage location (SPRO)
3     Define Control Parameters for Warehouse Number (SPRO)
4     Define Number Ranges (OMLW)
5     Define Storage Type (Trans : SPRO)
6     Define Storage Sections (SPRO)
7     Define Storage Bin Types (SPRO)
8     Define Blocking Reasons (SPRO)
9     Define Storage Bin Structure (LS10)
10     Define Storage Type Indicators (SPRO)
11     Define Storage Unit Types (SPRO)
12     Define Storage Section Indicators:
13     Activate Storage Type Search (OMLY)
14     Activate Storage Section Search (OMLZ)
15     Activate Storage Bin Type Search (OMM1)
16     Define Sort Sequence for Putaways (Cross-line Stock Putaway) (OMLM)
17     Define Sort Sequence for Stock Removal (Picking) (SPRO)     27
18     Define Requirement Types (OMNF)
19     Define Shipment Types (SPRO)
20     Define Movement Types (SPRO)
21     Confirmation (OMLX)     34
22     Define Print Control (OMLV)
23     Define Default Values (SPRO)
24     Define Types per Storage Type (OMNK)
25     Define Differences and Document Limits (SPRO)
26     Clear Differences (Interface to Inventory Management) (SPRO)
27     Maintain Number Ranges   (OMMB)
28     Activate Storage Unit Management per Warehouse Number (SPRO)
29     Activate Warehouse Activity Monitor Objects (SPRO)
30     Define Critical Parameters (SPRO)
31     Define Variant for "Object Overview" Program (OML1)
32     Define Variants for Selection Programs (OML2 & OML7)
33     Define Movement Types (Interfaces) (OMLR)
34     <SAP OSS Notes and User Exits>
Thanks & Regards,
Krish

Logical Warehouse Management System

Dear All,
I want to know the concept of <b>'Logical Warehouse System'</b> in SAP.
Are all steps of Warehouse Management Syst Implementation to be followed?
Can the stock in Warehouse be considered in MRP?
Where in SPRO can I get exact steps for LOGICAL warehouse Management Syst Implementation.
Regards,
Sudhanshu

Hi
Please see the attached
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LEWM/MMWM.pdf

Warehouse Management for Third Party Logistic Company

Dear All,
I need your input for the following scenarios:
Company having 5 legal entities
One Legal entity ( X) is Mnaufacturing Cosmetics
Legal entities ( A, B & C ) are the Distribution Companies
5th legal entity ( Y ) is 3PL for the 3 Distribution Companies, A, B & C. Y has a warehouse which stocks the goods of the 3 distribution companies A, B and C. Inventory and goods still belongs to A, B & C
We need to implement warehouse management for Y ( 3 PL) company
Our proposition is to create warehouse structure which will address all the 3 legal entities ( A, B & C). So essentially the assumption is that warehouse is above the company code
We wanted to know the folloiwing:
1)If Y has to service all A, B and C at the same time and it needs to plan the routes for the deliveries created across the legal entities, how is this possible?
2) How will this impact the shipment planning, pick pack and the shipment cost?
Thanks in advance.

I would assume you have separate sales orgs and distribution channels for A, B and C.
But you would have to tie them together at a higher level may be at the comp code level and plan the supply chain from a higher level.
A good forecasting tool will help in distributing and managing inventory across the 3 different distribution companies.
There has to be some type of segregation of distribution between the 3 companies either at geographic level or by volume or something else. Otherwise it will be a real complex business planning and forecasting process if the 3 companies overlap in all aspects.
Hope this helps.
Good Luck.
M.

Re : Reservation stock in warehouse management

Similar Messages

Maybe you are looking for