Message Type, Basic Type and Extension

Explanation

Message type represents the business meaning of an IDoc, such as ORDERS, INVOIC, MATMAS or DEBMAS. Basic type defines the technical segment structure of the IDoc, such as ORDERS05 or INVOIC02. An extension is used when customer-specific segments or fields are added to a standard IDoc structure. Many developers confuse message type and basic type. The message type tells what business document is exchanged, while the basic type tells how it is structured.

Code example

* Purpose:* Show the conceptual difference between message type and basic type.* Message type tells what business document is being exchanged.* Basic type tells which segment structure is used. * Examples:* ORDERS = Message type for order exchange* ORDERS05 = Basic type with technical segment structure * INVOIC = Message type for invoice exchange* INVOIC02 = Basic type with invoice segment hierarchy * Extension example:* ZINVOIC_EXT may add a custom Z segment under the standard INVOIC02 structure. * Interview tip:* Message type = business meaning.* Basic type = technical structure.

Real project scenario

A customer invoice interface used message type INVOIC and basic type INVOIC02. A custom Z segment was added to pass additional tax information through an IDoc extension.

Common mistakes

- Confusing message type and basic type. - Adding extension segment at wrong hierarchy level. - Not coordinating extension with middleware or partner. - Forgetting partner profile update after extension.

Best practices

- Use standard basic type where possible. - Create extension only when standard segments are not enough. - Keep custom segments minimal. - Validate extension with receiver system.

Interview angle

Interviewers commonly ask the difference between message type and basic type. A strong answer should include extension concept.