Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

An IDoc message type names the logical business message. Its basic type describes the data structure, while an agreed extension can add supported fields or segments.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

Integration connects applications so they can exchange information. A delivered message still needs the receiving application to understand and accept its business meaning.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SAP IDoc message type versus basic type: Read the business purpose and structure
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

Classic IDoc Interface/ALE message/basic-type concepts and the cited S/4HANA MATMAS example. Supported combinations depend on release, partner setup and interface contract.

Documentation review on 14 November 2026 using official SAP sources and indexed official excerpts where full Help text was unavailable. Scope and service or release differences are explained in the lesson. All datasets, requests and checks are illustrative; no customer SAP runtime execution or measured results are claimed.

A MANUFACTURING EXAMPLE

Read the purpose and structure of a plant IDoc

Read the IDoc contract

Message type: MATMAS. Basic type: MATMAS05. Extension: As agreed. Verification: Receiver contract
What to notice: Business purpose, structure and successful receiver processing are separate things to verify.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Message type
MATMAS
Basic type
MATMAS05
Extension
As agreed
Verification
Receiver contract
Words you’ll meet in this guide
Message
A package of information sent between systems.
Payload
The business content carried in a request or message.
API
A defined interface for another program to use.
Receiver
The system to which a message or request is sent.
IDoc
A structured SAP document format used to exchange business data.
HANA
SAP’s database platform.
XML
A format that organizes data into named, nested elements.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Business message → Basic type and extension → Receiver processing. Conceptual diagram for SAP IDoc message type versus basic type: Read the business purpose and structure.
Apply the idea: A manufacturer investigates an operational IDoc and needs both its business message purpose and concrete segment structure.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Read the purpose and structure of a plant IDoc

    A manufacturer investigates an operational IDoc and needs both its business message purpose and concrete segment structure.

  2. Read business purpose and structural type as separate identifiers

    An IDoc message type names the logical business message, while the basic type defines its segment structure.

  3. Understand the many-to-many assignment relationship

    SAP documents assigning basic types to logical messages and notes that a type can serve several logical messages and a message can have several type assignments.

  4. Worked case: MATMAS purpose, MATMAS05 structure, unexpected extension

    Imagine an interface agreed to send material master data using logical message MATMAS, basic type MATMAS05 and no custom extension.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.