Use this entry point to take over before the write in the STOPRELISW work file of each subcontract order, reorder or shortage line record to prepare.
It is called in the FUNAUTPREP processing for the generation of preparation lists.
There is one transaction in progress.
There is an open log file.
The entry point is called from the generation of preparation lists function, for each write of a record in the STOPRELISW work file.
Depending on the value of the [L]WTYPTRT local variable, an order detail, sub-contractor location reorder or sub-contractor shortages record is on line.
If [L]WTYPTRT=1 (preparation of an order line), the corresponding records SOH, SOQ, SOC are on line if [F:SOH]SOHCAT=4. Otherwise, SOP is on line.
If [L]WTYPTRT=2 (preparation of a subcontract reorder), the corresponding record REO is on line.
If [L]WTYPTRT=4 (preparation of a subcontract shortage), the corresponding record STA is on line.
In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…). It is usually the case for the file containing the header, but not for the file containing the lines…
Table | Significant content | Table Title |
STOPRELISW | Yes | Preparation list work file |
SORDER | Yes if WTYPTRT=1 | Order headers |
SORDERQ | Yes if WTYPTRT=1 | Order line quantities |
SORDERP | Yes if WTYPTRT=1 and [F:SOH]SOHCAT<>4 | Order line prices |
SORDERC | Yes if WTYPTRT=1 and [F:SOH]SOHCAT=4 | Contract order by product |
STOREO | Yes if WTYPTRT=2 | Reorders |
STOALL | Yes if WTYPTRT=3 | Allocations |
|
|
|
Use this entry point to take over during the control of order lines to prepare.
It is used to add extra controls on these order lines.
It is called in the FUNAUTPREP processing for the generation of preparation lists.
There is no transaction in progress.
No log file is open when in the control phase for the order lines to prepare.
The entry point is called in the preparation list generation function upon the order lines control for the STOPRELISW work file generation.
To go to the next order line, set the GPE variable to 1.
In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…). It is usually the case for the file containing the header, but not for the file containing the lines…
Table | Significant content | Table Title |
SORDER | No | Order headers |
SORDERQ | No | Order line quantities |
SORDERP | No (if standard order) | Order line prices |
SORDERC | No (if contract order) | Product / customer orders (open orders) |
Use this entry point to take over following the generation of pick tickets.
It is used to intervene again on generated pick tickets.
It is called in the FUNAUTPREP processing for the generation of preparation lists when set up with generation of pick tickets.
There is no transaction in progress.
There is an open log file.
Call context
This entry point is called in the generation of preparation lists function after the generation of pick tickets.
The work file used for the generation of the pick tickets is available.
In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…). It is usually the case for the file containing the header, but not for the file containing the lines…
Table | Significant content | Table Title |
STOPREW | No | Pick ticket work |
STOPREH | No | Header pick ticket |
STOPRED | No | Detail pick ticket |
|
|
|
This entry point is used to take over the pick ticket generation order.
It is called in the FUNAUTPREP processing for the generation of preparation lists when set up with generation of pick tickets.
There is no transaction in progress.
There is an open log file.
Call context
This entry point is called in the generation of preparation lists function.
It is used to define the read order for the STOPREW/PRW work file.
To take into account the read order defined in the EP set the GPE variable to 1.
The work file used for the generation of the pick tickets is available.
In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…). It is usually the case for the file containing the header, but not for the file containing the lines…
Table | Significant content | Table Title |
STOPREW | Yes | Pick ticket work |
STOPREH | No | Header pick ticket |
STOPRED | No | Detail pick ticket |
|
|
|