Skip to main content

Table Import

As mentioned in the overview, the ASCII files and SQL tables have the same data structures. The difference is that fields are referenced by column order in ASCII files and by name in SQL. We will be referring to the SQL field names as convenience.

Please refer to the SQL and ASCII spec for more details and the Sample SQL Script for table structure.

Orders​

Orders have one required table and one optional table.

Order Items (orderin)​

The is where cutlists are imported. The required fields are:

  • order
  • material
  • pcode
  • quantity
  • length
  • bundle

With these fields, a simple machine can produce parts. Of course, this is often not enough. Some machines support punching standard or custom punch patterns. Other details such as stitching, hole counting, and other details are required for certain machines as well. Other fields are also used for printing (on the part and bundle tags) and for informing the machine operator about other details.

Order Headers (bundlein)​

This data is generally used to inform users and for printing. The same table can be used to import data at both the order header level and at the bundle level. The bundle field is used to indicate what level the record is for. If the bundle field is 0 (zero), the row is targeting the order header. If this data is not sent, a header record will still get created from orderin but it will only have the order, material, and pcode values set.

Punch Pattern (partin)​

Punch pattern details can be imported. This data is usually created by design software but can also be programmatically generated by an ERP. Punch Patterns are referenced by the Punch Pattern Name ("Part Name" in Eclipse Classic). An order line that needs punching specifies the Punch Pattern Name and Eclipse will send the pattern to the controller automatically.

Materials​

This is used for one-time import of new material detail (color, gauge, width, etc.). If it is not used, Eclipse can automatically create new Material records with empty details. Users can then manually add the details if desired.

Missing Material Details (Pro Only)​

When an order is imported with a new Material Code, Eclipse Pro can detect this and query a database for the missing details.

PCode (Product Codes, aka Tooling Codes)​

This is used for one-time import of Product related detail (finished width, assigned machine, etc.). If it is not used, Eclipse can automatically create the records but not assign them to a machine. A user will need to configure which machine is capable of producing the PCode.

Coils (coilin) * not recommended *​

Coils inventory can be imported into Eclipse as well. This is generally not recommended as other mechanisms are more appropriate. The issue with importing coils is that the external system is responsible for sending changes to coils as they happen, otherwise the inventory gets out of sync. If the external system is the holder of truth, it is better to either:

  • Don't store coil inventory in Eclipse and use a SQL view to query the source data when needed (coil validation)
  • Use the coil sync feature of Eclipse Pro to synchronize the external system coil inventory automatically.