In Sage 500, sales order lines can be allocated as soon as the line is added, without leaving the grid to save the entire thing. X3 7 requires me to hit Save or tap Enter, which saves and reloads the order and changes focus to the SO document number. You can tab through line-by-line, but that's not saving anything, and allocation only happens on save. So basically the sales orders function, from a data entry standpoint, is less efficient than it could be.
What would solve this (in my view) is if the lines could optionally be saved and allocated asynchronously as the user is tabbing through the grid, without leaving to hit Save or losing focus on the grid.
Maybe it's possible to do configure the system to do this somehow, or in Eclipse. (That won't be asynchronous, though.)
by: James G. | over a year ago | User Interface
Comments
That's excellent, it would also avoid lag (processing time) when creating order lines (including during EDI).
This being said:
1. You can disable immediate allocation and use Automatic Allocation through a batch job that runs periodically, to allocate orders in the background
2. You can actually develop a small customization that will order the batch server to allocate your lines as they are entered, in the background. It's quite easy using batch job tasks (file submission) and using the standard code that actually allocates the order in real time base from the Allocation Qty field.
@Stephane A: Ours was originally set up basically doing #1, and the problem was that the batch server wouldn't process the order allocations because the order was locked. So a sales rep could be working on an order for a long period of time and nothing would ever allocate. #2 would be possible if it there's a way to ignore that record lock and allocate without actually saving the lines first. (Unless saving was implied, but that's what triggers the automatic allocation.) Then if the lines aren't saved but are allocated, there would have to be a way to clean up those allocations in the case that the order isn't saved, otherwise there would be orphaned allocations.