High- Level Specification
| Implementing System | S/4 Hana |
|---|---|
| Invoked by/Invokes | |
| Business Process Reference | 03.04.05.02. Manage Service Entry Sheets |
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
| Step | Description | Comment |
|---|---|---|
| 1. | Requester enters Service Entry sheet against a CW PO in Fiory | |
| 2. | Approved Service Entry sheet triggers create / change event over predefined Business Object | |
| 3. | CIG provided BAPI is executed | |
| 4. | Web Service Call is placed to the CIG | |
| 5. | CIG translates message into cXML format | |
| 6. | cXML is sent to the Business Network, received in the Buyers Account | |
| 7. | Service Entry Sheet is translated into Suppliers account and is matched against the Purchase Order |
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
Special Requirements
Design Rationale
API Use
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 |
|---|---|---|---|