High- Level Specification

Functional Overview

Service Entry Sheet entered against CW Service POs in ERP system is send to the Business Network after its approval. 

Service Entry Sheet from ERP is triggered upon the create or change event over the business object. As opposite to other Business Network flows, message is send as a regular Web Service Message and is translated to the CXML message in the CIG. 

Service Entry Sheet is received in Business Network Buyers account and is routed to the Business Network Suppliers account, where the supplier is notified based on his preference. Assumption is that the supplier already has a trading relationship established,

due to the fact the Service Entry Sheet follows previously created Purchase Order.

Scope and Objectives

This document describes S/4 Hana outbound interface for sending ERP Initiated Service Entry Sheets into Business Network and the basic configuration needed in all the components in order for this interface to be operational.

Process Flow Diagram

Assumptions

• In SWEC transaction, document type ENTRYSHEET is assigned to the business object BUS2091 for On Create and On Change event
• Ariba source object and S/4HANA System target field mappings, including custom fields, will be updated based on mapping requirements in S/4HANA System

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 ServiceEntrySheet

CIG Routing

Each Soap message sent from S/4 Hana contains System ID reference. No additional routing is needed in the CIG Addon - any subsequential message related to the Purchase Order sent from the S/4 Hana will use the System ID of the Purchase Order or the system id of the follow up document from S/4 Hana

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 Web Service select EU Data Center for Europe and same credentials as in the RFC Destination
  • General Settings.Setup Interface.Configure the Connections to Send Messages In the section for Interface Setup for Web Service, under the Outbound messages sent to Managed Gateway for Spend&Network select ERP Initiated Service Entry Sheet
    • execute the program Configure the Connections to Send Messages. This execution effectively creates the web service definition in the SOAMANAGER
  • Application Specific Settings 
    • ERP-initiated Service Sheet.Maintain Parameters for ERP-initiated Service Sheet: Parameter ERP_SES_ENABLED set to X. Official documentation can be found here
    • ERP-initiated SErvice Sheet.Maintain the Change Document Event for ERP-initiated Service Sheet - create CHANGED and CREATED event types for the document object ENTRYSHEET for object type BUS2091. Offcial documentation can be found here
    • ERP-initiated SErvice Sheet.Maintain Event Type Linkages for ERP-initiated Service Sheet - for object type BUS2091,  define Receiver Function Module ARBCIG_EXT_EVENT_ERP_SES for event Create. Official documentation can be found here

Special Requirements

Not Applicable

Design Rationale

Not Applicable

API Use

Not Applicable

Data 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

• ERPSES(proxy-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

Describe the processing requirement in the System

Delta or Full Load Requirements

Please describe change tracking requirements, i.e. transferring only delta, or always full load

Interface Alert & Monitoring

Please describe any alert & monitoring requirement for business users and support organization, i.e. AIF

Language Requirements

Specify multi language requirements

User Interface Requirements

Capture the requirements for the user interface (UI) associated with the interface. It should provide a clear description of how users will interact with the interface and how information will be presented to ensure usability and accuracy. 

Sequencing

Please describe delivery requirements driven by message sequencing, i.e. specific order, impact of disruption of sequence, are duplicates allowed, etc.

Volumetrics

Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)

Performance Consideration

Specify if there are any specific performance factors that need to be taken into consideration during development i.e. interface must be able to handle 100 posting per-hour, etc.

Error Handling

Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures

Testing

How to Test

Please provide some guidance and/or test data to help the developer unit test the interface. Please include both positive and negative testing (to validate error situations handling)

The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again, or explain how to create new input data to the test. In particular, the developer will need logons for test users representing the various roles within the approval process.

Test Conditions and Expected Results

Test Considerations/Dependencies

List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log