Prerequisites for Intercompany Purchasing in SAP ECC in Integration Hub

Prerequisites for Intercompany Purchasing in SAP ECC in Integration Hub

  1. You have set-up the system landscape and you have tested the technical connections between the systems.

For more information about setting up your technical system landscape, refer the Setting Up the System Landscape for SAP ECC Knowledge article. 

  1. Copy the scenario steps of the packages to your namespace, create a scenario package in your namespace, and adjust the definitions.

Data Initialization and Synchronization

Initialize and synchronize the subsidiaries with business partner, product, customizing, and values settings for this scenario.

For more information about the data structure and SAP ECC reference tables for each value, see the Value Mapping section of this guide.


Creating Customer Master Records for Subsidiaries in SAP ECC

In SAP ECC, the subsidiary is a managed as a customer and therefore create a customer master record for each subsidiary that provides all necessary information to process sales transactions with the subsidiary. 

The following configuration steps are also relevant for a subsidiary customer master record: 

  1. Output condition records

Create output condition records for this customer number to automatically send out documents to the subsidiary using ALE.

  1. Partner function

To store the subsidiary’s customer ship-to address, which ALE transfers, set up the ZH partner function and assign it to the subsidiary customer master record.


Adding SAP ECC Information in SAP Integration Framework 2.0

Add the following information in SAP Integration Framework 2.0:

  1. SysID-specific properties

Maintain the SAP ECC customer master number in the SysID-specific properties for each subsidiary.

  1. Scenario step-specific filter criteria

Maintain the SAP ECC customer master record as a filter criteria value in the scenario package definition to route the relevant document (message) to the corresponding receiver system.


Creating a Vendor Record in SAP Business One

In the scenario, you purchase (inter-company) products from the headquarters. The headquarters is your vendor. Create a vendor master record in SAP Business One to store all necessary information for processing purchase transactions with the headquarters. SAP Business One creates purchase orders, goods receipt drafts, and A/P invoices for this vendor number.


Adding SAP Business One Information in SAP Integration Framework 2.0

Add the following information in SAP Integration Framework 2.0:

  1. SysID-specific properties

Maintain the SAP Business One vendor master number in the SysID-specific properties for the headquarters.

  1. Filter criteria

Maintain the SAP Business One vendor master record as a filter criteria value in the scenario package definition to route the documents to the corresponding receiver system.