Important Sap Ewm Tables: Tkreddy 11 Comments
Important Sap Ewm Tables: Tkreddy 11 Comments
I am posting this blog after a long time, this time i would like to share some of the tables which
we should come across every day in SAP EWM system.These are very important tables that
every functional consultant should know and work mostly.The SAP EWM Tables list is as
follows:
Function Table
Description
Wave
/SCWM/WAVEHDR
/SCWM/WAVEITM
Wave Item
/SCDL/DB_PROCH_O
/SCDL/DB_PROCI_O
/SCDL/DB_DLVH_O
/SCDL/DB_DLVI_O
ODO
OD
ID
/SCDL/DB_PROCH_I
/SCDL/DB_PROCI_I
Referenc
/SCDL/DB_REFDOC
e
Status
HU
WT
WO
Reference
/SCDL/DB_REQH
/SCDL/DB_REQI
/SCDL/DB_STATUS
Status
/SCDL/V_STATUS
/SCWM/HUHDR
/SCWM/HUSSTAT
/SCWM/HUREF
/SCWM/HUSTOBJ
/SCWM/GMHUSTAT
TJ02T
Status table
/SCWM/ORDIM_O
/SCWM/ORDIM_C
/SCWM/WHO
Warehouse Order
Quantity /SCWM/AQUA
/SCWM/QUAN
Available Quantity
Quant Attributes
BINS
PI
/LIME/NQUAN
/SCWM/STOCK_IW01
/SCWM/LAGP
Storage Bins
/SCWM/LAGPS
/LIME/PI_DOC_IT
/LIME/PI_LOGHEAD
/
Log Table for Item Data of a Physical
LIME/PI_LOGITEM/LIME/PI_DO Inventory documentQuantities for Physical
C_TB
Inventory Document
TU
/SCWM/TU_DLV
/SCWM/TU_STATUS
/SCWM/TUNIT
TU &other GUIDs
Masterda
/SAPAPO/MATKEY
ta
BP
Product
/SAPAPO/MATMAP
/SAPAPO/MATLWH
/SAPAPO/MATEXEC
/SAPAPO/MATLWHST
/SAPAPO/MATTXT
Material Descriptions
ADRC
/SCDL/DB_BPLOC
Partner/Location
BUT000
BUT020
BP: Addresses
I have seen this issue being discussed in the past in the SCM community a couple of times, but I did not find a clear
answer. Most topics were about 2 years old, so maybe things have changed.
My question is: Is it possible to create a WareHouse Product automatically using the CIF interface from ECC?
Our situation is like this:
Materials are created in ECC they are being transferred to EWM using the CIF interface. The EWM products are
created fine, but we also need them to be created/extended as Warehouse products.
I have found a BAdi which is executed by the CIF Create-product-interface on EWM, where I actually can populate
and add the structures for MATLWH and MATLWHST, but then the Product Creation ends in error in SMQ2.
My second question is then:
What is the best way to create Warehouse Products from existing Products? In other words, is there a BAPI or other
FM which I can use in my own Report to create the entries in the /SAPAPO/MATLWH and ~/MATLWHST tables? I
think a recording BIM can do the job, but I would create a job for it.
I tried /SAPAPO/DM_PRODUCTS_MAINTAIN, but this is also not working, or I do not know how to use it...
In this BAdi I populated and added the structures ET_MATLWH(X) and ET_MATLWHST(X) (which correspond to the
warehouse product tables /sapapo/matlwh and /sapapo/matlwhst), and that's it.
I looped over the structure ET_MATLOC to get the actual Locations which is needed for the 2 structures to be
processed correctly. It took some trial and error for finding that out.
code used in BADI implementation to populate table /sapapo/matlwh?
o
ls_matlwhx-ext_entitled = ls_sc_unit-entitled.
* Data-velden / scherm-velden
ls_matlwhx-ptdetind = 'X'.
ls_matlwhx-put_stra = 'X'.
ls_matlwhx-ccind = 'X'.
APPEND ls_matlwhx TO lt_matlwhx.
ls_matlwhstx-method = ls_sc_unit-upd_code_matlwhst.
ls_matlwhstx-ext_matnr = lv_extmatnr.
ls_matlwhstx-ext_entity = ls_sc_unit-scguid_ext.
ls_matlwhstx-scutype = '1001'.
ls_matlwhstx-ext_entitled = ls_sc_unit-entitled.
* Data-velden / scherm-velden
ls_matlwhstx-lgtyp = 'X'.
APPEND ls_matlwhstx TO lt_matlwhstx.
ENDLOOP.
* Schrijf de gevulde structuren weg tbv. de verwerking
et_matlwh = lt_matlwh.
et_matlwhx = lt_matlwhx.
et_matlwhst = lt_matlwhst.
et_matlwhstx = lt_matlwhstx.
<<<<<<<<<<<<<<<<<<<
lt_sc_unit
lv_extmatnr
<<<<<<<<<<<<<<<<<<<<<
tables /SAPAPO/MATLWH and /SAPAPO/MATLWHST yourself.
Use Case 1
Two different location-related objects have the same number in the SAP ERP client
connected to EWM. For example, plant 0001 and shipping office 0001 or vendor 123456
and customer 123456. This use case is relevant for the standard warehouse with
preconfigured processes.
Use Case 2
Two different location-related objects of the same type have the same number in two ERP
clients connected to the same EWM client. For example, plant 0001 in ERP systems ABC
client 001 and XYZ client 001
Use Case 3
Combination of use case 1 and 2
Note
If you connect one EWM client to one ERP client, only use case 1 might occur.
To create two different location/SCU master records in EWM, you implement the BAdI
SMOD_APOCF001.
Caution
Activate the BAdI before you transfer the first location-related object to EWM using Core
Interface (CIF).
Procedure
Carry out the following steps in an EWM client allowing the creation of workbench requests. If
necessary, transport the workbench request to other EWM systems.
1. In Customizing for SCM Basis under Integration BAdIs for Specific Applications
Location and Business Partner BAdI: Inbound Processing for Location , select the
sample implementation relevant to your use case. For example, select
APOCF001_TYPEDIF if you connect one ERP client to one EWM client and choose
Display.
2. On the Interface tab, double-click the BAdI method.
3. Select the source code and copy it.
4. Go back to the Customizing and choose the same node as in step 1.
5. Choose Create.
6. In the Implementation Name field, enter a name for your implementation, for example,
Z_APOCF001_TYPEDIF.
7. Choose Continue.
8. In the Implementation Short Text field, enter a description for your implementation.
9. Save your implementation in a customer-own package or as a local object.
10. On the Interface tab, double-click the BAdI method.
11. Replace the existing coding with the coding you copied in step 3.
12. Save the coding and go back to the Business Add-In Builder screen.
13. In the menu, choose Implementation Activate .
Example
SAP provides a sample implementation for the BAdI in all three use cases. The sample
implementations handle the location/SCU number as follows:
Sample
Implementation
Relevant
For
APOCF001_TYPEDIF
APOCF001_SYSDIF
APOCF001_TYPESYSDIF
Use Case 3
Adds the location type as prefix and the ERP system and
client as suffix
Description
EWM Location/SCU
0001
Plant 0001
PL0001
0001
SP0001
The following table shows the prefixes used in use case 1 and 3 for the EWM-relevant objects:
Location Type
Name
Prefix Added
1001
Plant
PL
1003
Shipping Point
SP
1005
Transportation Zone
No prefix
Location Type
Name
Prefix Added
1010
Customer
CU
1011
Supplier
SU
1020
Carrier
CA
You can copy one of the sample implementations to your own implementation as described in the
procedure above.
Note
This procedure is not necessary if you connect one EWM client to one ERP client.
To create two different product master records in EWM, you implement the BAdI
SMOD_APOCF005.
Caution
Activate the BAdI before you transfer the first product to EWM using CIF.
Procedure
Carry out the following steps in an EWM client allowing the creation of workbench requests
only if you use the same material numbers for different products in ERP clients connected to the
same EWM client. If necessary, transport the workbench request to other EWM systems.
1. In Customizing for SCM Basis under Integration BAdIs for Specific Applications
Product BAdI: Inbound Processing for Product , select the APOCF005_SYSDIF
implementation.
2. Choose Create.
3. In the Implementation Name field, enter a name for your implementation, for example,
Z_APOCF005_SYSDIF.
4. Choose Continue.
5. In the Implementation Short Text field, enter a description for your implementation.
6. Save your implementation in a customer-own package or as a local object.
7. In the menu, choose Goto Sample Code Copy and confirm the message in the Copy
Example Code dialog box with Yes.
8. In the menu, choose Implementation Activate .
Example
SAP provides a sample implementation for the BAdI. The sample implementation adds a suffix
to the ERP material number when creating the EWM product master record.
ERP Material Number Material Description ERP System/Client EWM Product Number
4711
Small Part
ABC/001
4711@ABC001
4711
Large Part
XYZ/001
4711@XYZ001
You can copy the sample implementation to your own implementation as described in the
procedure above.
Name
ERROR_INBOUND
WMTOCO_INBOUND
WMCATO_INBOUND
WMBBIN_INBOUND
WMSUMO_INBOUND
WMTORD_INBOUND
Tables EWM
/SCWM/O* -- Warehouse task