- This document will explore scenario where there is a need to integrate a cloud-based application with older version of SAP ECC or S/4 HANA where integration cannot be achieved using WebSocket RFC.
- Integration between SAP S/4 HANA Public Cloud and Central Finance (CFIN) system is a critical component that need to consolidate their financial data across multiple systems.
- SAP S/4 HANA Public cloud is a cloud-based ERP solution that offers a comprehensive suite of business applications for various industries, while CFIN is a SAP solution that enables companies to integrate and consolidate financial data from various system into a single unifies system.
- The Integration between these two systems can be achieved using SAP Landscape transformation and Business connector.
- SLT is a real-time data replication and transformation tool that allows companies to extract data from various source systems, including S/4 HANA Public Cloud and load it into CFIN system.
- Business connector is a middleware solution that provides a seamless and efficient way to connect SAP and non-SAP systems, allowing companies to integrate data from different source systems into their CFIN systems
- Integrating S/4 HANA Public Cloud with CFIN system, companies can gain real-time insights into their financial data, streamline their financial processes, and ensure data consistency across different systems
2. Pre-requisites
- Access to S/4 HANA Public Cloud system
- Build CFIN S/4 HANA system
- Build SLT system
- Install Business connector 4.8.1 SR2
3. Steps Required in S/4 HANA Cloud Systems
o Create Communication User
To create a Communication User, navigate to “Maintain Communication Users” tile in S/4 HANA Cloud tenant and create a new user
o Create Communication System
Navigate to Communication System Tile and provide CFIN system details
Provide the communication user details created in step 3.1 in inbound communication section.
Also, note down the Logical System details of S4HANA cloud which will be required to create Logical system in CFIN system
o Creation Communication Scenario
- Communication Arrangement SAP_COM_0574
This is required to integrate On-Prem system with S4 HANA Cloud.
- To create a communication arrangement that activates the connection to the SAP BTP Connectivity Service, open the Communication Arrangements app from the SAP Fiori Launchpad and click New.
- Select the scenario SAP_COM_0574 and enter a meaningful arrangement name.
- Paste the service key of the SAP BTP Connectivity Service instance.
- Click Create to proceed.
- The Communication Arrangement and corresponding Communication User and System is automatically created with the information provided in the service key.
- Once above steps are completed successfully add the on-prem server to the cloud connector and use the virtual host name and location ID in next communication arrangement.
- Communication Arrangement SAP_COM_0083
Navigate to Communication arrangement Tile in S4 HANA Cloud and create below communication arrangement
Provide the details of Communication system and communication user created on the previous step.
4. CFIN to Cloud Connectivity
In CFIN source system create a WebSocket RFC pointing to S/4 HANA Cloud system from CFIN S4 system by providing below details
- API End Point URL of S/4 HANA Cloud
- Port number (Usually 443)
- CFIN User created in step 3.1
- In Logon and security tab, please make sure to define client as 100 which is standard across all cloud systems
- Check the alias button which is mandatory to connect to S/4 HANA Cloud system
5. Connection setup for On-premises System to S/4HANA Cloud
5.1. Create SAP Server for backend SLT system
- Adapters – SAP
- Press ‘Add SAP Server’
- Section ‘System’
- Name = <SID> of Backend system. E.g. SID
- Connection Type = CPIC Connection
- Section ‘Server Logon’
- Application Server = host name of the backend system. E.g., xyz.com
- System Number = Instance Number of backend system. E.g., 00
- Other settings: keep default value
-
- Section ‘System’
- Press ‘Add SAP Server’
5.2 Create SAP Servers for SAP S/4 HANA Cloud
- Adapters – SAP
- Press ‘Add SAP Server’
- Section ‘System’
- Name: <SID of S/4HANA Cloud system> _<S/4HANA Cloud Client>_<COM_SCENARIO>. e.g. S4H_100_SAP_COM_0083
- Connection Type: WebSocket Connection
- Section ‘Login Defaults’
- User: Inbound communication user for the communication scenario
- Password: Password of the Inbound communication user for the communication scenario
- Is Alias-User: Checked
- Client: Client number of the S/4HANA Cloud test target client. E.g. 100
- Language = EN
- Section WebSocket Server
- WebSocket Host: API host of the S/4HANA Cloud test target client. e.g. myhostname-api.s4hana.ondemand.comWebSocket Port: 443
- Section Advanced Settings
- RFC Trace: Off
- Repository Round trip Optimization: System (→Default value)
- Serialization Format: Column Based
- Network: WAN
- Save
- Test Connection
- Section ‘System’
- Perform Connection test and connection test should be successful
5.3 Create a Listener for backend System
- Adapters – SAP
- Click on the SAP Server that was created in the previous step ‘Create SAP Server for Backend’
- Column ‘Listeners’, click on the link at ‘0’
- Press ‘Add Listener’
- Maintain the following fields
- Connection Type = TCP/IP
- Program ID = BC_<SID_Backend>_<SID_S/4H><ClientS/4H>_<Comm Scenario ID without SAP_> e.g. S4H_100_SAP_COM_0083
- Number of Threads = 2
- Gateway Host = prim. app server of backend system, E.g. hostname.xyz.com
- Gateway service = sapgw<instance no. of backend>. E.g. sapgw01
- Autostart = Yes
- Repository Server = <SAP Server for S/4HANA Cloud Client> which was created in the previous step
- Security settings
- SNC enabled = No (default)
- Press ‘Save’.
- Press “Red Button” in column ‘Started?’
- After ~ 30 seconds refresh the browser window and check if the icons in columns ‘Started?’ and ‘State’ are green.
- If not: check for error messages.
5.4 Create a SM59 TCP/IP Destination in the Backend system
- In the backend system (any client), open transaction SM59
- Press ‘Create’ to add the following destination
- Tab ‘Technical Settings’
- RFC Destination name = BC_<SID_Backend>_<SID_S/4H><ClientS/4H>_<Comm Scenario ID without SAP_>. e.g. S4H_100_SAP_COM_0083
- Connection Type = T (TCP/IP)
- Description = BCM Request Number if integration setup via DLM team or DLM Incident number if integration scenario is setup by Dev team directly
- Activation Type = Registered Server Program
- Program ID = BC_<SID_Backend>_<SID_S/4H><ClientS/4H>_<Comm Scenario ID without SAP_> e.g. S4H_100_SAP_COM_0083
- Remark: must match with the Program ID defined in the Listener
- Gateway Host = prim. app server of backend system. E.g. hostname.xyz.com Gateway service = sapgw<instance no. of backend>. E.g. sapgw00
- Tab ‘Unicode’
- Communication Type with Target System = Unicode
- Other settings: default values
- Save.
- Press button ‘Connection test’ to check if the connection works successfully.
- Tab ‘Technical Settings’
5.5 Create Routing
- Adapters – Routing
- Section ‘Add Routing Rule’
- Maintain
- Sender = *
- Receiver = SM59 TCP/IP destination created in the backend system. e.g.MTE_100_SAP_COM_0083
- Message Type = *
- Press ‘Add’
- Section Routing Rule Flow
- Field Comment
- Add:
- If requested via BCM request:
- SI <Scope Item ID>
- BCM request <request number>
- If requested via DLM Incident:
- DLM Incident <URL to DLM Incident>
- Section Transport
- Select ‘RFC’
- Section ‘Configure RFC Transport’
- Specify SAP Destination = select the entry that was created previously in chapter ‘SAP Server for S/4HANA Cloud Client. e.g. MTE_100_SAP_COM_0083
- Press Save.
- Press ‘No’ in column ‘Enabled’ to enable the Routing.
- If requested via BCM request:
- Add:
- Field Comment
- Section Routing Rule Flow
After completing all the above steps integration of S/4 HANA Cloud system is completed and we can proceed with standard configuration of CFINIMG and MTID creation.
Subscribe
Login
Please login to comment
0 Comments