All interfaces to and from non-SAP systems and services providers run via the central middleware solution.
a) KPS’s challenge was to provide a central enterprise application integration (EAI) solution as part of introducing a fulfillment template based on SAP software.
b) It should focus strongly on reusability and the rapid implementation of client-specific requirements for the template.
Use of SAP PO 7.4
a) All interfaces to and from non-SAP systems and services providers run via the central middleware solution.
b) Introduction of a “global data type” (GDT) to ensure that conversions between “GDT” and “SAP format” are implemented in the same way for all clients and can therefore be provided consistently in the template. Client onboardings can be reduced to conversions between “customer format” and “GDT” – and with considerably less effort.
a) One central location for receiving messages throughout the SAP system environment. Thus significantly reduced operating expenses for monitoring and so on.
One central location and standardized technology for converting data throughout the SAP system environment.
b) Possibilities for much quicker onboarding of additional fulfillment clients, each of which involves less effort. Avoidance of SAP terminology and specific features during client discussions. For example, instead of discussing IDoc field names, constant field content, and segments, participants can concentrate on the content of fields with descriptive field names.
When the template was introduced, the customer learned the methods and techniques for implementing further onboarding interfaces himself, which he successfully put into practice over the following years.