You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Status

  Approved

Owner
Stakeholders
Jira Request ID
Jira Development ID

High- Level Specification

Implementing SystemSAP S/4HANA 
Invoked by/Invokes

ERP-1138 - Getting issue details... STATUS

Business Process Reference02.04.02.01. Manage Standard Sales Order


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

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

  1. No system interface functional specification is required for Elemica as the approach is to keep as-is the process on the Elemica side for the SyWay project. 
  2. API Management is for security/routing and do not change the message structure or format

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 - Getting issue details... STATUS

3

Sales Order is created in SAP S/4HANA based on the message received from SAP CPI


Assumptions

  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

  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

tbc

Special Requirements

tbc

new custom table to map Header DUNS and Body DUNS

Design Rationale

API Use

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:

ParentFieldDescriptionMandatory (Y/N)Data Type
ZDocumentHeaderDocumentIdentifier
Y

DocumentIdentifierDateTime
Y

RequestingDocumentIdentifier
N

RequestingDocumentDateTime
N

SenderPartnerName
Y

SenderPartnerRole
Y

SenderDUNS
Y

SenderContactName
N

SenderContactDescription
N

SenderTelephoneNumberTelecomCountryCode
N

SenderTelephoneNumberTelecomAreaCode
N

SenderTelephoneNumberPhoneNumber
N

SenderFaxNumberTelecomCountryCode
N

SenderFaxNumberTelecomAreaCode
N

SenderFaxNumberPhoneNumber
N

SenderEmailAddress
N

SenderAlternativeCommunicationMethod
N

SenderAddressLine
N

SenderCityName
N

SenderStateProvince
N

SenderPostalCode
N

SenderPostalCountry
N

SenderLocationCode
N

SenderTaxIdentifierNumber
N

ReceiverPartnerName
Y

ReceiverPartnerRole
Y

ReceiverDUNSCode
Y

ReceiverContactName
N

ReceiverContactDescription
N

ReceiverTelephoneNumberTelecomCountryCode
N

ReceiverTelephoneNumberTelecomAreaCode
N

ReceiverTelephoneNumberPhoneNumber
N

ReceiverFaxNumberTelecomCountryCode
N

ReceiverFaxNumberTelecomAreaCode
N

ReceiverFaxNumberPhoneNumber
N

ReceiverEmailAddress
N

ReceiverAlternativeCommunicationMethod
N

ReceiverAddressLine
N

ReceiverCityName
N

ReceiverStateProvince
N

ReceiverPostalCode
N

ReceiverPostalCountry
N

ReceiverLocationCode
N

ReceiverTaxIdentifierNumber
N










A_SaleOrderDsitributionChannel
Y

OrganisationDivision
Y

SalesOrderType
Y

SalesOrgansation
Y

PurchaseOrderByCustomerCustomer reference number that the customer uses to uniquely
identify a purchasing document (for example, a sales inquiry or
a purchase order)		Y

ZContractNumberCustomer reference number that the customer uses to uniquely
identify a purchasing document (for example, a sales inquiry or
a purchase order)		N

TransactionCurrencyThe currency that applies to the sales order

N



ZRevisionNumber

N



ZReleaseNumber

N







A_SalesOrderHeaderPartnerPartnerFunction



ContactPerson












A_SalesOrderTextLanguage
(key)		The language key indicates the following:

  • The language in which texts are displayed

  • The language in which you enter texts

  • The language in which the system prints texts

Y

LongTextID
(key)
Y

LongText
Y


Calculation and Validation 

Not needed as information will be in the processing logic section

ParentFieldRule TypeRule Instruction












Processing Logic

describe the custom table for the header and body DUNS

how the header DUNS is fetched (which field in XML) and where it is stored

EDPAR look ups

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

IDConditionExpected Results






Test Considerations/Dependencies


Other Information


Development Details

Package

Package NameParent Package




Other Development Objects

Object TypeObject NamePurpose/High Level LogicDesign Rationale Reference









Appendix

See also


  File Modified
No files shared here yet.

Change log

Version Published Changed By Comment
CURRENT (v. 12) Apr 17, 2026 07:41 ABOLAJI-ext, Luqman
v. 67 Apr 15, 2026 21:44 ABOLAJI-ext, Luqman
v. 66 Mar 26, 2026 17:55 ABOLAJI-ext, Luqman
v. 65 Mar 25, 2026 23:12 ABOLAJI-ext, Luqman
v. 64 Mar 25, 2026 11:39 ABOLAJI-ext, Luqman
v. 63 Mar 24, 2026 18:47 ABOLAJI-ext, Luqman
v. 62 Mar 24, 2026 15:44 ABOLAJI-ext, Luqman
v. 61 Mar 24, 2026 11:53 ABOLAJI-ext, Luqman
v. 60 Mar 24, 2026 08:29 ABOLAJI-ext, Luqman
v. 59 Mar 13, 2026 12:18 ABOLAJI-ext, Luqman

Go to Page History

  • No labels