Hi guys,
In this topic, i will show you step by step to send data from third party system to SAP CAR or SAP S/4 HANA by abap proxy.

STEP 1: CREATE INTEGRATION OBJECTS IN ESR (ENTERPRISE SERVICE REPOSITORY)

1 – Data type:
Source: DT_{NAME}_IN
Target: DT_{NAME}_OUT
2 – Message Type:
Source: MT_{NAME}_IN, assign data type: DT_{NAME}_IN
Target: MT_{NAME}_OUT, assign data type: DT_{NAME}_OUT
3 – Service Interface:
Source: SI_{NAME}_IN, assign message type: MT_{NAME}_IN, direction: Outbound
Target: SI_{NAME}_OUT, assign message type: MT_{NAME}_OUT, direction: Inbound
4 – Message Mapping:
Name: MM_{NAME}
Source Message Type: MT_{NAME}_IN
Target Message Type: MT_{NAME}_OUT
5 – Operation Mapping
Name: OM_{NAME}
Source Service Interface: SI_{NAME}_IN
Target Service Interface: SI_{NAME}_OUT
Message Mapping: MM_{NAME}
=>>>> {NAME} is your interface name
STEP 2: CREATE INTEGRATED CONFIGURATION OBJECTS IN IB (INTEGRATION BUILDER
1 – BUSINESS SYSTEM
Create business system for sender system
Create business system for SAP CAR | SAP S/4 HANA receiver system
Import new business systems to IB
2 – SENDER COMMUNICATION CHANNEL
Create SFTP Sender communication channel.

Attribute Name | Attribute Values |
---|---|
Transport Protocol | SFTP |
Message Protocol | File Content Conversion |
Adapter Engine | Central Adapter Engine |

Content Conversation for SFTP sender channel: https://help.sap.com/viewer/5336c62e683348a8886ff7ef4b15c40f/1.0.5/en-US/2e99f0fb5a9e45b3b148c90e87fafcd1.html
Attribute Name | Attribute Values | Remarks |
---|---|---|
Document Name | MT_{NAME}_IN | Source message type name |
Document Namespace | {Namespaces} | Source message type namespaces |
Recordset Name | RECORDSET | Sub-segment of source message type |
Recordset Structure | DATA,* | Sub-segment of Recordset Name and all fields |
DATA.fieldSeparator | , | Your CVS delimiter rule |
DATA.fieldNames | AAA,BBB,CCC | Your MT_{NAME}_IN fields name |
DATA.ignoreRecordsetName | TRUE | if you want ignore recordset name |
DATA.endSeparator | ‘nl’ | |
DATA.missingLastFields | ignore | |
DATA.additionalLastFields | ignore |
3 – RECEIVER COMMUNICATION CHANNEL

Attribute Name | Attribute Values |
---|---|
Adapter Type | SOAP |
Transport Protocol | HTTP |
Message Protocol | XI 3.0 |
Adapter Engine | Central Adapter Engine |

Attribute Name | Attribute Values |
---|---|
Addressing Type | https://{HOSTNAME}:{PORT}/sap/xi/engine?type=entry |
User Name | SAP User Name |
Password | SAP User’s password |
Login Language | EN |
SAP Client | Your SAP client |
STEP 3: IMPLEMENT AND CONSUME MESSAGE ON SAP
1 – SETUP HTTP CONNECTION IN SAP
Refer to this document https://sapzero2hero.com/2019/10/22/sap-po-abap-proxy-configuration-step-by-step/
2 – IMPLEMENT ABAP CODE TO USE DATA
Tcode: sproxy
STEP 4: CHECK INCOMING MESSAGES
TCode: SXMB_MONI

Thank you and hope can help you when develop integration scenarios easier.
Cuong Dang