You are on page 1of 4

WM Roadmap-- prasanth.

naidu334
Satish334
1- WM Organization Structure
 Warehouse Number
 Storage Type
 Storage Section
 Picking Area
 Material Staging Area
 Door

2- Master Data
 Storage Bin(LS01 and LS01N)
 Material Master
 WM views in material master (MM01 /MM02 / MM17)
 Control cycles (LPK1 / LPK2)

3- Put away Strategy


 Fix Bin Strategy
 Next empty Bin Strategy
 Open Strategy
 Add to existing stock
 Pallet Strategy
 Bulk Strategy

4- Picking Strategy
 FIFO
 Strengthen FIFO
 LIFO
 Partial pallet
 Large Small Quantity
 Shelf life
 Fix bin from material master

5- Two step picking strategy


6- HU Management
 In Inbound delivery
 Outbound delivery
 Production planning
 Automatic planning
 Manual HU

7- SU Management
 Automatic SU
 Manual SU

8- WM integration with IM
9- WM integration with PP
10- WM integration with SD
WM Roadmap-- prasanth.naidu334
Satish334
11- WM integration with QM
12- Batch Management
13- Serial number profile
14- Shelf life
15- Special movement indicator
16- Cross docking
17- Crossline Put away
18- Mobile Data in WM
1. You can test the Idoc using idoc test tool. Just follow the steps above.
1. Go to transaction WE19.
2. Enter the idoc number you want to test.
3. Go to menu IDOC - WE05 /WE19Debugging an IDOC  WE02  BD88 Process outbound IDocsTo Display the
executed IDOC to check the status of idoc.  BD87 Process inbound IDocs 1. IDOC TestingT-Codes.WE19 Test tool
WE12 IDoc test: Inb. Proc of Outb. File WE16 IDoc test: Inbound File WE17 IDoc test: Inbound status report If you want
to reprocess IDOCS > test inbound idoc -> standard inbound
4. One popup screen comes get the "FUCTION NAME" to test the idoc.
5. Click on "INBOUND FUNCTION MODULE" button.
6. Enter function module name.
7. Click on CALL IN DEBUGGING MODE check box and choose foreground mode. And choose yes to run it.
2. 2. EDIT IDOC Go to transaction WE19. Enter the idoc number you want to test. Double click on each segments and u
can edit the values. Then click start inbound WE02, WE05 (DISPLAY IDOC FOR STATUS CHECK) Basically WE02 and
WE05 are same in terms of Functionality. Displays the IDocs. But there is one diff. One of these transactions is for
Administration purpose.
3. And WE07 is for Error statistics. It displays the IDocs which went into errors. It classifies the IDocs in there error
types.Use transaction WE05 or WE02 to add missing data for your inbound Idoc, If you use transaction WE19, system
will generate new IDoc. However, system will not generate new IDoc if you use WE05 or WE02.
1. Go to transaction WE05 or WE02.
2. Enter the corresponding inbound IDoc number and execute
3. Double click on the segment (page Icon) where you want to add missing data.4. In the screen "Display Data
Record for IDoc", go to menu "Data Record" and click on"Display - > You have an error idoc and if you want to
edit it and reprocess you can do it in BD87. Suppose there was RFC Issue, connection got failed then after
rectifying RFC Connection then you can reprocess same idoc number.  Use BD87 if you want to reprocess
same idoc number, here it will not generate new idoc number. Change". Then system will display a popup
information "Changes to the IDoc arewritten to the database", then press enter .In order to process the edited
inbound IDoc, please execute standard program RBDAGAIE byproviding the above IDoc number.BD87 (Status
Monitor for ALE Messages) To reprocess same idoc number
4. 3. Go to BD87 -EDIT IDOC IN BD87 Follow the steps. > Choose Data-Record- Double click on the paper-icon
(important!!! ), not on the segment name  Search your segments with errors.  Double click on the idoc with error until
you reach the Idoc-tree. enter error idoc number > Finally, you can choose to save the IDoc in a file. You can also
start the function module in debug mode and select the processing option for your posting module.  Alternatively, you
can pass the process to a function module directly, by clicking the Inbound Function Module button. In this case, the
system bypasses the checks for partner profile and hands the IDoc data to your inbound function module directly. This
approach is useful for testing an inbound process without having to maintain any inbound configuration.  You can call
the inbound process using the normal path by clicking the Standard Inbound button, in which case the process goes
through the checks as if it had been sent in by the subsystem.  Go back until you reach BD87 again. Reprocess the
Idoc.Difference between 3 options in WE19In WE19 your get 3 options Start Inbound, Start Inbound Function Module,
and Inbound file .  Change the values, Click Save, confirm the message, that the changes will be written to database
(creates an idoc with the original values and status 70). Display-change from the menu.
WM Roadmap-- prasanth.naidu334
Satish334
Please go thorugh the following steps for WM & QM interface.
1.Good receipt :MB01/MIGO :Post stock in IM
2.Good receipt will create TR for WM. TO is created from TR which will have destination storage type 917 & bin
as quant number. Here for storage type 917 you have to select putaway strategy as "Q" in config.
3.The transfer order created will post stock in quality area (917)for usage decision.
4.After that you can have three type of usage decision
*Full qty approval.
*Partial qty approval & rejection.
*Full rejection.
5.Whenever you will take usage decision through QA32 system post stock with movement type 321& create
posting change notice(PCN) in WM
6.You can see material document number & PCN posted after QD by displaying inspection lot.In inspection lot
through material document tab you can see material document number.If you double click second material
document number it will dispaly material document. On WM tab of material document you can see PCN .
7.This PCN can be seen in LU04 .You can convert PCN into TO manually as well as automatically through TO
background job.
8.Transfer order created will move material from 917 to 922 & from 922 to final destination storage type &
bin to complete final putaway in bin.
9.TO created after UD will put material finally in bin.
I am confident if you follow above process your scenario will complete.
Regards,
Prashant

Price without taking any possible discounts and surcharges into account.
Net price
Price taking any applicable discounts and surcharges into account.
Effective price
Net price after deduction of cash discount, with allowance for any miscellaneous provisions,
delivery costs, and non-deductible taxes.

Gross price:
It is the basic price of the material w/o discounts, surcharges and taxes
Gross price = Basic Price of the Material
o Net Price:
The Gross price after considering duties & taxes into account.
Net Price = Gross Price + Duties + Taxes
o Effective price:
? The net price after considering surcharge and discount
Effective price = Net price + surcharges + discounts

Third Party Sale through Subcontracting Vendors (SC Vendor Dispatch


Direct to Customer

Create third party sale order-Va01


2) Convert PR into PO-me53n
3) Issue components to subcontracting vendor- 541/mb1b
4) Post statistical GR with consumption of components
WM Roadmap-- prasanth.naidu334
Satish334
5) Verify Invoice from subcontractor
6) create billing and send it to the Customer
For technical configuration, please refer the following link:

You might also like