Select language:

Material Master

To be able to carry out stock movements (putaways and picks) in the decentralized WM system, material masters must exist in this system. The material master must be distributed between the central ERP system and the decentralized WMS.

The leading system for the material master is the central ERP system. In the central system, the material master is created and distributed to the decentralized WMS. The material master views defined in the central system must not all be available in the WM system. The material master views depend on the decentralized processing functions used in the WM system.

The following basic rules apply:
Distribute only the necessary master data so that the WM system remains able to operate.

Be aware that you must manually maintain all necessary Customizing settings for the material master in the decentralized WMS. Maintain the warehouse-relevant data of the material master (Warehouse Management view) in the decentralized WMS since this data is of local nature.

For general information on master data distribution, refer to the ALE documentation Master Data Distribution.

Reduction for material master

To distribute not all material master data, reduce the standard IDoc MATMAS (see also: ALE documentation Create reduced message type for master data ).

The reduced IDoc must contain the following segments:

  • E1MARCM - C segment (MARC)
  • E1MARDM - Warehouse / batch segment (MARD)
  • E1MARMM - Units of measure (MARM)
  • E1MEANM - European Article Number (MEAN)
  • E1MVKEM - Sales data (MVKE)
  • E1MLANM - Tax classification (MLAN)
  • E1MTXHM - Long text header
  • E1MTXLM - Long text line

If you want to use split valuation of materials, you must also activate segment E1MBEWM (material valuation MBEW) for the reduced IDoc.

Within the individual segments, you can also carry out reductions at field level. To do this, deactivate the fields that you do not need. See the example for a possible field-level reduction.

When reducing fields, be aware that deactivated required fields that do not belong to the core maintenance status can cause errors in the decentralized WM system when the IDoc is imported (for example, EKGRP - purchasing group). In this case, you must adapt the required field check in the decentralized WMS as follows: Logistics - General -> Logistics Basic Data: Material Master -> Material -> Control Data -> Define required-field check for ALE/data transfer (see also: ALE documentation Define required-field check for ALE/data transfer )

Material master distribution

The material master distribution is carried out based on the reduced message type and controlled through the filter objects. The filters define the amount of data to be distributed. Set the filters appropriately so that only material master data relevant for the decentralized WMS is distributed (for the relevant plants/storage locations, sales organisation or only for specific material types).

If you define a filter object (plant or sales organisation, for example) that does not refer to the root segment (E1MARAM), the filtering process during distribution only starts with the specific segment that is assigned to the filter. If, for example, a plant is defined as the filter, then only the segment of this plant is distributed. All other segments that are plant-independent are passed on without being filtered. For a material that is not created for a specific plant, the root segment is distributed to the decentralized WMS as a minimum. The master data can also be distributed using classes. In this case, only materials of a specific class are distributed to the decentralized WMS (see also: ALE documentation Distribution Using Classes .) To maintain the required settings, go to ALE Customizing and choose Distribution (ALE) -> Master Data Distribution -> Distribution Using Classes.

Article master

If you use the SAP Retail System, the article master needs to be distributed as well. The distribution is carried out using BAPI RetailMaterial.Clone (Method Clone for object type BUS1001001 = RetailMaterial). Communication is asynchronous and takes place using the IDoc of message type ARTMAS generated from the BAPI. Since this IDoc cannot be reduced, all article master data is distributed to the decentralized WMS. You must also define a meaningful filtering for this message so that only the article masters relevant for the decentralized WMS are distributed.

Example

Reduced IDoc MATMAS:


MATMAS03
|
---# E1MARAM (*) Master material general data (MARA)
|
|------E1MAKTM (*) Master material short texts (MAKT)
|---# E1MARCM (+) Master material C segment (MARC)
| |
| -------E1MARDM (+) Master material warehouse/batch segment
|
|---# E1MARMM (+) Master material units of measure (MARM)
| |
| -------E1MEANM (+) Master material European Article Number
|
|------E1MVKEM (+) Master material sales data (MVKE)
|------E1MLANM (+) Master material tax classification (MLAN)
----# E1MTXHM (+) Master material long text header
|
-------E1MTXLM (+) Master material long text Line

Segment E1MARAM:

MSGFN (*) Function
MATNR (*) Material
ERSDA (+) Character field, 8 characters long
ERNAM (+) Name of person who created object
LAEDA (+) Character field, 8 characters long
AENAM (+) Name of accounting clark who changed record
PSTAT (+) Maintenance status
LVORM (+) Indicator: Flag material for deletion at client level
MTART (+) Material type
MBRSH (+) Industry sector
MATKL (+) Material group
BISMT (+) Old material number
MEINS (+) 3-Byte field
BSTME (+) 3-Byte field
BRGEW (+) Text field length 14
NTGEW (+) Text field length 14
GEWEI (+) 3-Byte field
VOLUM (+) Text field length 14
VOLEH (+) 3-Byte field
BEHVO (+) Container requirements
RAUBE (+) Storage conditions
TEMPB (+) Temperature conditions indicator
TRAGR (+) Transportation group
STOFF (+) Hazardous material number
SPART (+) Division
KUNNR (+) Competitor
EAN11 (+) International Article Numbers (EANs/UPCs)
LAENG (+) Text field length 14
BREIT (+) Text field length 14
HOEHE (+) Text field length 14
ERGEW (+) Text field length 14
ERGEI (+) 3-Byte field
ERVOL (+) Text field length 14
ERVOE (+) 3-Byte field
GEWTO (+) 3-Byte field
VOLTO (+) 3-Byte field
XCHPF (+) Batch management requirement indicator
VHART (+) Shipping material type
FUELG (+) 3-Byte field
STFAK (+) R/2 table
MAGRV (+) Material group: shipping materials
MHDRZ (+) Character field of length 6
MHDHB (+) Character field of length 6
VPSTA (*) Maintenance status of complete material

Segment E1MAKTM:

MSGFN (*) Function
SPRAS (*) Character field of length 1
MAKTX (+) Material description
SPRAS_ISO (+)

Segment E1MARCM:

MSGFN (*) Function
WERKS (*) Plant
PSTAT (*) Maintenance status
LVORM (+) Deletion flag
BWTTY (+) Valuation type
MAABC (+) ABC indicator
EKGRP (+) Purchasing group
AUSME (+) 3-Byte field
LADGR (+) Loading group
XCHPF (+) Batch management requirement indicator
VRVEZ (+) Character field of length 6
VBAMG (+) Text field length 14
VBEAZ (+) Character field of length 6

Segment E1MARDM:

MSGFN (*) Function
LGORT (*) Storage location
PSTAT (*) Maintenance status
LVORM (+) Ind.: Flag material for deletion at storage loc. level
DISKZ (+) Storage location MRP indicator
LGPBE (+) Storage bin
LWMKB (+)

Segment E1MARMM:

MSGFN (*) Function
MEINH (*) 3-Byte field
UMREZ (+) R/2 table
UMREN (+) R/2 table
EAN11 (+) International Article Numbers (EANs/UPCs)
NUMTP (+) Number Category of International Article Number (EAN)
LAENG (+) Text field length 14
BREIT (+) Text field length 14
HOEHE (+) Text field length 14
MEABM (+) 3-Byte field
VOLUM (+) Text field length 14
VOLEH (+) 3-Byte field
BRGEW (+) Text field length 14
GEWEI (+) 3-Byte field

Segment E1MEANM:

MSGFN (*) Function
MEINH (*) 3-Byte field
LFNUM (*) Consecutive number
EAN11 (+) International Article Numbers (EANs/UPCs)
EANTP (+) Number Category of International Article Number (EAN)
HPEAN (+) Flag main International Article Number (EAN)

Segment E1MVKEM:

MSGFN (*) Function
VKORG (*) Sales organisation
VTWEG (*) Distribution channel
LVORM (+) Ind.: Flag material for deletion at distr. chain lvl
LFMNG (+) Text field length 14
SCMNG (+) Text field length 14
SCHME (+) 3-Byte field
VRKME (+) 3-Byte field
MTPOS (+) Item category group from material master

Segment E1MLANM:

MSGFN (*) Function
ALAND (*) Departure country (country from which goods are sent)
TATY1 (*) Tax category (sales tax, federal sales tax,...)
TAXM1 (*) Tax classification for this material
TATY2 (*) Tax category (sales tax, federal sales tax,...)
TAXM2 (*) Tax classification for this material
TATY3 (*) Tax category (sales tax, federal sales tax,...)
TAXM3 (*) Tax classification for this material
TATY4 (*) Tax category (sales tax, federal sales tax,...)
TAXM4 (*) Tax classification for this material
TATY5 (*) Tax category (sales tax, federal sales tax,...)
TAXM5 (*) Tax classification for this material
TATY6 (*) Tax category (sales tax, federal sales tax,...)
TAXM6 (*) Tax classification for this material
TATY7 (*) Tax category (sales tax, federal sales tax,...)
TAXM7 (*) Tax classification for this material
TATY8 (*) Tax category (sales tax, federal sales tax,...)
TAXM8 (*) Tax classification for this material
TATY9 (*) Tax category (sales tax, federal sales tax,...)
TAXM9 (*) Tax classification for this material
TAXIM (*) Tax indicator for material (Purchasing)

Segment E1MTXHM:

MSGFN (*) Function
TDOBJECT (*) Texts: application object
TDNAME (*) Text name
TDID (*) Text ID
TDSPRAS (*) Character field of length 1
TDTEXTTYPE (*) SAPscript: Format of a text
SPRAS_ISO (+)

Segment E1MTXLM:

MSGFN (*) Function
TDFORMAT (*) Tag column
TDLINE (*) Text line

Activities

  • Reduce the standard message type MATMAS for the distribution of the material master. To maintain the message type, go to ALE Customizing and choose Distribution (ALE) -> Master Data Distribution -> Create reduced message type for master data.
  • Perform all additional activities (such as activating the change pointer, setting the distribution using classes) for the new message type you have created. To do this, go to ALE Customizing and choose Distribution (ALE) -> Master Data Distribution.
  • If you have reduced required fields, you must adapt the required field check in the decentralized WMS: Logistics - General -> Logistics Basic Data: Material Master -> Material -> Control Data -> Define required-field check for ALE/data transfer.
  • So that the material master changes can be distributed, you must schedule a report that evaluates the change pointers and generates the IDocs. To schedule the report, go to ALE Customizing and choose Distribution (ALE) -> Scheduling Periodic Processing -> Scheduling IDoc Creation from Change Pointers.
  • Check within ALE if further activities such as serialized distribution are still necessary.
  • Maintain the distribution model for the new message type you have created. Maintain this message together with all other distribution objects when the distribution model is generated.