SAP ECC MATMAS05 Material Master IDoc Segments Reference
This reference lists the MATMAS05 segments for the material master IDoc in SAP ECC 6.0, with the parent segment, the material master table each one carries and whether it is mandatory. Use it to build a reduced message type, map a non-SAP system or read a failed IDoc.
| Segment | Parent | Material master table | Description | Mandatory | Occurrence | Key fields |
|---|---|---|---|---|---|---|
E1MARAM | Root | MARA | General material data | Y | Once per IDoc | MSGFN, MATNR, MTART, MBRSH, MEINS, MATKL |
E1MARA1 | E1MARAM | MARA | Additional fields for E1MARAM (long material number, EWM and handling unit fields) | N | Once | MATNR_EXTERNAL, MATNR_VERSION, MATNR_GUID |
E1MAKTM | E1MARAM | MAKT | Material short texts | Y | One per language | MSGFN, SPRAS, MAKTX, SPRAS_ISO |
E1MARCM | E1MARAM | MARC | Plant data | N | One per plant | MSGFN, WERKS, DISMM, DISPO, BESKZ, PRCTR |
E1MARDM | E1MARCM | MARD | Storage location data | N | One per storage location | MSGFN, LGORT, LGPBE |
E1MFHMM | E1MARCM | MFHM | Production resource/tool data | N | Repeating | MSGFN, OBJTY, OBJID |
E1MPGDM | E1MARCM | MPGD | Product group (planning material) data | N | Repeating | MSGFN, PRGRP, PRWRK, UMREF |
E1MPOPM | E1MARCM | MPOP | Forecast parameters | N | Repeating | MSGFN, PERKZ, PRMOD |
E1MPRWM | E1MARCM | PROW | Forecast values | N | Repeating | MSGFN, ERTAG, PRWRT |
E1MVEGM | E1MARCM | MVER | Total consumption | N | Repeating | MSGFN, ERTAG, VBWRT |
E1MVEUM | E1MARCM | MVER | Unplanned consumption | N | Repeating | MSGFN, ERTAG, VBWRT |
E1MKALM | E1MARCM | MKAL | Production versions | N | One per production version | MSGFN, VERID, BDATU, ADATU, STLAL, PLNNR |
E1MARMM | E1MARAM | MARM | Units of measure | N | One per alternative unit | MSGFN, MEINH, UMREZ, UMREN |
E1MEANM | E1MARMM | MEAN | International article numbers (EANs) | N | Repeating per unit | MSGFN, EAN11, EANTP |
E1MBEWM | E1MARAM | MBEW | Valuation data | N | One per valuation area and type | MSGFN, BWKEY, BWTAR, BKLAS, VPRSV, STPRS, VERPR |
E1MLGNM | E1MARAM | MLGN | Warehouse number data | N | One per warehouse number | MSGFN, LGNUM |
E1MLGTM | E1MLGNM | MLGT | Storage type data | N | One per storage type | MSGFN, LGTYP, LGPLA, LPMAX, LPMIN |
E1MVKEM | E1MARAM | MVKE | Sales data | N | One per sales organization and distribution channel | MSGFN, VKORG, VTWEG, MTPOS |
E1MLANM | E1MARAM | MLAN | Tax classification | N | One per country | MSGFN, ALAND, TATY1, TAXM1 |
E1MTXHM | E1MARAM | STXH | Long text header | N | One per text object, ID and language | MSGFN, TDOBJECT, TDNAME, TDID, TDSPRAS |
E1MTXLM | E1MTXHM | STXL (text lines) | Long text lines | N | One per text line | MSGFN, TDFORMAT, TDLINE |
Segment list and hierarchy as in SAP ECC 6.0 MATMAS05; check WE30 or WE60 in your system for exact occurrences and for any customer extension segments. Field lists show the most used fields, not every field.
Get your material distribution reviewed
Send your reduced message type and a failed MATMAS IDoc and we will tell you which segments or customizing gaps cause the errors.
Optional. The tool and every export work without this. No spam.
Where this lives in SAP ECC
Material master distribution uses message type MATMAS with basic type MATMAS05. BD10 sends materials manually; change pointers (BD50 to activate per message type, BD52 for relevant fields, BD21 to process) send changes automatically. On the receiving side, process code MATM calls IDOC_INPUT_MATMAS01, which creates or changes the material through the same logic as direct input. Distribution model (BD64) and partner profiles (WE20) decide who receives what. A reduced message type created in BD53 lets you strip segments and fields you do not want to send, for example valuation data to a non-SAP warehouse system.
- BD10: send material
- BD53: reduce message type
- BD50 / BD52 / BD21: change pointers
- WE30 / WE60: segment tree and documentation
Worked example: one material, two plants
A raw material with two plants, three storage locations, one sales area, two languages and valuation in both plants produces: one E1MARAM; two E1MAKTM (EN, DE); two E1MARCM, each with its E1MARDM children (three in total); two E1MBEWM, one per valuation area; one E1MVKEM; one E1MARMM per alternative unit with any E1MEANM below it; and E1MLANM per country. Each segment carries a message function in MSGFN: 003 delete, 004 change, 005 replace, 009 original, 018 resend; check which value your sender uses, because the receiver treats them differently. To leave a field unchanged on the receiver, send the NODATA character '/' in it rather than a blank, because a blank overwrites the existing value.
Common errors and gotchas
Status 60 or 51 with a mandatory segment message means E1MARAM or E1MAKTM is missing, often because a reduced message type dropped texts. Errors such as plant or valuation area not defined appear when the receiver lacks the organizational units; fix customizing, not the IDoc. Material type and industry sector in E1MARAM must exist in the receiver. The material number fields MATNR_EXTERNAL, MATNR_VERSION and MATNR_GUID in E1MARA1 relate to long material numbers and are normally empty in ECC. Custom fields need a segment extension (WE30 extension, then the user exits in the MATMAS inbound and outbound function modules); do not add fields to the standard segments.
How to check the result in the system
WE02 shows the segment tree of the IDoc; expand E1MARCM to confirm each plant arrived. Status 53 means the material was posted. Compare the material in MM03 on both systems, or read MARA, MARC and MBEW in SE16 for the same MATNR. For change pointers, BDCP2 (or BDCPV) shows which pointers were created and processed.
Frequently Asked Questions
What is the IDoc for material master in SAP?
Message type MATMAS with basic type MATMAS05 in SAP ECC 6.0. Outbound uses BD10 or change pointers; inbound uses process code MATM with function module IDOC_INPUT_MATMAS01. MATMAS_BAPI is an alternative message type based on the BAPI interface, with its own structure.
Which MATMAS segments are mandatory?
E1MARAM (general data from MARA) and E1MAKTM (material description from MAKT) are mandatory. All other segments are optional and can repeat, such as E1MARCM per plant and E1MBEWM per valuation area. If a reduced message type removes E1MAKTM, the receiver rejects the IDoc.
How do I add custom fields to MATMAS?
Create an extension of MATMAS05 in WE30 with a Z segment under the right parent, for example under E1MARAM for MARA Z fields, link it to message type MATMAS in WE82, then fill it in the outbound user exit and read it in the inbound user exit. Never change standard segment definitions.
What does '/' mean in a MATMAS IDoc field?
The slash is the NODATA character. It tells the inbound function module to leave the existing value unchanged. A blank field instead means clear the value. This matters on change sends from non-SAP systems that only know some fields of the material master.
If your master data team wants to ask in plain English which materials failed distribution and why, we can add a private AI layer over SAP ECC on your own servers.
Related Tools
SAP ECC ORDERS05 IDoc Segments and Qualifiers Reference
The ORDERS05 segments and qualifier values used for inbound sales orders and outbound purchase orders, with the SD and MM fields they map to.
SAPSAP IDoc Message Types Reference (ORDERS, DESADV, INVOIC, MATMAS, DEBMAS)
Searchable list of common SAP IDoc message types with the basic IDoc type, business meaning and the X12 or EDIFACT message they usually map to.
SAPSAP IDoc Status Codes Reference
Look up any IDoc status code, see whether it is inbound or outbound, whether it is an error, and which transaction to use to fix it.
SAPSAP IDoc and ALE Transactions, Tables and Programs Reference
One searchable list of the transactions, tables and standard programs an SAP integration developer uses to build, monitor and repair IDoc and ALE interfaces.
More SAP tools
See all- SAP ECC Private AI Layer Blueprint Generator
- SAP ECC AI Assistant Sizing and Value Calculator
- SAP ECC SD User Exit Forms Reference (MV45AFZZ, RV60AFZZ, MV50AFZ1)
- SAP ECC Customer Exits (SMOD Enhancements) by Module Reference
- SAP ECC Classic BAdI Definitions Reference (MIGO, ME21N, MIRO, Deliveries, PM Orders)
- SAP ECC Background Job Tables Reference (TBTCO, TBTCP, Job Status Codes)
- SAP ECC Output Determination Tables and Codes Reference (NAST, TNAPR, NACE)
- SAP ECC Movement Type Configuration Tables Reference (T156, T156T, T157D)
- SAP ECC Stock Type and Location Transfer Movement Type Matrix
Keep exploring
Free tools
- SAP ECC ORDERS05 IDoc Segments and Qualifiers ReferenceThe ORDERS05 segments and qualifier values used for inbound sales orders and outbound purchase orders, with the SD and MM fields they map to.
- SAP IDoc Database Growth CalculatorEstimate IDoc table growth from daily volume, segments per IDoc and retention days, and see when archiving pays off.
- SAP ECC Custom Inbound IDoc Function Module Skeleton GeneratorGenerate a ready-to-adapt inbound IDoc function module for a custom message type and segment: standard interface, segment cast, validation, status 51 or 53, workflow return variables and the configuration steps.
ERP fixes and how-tos
- SAP IDoc Status 51: Application Document Not PostedIDoc status 51 means Application document not posted, a category, not a diagnosis. Find the real cause in WE02 or SLG1 and reprocess safely with BD87.
- Teamcenter to SAP BOM transfer: why releases fail and how to fix themTeamcenter to SAP BOM and material transfer failures: Gateway for SAP, IDoc and BAPI errors, material before BOM order, units, change numbers and checks.
- How to add AI to SAP ECC 6.0 on-prem without moving data to a cloudReference architecture for a private on-prem AI assistant on SAP ECC 6.0: RFC and BAPI reads, SLT replica, retrieval index, local LLM, permission mirroring.
Integrations
- How to use ChatGPT with SAP ECC 6.0Using ChatGPT with SAP ECC 6.0: custom GPT actions, exports versus live access, an OData or MCP bridge, enterprise data controls, and when a private model is safer.
- How to add AI agents to SAP ECC 6.0How to add AI agents to SAP ECC 6.0: a tool layer over BAPIs, RFC and IDocs, human approval before any posting, and an on-prem model that never leaves your network.