Flexible integration into existing company processes and conscious expansion of existing strengths

• Dashboard for transferring, approving and tracking procurement processes

• Fully automated purchase requisition and order creation according to company specifications

• Cross-supplier order integration via an interface

• Based on existing internal guidelines

• Further processes such as integration of accounting, goods receipt and invoice reconciliation / credit note creation in the leading merchandise management system

Transparency and user-friendly interface with low training requirements

• Highuser acceptance through the use of a modern web application

• Users do not require any training in the merchandise management system

• Reporting / evaluations of all orders in the merchandise management system or in simple system possible

Fast implementation with minimal strain on the internal IT department

• Turnkey solution for the integration of SAP ERP® and SAP S/4HANA®

• Numerous successful projects with SAP SRM®, abas ERP, Infor CloudSuite™, Microsoft Dynamics NAV and AX, proALPHA ERP, PSIpenta ERP, various Sage ERP and other leading merchandise management systems‍

With the Cockpit Order variant, the customer logs in to simple system and places the items in the shopping cart. Sending the shopping cart triggers the order with the supplier and the order is created in the ERP system via the EDI interface at the same time. In this way, the entire process is automatically recorded directly in the ERP system and all data relating to the order is transferred to the ERP system. Any approval processes can be configured in simple system and releases are usually made via automatically generated e-mails. There is no need to log in to the platform. The company benefits from a reduced workload and retains data sovereignty over all order processes. With the cockpit workflow variant, the customer accesses the supplier's catalog via simple system and creates a shopping cart. However, if they send the shopping cart, the order is not triggered at the supplier - as with Cockpit Order - but only a purchase requisition is initially created in the ERP. For the approval process, the steps of the approval process applicable in the company are run through in the ERP. Only once this has been completed is the order transferred to the supplier via the e-procurement system and thus triggered. All these steps are automated - the workload is correspondingly low.

This depends on the type of connection. If approval processes, order number assignment and the triggering of the order are still to take place in the ERP, then the connection options OCI Punchout and Cockpit Workflow are suitable. If these functions are to be handled in simple system in the future, then Cockpit Order is the right integration for you.

Which connection is right for you depends largely on your purchasing strategy and your system landscape. The table above can serve as a guide. If you want to start the ordering process in your ERP environment, then only OCO-Punchout is suitable. If customers are to be able to order directly in simple system, then Cockpit Order or Cockpit Workflow are suitable. If approval processes and order number assignment are still to take place in the ERP, Cockpit Workflow is the right choice for you. If approval processes and order number assignment are to take place in simple system, Cockpit Order appears to be a good option.