The guiding principle for programming standards and guidelines at Syensqo is to use what is generally accepted by the industry as “best-practice”, rather than defining a bespoke set of rules. By adopting this approach, it is more likely that developers engaged by Syensqo are already familiar with the “best-practice” approach and can work effectively in the Syensqo environment immediately.
This document’s purpose is to provide developers with the standards and guidance required to develop in Syensqo’s landscape.
All tools required to develop best-practice based are available.
Since SAP development tools and approaches are evolving so does this document.
The SAP Development Approach has been understood.
automated testing
itelliJ integrated with SCPI/eclipse integration
inline iflow editor
Pending Business requirements/NFR's, standard alerting should be in place
Retry based on business requirements and data/message criticality
IDOC post ALEAUDIT with error messages
Catch exceptions for alerting (if not posting error to another application system).
All return appropriate errors to calling system - be as informative as possible
Certificates > oAuth > Basic
Integration should NOT maintain data at rest
Stored in secure store
DO NOT ! including JSON/XML formatter of data, LLM based coding agents (is there a co-pilot sanctioned by Syensqo ?).
ALWAYS document Iflow sender and receivers
ALWAYS Iflow Description
ALWAYS give descriptive name to flow steps, including sender and receiver default system and internal integration processes (do not leave as default)-
example
should be 
As build with reference to MAPPING/FUNC SPEC/TECH OBJECT in SCPI
MUST use logging - messageLog.addCustomHeaderProperty("LABEL", "INFO like IDOC_NUM/MATNR/KUNNR");
When Authentication is available -
oAuth + api-key
When oAuth or basic auth isnt available -
ipwhitelist + api-key