This entry point is called when using the 'Pick ticket' button from order management.
It is called just before the processing of an order line in order to modify the desired allocation type on the pick ticket.
There is one transaction in progress.
There is no open log file.
To modify the allocation type, it is necessary to intervene on the WALLTYPFLG local variable.
By default WALLTYPFLG = 2 (detailed allocation).
To force the global allocation, set: WALLTYPFLG = 1 (this will however have no effect if the order is already allocated in detail).
To comply with the order allocation type, set: WALLTYPFLG = [F:SOQ]ALLTYP
This entry point is called before the "Write" instruction for each new pick ticket header.
The STOPREH [PRH] table buffer is loaded and can be modified with the usual care.
There is one transaction in progress.
There can be an open log file according to the movement type (GTRACE test).
Different call cases
Systematic call.
In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded…).
Table | Significant content | Table Title |
SORDER | Yes | Sales orders - header |
This entry point is called before the "Write" instruction for each new pick ticket detail.
The STOPREH [PRE] table buffer is loaded and can be modified with the usual care.
There is one transaction in progress.
There can be an open log file according to the movement type (GTRACE test).
Different call cases
Systematic call.
In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded…).
Table | Significant content | Table Title |
SORDER | Yes | Sales orders - header |
SORDERQ | Yes | Sales order - details |
SORDERP | Yes | Sales order - price |