Incoplan Interface

1. Introduction

Incoplan is a add-on software to any ERP system. Hence it is absolutely necessary to exchange the data from the ERP database to the Incotec’s database to avoid any duplicate data entry. It is also interesting to observe that the material flow through the organization is govern and controlled mainly by manufacturing activities. Naturally, when a function is a central activity with lot of surrounding factors, it is obvious to have deviations, critical decision points and inter-dependencies. This leads to specific data requirement for Incoplan which may not be available in ERP but may be available in some electronic form like Excel sheets, CSV files or Flat files. To avoid re-entry of the data in electronic form, Incoplan has its own interface called as IncoInteface. This Interface takes care of data exchange from ERP to Incoplan.

2. How Data transfer happens

As the database of ERP can be different than database of Incoplan we need to extract the data from ERP to Incoplan Database.


Both way exchange of data is possible. It means the interface can extract the data from the client ERP and insert the same in Incoplan database as well as it can post back the data to theb client ERP database. Interface acts as an independent entity controlling data traffic.

2.1. Ways of Data Transfer

Various possibilities of data transfer can be

i. Direct connection to ERP database by Interface
ii. Creating view tables in ERP database and accessing this data by Interface.
iii. Using flat files, CSV, XML files generated by ERP system as input to Interface.
iv. Using standard data connection methods of ERP system.
v. Other

3. Data transfer frequency

The data transfer can be automatic as well as manual. In case of manual data transfer, it is very much in control of the user to define the way of transferring the data. This method is very useful at the start of the implementation as it gives control over the actual data transfer. After some days of implementation the data transfer can shift to automatic mode. But it is very much required that the user should go through the log files generated by the interface.
Depending upon the volume of data to be transferred and the frequency of data updation on the shop floor, the frequency of data transfer from ERP to Incoplan is decided.
The data transferred is normally divided into different modes such as Static and Dynamic. Every mode has its own function. Based on this function data transfer frequency can be decided.


3.1. Static Data

The data such as parts, Bill of Material [BOM], Resource information, routings, which are not subjected to frequent daily changes is called as a static data. This data transfer normally takes more time. Frequency of updation of this data can be daily. This mode can be automatically activated on the timings specified.

3.2. Dynamic Data

The data such as sales order, production order, stock, etc which happens on daily basis is called as a dynamic data. This data transfer normally takes little time. Dynamic data can be updated after the updation of production data. In normal scenario production data is updated once after the shift. Hence the frequency of updation of dynamic data can be after every 8 hours.

Capturing progress of the production is also a vital data transfer activity. We call it as progress updation. Based on the customer requirement this activity can be almost in the form of online data transfer.

4. Data Required for Incoplan

Incoplan fetches data from ERP and stores the same in Incoplan Database. Based on various Incoplan modules following data are required.

Parts
Domain, Family, Sub-Family of Parts
Unit of Measure
Resource details
Bill of Material [BOM]
Routing including part requirement
Sales order [In case of Work Order Generator]
Production orders [After successful MRP run]
Stock


5. ERP – Is type of ERP a limitation for Interface to fetch data.

Incoplan’s interface can get the data from any ERP. There is no limitation on the same. The only requirement is that a data connection to ERP database should be made available. In some cases it is not possible to provide the data connection then in that case, ERP should provide the data in the form of csv or xml files.

Interface has also a capability to fetch data from Excel files. So if you have some data available in such format then Interface can fetch such data.

6. Role of Client in Interface design

Client plays important role in interface design. He has to share the information and the method in which they understand the information. It is very crucial for Incoplan to understand this so as to make it a seamless integration with the ERP. Client is also required to provide data which is required for Incoplan. The data requirement is already explained above. Client should give legitimate access to the ERP data and the data which is available in some other electronic format.

7. Interface

Some screen shots explaining the functionality of Interface are given below.



Interface is currently fetching data from ERP database and the progress of various import tasks are shown on interface screen.


It is possible to make various settings in the setting tab. You can select the path/method of source ERP data and also Incoplan destination data. Also it is possible to define a sequence in which you want to import tables/files from the source data.


Data error log is generated. This error log helps to correct the existing records from ERP as well as records the start time end time of interface.