Seamless System Integration

If you have an existing system, you probably want to take advantage of that system and the data stored in it. Data that you want to keep in the existing system, you can input and maintain in the existing system, while inputting and maintaining in Asprova only the detailed data required only for scheduling. Furthermore, you can use differential data import and export to minimize the amount of data exchanged between Asprova and the existing system. Since only the data that changed is imported and exported, data is transmitted more quickly, enabling you to issue work instructions and quote delivery dates faster.

1. Data I/O Settings

You can define correspondences between internal objects (such as orders and items) and external RDB tables and CSV text files. N to N correspondence is possible.
Example: Input and output orders to and from multiple external tables.

Data I/O Settings

1-1. Import Filter Expression

You can specify a conditional expression to load only the necessary data when importing records.
Example: Load only the records whose valid flags are set.
Example: Load only the orders with due dates in this month.

1-2. Import Property Conversion Expression

You can specify an expression to convert values when importing records.
Example: Add ‘A’ to the beginning of each order code.
Example: Input today’s date in the comments field of each order.

1-3. Export Filter Expression

You can specify a conditional expression to filter the data you want to write when exporting records.
Example: Export only the orders with due dates in this month.
Example: Export only the orders that have been changed.

1-4. Export Property Conversion Expression

You can specify an expression to convert values when exporting records.
Example: Delete ‘A’ from the beginning of each order code.
Example: Clear the comments field of each order.

1-5. Record Merge Rule

When an internal object and external record having the same key (for example, the same order code) both exist, you can specify which one you want to prioritize.

Record Merge Rule

2. Field Mapping

You can define correspondences between internal properties and external fields. You can specify that only properties of interest be imported and exported.

Field Mapping between internal properties and external fields

2-1. Property Merge Rule

When internal and external values both exist, you can specify which value you want to prioritize. By specifying “External preferred” for fields maintained in the existing system and “Internal preferred” for other fields, you can take advantage of data in the existing system while inputting directly in Asprova data that the existing system lacks.

Property Merge Rule specify which value to prioritize


System Integration