High- Level Specification

Functional Overview

Interface describes the Purchase Order message send from S/4 Hana to the suppliers in Business Network. Origin of the Purchase Order is not relevant, any Purchase Order from S/4 Hana that falls under the Output Control definition is send to the Business Network

Supplier receives Purchase Order via Business Network based on his integration setup. Once a PO is generated in S/4HANA, it is transmitted to the SAP Business Network. Suppliers are instantly notified via an email, which contains the PO as a PDF attachment. Suppliers have the flexibility to review the PO details either in their email inbox or by logging into their SAP Business Network account.

Fully integrated Suppliers receive POs directly within their ERP 

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 sent 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 SAP 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

• Purchase order Document Types are configured in S/4 Hana
• Output control using NAST via IDOC is configured in S/4 Hana and output conditions are maintained.

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

The following are the Security and Authorization considerations for this interface:

• Message exchange between S/4 and CIG is encrypted over https. 
• Access to interface parameters in CIG Addon is only available to the person with access to the SPRO authorization.
• Access to the CIG is restricted to the integration administrators within Ariba Guided Buying or Ariba Business Network

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 ServiceSheetExportRequest. 

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:

    • Parameter Name	Value - TEST	Value - PROD
      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	TBD - Not available at the moment
      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. CIG Addon uses NACE output management

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 specific segments. These segments are added by the following includes.

• ARBCIG_ORDER_REQUEST_002
• ARBCIG_ORDER_REQUEST_011
• ARBCIG_PO_ITEM_LINEDEL_002

Above includes are activated in customer exists of MM module - as referenced in the official documentation

Processing within Middleware

At this moment, standard transformation as referenced above is in place. In a case of any custom field is needed, custom fields must be added to the IDOC via CIG Includes, then mapped in the CIG OrderRequest Map into <Extrinsic> elements

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

Not Applicable

User Interface Requirements

Not Applicable 

Sequencing

Not Applicable

Volumetrics

approximately 50-100 POs a day are expected on the PROD environment.

Performance Consideration

There are no specific performance requirements or considerations related to this interface.

Error Handling

In a case IDOC fails to be sent to the CIG, it can be reprocessed from WE02. 

In a case Purchase Order fails to be sent to the supplier, it can be found under "Failed Orders to Private Supplies" from where it can be resend or permanently removed

Testing

How to Test

Test Supplier account must be available and accessible. 

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log