High- Level Specification
| Implementing System | S/4 Hana |
|---|---|
| Invoked by/Invokes | |
| Business Process Reference | 03.04.03.05. Process PO Output |
Functional Overview
Indirect Purchase Order created in S/4 Hana originating in Ariba Guided Buying is send to the Business Network. Ariba Guided Buying originated Purchase Order is identified by the custom document type - ZAR.
Direct Purchase Order created in S/4 is send to the Business Network. Standard Purchase Order is identified by the document type NB.
Supplier receives Purchase Order via Business Network based on his integration setup. For the light integrated suppliers, Purchase Orders are sent via eMail and available in the Business Network Suppliers account. Supplier can access Business Network account once the Trading Relationship is created.
Fully integrated Suppliers integrate Purchase Orders from Business Network to their ERP System.
Interface is triggered via the standard Output Control of the Purchase Order in S/4 Hana. IDOC message is send to CIG where it's translated into cXML message that is send to the Business Network. In the Business Network the PO is routed to the suppliers account in a case the trading relationship is created with the supplier. If the supplier doesn't have the trading relationship created yet, PO is sent to him via email along with the invitation to join Syensqo Business Network.
Scope and Objectives
This document describes S/4 Hana outbound interface for sending Purchase Order information into Business Network and the basic configuration needed in all the components in order for this interface to be operational.
Message is generated real time via the S/4 standard Output Control. Type of the IDOC is ARBCIG_ORDERS.
Process Flow Diagram
| Step | Description | Comment |
|---|---|---|
| 1. | Indirect Purchase Order is created in S/4 Hana from Guided Buying | |
| 2. | Indirect Purchase Order is created with the document type ZAR | |
| 3. | Output control defined for the document type ZAR triggers IDOC generation | |
| 4. | IDOC of type ARBCIG_ORDERS is generated and send over to the CIG | |
| 5. | CIG receives the message and applies the standard mapping over the IDOC, generates cXML document | |
| 6. | cXML document is sent to the Business network | |
| 7. | Business network receives the cXML order in the buyers account and routes it to the suppliers account, if account is created - trading relationship is already established with the supplier |
| Step | Description | Comment |
|---|---|---|
| 1. | Direct Purchase Order is created in S/4 Hana from Guided Buying | |
| 2. | Direct Purchase Order is created with the document type NEU | |
| 3. | Output control defined for the document type NEU triggers IDOC generation | |
| 4. | IDOC of type ARBCIG_ORDERS is generated and send over to the CIG | |
| 5. | CIG receives the message and applies the standard mapping over the IDOC, generates cXML document | |
| 6. | cXML document is sent to the Business network | |
| 7. | Business network receives the cXML order in the buyers account and routes it to the suppliers account, if account is created - trading relationship is already established with the supplier |
Assumptions
- Document Types ZAR and NEU are setup in S/4 Hana
Dependencies
- CIG Addon installed in S/4 Hana
- Cloud Connector installed in Syensqo landscape
- Initial setup of CIG Addon is done already as described in ERP-92, section Configuration Requirements.CIG Configuration.
- Connectivity from CIG Addon to CIG is established, as described in ERP-92
Security, Integrity and Controls
Configuration Requirements
CIG Configuration
Project setup is required in CIG to cover product type Ariba Network. One project is required per system ID of the backend S/4 system - Global, US and China. There are no additional setting for the Document Type Order Request.
CIG Routing
Each IDOC sent from S/4 Hana contains System ID Reference. No additional routing is needed in the CIG Addon as all the messages related to the initial Purchase Order sent from S/4 Hana will use System ID of the initial Purchase Order
CIG Addon Configuration
Configuration for CIG addon is consolidated in one place and should be completed in the logical order of the menu items. In the S/4 instance, navigate to SPRO → SAP Reference IMG →SAP Customizing Implementation Guide → Integration with Other SAP Components → Managed Gateway for Spend&Network for Buyer
Logical order of the menu is as following :
- Global Settings - majority of the common configuration is shared with Procurement solution and is already described in ERP-92, section Configuration. Only sections that are different are described in here
- Create RFC Destination - new RFC destination to be added under HTTP Connections to External Server. Official documentation can be found here. Values are as following:
Technical Settings.Target System Settings.Host http://integration.eu.managedgateway.cloud.sap Technical Settings.Target System Settings.Path Prefix /cxf/receiveAddonIDOC /cxf/receiveAddonIDOC Login And Security User P007937 P007937 Login And Security Password <confidential> <confidential>
- Create Logical System - new Logical System to be created for Business Network. Apart from the name definition, there's no additional setting needed. Official documentation can be found here
- Create RFC Destination - new RFC destination to be added under HTTP Connections to External Server. Official documentation can be found here. Values are as following:
- SAP Business Network Integration
- General Settings.Setup Interface.Configure the Connections to Send Messages In the section for Interface Setup for IDOC select Logical System created for the Business Network. Select Purchase Order document type and execute program
- Application Specific Settings.Purchase Order.Define Message Output Control for Purchase Order - official documentation can be found here. Idea is to setup output control for both, NEU and ZAR document types.
Special Requirements
Not Applicable
Design Rationale
Not Applicable
API Use
Not Applicable
Data Structure
The following fields will be used to provide the required data structure of the interface:
| Parent | Field | Description | Mandatory (Y/N) | Data Type |
|---|---|---|---|---|
Calculation and Validation
| Parent | Field | Rule Type | Rule Instruction |
|---|---|---|---|
eDocument mapping
| General | Syensqo XML (Target) | SAP eDoc Standard Mapping (Source) | Custom Mapping (Source) | ||||||
|---|---|---|---|---|---|---|---|---|---|
| S-NR | Flow (SD/FI/MM/ALL) | Field Details | Condition | Syensqo XML Node | Syensqo XML Field | SAP eDoc Standard Node | SAP eDoc Standard Field | Fixed Value | Custom Logic |
Processing Logic
Delta or Full Load Requirements
Interface Alert & Monitoring
Language Requirements
User Interface Requirements
Sequencing
Volumetrics
Performance Consideration
Error Handling
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|---|---|
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|