Setting System Type-Specific Properties for the Subsidiary SAP Business One System(s) in SAP Integration Framework 2.0 for Master Data Distribution in SAP S/4 HANA
Maintain SysID-specific properties for each subsidiary in the system landscape. System ID-specific properties are available per system type. When you create a system landscape entry, this entry gets a unique system ID (SysID). You can maintain fixed values for properties for the SysID.
SAP Integration Framework 2.0 accesses the properties at runtime and uses them for message processing, for example, for automatically defaults setting, option selection, and so on.
All scenario packages that use the systems as senders or receivers, can access the SysID-specific properties.
From a business point of view, the aim of using the SysID-specific properties is to place the subsidiary in the company organization environment. In the large account environment, the settings represent the organizational entity of the subsidiary from the headquarters’ point of view. The settings describe the subsidiary with SAP S/4 HANA organization units. For example, the subsidiary represents the sales channel for the headquarters’ products in a foreign country.
Prerequisites
You have set up the system landscape with all sender and receiver systems in SAP S/4 HANA and in SAP Integration Framework 2.0.
For more information about setting up your technical system landscape, refer the Setting Up the System Landscape for SAP S/4 HANA Knowledge article.
Procedure
- To start SAP Integration Framework 2.0, choose Start → All Programs → Integration Framework for SAP Business One → Integration Framework.
- To log on, in the B1i Administrative Login user interface, enter the user name and password.
- Choose SLD and select the SLD entry for your subsidiary.
- Select the Properties button to set the following properties:
|
Field Name |
Field Value |
Description |
|
Company Code |
<Company code key from S/4 HANA system> This is a four-digit key representing the company code. It structures the business organization from a financial accounting perspective. |
For the respective company code values or entries, see the company codes set up in your headquarters SAP S/4 HANA system. When you enter the company code representing your subsidiary in your network, financial accounting-specific data is selected from the SAP S/4 HANA message accordingly. |
|
Company Language |
Language key> Example: EN English |
It defines the main company language for the subsidiary and enables access to the language-dependent values in the message, valid for the respective target subsidiary system. For country-specific values or entries, see the ISO codes for countries. |
|
Country |
<Country key> Example: EN ISO code for UK |
Enables access to the country-dependent values in the message, valid for the respective target subsidiary system For country-specific values or entries, see the ISO codes for countries. |
|
Distribution Channel |
<Distribution channel key from S/4 HANA system> The two-digit key represents the distribution channel. Used to structure the business organization from a distribution channel perspective. You can set up distribution channel-specific data per customer master data record, to maintain, for example, specific conditions and pricing. |
For distribution channel values or entries, see the distribution channels set up in the headquarters SAP S/4 HANA. Refer to the organizational structure set up in the headquarters SAP S/4 HANA. When you enter the distribution channel representing your subsidiary in the company network, processing selects distribution channel-specific data from the SAP S/4 HANA message. A distribution channel is not a single filter or selection criterion. It is used in combination with a sales organization and (for some master data) with a division. The combination of the keys represents the SAP S/4 HANA sales area. |
|
Division |
<Division key from S/4 HANA system> The two-digit key represents the product division. It structures the business organization from a product division perspective. You can set up product division-specific data per customer master data record, to maintain, for example, specific conditions and pricing. |
For the product division values or entries, see the product divisions set up in your headquarters SAP S/4 HANA system. When you enter the division representing your subsidiary in the company network, processing selects division-specific data from the SAP S/4 HANA message. A division is not a single filter or selection criterion. It is used in combination with a sales organization and a distribution channel. The combination of the keys represents the SAP S/4 HANA sales area. |
|
Foreign Language |
<Language key> Example: DE German |
It defines the foreign company language for the subsidiary and enables access to the language-dependent values in the message, valid for the respective target subsidiary system. For language-specific values or entries, see the ISO codes for countries. |
|
Plant |
<Plant key of SAP S/4 HANA> The four-digit key represents the plant. It structures the business organization from a plant perspective. |
You can maintain data at plant level for the following views on a material master record: MRP, Purchasing, Storage, Work Scheduling, Production Resources/Tools, Forecasting, Quality Management, Sales and Costing. For plant values or entries, see the plants set up in SAP S/4 HANA. When you enter the plant representing your subsidiary in the company network, processing selects plant-specific data from the SAP S/4 HANA message. |
|
Sales Organization |
<Sales organization key from S/4 HANA system> The four-digit key represents the sales organization. It structures the business organization from a sales perspective. |
You can set up sales-specific data per customer master data record, to maintain, for example, specific conditions and pricing. For sales organization values or entries, see the sales organizations set up in your headquarters SAP S/4 HANA system. When you enter the sales organization representing your subsidiary in the company network, processing selects sales organization-specific data from the SAP S/4 HANA message. A sales organization is the highest summation level (after the Client organizational unit) for sales statistics with their own statistics currency. |
Note
All other properties are not relevant for the current scenario. You can ignore them.
Save your settings.
Related Articles
Setting System Type-Specific Properties for the Headquarters SAP S/4 HANA in SAP Integration Framework 2.0 for Master Data Distribution
Prerequisites You have set up the system landscape with all sender and receiver systems in SAP S/4 HANA and in SAP Integration Framework 2.0. For more information about setting up your technical system landscape, refer the Setting Up the System ...Setting Up the Scenario Package in SAP Integration Framework 2.0 for Master Data Distribution in SAP S/4 HANA
You use the setup functions for scenarios to configure your intercompany purchasing scenario. To set up the scenario, do the following: Select the scenario package Select the scenario Select the scenario step. Select the sender systems. Select the ...Scheduling Jobs for Master Data Distribution in SAP S/4 HANA in Integration Hub
This section describes how to schedule jobs for the periodic creation of intermediate documents (IDocs) for master data. You schedule the jobs for each defined variant, hence, for each message type. For example, if you want to distribute customer ...Creating System ID-Specific Properties for Subsidiary SAP Business One Systems in SAP Integration Framework 2.0 for Intercompany Purchasing in SAP S/4 HANA
Maintain SysID-specific properties for each subsidiary in the system landscape. System ID-specific properties are available per system type. When you create a system landscape entry, this entry gets a unique system ID (SysID). You can maintain fixed ...SLD System Assignment in SAP Integration Framework 2.0 for Master Data Distribution in SAP S/4 HANA
Expand the scenario sap.MasterData to open associated scenario steps. There will appear 4 scenario steps: OE.HUB.S4BP2B1BP.Main (Receiver of the IDoc) , OE.HUB.S4BP2B1BP.RCV (B1 Outbound), OE.HUB.S4PR2B1IT.Main (Receiver of the IDoc), ...