Warehouse Management - XML standards

Hello Everyone,
For an upcoming project, we are at present evaluating the various XML based open standards. All our interfaces would be Warehouse Management (e.g. Stoks, Inventory, Orders, Invoices etc.) related. Please suggest some widely accepted XML based standard which could be used for such integration scenario. This would mean that we would get some standard schema to be used for various typed of communication. We have opted out EDI as it is not really XML based.
I have posted this on Standards forum (in a different way)
Business Specific Schema Standards
Best regards,
Prateek

Hi Prateek,
For Rosettanet
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0222aba-0516-2c10-67a9-d8d37af83861
Rosettanet PIP codes
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/rosettanetPIPCodesinOrder+Management
Regards
Ramesh

Similar Messages

What are all the Standard Data targets&Data source for Warehouse management

Hi,
What are all the Standard Data targets & Data source for Warehouse management.
Thanks,
Ahmed.

HI,
the master data
1.equipment data --IE01
2.All functional locatiions -IL01
3.Maintainnace work centers - IR01
4.Task list data - IA05
4.Schedule maintanence plan
6.Strategies
7.Measuring points
8.Characters for calibration
9.Equipemnt BOM
10.Material BOM
Regards,
Anddra

Report for List of Transfer orders in warehouse management

hi,
i want generate a report for list of transfer order orders in warehouse management
is there any report with you guys kindly help me,
or any standard report is there to display list of transfer orders in warehouse management
Thanks,
Rajesh
Edited by: rajesh kumar kandagatla on Feb 11, 2009 9:27 PM

Hi,
If it is one time requirement, you can run the report LT23 and download the data to excel sheet and donwload material details in another sheet and you can match the temperature column in excel file.
If it is permanent requirement, create a query and attach transaction code to that or write a seperate report for this requirement.
Please let me know.
Thanks
Nagarajan

Q&A db for warehouse management and inventory management

Hello Everybody,
i read on the help.sap website that standard as well as industry specific versions of Q&A db are available. but the website doesnt say where. i searched a lot but the links dont lead to the actual Q&A db.
i would like to request you to kindly share the Q&A db for inventory management and warehouse management with me as i need it for preparing the AS IS documentation.(preferably automotive industry but if not then even standard Q&A db is fine).
thanks a lot.
sapman.

Now QADB will not help to map the clinets requirement. Instead of QADB get AS IS information form Coreusers... thats best practice now....
Go through www.sap-img.com for further details...
Edited by: Ganti on Jul 26, 2008 7:26 AM

Service Manager data warehouse management server Installation fails

Hi there,
In Virtual Machine Windows Server 2012 R2 Standard with my user being a Local Admin and SQL Admin. I tried to do a Service Manager data warehouse management server
first installation I am facing the following image as error:
In the event viewer I get the following error:
"Microsoft System Center 2012 R2 Service Manager -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25211
The arguments are: -2147024809, The parameter is incorrect."
In the Setup log, some of the errors are:
WixRemoveFoldersEx: Entering WixRemoveFoldersEx in C:\Windows\Installer\MSI35E.tmp, version 3.7.1224.0
WixRemoveFoldersEx: Error 0x80070057: Missing folder property: PSCONFIGFOLDER.A591E3B4_D228_431D_BF89_99D52C8FFB76 for row: wrf4582BC4C5CC47B1D2380408CD7A752DC.A591E3B4_D228_431D_BF89_99D52C8FFB76
CustomAction WixRemoveFoldersEx.A591E3B4_D228_431D_BF89_99D52C8FFB76 returned actual error code 1603 but will be translated to success due to continue marking
CAStartServices: CAStartServices was passed . OMCFG
CAStartServices: Checking if service already started. OMCFG
CAStartServices: Attempting to start service. OMCFG
CAStartServices: StartService failed. Error Code: 0x8007042D.
ConfigureSDKConfigService: CAStartServices failed, trying again.... Error Code: 0x8007042D. OMCFG
Action start 17:47:05: _SetHealthServiceConfig.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.
GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMServer
MSI (s) (EC!4C) [17:47:05:483]: Note: 1: 2711 2: MOMGateway
SetHealthServiceConfig: Failed to get Feature State.. Error Code: 0x80070646. MOMServer
GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMGateway
I have checked the following post but it did not help me:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/c42bb04d-a51e-4037-a8a3-37d714d6faac/scsm-management-server-installation-fails?forum=systemcenterservicemanager
Could you please help me with this issue?
Thanks a lot,
M

Hi,
Sorry I cannot post the full log. I have found also these errors in the log:
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.RegisterSdkSCP
RegisterSdkSCP: There is no previous serviceConnectionPoint
RegisterSdkSCP: Creating New serviceConnectionPoint
RegisterSdkSCP: Adding ACL for current user: DOMAIN\InstallationAccount
RegisterSdkSCP: Adding ACL for SM Admini: DOMAIN\SCSMDWadmins
RegisterSdkSCP: Error: Access is denied.
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "D:\Program Files\Microsoft System Center 2012 R2\Service Manager\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallHSPerfCounters: Failed to install agent perf counters. Error Code: 0x80070057.
Thanks for your reply.

Warehouse management flow document needed

hi all
Can any one give the link which gives the bussiness flow of warehouse management. Please dont give Oracle standard document. I want the document that should be manually created. should be like this
http://erpschools.com/Apps/oracle-applications/Articles/General/Order-to-Cash-Cycle/index.aspx

Hi
Can any one give the link which gives the bussiness flow of warehouse management. Please dont give Oracle standard document. I want the document that should be manually created. should be like this
http://erpschools.com/Apps/oracle-applications/Articles/General/Order-to-Cash-Cycle/index.aspx
If you dont want formal oracle document than you have one chance, googling
Check below googling:
http://www.google.com.tr/#hl=tr&source=hp&biw=1276&bih=793&q=bussiness+flow%2Bwarehouse+management&aq=f&aqi=&aql=&oq=&fp=64d53dfd7a69225a
Regard
Helios

Serial Numbers in Inventory Management – Warehouse Managed storage location

Serial Numbers in Inventory Management u2013 Warehouse managed storage locations
We want to run inventory cycle at the warehouse for materials. These materials are u2018serial numberedu2019 in the material master. During the initial entry (say GR) of the materials, systems prompt for the serial numbers. At this point, system offers option of assignments of serial numbers automatically.
While running an inventory cycle for warehouse u2013 and posting difference at WM level (LI01), system is throwing error as u201Cmaintain serial number for totol quantityu201D. System does not promt me to enter the serial number for the materials (count) which are found excess/shortage duing the inventory cycle.
Is there any configuration where this scenario can be managed; system should prompt us to enter serial number while posting differenes at WM level (LI20).
The inventory cycle is -
1.     Create Physical Inventory Documents - LI01N
2.     Activate Physical Inventory Document -      LI02N
3.     Enter Count -     LI11N
4.     Post Differences at WM level -     LI20
5.     Post Differences at IM level(If Differences are posted at WM ) -     LI21

Curious to know: The WM Inventory transaction - LI11N - (where we enter physical count. )
1. Compared to MI04 - IM Inventory Transaction: where a pop-up window asks for serial number of the material.
2. We expect a similar pop-up at LI11N transaction- where the system should ask serial numbers.
Q.1 How can we achieve this?
Q.2 Will this be a standard SAP practice? (if we do customizing to get serial nos. pop-up window at LI11N)
thanks,

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

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

Experiences with ES Bundle "Integration of external Warehouse Management" ?

Hi PI Experts,
anybody who can share experiences with the ES Bundle Integration of [External Warehouse Management System |https://www.sdn.sap.com/irj/scn/wiki?path=/display/espackages/integrationofExternalWarehouseManagement+System] and the usage of its Enterprise Services "Confirm Goods Movement_V1" or "Confirm Goods Movement" ?
As far as I understood these ES can be used for goods movements out of the ERP System.
Is it really possible to use these ES while creating an goods movement with Transaction MIGO ??
As far as I know it is only possible to send Transport Orders with WMTORD IDOCS out of SAP to externa Systems (!!) without any custom coding (!!) . Using instead an WMBXY message type (IDOC WMBIDO02) is only for inbound IDOC processing. If using this Standard IDOC for outbound IDOC processing the only way is implementing the BADI called while perfoming the TA MIGO. Correct?
Any experiences either with the ES Bundle or the IDOC goods movement out of SAP ERP are welcome.
Kind regards,
Dries

you can use ES for creating goods movement in SAP ( see the esoa sample apps on sdn) or you can make your won service published using BAPI .
I am not catching you in the use of BADI , elaborate more about that.

Warehouse Management in BI

Hi experts,
I have a new requirement to design reports on Warehouse Management,
I am new to this extraction, could any one share their experience How to extract data from WM to BI, give steps if possible.
what are Standard Data Sources.
I could not find any Info Area for this WM, I found 2 Data sources under SRM, is WM has different server?
I need some brief on this.
Regards,
Vijay

Hi,
The SAP Warehouse Management system (WMS) provides flexible, automated support in processing all goods movements and in managing stocks in your warehouse complex. The system supports scheduled and efficient processing of all logistics processes within your warehouse.
Pls chk this: Datasource
[http://help.sap.com/saphelp_nw04/helpdata/en/a9/0a383fdb800804e10000000a114084/frameset.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/c1/376899449a11d188fe0000e8322f96/frameset.htm]
Just activate the Std Business Content from the above link, and do the data loading steps in BI as usal.
Regards,
Muralidhar

Implementing Decentralized Warehouse Management (LE-IDW)

My company recently acquired another business. The acquired company is on SAP. In order to integrate the business more quickly without having to do a complete SAP overhaul at this moment, we are planning to implement LE-IDW (Decentralized Warehouse Management).
Using this tool we plan to connect the other SAP system which handles the distribution, warehousing and manufacturing plant by using ALE.
Because both companies operate in different company codes, the idea is to leave ownership of the finished goods with the distribution company until the goods have been shipped to the customer and invoiced to the selling company.
This would require that we use some level of IM in the distribution company (i.e. the decentralized warehouse). The stock would be valuated in the distribution company not in the selling company.
Out of the box LE-IDW is only set up to handle WM functions even though it uses deliveries to correspond to the other system. We would use the deliveries also to update the IM side of the distributing company.
Does anyone have experience using LE-IDW this way? If so, I would be interested in your experiences.
Thank you.

Dear Sandar
Sorry .We used <b>MIGO BAPI </b> trigger the goods movement.
You will face some problem in cycle counting .
We used 4.6c.
We make GR /GI using MIGO .
Cycle count we use default one.
We used SAP standard message type.
but change in inbound and outbound you have to do more testing.
Check this link .This may be very useful for you.
help.sap.com/printdocu/core/Print46c/en/data/pdf/LEIDW/LEIDW.pdf - Similar pages
http://www.sap-img.com/lg001.htm

User Exit for warehouse management - transfer order sorting

Hi,
I want to sort transfer order of warehouse management by user exit, which user exit I can use?
Kindly please advise.
Regards

Hi,
I worked on the same object.
For sorting you have to place a button in the standard transaction,
I found some screen exits but they are not working.
Finally I developed the total customized transaction for that standard LM45.
If you have any doubts let me know.

Help..Problem GI for Warehouse Management

Dear Expert,
I have a problem for GI process in warehouse management. When there are stock transfer material sloc non WM to sloc WM , user have to create transfer order and confirm transfer order to place material in storage bin. Otherwise, if user didn't create transfer order, material will stay in Storage Type 998 (AUFNAHME).
If there are GI process after that, for example GI to cost center, user still can issue material from Sloc even material hasn't placed into storage bin. Then material issued will stay in Storage Type 911 (GI Area for Cost Center).
Question is...how can i clear Storage Type 911 (GI area for Cost Center) after GI process??Is there any way i can restrict GI process so that user can't issue material which hasn't placed into storage bin (still in AUFNAHME)???
Help me please...
Rgds,
Aleluya.

First of all:
It's strange that storage type 998 is used in your system for GR in transfer posting process - it is used for initial stock upload in standard system. Interim storage type 921 is used for SLoc-SLoc transfer posting.
Is there any way i can restrict GI process so that user can't issue material which hasn't placed into storage bin (still in AUFNAHME)???
In standard system not. Maybe through development you could do a check whether there're open TR for the material in connection with the interim storage type or you could check the quants for the interimn storage type...
But I think and strongly recommend you should not do this.
The process in SAP (process in ERP) and the physical process (moving the goods physically) should go paralelly. So, my opinion is that you should find out why the goods are not placed in storage bin in SAP whilst they are already in the bin physically. Maybe workers need training / workers have to keep to the rules / you have to revise the process/ use RF devices / etc.
Question is...how can i clear Storage Type 911 (GI area for Cost Center) after GI process
You can solve it (e.g.):
1. Manually, in the sort run: you move the suitable quant from the interim storage type used for SLoc-SLoc stock transfer (921) to interim storage type 911 by LT01 / LT10 (because you should have a +quant in 921 and a -quant in 911).
2. In the long run: e.g. you can set TR creation for your movement type and processing those TRs (from LB10) you will get the TO and realize the goods movement.
SPRO > LE > WM > Interfaces > IM > Define Movement Types > LE-WM Interface to Inventory Management
3. Immediate TO creation for these postings. Please sea OSS note 136796 if you are interested in this solution.
Regards,
Csaba
Edited by: Csaba Szommer on Jan 3, 2010 6:10 PM

Difference between inventory management and warehouse management

can any body tell me the difference between inventory management and warehouse management i need atleast five differences

hi
1.
Processes in the area of Inventory Management address the recording and tracking of materials on a quantity and value basis. This includes planning, entry, and documentation of stock movements such as goods receipts, goods issues, physical stock transfers, and transfer postings as well as the performance of physical inventory (stocktaking).
Warehouse Management Processes cover warehouse-internal movements and storage of materials.
2.
SAP Warehouse Management allows you to manage your material flow, using advanced putaway and picking strategies. In the standard system, these strategies for putaway include random putaway (next empty bin), bulk storage, fixed bin, or addition to stock. The picking strategies include standard strategies first-in first-out (FIFO), last-in first-out (LIFO), picking by shelf life expiration date (SLED), or partial quantities first. For customer-specific strategies, solutions can be self-defined in user exits.
3.
While Inventory Management manages the stocks by quantity and value, the Warehouse Management component reflects the special structure of a warehouse, and monitors the allocation of the storage bins and any transfer transactions in the warehouse.
Reward points if helpful

Warehouse Management - XML standards

Similar Messages

Maybe you are looking for