/SCWM/CL_EX_ERP_INT_CONF_PLANT - Example: Item Type dep. Plant/Party Entitled to Dispose
CPI1466 during Backup TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
Functionality
Class /SCWM/CL_EX_ERP_INT_CONF_PLANT is an example implementation for BAdI /SCWM/ERP_INT_CONF.
The aim of the example is to show that various item types for the delivery in EWM can be found for the same item type in the ERP system, depending on the party entitled to dispose (plant of the ERP system). Using determine warehouse process type various warehouse processes can be found.
The determination of the document type in EWM for the ERP document type and the ERP document type forthe EWM document type is standard. For this, the source code of methods DET_DOCTYPE and DET_ITEMTYPEwas copied from the default implementation in class /SCWM/CL_DEF_IM_ERP_INT_CONF to class /SCWM/CL_EX_ERP_INT_CONF_PLANT. This requires the activityMap document types from ERP System to EWM to be maintained in Customizing.
To determine the item type in EWM, a separate logic must be implemented in the method DET_ITEMTYPE.This requires a separate table that, depending on the document and item type in the ERP system as wellas the plant, finds an item type in EWM. For this the example uses a separate table ZTMAPITMTYPPLANT,that differs from the table /SCWM/TMAPITMTYP used in the default implementation in that it has the additional key field PLANT (data element PLANT_D). This table is maintained instead of the IMG activityMap Item Types from ERP System to EWM. If the differentiation attribute is to be used as it is in the standard system, then the activityDefine ERP Document Types for Differentiation Attribute must also be maintained.
The table ZTMAPITMTYPPLANT used in the example is from delivery class C, with the Data Browser/Table View Maintenance setting 'Display/Maintenance permitted'. The structure used is as follows:
| Field | Key | Data Element | Check Table | Search Help |
|---|---|---|---|---|
| MANDT | X | MANDT | - | - |
| ERPBSKEY | X | SLD_BSKEY | - | /SCMB/SH_BSKEY |
| ERPDLVTYPE | X | /SCWM/DE_ERP_DLV_TYPE | - | - |
| ERPITMTYPE | X | /SCWM/DE_ERP_ITM_TYP | - | - |
| DOCTYPE | X | /SCDL/DL_DOCTYPE | /SCDL/TTYPE | - |
| ITMMAPDIF | X | /SCWM/DE_DIF_ITEM | - | /SCWM/ERP_DIFF_ATTR_ITEM |
| PLANT | X | WERKS_D | - | - |
| ITEMTYPE | /SCDL/DL_ITEMTYPE | /SCDL/TITMTYPE | /SCWM/ITEMTYPE |
In the example implementation, it is possible to use one entry for multiple plants (PLANT field), logicalsystems (ERPBSKEY), differentiation attributes (ITMMAPDIF) or EWM document types (DOCTYPE). An initialfield is used as a wildcard for these fields. Therefore read access occurs with both the value fromthe ERP document and the initial value. Subsequently, the table with the possible entries is sorted and . and the first entry is used. The sequence of the sort fields means that prioritization is possible.
Using the same principle, other location and organizational data can be be used to determine document types or item types.
Relationships
Example
In the described table ZTMAPITMTYPPLANT, the following entries are maintained:
| Field | Entry 1 | Entry 2 |
|---|---|---|
| ERPBSKEY | ||
| ERPDLVTYPE | LF | LF |
| ERPITMTYPE | TAN | TAN |
| DOCTYPE | ||
| ITMMAPDIF | ||
| PLANT | 0001 | |
| ITEMTYPE | ODLV | ZOD1 |
For plant 0001, the item type ZOD1 is used in EWM for the ERP document type LF with the item type TAN.Item type ODLV is found for all plants. This means. for example, that the warehouse process type 2010 could be found for plant 0002 and the warehouse process type Z201 could be found for plant 0001.
Notes
Further information
Addresses (Business Address Services) ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 5932 Date: 20120526 Time: 073703 triton ( 181 ms )
