The right integration for your system
completely tailored to your individual requirements.
Choose from a range of options, including a seamless transition to your ERP platform via the simple system OCI/Punch Out to optimize your order processing. You can between “Cockpit Order” directly on the platform or “Cockpit Workflow” select for processing in your ERP. Our flexible integration fits seamlessly into your existing business processes and builds specifically on your strengths while taking into account your internal guidelines.
Discover the wide range of options
SAP integration
Through a connection with our SAP Cockpit®, all order data can be transferred directly from the simple system platform to your SAP system.
Fast | Standardized | Safe
SAP Cockpit® range of functions
- Flexible integration into existing business processes and conscious expansion of existing strengths
- Transparency and user-friendly interface with little need for training
- Quick implementation with minimal stress on the internal IT department
- Turnkey solution for SAP ERP® and SAP S/4HANA® integration
- Cross-vendor order integration via an interface
- Fully automated order request or order system according to company specifications
- and much more...
Your purchase. Your processes.
You define how to integrate simple system into your system landscape.
Your Strategy | Your Format | Your transmission path
Three options for ERP integration
Trigger shopping and ordering in simple system
Orders are placed, approved and transferred to the supplier in a simple system. The ERP system is carried out in parallel. The cockpit is more than just an interface: It can be configured as required how and with which parameters placed orders are enriched and created in the ERP.
Your process | Your configuration | Your parameters
Shop in simple system — trigger an order in ERP
The customer directly accesses the vendor's catalogues and price lists via a simple system. If he submits the shopping cart, a purchase request is created in the ERP, where approval also takes place. The order is then transferred to the supplier via a simple system.
Your vendors | Your catalogue | Your approval process
Start in ERP, buy in simple system, trigger an order in ERP
Define vendor numbers for vendors and define a standard vendor number. This eliminates the annoying task of assigning invoices to creditors from your ERP/SRM.
Easy | Secure | Structured
FAQ
The price depends on the complexity of the connection. We would be happy to discuss a solution suitable for your system landscape and purchasing strategy with you in a personal conversation.
Which connection is right for you depends largely on your purchasing strategy and your system landscape. The table shown above can be used as a guide. If you want to start the ordering process in your ERP environment, then OCO PunchOut is the only option. If customers should be able to order directly in a simple system, Cockpit Order or Cockpit Workflow are suitable. If approval processes and order number assignment should continue to take place in ERP, Cockpit Workflow is suitable for you. If approval processes and order number assignment are to be carried out in a simple system, Cockpit Order appears to be a good option.
It depends on the type of connection. If approval processes, order number assignment and order activation are to continue to take place in ERP, then the OCI Punchout and Cockpit Workflow connection options come into question. If these functions are to be handled in a simple system in the future, Cockpit Order is a suitable integration for you.
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, in parallel, the order is created via the EDI interface in the ERP system. In this way, the entire process is automatically recorded directly in the ERP system and all data associated with the order is transferred to the ERP system. Any approval processes can be configured in a simple system; approvals are usually carried out via automatically generated emails. It is not necessary to log in to the platform. The company benefits from reduced workload and maintains data sovereignty over all order processes.
In the Cockpit workflow variant, the customer accesses the supplier's catalog via a simple system and creates a shopping cart. If he submits the shopping cart, the order is not triggered with the supplier — as with Cockpit Order — but only a purchase request is initially created in the ERP. For the approval process, the steps of the approval process that apply in the company are carried out in the ERP. Only when this is completed is the order transferred to the supplier via the e-procurement system and thus triggered. All of these steps are automated — the workload is therefore low.
A wide range of ERP/SRM systems are supported, including SAP ERP, SAP S/4 Hana, SAP SRM, sage 100cloud, sage b7, sage Business Cloud, infor CloudSuite, proALPHA, ABAS, Microsoft Dynamics 365, Microsoft Dynamics AX, PSI. Contact us with your ERP system and we will tell you which connection options to simple system are possible.