| Status | Approved |
|---|---|
| Owner | |
| Stakeholders | |
| Jira Request ID | |
| Jira Development ID |
High- Level Specification
| Implementing System | SAP S/4HANA |
|---|---|
| Invoked by/Invokes | ERP-1138 |
| Business Process Reference | 02.04.02.01. Manage Standard Sales Order |
Functional Overview
The functional design of the system interface defines the API to be provided or consumed.
EDI customers sends their Sales Order creation message through Elemica to Syensqo. Elemica sends the OrderCreate XML to SAP CPI which then calls a custom API to create the Sales Order in Syensqo's S/4HANA system.
The purpose of this functional specification is to create the custom API for the creation of a sales order in S/4HANA either
- From data directly available in the Elemica XML or
- from data derived from S/4HANA based on data in the Elemica XML.
Scope and Objectives
This System Interface, a custom implementation in SAP S/4HANA,
- consumes the OrderCreate data from SAP CPI
- maps this data into a structure to create a sales order in SAP S/4HANA
- transform some data OrderCreate message from SAP CPI into the Sales Order structure in S/4HANA
- performs lookup of specified data (as applicable) in S/4HANA
- stored certain data from OrderCreate message from SAP CPI into a S/4HANA custom table
The standard SAP Sales Order API is unable to support the above functions, hence the need for a custom API.
Process Flow Diagram
Step | Description | Comment |
|---|---|---|
1 | Based on the purchase order received from Syensqo's EDI customer, Elemica converts this into OrderCreate message and sends to SAP CPI via API Management |
|
2. | SAP CPI receives the OrderCreate XML message from Elemica and maps to SAP Sales Order in S/4HANA. To create the Sales Order, SAP CPI calls the custom API which is the scope of this functional specification | This is covered in Integration Process functional specification ERP 1138 |
3 | Sales Order is created in SAP S/4HANA based on the message received from SAP CPI |
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 (Intermediate Target) | SAP eDoc Standard Mapping (Source) | Custom Mapping (Source) | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| S-NR | Flow (SD/FI/MM/ALL) | Target Field | Target 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 |
|---|---|---|---|