High- Level Specification

Functional Overview

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

1. From data directly available in the Elemica XML or
2. 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

Insert the flowchart and fill in the steps

Assumptions

Describe any assumptions that have been made in the process of completing this design. What functionality is expected of configuration or other developments that pass information to this development and/ or retrieve the information processed by it (performance, triggers, exceptions, etc.)

1. The custom Sales Order Create API will be called from SAP CPI and be able to lookup data from SAP S/4HANA to feed the target structure to create 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

Dependencies

Indicate any dependencies or constraints that may impact development, in terms of requirements from internal or external applications or teams, limited access to legacy systems, time constraints or data restrictions. Also, please specify schedule dependencies e.g. interface or batch jobs that must run prior to execution.

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

To detail the security requirements for processing this object, any data integrity issues associated with the object and the teams that will be responsible for processing the object, i.e. authorization/roles required to who can execute the interface, encryption requirement, etc.

• 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

Specify the configuration requirements for this object. Like in case of substitution/ routine specify the configuration needed

tbc

Special Requirements

Specify any special requirements or considerations that may impact the interface based on specific locations, regulatory compliance or system limitations. Clearly outline requirements e.g. localization rules for countries like China

If the interface interacts with third-party systems such as Icertis, describe any additional integration, security or authentication considerations that must be taken into account.

tbc

new custom table to map Header DUNS and Body DUNS

Design Rationale

This template section may be used to specify the custom API design. The requirement can be for an API provider which means the API will be designed in the system or can be for an API consumer which means that an API will be consumed in the system.

API Use

Populate the type of the API use  in this section. Will the API be Consumed or Provided. 

Custom API from API_SALES_ORDER_SRV_0001

Data Structure

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

Calculation and Mapping

Populate the table below to list the calculation and validation rules per field. Can be deleted if not needed.

Note for LA: if it is based on received value, ok in calculation table. if based on other logic not from received value, in processing logic