How to Import Work Tickets into Operations Management using Visual Integrator in Sage 100?

Resolution

ALWAYS TEST VISUAL INTEGRATOR JOBS IN A BACKUP/TEST COMPANY BEFORE IMPORTING INTO LIVE COMPANY

Importing Work Tickets will use the SO_SalesOrderHeader table and will follow the same general rules with some additional requirements outlined below.

1. Import Table: SO_SalesOrderHeader Line or Item Based Work Tickets
2. Required Fields Parent Items:
   
   • JT158_WTClass = Valid Line or Item Based WT Class
   • JT158_WT Parent = Y
   • JT158_WTCreateFrom = M or T (M is manual WT creation, T is from Template)
   • JT158_WTCreateSource = A valid WT Template if CreateFrom = “T”
   • JT158_Part = N
3. Required Fields Component Items:
   
   • JT158_WT Parent = N
   • JT158_Part = Y
   • JT158_WTChargePart = Y or N
   • JT158_WTPrintPart = Y or N
   • Note: Assigning the JT158_WTCreateFrom field on a component item record will make it a parent item instead and create a work ticket.
4. DFLT Activity Code must exist
5. NEW Status Code must exist

Rules:

Parent line item must be added before components.

1. If the SO_SalesOrder_bus.Lines JT158_WTStep field is not populated, we assume Step “000”
2. If the SO_SalesOrder_bus.Lines JT158_WTStep specified does not yet exist, the Work Ticket Step record will automatically be created using an Activity Code of “DFLT” and a Status Code of “NEW”
3. The Step Description will be defaulted from the Activity Code’s description
4. User Defined Information fields on the step record will NOT be set.
5. If Work Ticket Class parameters do not allow steps, the part is assigned to Step 000
6. If the SO_SalesOrder_bus.Lines JT158_WTChargePart field is not set, we assign using the following hierarchy:
   • Setting from the Template part (if building from a Template)
   • The Default Parts to Chargeable part setting from the Work Ticket Class
7. If the L.WarehouseCode field is not set, we assign it using the value from the
   Sales Order Header or Item Masterfile (depending on the setup options).
8. If Capable to Promise is turned on, we assume “Yes” to the prompt for setting the Promise Date to the CTP Date (no prompt will be displayed to the user).
9. Order Based Work Tickets Creation Type (JT158_WTCreateFrom) can only be Manual
10. Required Fields:
    
    • JT158_WTClass = Valid Line or Item Based WT Class

Rules:

1. If L.JT158_WTStep field is not populated, we will assume Step “000”.
2. If the SO_SalesOrder_bus.Lines
3. JT158_WTStep specified does not yet exist, the Work Ticket Step record will automatically be created using an Activity Code of “DFLT” and a Status Code of “NEW”
4. The Step Description will be defaulted from the Activity Code’s description.
5. User Defined Information fields on the step record will NOT be set.
6. If Work Ticket Class parameters do not allow steps, the part is assigned to Step 000
7. If the L. JT158_WTChargePart field is not set, we will assign it using the Default Parts to Chargeable setting from the Work Ticket Class.
8. If the L.WarehouseCode field is not set, we assign it using the value from the
   Sales Order Header or Item Masterfile (depending on the setup options).
9. If Capable to Promise is turned on, we assume “Yes” to the prompt for setting the Promise Date to the CTP Date (no prompt will be displayed to the user).