Scenario 7 – Import Routing

In this scenario of import routing, we will teach you the following:

• Import the routing data from the TSV file
• Import the process number, resource, setup time, production capacity etc.

Please open the file 25.09 Scenario 7 – Import Routing.

asprova1

This is the [Data I/O table].

asprova2

You will see the Routing in the 3rd row. Please click on the Field mapping to see the format of TSV file for “Routing”.

asprova3

This is the imported TSV file. In this file, you will see the following fields: final item code, process number, process code, instruction code, item/resource code, setup, production, and teardown.

asprova4

The Import field in the Data I/O table is “Yes (differential)”. The Import property conversion expression is “Instruction Type = U”. The letter “U” here denotes “Use instruction”.

asprova5

Now, let’s open the Integrated Master Editor. You will see that it is still blank.

asprova6

Let’s import by clicking the File tab, and then Import. As a result, the imported integrated master data is as shown below.

asprova7

Please go to the Resource Gantt chart and then press the Reschedule button.
The resource has been assigned, based on the imported “Routing”.

asprova8

To learn more about Asprova specific to this sample demonstration, you may visit Asprova’s online help and its e-Learning videos at http://lib.asprova.com/ (see 25. ERP Interface).

 

Scenario 6 – Import BOM and Material

In this scenario, we will show you how to import to Asprova the Manufacturing BOM and Items data.

We will use the file “25.08 Scenario 6 – Import BOM and Material”.

Asprova1

This is the Data I/O table.

Asprova2

The item code is connected with the Item name at the Material (Import).

Asprova3

This is the actual Material (import) file. It includes the item code and item name.

Asprova4

This is the data I/O setting for M-BOM. This is its TSV file. In this file, you will see its product code, process number, process code, instruction code, input item and the required quantity.

Asprova5

Confirm the settings for Material and BOM in Data I/O table by checking the parameter setup below.

Verify that the Import column is set as “Yes (differential)” and Import property conversion expression column is set as “Instruction Type = I”.

Asprova6

This means that the Instruction type will be automatically set as Input instruction as soon as you import the file.

Asprova7

This is the Item table. You will see that the Item name is blank at the beginning. The Item name will be imported from the TSV file.

Asprova8

This is the Integrated Master Editor. The Use instruction will be maintained in Asprova and the Input instruction will be imported from ERP.

Asprova9

Let’s start importing the TSV files.

Asprova10

Once completed, the item name will be displayed in the Item table and the Input instruction has been imported. See table below.

Asprova11

Asprova12

Go to the Resource Gantt chart and press the Reschedule button to see the scheduling according to the imported BOM and items data.

Asprova13

To learn more about Asprova specific to this sample demonstration, you may visit Asprova’s online help and its e-Learning videos at http://lib.asprova.com/ (see 25. ERP Interface).

 

Scenario 5 – Export Purchase Requisition

In this scenario, we will export the “Purchase requisition”:

  • We will figure out the required quantities of purchasing items and auto-replenish the manufacturing orders
  • We will schedule the time to place an order and the due date.
  • We will export to the external file the scheduled due dates and quantities of purchasing items.

We will start with the last state of Scenario 4.Using the purchase item “X”, switch the Auto-replenish flag to “Yes” in the Item table. Set “Prefer to purchase” as Obtain method and “10000” as Purchase lot size MIN/MAX.

Asprova1

Go to the Data I/O table and select the Field mapping of “Purchase requisition (Export)”.

Asprova2

This is the format of the TSV file for purchase requisition.

Asprova3

The due date is connected with the end time of the order.

Asprova4

Let’s export the due date as the end time.

Asprova5

Click on the Export filter expression to set the Export filter expression. Switch the Export to “Yes (all)” and set “Type==P” as [Export filter expression].

Asprova6

Switch to the Order table and run the Reschedule button.

Asprova7

 

You will then see that the purchase order has been auto-replenished with 10000 items of Item “X”.

Asprova8

Go to the Resource Gantt chart to check on the purchase order.

Asprova9

The lead time for purchasing is 24hours where the start time means the time to place an order and the end time means the due date. The due date for this purchase order is 10:40 on June 10th as stated in the box above.

Let’s export this. The file “25.07 Purchase Requisite (Export)” will be created and the data of the purchase order will be the output. It is the plan that will purchase 10000 items of “X” at 10:40 on June 10th.

Asprova10

To learn more about Asprova specific to this sample demonstration, you may visit Asprova’s online help and its e-Learning videos at http://lib.asprova.com/ (see 25. ERP Interface).

 

Scenario 4 – Export Production Orders

In this scenario, let’s export the production order including the start time and end time from Asprova. This can be done through ERP importing the TSV file for Production order and creating the purchase information by running MRP.

Let us open the Data I/O table from the final stage of the previous scenario (refer to Scenario 3 article) and confirm the Production order (Export).

Asprova1

Open the Field mapping dialog by clicking on the cell of the same name.

Asprova2

This is the format of TSV file for the production order.

Asprova3

Asprova4

Switch the Export field to “Yes (all)” and set “Type=M'” as Export filter expression.

Asprova5

Asprova6

Let’s export it. Go to the File tab and select Export.

Asprova7

The TSV file for this production order will be created and the auto-generated manufacturing order will be its output. You will also see when you open the TSV file that the orders already include the start time and the end time.

Asprova8

To learn more about Asprova specific to this sample demonstration, you may visit Asprova’s online help and its e-Learning videos at http://lib.asprova.com/ (see 25. ERP Interface).

 

Scenario 2- Use MRP and Finite Capacity Scheduling of Asprova

In this scenario, we will use MRP and Finite Capacity Scheduling of Asprova – how to import the manufacturing order for the production and inventory from TSV files and how to auto-replenish the manufacturing order for parts and schedules.

After importing the manufacturing order for the production and inventory of parts, the manufacturing order for “A” will be created automatically by MRP. It is important to input the manufacturing order for Item “A” from ERP. But first, we need to know the inventory of “A” in order to run the MRP.

Open the file “25.04 Scenario 2 – Use MRP and finite capacity scheduling of Asprova” as shown in the figure below.

asprova1

The table below shows the data settings for inventory of “A”.

Asprova2

The contents of the TSV file for planned order is the same as Scenario 1.
The order code is “Inventory 1”. The item code is “A”. The due date is June 3rd. The quantity is 1000.

Asprova3

Open the Order table and import the TSV file. The inventory order can be seen in the order table. The Order code is “Inventory 1” and the Order type is set as “Inventory (absolute)”.

Asprova4

The order type can be changed to “Inventory (absolute)” by Import property conversion expression in the Data I/O table.

Asprova5

You may refer to the Online Help if you want to know the details about expressions.

Asprova6

In the Item table, switch the Auto-replenish flag of “A” to “Yes”. Then, run the Reschedule button.

Asprova7

You will then see that a manufacturing order has been auto-created in the Order table. The order quantity for Item “A” is 5000.

Asprova8

Check the Resource Gantt chart to see the results. This Inventory order is seen in the chart below. 1000 items will be used in Order 2. The shortage of 2000 items will be supplied by an auto-replenished manufacturing order.

Asprova9

Go to the Inventory Graph – the inventory of Item “A” is displayed.

Asprova10

It is 1000 at first, and increases to 6000. Then 3000 items will be used and the quantity will be decreased to 3000.

Asprova11

Please refer to this page to find the details about auto-replenishment.

Asprova12

To learn more about Asprova specific to this sample demonstration, you may visit Asprova’s online help and its e-Learning videos at http://lib.asprova.com/ (see 25. ERP Interface).

 

Scenario 1 – Import planned orders and production orders

Before explaining Scenario 1, please ensure to watch first “21.01 Mixing – Packing – Inspection process” to study the basic function of Asprova.

In this scenario, Asprova will import planned order and production order from external files, and then schedule the imported manufacturing orders with finite capacity.

We will import order data from two TSV files.

asprova1

In the initial screen view of Asprova, open the file “25.03 Scenario 1 – Import planned orders and production orders”.

asprova2

Open the Data I/O settings from File.

asprova3

This is the data input and output setting table for Planned Order.

asprova4

The Internal table name is “Order”. The Data source is “Text file” where you can also choose OLEDB, which is connected with the database through a dropdown. The Folder Database is blank. The target file is the same as the project file. The External table name is “25.03 Planned Order (import).txt”. The Field and decimal is “Tab&Dot”.

Click the block on the right in Field mapping to see the link between Asprova and the external file.

asprova5

The left side is the Order table of Asprova where the properties for the order are placed. The right side is the TSV file where the fields are placed. Connect the properties on the right side with properties on the left side.

Order code, Item code, EST (Earliest start time), Due date, Order quantity, Reported quantity -this is the format for the TSV file. The format of time is “yyyy/mm/dd hh:mm:ss”.

This is the DBIO of Production Order.

In Asprova, planned order has the same meaning as production order.

Please refer to the online help if you want to know the details of DBIO.

Asprova6

The highlighted file below is the TSV file for planned order. The order code is 2. The item code is “AX”. The due date is June 11th and the order quantity is 3000.

Asprova7

The highlighted file below is the TSV file for production order. The order code is 1. The item code is “A”. The due date is June 7th and the order quantity is 5000.

Asprova8

In ERP, MRP, the due date of June 7th is considered as a 4-day-fixed lead time from June 11th. Select the Order table and import the TSV file.

Asprova9

Two Manufacturing order was added to the Order table.

Asprova10

Switch to the Resource Gantt chart and press the Reschedule button to get the scheduling result. In the Gantt chart, you will be able to see the schedule that produces 3000 items of “AX” and produces 5000 items of “A”.

Asprova11

To learn more about Asprova specific to this sample demonstration, you may visit Asprova’s online help and its e-Learning videos at http://lib.asprova.com/ (see 25. ERP Interface).

 

Relationship between ERP and Asprova

Asprova can be integrated with any ERP system. It is ready to be interfaced with SAP, Oracle EBS, JD Edwards, Dynamics AX, QAD and legacy systems.

Asprova1

The table below shows how Asprova is integrated with an ERP system – the data can be interchanged using Tab Separated Value (TSV) files.

Asprova2

There are several data tables in ERP, such as: Planned independent requirement, Customer requirement, Planned order, Production order or Process order, Purchase requisition, and Inventory. For master data, there are Material, BOM (input items and quantity), and Routing.

In Asprova, there are 3 corresponding data tables related to an ERP System – Order, Item, and M-BOM (Manufacturing Bill of Materials).

There are several types of orders, such as Sales, Manufacturing, Purchase and Inventory.

There are 2 types of instructions in M-BOM: Input and Use instructions. Input instruction includes input items and its quantities as it relates to an ERP system’s master data BOM. Use instruction includes usable resource and production capacity of each process as it relates to an ERP system’s master data Routing.

It is necessary to prepare the interface program for the ERP side.The typical interface program for SAP is BAPI interface. In Asprova, data import/export is implemented by the DBIO feature. Thus, in most cases, there is no need to develop the software from Asprova’s side.

To learn more about Asprova specific to this sample demonstration, you may visit Asprova’s online help and its e-Learning videos at http://lib.asprova.com/ (see 25. ERP Interface).