btmlinesoft - not sure if you imported the transaction entry issue lines or not, but what is likely missing is the link between the work ticket and the issue line.

When you do the entries manually, in order to actually issue a qty against the line on the work ticket you need to select the row from the 'Original Item List' lookup ,which is the binoculars button above the grid to the left.  If the line is not chosen from this list, it will be considered a new material line for the work ticket.   (This is similar to what Work Order used to do as well)  What this does is populates the 'WorkTicketLineKey' from the LineKey of the PM_WorkTicketDetail table, forming the link that is needed for the update.   We are improving this behaviour in the 2023 release.

If you are importing the transaction entry material issue lines, you will need to populate the 'WorkTicketLineKey' from the PM_WorkTicketDetail line.

Hope this helps

Elliott

Elliot,

Thanks for the clarification.  Much appreciated.

I am pleased with the ability to import requirements from a CSV file feature.  Unfortunately, adding material transactions through the above method NOR creating a VI to import the data is intuitive or user friendly.  You are starting to set my expectations by mentioning improvement in 2023.  I hope I and others are not disappointed.  After all, it will soon be 2023, not the late 80's/early 90's when the base functionality was designed.

Jeff

btmlinesoft - Do you see the same results when entering materials manually on WT and using Transaction Entry to post a material issue?

We noticed after upgrading to 2022.1 with PM that after populating WT materials from templates and then using Transaction Entry to issue materials, we are faced with exact duplicate lines of the originals.  One shows required with 0 issue and the other is exact opposite.

We have reported this to our reseller to forward to SAGE and wondering if others are having the same issue.

**Edit

After looking through SAGE Knowledgebase, this is appears as an intended processing "feature" forcing the user to use the binoculars during manual entry.  This has created an issue using MFG100 from Scanco as our data flow now appears like a manual import with duplicated lines like above.  Submitted to Scanco Development to work on adding WorkTicketLineKey when processing entries back into SAGE for material issues on Work Tickets.

Unsure.  Have moved on from that (unfortunately).  Company is hiring a new cowboy to ride herd over their shop floor process.  Will give him some time to beak in the saddle.