This section gives you an overview of systems you can use in the SAP Integration Framework 2.0 system landscape and provides you with information about how to technically connect the systems with each other.
The system landscape setup tasks depend on which integration scenarios you want to use.
SAP Integration Framework 2.0 acts as a bridge between the headquarters and the subsidiaries. SAP Integration Framework 2.0 uses the DI API through the DI Proxy component to communicate with SAP Business One in the subsidiary. SAP Business One Event Sender collects data change events in SAP Business One and transfers them to SAP Integration Framework 2.0. SAP Integration Framework 2.0 uses RFC to connect to SAP ECC in the headquarters.
The following table gives you an overview of the available integration scenarios, the required system landscape you must setup, which component triggers the scenario, and the technical connections the systems use:
Integration Scenarios, Systems and Technical Connections
Integration Scenario |
SAP Integration Framework 2.0 |
SAP Business One Communication Components |
SAP ECC |
Master Data Distribution Product Master Data Distribution Customer SAP ECC -triggered |
Receiver SAP Business One Sender SAP ECC |
SAP Business One DI Proxy |
SAP ECC with ALE, RFC, BAPI |
Intercompany Purchasing Sales from Central Stock Sales from Local Stock SAP Business One event-triggered |
Receiver SAP Business One, SAP ECC Sender SAP Business One, SAP ECC |
SAP Business One DI Proxy SAP Business One Event Sender |
SAP ECC with ALE, RFC, BAPI |
To Import the package provided by walldorf solutions, perform the following steps.