Short description:

Analysis of existing Seeburg BIS 5/6 systems and detailed cost estimate for the migration to SAP PO 7.5. Configuration, documentation and testing of the scenarios considering existing development guidelines and naming conventions of the customer. Use of the B2B integration cockpit for EDI scenarios.

Supplement:

The new scenarios are based on a SAP PO 7.5 single stack java system (SAP Process Orchestration / Advanced Adapter Engine AEX). Only internal systems / applications are maintained in the System Landscape Directory (SLD). External systems (hosted by the partner / customer) are created as business components or party / business components in the integration directory. A two-component model is used in the Enterprise Service Repository (ESR); interface objects are created separately from sender and receiver. Sender objects are in the sender component and receiver objects are in the receiver component. Mappings (operational and message / XSLT) are created in the receiver component. The technical configuration of the interfaces done in the Integration Directory (ID). All objects (systems, channels, etc.) for an interface scenario are bundled in a configuration scenario. Communication adapters (Communication Channel) are also configured in the ID.

Technical description:

All Seeburger BIS 5/6 interfaces to partners are migrated to SAP PO 7.5 in order to guarantee a uniform system landscape. License costs for Seeburger products are saved. The interfaces are maintained and monitored centrally by customer service team.