WALLQTY = WREQQTY - ENT_CUMALLQTY
[M:MLIK]LIKQTY = WALLQTY
Endif
Return
In the table below, the significant content flag indicates that the content is in phase with the context (…).
Table | Significant content | Table Title |
MFGHEADTRK | Yes | Tracking header |
MFGITM | Yes | Released product tracking |
SORDER | Yes | Sales order |
SORDERQ | Yes | Sales order line |
In the creation and cancellation of production reporting on the back-to-back works orders, this entry point is used to insert additional logic in the sales order allocation management, in order, for example, to manage global allocations instead of detailed allocations.
There is one transaction in progress.
The MFGHEADTRK ([F :MTK], MFGITMTRK ([F :MKI]) , SORDER ([F :SOH]), and SORDERQ [F :SOQ] tables are loaded at the moment that the entry point is called.
Testing the value of the [M:MILK]MAJCOD variable(possible values "E" for receipt into stock and "S" for deletion) in order to identify the call context.
In production reporting ([M:MLIK]MAJCOD="E"), the work variables WALLQTY and WREQQTY are loaded respectively with the quantity remaining to be allocated for the order line and the quantity produced under this production tracking.
In production reporting cancellation ([M:MLIK]MAJCOD="S"), it is necessary to assign the SAV_WALLQTY variable with the de-allocated quantity * - 1 (de-allocation quantity as a negative).
In creation, SAV_WALLQTY is managed as standard.
On exiting the entry point, the GPE global variable should be set to 1 to inhibit the standard processing of creation or the cancellation of detailed allocations.
In the table below, the significant content flag indicates that the content is in phase with the context (…).
Table | Significant content | Table Title |
MFGHEADTRK | Yes | Tracking header |
MFGITM | Yes | Released product tracking |
SORDER | Yes | Sales order |
SORDERQ | Yes | Sales order line |