Maintaining the Distribution Model in SAP S/4 HANA for Intercompany Purchasing in Integration Hub
When you model the message flow, you specify the applications that communicate with each other in an ALE business process. A message flow defines the sending and receiving systems and the message type. Sending and receiving systems are logical systems and must be defined in the SAP S/4 HANA. Define the message flow in the distribution model.
To model a message flow using IDocs or BAPIs, specify a model view in the distribution model. In the model view, add the respective message type.
To model the communication between SAP Integration Framework 2.0 and SAP S/4 HANA for the OE.HUB.SubsidiaryIntegration package, define the following entries in the distribution model:
- The ORDERS message type defines the inbound sales order from SAP Integration Framework 2.0 (sending system) to SAP S/4 HANA (receiving system).
- The ORDRSP message type defines the outbound order update from SAP S/4 HANA (sending system) to SAP Integration Framework 2.0 (receiving system).
- The DESADV message type defines the outbound shipping notification from SAP S/4 HANA (sending system) to SAP Integration Framework 2.0 (receiving system).
- The INVOIC message type defines the outbound A/R invoice from SAP S/4 HANA (sending system) to SAP Integration Framework 2.0 (receiving system).
Prerequisites
- You have set up the logical systems for your sender and receiver systems.
- You have set up the RFC connection to your SAP Integration Framework 2.0 server.
- The model view names in the entire distributed environment of the organization are unique.
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
- From the IMG menu, choose SAP NetWeaver → Application Server → IDoc Interface / Application Link Enabling (ALE) → Modeling and Implementing Business Processes → Maintain Distribution Model and Distribute Views.
Alternatively, call the BD64 transaction.
- Change to Edit mode and choose Create Model View.
- In the Create Model View window, enter the following:
Field Name
Field Value
Description
Short Text
<Distribution model name>
Example: IC-SfLS/SfCS
The short text of a distribution view describes the communication relationships entered in the model view and it is displayed in the distribution model maintenance.
Technical name
<Distribution model technical name >
Example: B1ICSALES
The technical name of the distribution model is unique.
Start date
The creation date is the default value.
This is the start date of the validity period. Change the default value only, if you want the validity period to start later.
End date
The default value is 31.12.9999.
This is the last day of the validity period.
- To add message types to the distribution model, in the Distribution Model Changed window, select your previously created distribution model and choose Add message type.
- In the Add message type window, enter the following:
Field Name
Field Value
Description
Model view
The system displays the <Name of your distribution model> by default.
This is the technical name of the model view for which you create the message flow. It is the technical name of your distribution model view; do not change it.
Sender
<Logical system name for the SAP Integration Framework 2.0 server>
Receiver
<SAP S/4 HANA logical system name>
Message type
ORDERS
- Choose Enter and repeat the steps above to add the following message types to your distribution model:
Sender
Receiver
Message Type
Remarks
<SAP S/4 HANA logical system name>
<Logical system name for the SAP Integration Framework 2.0 server>
ORDRSP
This is the order update outbound message from SAP S/4 HANA (sales order) to SAP Business One (purchase order).
<SAP S/4 HANA logical system name>
<Logical system name for the SAP Integration Framework 2.0 server>
DESADV
This is the shipping notification outbound message from SAP S/4 HANA (delivery) to SAP Business One (draft GR or GR).
<SAP S/4 HANA logical system name>
<Logical system name for the SAP Integration Framework 2.0 server>
INVOIC
This is the invoice outbound message from SAP S/4 HANA (A/R invoice) to SAP Business One (A/P invoice).
- Save the distribution model.
Note
Define data filters for the DESADV, INVOIC and ORDRSP message types, and group them according to the customer number representing your subsidiary. To do this, under your message type, double-click No filter set and Create filter group. Define your customer or vendor number.
Next Step: Generating Partner Profiles in SAP S/4 HANA for Intercompany Purchasing in Integration Hub
Related Articles
Configuration in SAP S/4 HANA for Intercompany Purchasing in Integration Hub
The setup and configuration in SAP S/4 HANA consist of the following steps: Creating output types for sales documents, outbound deliveries, and billing documents Creating output determinations for sales documents, outbound deliveries, and billing ...Maintaining the Distribution Model for Master Data Distribution in SAP S/4 HANA in Integration Hub
In ALE you model the message flow that defines the sender and receiver systems, and the message type in the distribution model. For master data distribution from SAP S/4 HANA to SAP Integration Framework 2.0, define the following for the distribution ...Creating Output Determinations for Billing Documents in SAP S/4 HANA for Intercompany Purchasing in Integration Hub
Define the output determinations for invoice document processing based one the previously created output types. Prerequisites You have created the output type for sending invoices to a subsidiary. Procedure Choose Sales and Distribution → Basic ...Generating Partner Profiles in SAP S/4 HANA for Intercompany Purchasing in Integration Hub
Define the partner profiles for all outbound and inbound messages based on the information in the distribution model. Generate the partner profiles based on the information you have already maintained in your relevant distribution model. ...Changing Partner Profiles in SAP S/4 HANA for Intercompany Purchasing in Integration Hub
For ALE communication, you define partners with inbound or outbound parameters in partner profiles. If any partner values are not applicable to the scenario, change them manually. Prerequisites You have generated the partner profile for the ...