Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
JuanDK78
Participant

The IDOC adapter, or IDOC_AAE, in SAP Process Orchestration is much more restrictive on the validation and requirements of a IDoc message.

The Control segment EDI_DC40 is mandatory for the sender IDoc_AAE adapter, and if you use for the receiver side (which is recommended); these are the fields you must map.

EDI_DC40 FieldExample
Description
@SEGMENT1Always = 1

TABNAM

EDI_DC40Value is arbitrary, but EDI_DC40 is the standard

DIRECT

1

2=Inbound

1=Outbound

IDOCTY

DELVRY07IDoc basic Type

CIMTYP

IDOC Extension, it must be blank if the Idoc is not extended

MESTYP

DESADVIDOC Message

SNDPOR

SNDCLNT800

It must match the Adapter-Specific Identifier of the Sender Business Component or Business System use in the ICO.

In the integration directory open the sender communication component.

Go to Menu: Communication Component->Adapter-Specific Identifiers

Check the value of: IDOC Adapter->Logical system

SNDPRT

LS

LS=Logical System, KU=Customer, LF=Vendor, etc

Must match the configured partner profile type in the back-end t-code: we20

SNDPRN

SENDER

Sender Partner number, must match 

Must match the configured partner profile in the backend t-code: we20

RCVPOR

SAPID3Receiver Partner number, arbitrary value recommended SAP<sys-id>

RCVPRT

LSReceiver Partner Type, arbitrary value recommended LS
RCVPRNID3CLNT800Receiver Partner number, arbitrary value recommended <sys-id>CLNT<client number>

Tip:

You can use the Override IDoc control Header in the receiver Communication channel to have more control from the configuration side.

10 Comments
Labels in this area