Skip to main content Skip to complementary content

Mandatory field values for IDoc files

When IDoc files are sent to an SAP system, they must be well-formed and they must include a number of mandatory field values.

You can either provide these values explicitly using mapping value expressions, or you can let Talend Data Mapper generate the values for you when it outputs an IDoc file.

The following tables show the fields that Talend Data Mapper can populate for you if you do not specify a value expression yourself, and provide rules showing how the value is obtained. In most cases the values come from context parameters set in Talend Studio or from the IDocs representation properties.

For information on how to set context parameters, see Using contexts and variables.

EDI_DC40 segment

Field

Rule

Example

TABNAM Constant value EDI_DC40
MANDT Context parameter "sap_client" 800
DOCNUM Sequence number starting at 1. Number is unique for each map execution. 0000000000000001
DOCREL Context parameter "sap_release" 731
DIRECT Constant value giving the direction (inbound from an SAP standpoint) 2
IDOCTYP Stored in the IDocs representation properties (Original IDoc type name) BANK_CREATE01
CIMTYP Stored in the IDocs representation properties (Original IDoc extension) -
MESTYP Stored in the IDocs representation properties (Original IDoc message type) BANK_CREATE
SNDPOR Context parameter "sap_sender_port" SAPCEI
SNDPRT Context parameter "sap_sender_partner_type" LS
SNDPRN Context parameter "sap_sender_partner_number" CEICLNT800
RCVPOR Context parameter "sap_receiver_port" TALENDF
RCVPRT Context parameter "sap_receiver_partner_type" LS
RCVPRN Context parameter "sap_receiver_partner_number" EEICLNT800
CREDAT Creation date -
CRETIM Creation time -

All data segments

Field

Rule

Example

SEGNAM

Constant value - Stored in the Initiator

E2BANK_CREATE001

MANDT

Same as EDI_DC40/MANDT

800

DOCNUM

Same as EDI_DC40/DOCNUM

0000000000814490

SEGNUM

Sequential number starting at 1 for this IDoc instance

-

PSGNUM

Parent SEGNUM for nested segments, 0 for top level segments

-

HLEVEL

Depth of the segment starting at 2 (1 for non looping segments)

-

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!