High- Level Specification

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

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://test-integration.eu.managedgateway.cloud.sap	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
• 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

Source Structure and Target Structure

Standard mappings are a subject to change and are not linked in this documentation, latest excel sheet can be downloaded from CIG → Resources → Implementation Guides → Mapping Specs → Ariba Network

• Order (IDOC to cXML)

Mapping contains basic field mapping from the IDOC message into the cXML target structure with a basic logic explained in the pseudo code

Processing Logic

Processing within Source

Message to the CIG is initiated by the standard SAP logic trough the output control defined for the document type. IDOC structure is enhanced by the CIG add on setup with a custom CIG elements. In a case custom fields are needed, customer exit can be implemented

• ARBCIG_ORDER_REQUEST_002
• ARBCIG_ORDER_REQUEST_011
• ARBCIG_PO_ITEM_LINEDEL_002

Processing within Middleware

At this moment, standard transformation as referenced above is in place. In a case of any custom field is needed, custom field will be mapped in the CIG to the predefined custom field structure in the SAP 

Processing within Target

Message Received by Business Network is routed to the Suppliers account if the trading relationship is established. In a case it's not, email is sent to the supplier with the invitation to join Business Network. 

Interface Alert & Monitoring

Language Requirements

User Interface Requirements

Sequencing

Volumetrics

Performance Consideration

Error Handling

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log