KoreSupport Logo

Welcome to KoreSupport's support center where you can submit support tickets and check on their progress.

Please use the links from the menu on the left to perform all your support needs.

HomeMTO ImporterPrinter Friendly Version

MTO Importer

Frequently Asked Questions for the Korecentric MTO Importer.

1. Introduction

1.1. Overview

Material Advantage clients usully generate a number of Drawings from either AutoCad and PDMS that they currently manually import into Material Advantage.

This takes time for a user to accomplish and can lead to delays in receiving the files.

The benefits of an automated system are that the client can export the files from the two packages to a folder, and have a service automatically pick the files up on a timer and import the data directly into the Material Advantage system.

A summary email would easily identify to key users what, if any, errors occurred during the import process.

1.2. Process Flow

MTO Importer Process Flow

1.3. Operational Flow

A profile should be configured for each import type and each project.

 

Each Project and import type should export to a different folder so that no manipulation of the file names needs to be accomplished.

 

The service should have a configuration option for the Poll time in minutes.

 

Once started the service should run without interruption. The service should be installed so that it is automatically started at system boot.

 

The service will poll a number of folders for new file creation.

 

  1. The Service will poll the profile defined directories and start the import routine for each file it finds.
  2. The service will use the data in tblImportSpecItem using a specified ImportSpecID for PDMS and a different one for CAD files. These settings should be configurable in the service in case they change in the future.
  3. The service will use the data in tblImportSpecItem to match MAColumn to ExColumn. Where ExColumn is null, the service should use DefaultValue column to populate. This is used when importing the data, to say that for column A in the File labelled as <ExColumn> it should be imported into MAColumn <MAColumn> in the staging table.
  4. The service will then call the following Stored Procedure:
    1. sp_ImportMTO_preProcess 2, <Profile Setting for MTO Type>, <Profile Setting for Material Catalogue
  5. The service will then check for errors by:
    1. Critical Errors by (Select Count(*) from tblImportWizErrorLog where XUserName=<UserName> And XWorkstation=<MachineName> And Severity=2)
    2. Warning Errors by (Select Count(*) from tblImportWizErrorLog where XUserName=<UserName> And XWorkstation=<MachineName> And Severity=1)
    3. Both Levels of Errors are deemed to be failures and the Second Posting should not be called
  6. If the error count is greater than 0 then an email should be generated to a Profile Email Address (or multiple using ; seperator). The email should state the drawing that failed to import, as well as listing out the warnings and critical errors.
  7. If the error count is 0 then the system should then call the following stored procedure
    1. sp_ImportMTO_UpdateLive
  8. If the Stored Procedure returns any errors then an email should be generated to a Profile Email Address (or multiple using ; seperator). The email should state the drawing that failed to import, as well as listing out the error returned by the server.
  9. The service should archive the file to an archived folder under the profile set directory and should append a timestamp to the end.
  10. The service should continue to process files as it finds them.

2. Frequently Asked Questions