Interfaces

In many cases, PlanTool is used in the toolmaking department. As a rule, an ERP system is then used for the production items that covers the entire company, especially in the business aspects. The work of the toolmaking department is then expense or inventory and must be evaluated accordingly and included in the reporting. Of course, there is a wide range of variants as to which data and how the data is exchanged. PlanTool contains standard output and import functions. These are the basis for creating connectors to the respective ERP system. The technical implementation varies depending on the update time requirements. Common intervals range from online, i.e. virtually in real time, to monthly data exchange.

SAP
with Web-Services

“Web-Services” are among SAP's preferred connection options for other systems. When a production order is released, the interface becomes active without operator intervention and transfers the order data to PlanTool. PlanTool checks the data and carries out the import. If the user opens the order mask in PlanTool after the release in SAP, the order is available there. The process also runs completely in the background the other way round. An employee books working time in PlanTime. By triggering the save in PlanTime, the data record is transferred to SAP, checked and accepted. The booking is immediately listed in the corresponding cost report in SAP. If SAP does not accept the booking (e.g. technical confirmation), the employee receives the original SAP message and the booking is not saved in PlanTool either. If a suitable web service module is available, it can be used. If not, it is created via pro-PlanTool and made available as a transport request in a separate namespace.

SAP
with RFC

RFC modules expose SAP transactions for external calls via the .Net connector. This form of connection is also an official SAP connection type. Technically, it is a synchronous connection. Both online and cyclical data exchange is possible. For example, PlanTool retrieves order data from SAP at night. However, the retrieval can also be started by the operator via the PlanTool menu if new data is required spontaneously. Conversely, the process runs completely in the background. An employee books working time in PlanTime. By triggering the save function in PlanTime, the data record is transferred to SAP, checked and accepted. The booking is immediately listed in the corresponding cost report in SAP. If SAP does not accept the booking (e.g. technical confirmation), the employee receives the original SAP message and the booking is not saved in PlanTool either. If a suitable RFC module is available, it can be used. If not, it is created via pro-PlanTool and made available as a transport request in a separate namespace.

NAVISION

This requires the involvement of your Navision partner. The exchange runs from SQL server to SQL server via transfer tables. We organize the retrieval and processing of data from Navision and the provision of data for Navision. Your partner organizes these processes in Navision. We have connected the following in this way: quotation data, order data, order hierarchies, order data, confirmations, outgoing and incoming invoices.

Radix, proALPHA,
AS-400 and others

Depending on the customer's situation and requirements, data exchange was implemented using various technical methods. Data exchange via tables, web service, text files.

pro-PlanTool GmbH & Co. KG

contact Impressum
Data protection

Our consultants:
Fon: +49 (0) 5731 49 585 0

Bad Oeynhausen
Zachenberg
Hongkong