I am working on importing into Work Ticket Header in Sage 100 version 2020 Premium working with Production Management. I am trying to create the same action that occurs in the user interface of Work Ticket Entry in Production Management. In the UI of Work Ticket Entry, I can select the following: Next Work Ticket No Make for: Sales Order Select the Sales Order and Sales Order Line (which selects the WT Item Code) Select the Copy From button Copy from the item’s Bill of Materials The Steps tab auto populates from the bill of materials and so does the Materials tab. In my import job, I am not able to create the same logic that will auto populate the steps and materials by only importing select header records. I receive a failed result with an error “Missing Steps.” None of the fields being imported show as failed, but I’m missing something. Here is my job. Has anyone been able to do this? Am I missing another field that will trigger the “Copy From” logic? Or do I need to rearrange the field order in the import job?

Work Ticket Entry – Import using Visual Integrator

Posted By Luke Pribbenow over 5 years ago

I am working on importing into Work Ticket Header in Sage 100 version 2020 Premium working with Production Management. I am trying to create the same action that occurs in the user interface of Work Ticket Entry in Production Management. In the UI of Work Ticket Entry, I can select the following:

Next Work Ticket No
Make for: Sales Order
- Select the Sales Order and Sales Order Line (which selects the WT Item Code)
Select the Copy From button
- Copy from the item’s Bill of Materials

The Steps tab auto populates from the bill of materials and so does the Materials tab.

In my import job, I am not able to create the same logic that will auto populate the steps and materials by only importing select header records. I receive a failed result with an error “Missing Steps.” None of the fields being imported show as failed, but I’m missing something. Here is my job. Has anyone been able to do this? Am I missing another field that will trigger the “Copy From” logic? Or do I need to rearrange the field order in the import job?

Parents

0 Kentaro over 1 year ago
Sorry, i don't have a good answer for you but I think the culprit is how (at least) the version of your PM brings in or validate the steps data, and I don't believe it's possible to create a ticket through VI. Something in the background is checking for a step number that's not available through VI.

Here are my rationale.

Sage allows a work ticket to be created with just the Header and Work Ticket Step data without line entries through the Work Ticket Entry task. So i did 2 tests.

Tried to create a ticket by assigning Header and Steps info without the line info

Tried to add material line info to an existing ticket that already has valid Header and Steps info.

Both ended up with the same or a similar error message about missing step number. The former would not write the steps info, as if the steps info in the source file doesn't exist or it's instructed to ignore. The latter returns "Record Invalid or Write Failed. The Step Number is required".

To import/create the line record into an existing ticket, per the specs, I supplied StepLineKey ItemType, and ItemCode. By passing the required StepLineKey, it should provide the corresponding Step Number after it's validated. In addition, there is no Step Number field for the line record so I cannot supply it. Supplying WT.StepNumber with the value that corresponds to the StepLineKey has no impact. So i can only conclude that the underlying design is most likely checking for a step number that's made available by a mechanism only when creating a ticket through GUI.

This might be different for the current Sage version. But at least for the Scanco version, this seems to be the case.

I hope other people who have more experience would share their thoughts.

I have not tried BOI but something tells me it could result in the same error.

Ken
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Kentaro over 1 year ago
Sorry, i don't have a good answer for you but I think the culprit is how (at least) the version of your PM brings in or validate the steps data, and I don't believe it's possible to create a ticket through VI. Something in the background is checking for a step number that's not available through VI.

Here are my rationale.

Sage allows a work ticket to be created with just the Header and Work Ticket Step data without line entries through the Work Ticket Entry task. So i did 2 tests.

Tried to create a ticket by assigning Header and Steps info without the line info

Tried to add material line info to an existing ticket that already has valid Header and Steps info.

Both ended up with the same or a similar error message about missing step number. The former would not write the steps info, as if the steps info in the source file doesn't exist or it's instructed to ignore. The latter returns "Record Invalid or Write Failed. The Step Number is required".

To import/create the line record into an existing ticket, per the specs, I supplied StepLineKey ItemType, and ItemCode. By passing the required StepLineKey, it should provide the corresponding Step Number after it's validated. In addition, there is no Step Number field for the line record so I cannot supply it. Supplying WT.StepNumber with the value that corresponds to the StepLineKey has no impact. So i can only conclude that the underlying design is most likely checking for a step number that's made available by a mechanism only when creating a ticket through GUI.

This might be different for the current Sage version. But at least for the Scanco version, this seems to be the case.

I hope other people who have more experience would share their thoughts.

I have not tried BOI but something tells me it could result in the same error.

Ken
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data

Sage 100

Work Ticket Entry – Import using Visual Integrator

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING