Bulk Materials Ideas
Idea and discussion portal for the bulk materials product line. Users may submit, view and vote on ideas submitted by all users.
Idea and discussion portal for the bulk materials product line. Users may submit, view and vote on ideas submitted by all users.
It would be incredibly useful to set the OKStatus default in the same way other system settings work such as Ship/Receive and Buy/Sell/Transfer and Post Zero Price options. Where the hierarchy is followed: System, Location, Customer, Order, Dispatch, Ticket and so forth.
For instance, one customer should have all their tickets default to on HOLD, while all other tickets should follow the system default. And at ticketing, the scale operator won't need to set the tickets for the one customer as on HOLD every time.
Two examples - 3rd Party location tickets the dispatch creates a HOLD ticket with all ticket information except quantities. The 3rd Party location sends ticket data the following day and then Ticket Import Service updates the HOLD tickets and sets to OK. Another example is waiting to invoice all truck tickets associated with one barge at the same time. Accruing tickets are put on HOLD until the full barge has been ticketed.
The back office likes to keep any ticket that they don't want to process yet, in Scale. So putting it on HOLD keeps it in the scale tables. Then when they are ready to process, they take them off HOLD and transfer the tickets in. Since the Transfer Tickets In function goes by location, we cant restrict certain customers.
Logan, can you elaborate on why you are placing tickets for a particular customer on hold?