High- Level Specification

Functional Overview

Service Entry Sheets (SES) created by the Supplier in Suppliers Account of the Business Network against the previously created Service POs. Service Entry Sheet can contain planned service or unplanned service, with or without the hierarchy. 

SES is send from Business Network as cXML document to CIG, where it's translated into SOAP message to be received in the S/4 Hana system.  

Scope and Objectives

This document describes S/4 Hana inbound interface for receiving Service Entry Sheets from Business Network and the basic configuration needed in all the components in order for this interface to be operational.

Process Flow Diagram

Assumptions

Service sheets with up to five levels of hierarchy (one parent item and four child line items) created against purchase orders containing service type line items from SAP Business Network are supported. Suppliers must create service sheets containing only one parent line item from a purchase order with multiple service type line items. Service sheets against the purchase order with service type line items can have both planned and unplanned line items. The service sheet must contain at least one-level service child line item in the hierarchical structure.

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
• SAP note 1832628 must be applied

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. Additional Settings are needed for ServiceEntrySheet Document Type

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 as the system id of the follow up document from S/4 Hana

CIG Addon Configuration

Connection settings are identical with the previously specified interfaces - please refer to the ERP 854. On top of this, following setup is needed in SPRO :

• SAP Business Network Integration.Application Specific Settings.Service Sheet
  • Maintain Parameters for Order Confirmation: set ENTRYSHEET_CREATE parameter with value 20, as described in the official documentation

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

• ServiceSheetExportRequest

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

Service Entry Sheet is submitted against the Purchase Order by the Supplier in the Suppliers account of the Business Network. Its routed to the Buyers Account of the Business Network and is routed to the source of of origin of the Original Purchase Order  

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

SOAP message is processed by the Class CL_ARBCIG_SERVICE_ENTRY_SHEET (transaction SE24 to debug). Message can be retrieved in SRT_MONI transaction

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