High- Level Specification

Functional Overview

The functional design of the system interface defines the API to be provided or consumed. 

EDI customers sends their Sales Order change message through Elemica to Syensqo. Elemica sends the OrderChange XML to SAP CPI which a custom API which compares the OrderChange fields (or a subset of) with the existing Sales Order fields (or a subset of) and identifies the fields that the OrderChange message is requesting to change. The Sales Order and the fields where new values are sent in the OrderChange message are then sent to the Order Modification Fiori App for CSR review and approval / rejection.  A notification is also sent to the CSR on the sales order with the changes requested by the customer. 

The purpose of this functional specification is to create the custom API for the identification of the changes to a sales order requested by the customer and sending notification of the changes to the CSR. This will be done by using

1. data directly available in the Elemica XML
2. data derived from S/4HANA based on data in the Elemica XML (e.g. using the Purchase Order Number in Elemica XML to find the Sales Order Number in S/4HANA)
3. data directly pulled from S/4HANA (e.g. Sales Order Number and specific sales order fields)

Scope and Objectives

This System Interface, a custom implementation in SAP S/4HANA,

• consumes the OrderChange data from SAP CPI
• maps this data into a structure to compare with existing sales order in SAP S/4HANA
• transform some data OrderChange message from SAP CPI into the Sales Order structure in S/4HANA
• performs lookup of specified data (as applicable) in S/4HANA
• stage certain data from OrderChange message from SAP CPI into a S/4HANA custom table

The standard SAP Sales Order Change API is unable to support the above functions, hence the need for a custom API.

Process Flow Diagram

Assumptions

1. The custom Sales Order Change API will be called from SAP CPI and be able to lookup data from SAP S/4HANA to feed the target structure of the sales order
2. The source object and S/4HANA System target field mappings, including custom fields, will be updated based on mapping requirements in S/4HANA System.
3. The Custom API should be able to map all source and target mappings to successfully create a sales order
4. The custom API should be able to send Fiori launchpad notifications to CSR identified on the sales order

Dependencies

1. All configurations in S/4HANA from where the custom API should look up values should already be implemented before the interface is deployed.
2. Connection between SAP CPI and S/4HANA already set up
3. Required master data in S/4HANA already loaded

Security, Integrity and Controls

• Required authorisations to execute the custom API need to be defined.
• Existing secure connectivity for communication between SAP S/4HANA and SAP CPI will be applied.

Configuration Requirements

N/A

Special Requirements

N/A

Design Rationale

API Use

Custom API based on API_SALES_ORDER_SRV_0001 (tbc)

Data Structure

The following fields will be used to provide the required data structure of the interface:

The following fields will be used to provide the required data structure of the interface:

Calculation and Validation

OrderChange API vs Sales Order Comparison Fields

eDocument mapping

Processing Logic

Sales Order Look Up using Purchase Order Number

Logic to find CSR for a sales order

Read VBPA-PERNR where::

VBPA-VBELN = Sales order number

VBPA-PARVW = 'ER' for Employee Responsible (tbc exact code after configuration)

Anything else needed to be able to send notification to this user?

Delta or Full Load Requirements

Interface Alert & Monitoring

Language Requirements

User Interface Requirements

N/A
 

Sequencing

N/A

Volumetrics

Performance Consideration

Error Handling

Integration errors: Between Elemica and SAP CPI

S/4HANA Error during trigger of notification to CSR's fiori launchpad

• technical issue
• data issue eg CSR not found in Sales Order

S/4HANA Error during 'staging' and/or update of sales order data to customer Fiori Launchpad

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log