Adapters

IDOC ---- ALE set up

Why do we create Inbound RA/Outbound RA?

Why do we import Metadata?

Why do we create Logical System?

IDOC Status Codes – Outbound

03 – Successful

01 – Idoc created

02 – Error (error passing data to port)

30 – Ready for dispatch

IDCO Status code – Inbound

56 – Idoc with Error

Idoc T-codes
WE30 – for Idoc creation

WE02 or WE05 – for Idco view or display

WE19 – for idoc trigger or for reprocess

SM58 – tRFC monitoring for Idoc stuck message

Idoc sender side configuration

Idoc receiver side configuration

Idoc bundling/packaging

Idoc serialization
ABAP Proxy

For ABAP Proxy, we connect using SOAP Adapter using XI 3.0 transfer protocol.

It is Synchronous and Asynchronous

For Configuring ABAP Proxy we create Software Component, Name Space, Data Type, Message Type,
and Service Interface.

We share the details of created Software component version, Namespace, and Service Interface
details to ABAP team via email.

The ABAP team will run TCode SPROXY and the EXR components have to be visible there, if the
components are not visible, we will go for PROXY set up.

In Proxy set up, we create 4 RFC destinations using TCode SM59

LCRSAPRFC - TCP/IP type

SAPSLDAPI – TCP/IP type

SAP_PROXY_ESR _ G type

4th Destination by any name G type

1st and 2nd destinations are for SLD connection