Sage 100

 View Only
  • 1.  OK JobOps people. We have a customer that is ente

    Posted 03-23-2016 12:57
    OK JobOps people. We have a customer that is entering customer orders for MTO items. These customer orders need items created that can also be MTO. This can create order chains that are several levels deep. What our customer thinks they want is for their original customer sales order # to be easily available on the header(For ALE lookup) of every subsequent sub-order created by Component Exception Manager. There don't seem to be Job Ops objects to allow UDF pass-thru. I thought about possibly doing something with a script but don't think i'll have the info I need from the original order in the context of a new order being created by the CEM. Anybody attempt something like this before or am i just sounding like a crazy person?


  • 2.  RE: OK JobOps people. We have a customer that is ente

    Posted 03-23-2016 13:39
    The subassembly work tickets have a reference to the parent work ticket number, and on the parent work ticket there is a reference to the subassembly work ticket - ""Being made on . . . "" These references are only in the Work Tickets, but of course the initial 7 digits of the work ticket numbers are the sales order number. The WTMadeOnOrder number is in the sales order detail table and so is the WTParent number. Those are at the end of that table (as ""JT158_"" fields), so you may be able to access those for the sales order.


  • 3.  RE: OK JobOps people. We have a customer that is ente

    Posted 03-23-2016 13:45
    CEM (the Component Exception Manager); can only generate Work Tickets as Make to Stock. If the sub-assembly work ticket component is marked as ""Make to Order"" it will be designated for the higher level sales order (with a reference and a comment) back to the original sales order. The Customer MTO Work Ticket will include reference on the component to the new work ticket. I don't believe it can be written into an order header.


  • 4.  RE: OK JobOps people. We have a customer that is ente

    Posted 03-23-2016 14:00
    Thanks Madeline and John, I may have mis-stated slightly I believe the sub assembly work ticket items are all set to Make to Stock or purchase to Stock. The real issue is that when looking at those sub-assembly WT it's impossible to tell what they were created for. John I know the ""JT158 made on field"" but Its kind of backwards of what I need. IS there a Made FOR reference somewhere? I haven't found it.


  • 5.  RE: OK JobOps people. We have a customer that is ente

    Posted 03-23-2016 14:27
    The Step Extended Description on Step 000 should state what work ticket the sub assembly is being made FOR. JT_WorkTicketText.Text. Should read something like (2) 0001609-001-020 Referencing the original customer MTO Sales Order, Work Ticket and Step and the quantity being made for that work ticket.


  • 6.  RE: OK JobOps people. We have a customer that is ente

    Posted 03-23-2016 19:23
    Thanks Madeline. I'll check it out.