Reasons Why The Manufacturing Order Schedule Interface May Fail When Importing from Preactor

TechKnowledge Content


Why does my Import back into eEnterprise from Preactor fail using the Manufacturing Order Schedule Interface?


Here are some items to check for if your Import fails:

1. The number of Manufacturing Orders that you Export must match the number being Imported back. For example it you Exported five Manufacturing Orders five must be Imported back or the Import will fail.

2. If you open your OrdersOut.csv file to see what Manufacturing Orders are being Imported back. Make sure to say no to the message would you like re-format this file.

The reason being for example you have a routing seq 001 it could reformat it to be 1. This can cause potential problems as the data will not match that of eEnterprise.

3. If you receive the error message: [Microsoft][ODBC SQL Server Driver][SQL Server]The specified @name (‘OrdersInExportJob’) already exists.[Microsoft][ODBC SQL Server Driver][SQL Server] The specified @step_name (‘executepkg’) already exists.[Microsoft][ODBC SQL Server Driver][SQL Server]' occurs when exporting the Manufacturing Order Schedule Interface.

The error is created when a schedule was already exported out of eEnterprise and not imported back in. The job(schedule) if exported in error can be deleted. It is located in the SQL Server Agent under Jobs. The name of the job is OrdersInExportJob.

4. Error SQLServerAgent is not currently running so it cannot be notified of this action.

The SQL Server Agent has to started. It is found in SQL Enterprise Manager under the SQL Server Group node, then the server node, and then the Management node. Right click on SQL Server Agent and click on Start Option.

5. If the User who is will be importing and exporting information from the Manufacturing Order Schedule Interface is not a Manufacturing system user. You must either give additional privileges to the user or change the SQL Server Agent properties.

6. All information in the package that you are Exporting to must match those of Manufacturing eEnterprise. You must use the same work center information: the number of employees and machines in work centers, the number of hours each work center is available and the percentage a work center can be overloaded.

If you import back different a work center that does not exist in Manufacturing eEnterprise you have potential issues. So it is important if you change something in your scheduler make sure to update eEnterprise first before importing back.

7. To use the integration, you must create a directory that is shared. The users doing the import\exports must have full permissions on this folder. It can not be Read only.

This article was TechKnowledge Document ID:28803