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 |
|---|---|---|
Assumptions
Dependencies
Security, Integrity and Controls
Configuration Requirements
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 |
|---|---|---|---|