TRTPREPA processing: Preparation plan
CRIT_SOQ Additional filter on the order files
Use this entry point to add an extra filter on the orders.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no log file.
Different call cases - Significant variables
This entry point is located in the SEARCH sub-program of the CALREO processing.
It is called right before the read of the order files.
It allows the description of a new filter, on the following files: SORDERQ SORDER SORDERC by means of the alphanumerical heading containing 250 characters: CRITSOQ made available.
The accessible parameters are:
- CRITSOQ (250) Filter on SORDERQ SORDER SORDERC
Open tables
In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…).
Table | Significant content | Table Title |
SORDERQ | No | Sales orders - quantities |
SORDER | No | Sales order - header |
SORDERC | No | Sales orders - A/R total |
BEFWRIPRH: Before writing the pick ticket header
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.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There can be an open log file according to the movement type (GTRACE test).
Different call cases
Systematic call.
Open tables
In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…).
Table | Significant content | Table Title |
STOPREW | Yes | Pick ticket work |
BEFWRIPRE: Before writing the pick ticket details
This entry point is called before the "Write" instruction for each new pick ticket line.
The STOPRED [PRE] table buffer is loaded and can be modified with the usual care.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There can be an open log file according to the movement type (GTRACE test).
Different call cases
Systematic call.
Open tables
In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…).
Table | Significant content | Table Title |
STOPREW | Yes | Pick ticket work |
ITMMASTER | Yes | Product |
SORDERQ | Yes if [F:PRW]ORITYP=1 or 2 | Order line |
STOREO | Yes if [F:PRW]=3 | Replenishable location |
ALIM_WDATA2: Adding grouping conditions for orders on a pick ticket
Use this entry point to take over before the write in the work file of each subcontract order, reorder or shortage line record to prepare. It is therefore used to add data that will be used as shortage criteria in the work file data ([F:PRW]WDATA2 field).
It is called in the TRTPREPA processing for automatic delivery.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is an open log file.
Different call cases
The entry point is called from the preparation plan, when clicking 'Generate pick ticket' each time a record is written in the STOPREW work file.
Available variables and masks
The PREPALN screen line with a I index is on line.
If [M:PREP]ORITYP(I)=1 or 2 (preparation of an order line), the corresponding records SOH, SOQ, SOC if [F:SOH]SOHCAT=4 or SOP and otherwise on line.
If [M:PREP]ORITYP(I)=3 (preparation of a sub-contract reorder), the corresponding record REO is on line.
If [M:PREP]ORITYP(I)=4 (preparation of a subcontract shortage), the corresponding record STA is on line.
To add shortage criteria, it is necessary to load the required information in the WDATA2 field.
e.g.: [F:PRW]WDATA2 += [F :SOH]xxx
Caution: The WDATA2 field is sized to 250 characters, which are all available if a subcontract reorder or shortage is being prepared.
When preparing an order line, this field already contains the following: 1st address line, postal code, city and state of the ship-to customers and invoice (all the spaces having been removed)
Open tables
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 file |
STOPRELIS | Yes | Preparation list |
SORDER | Yes if [M:PREP]ORITYP(I)=1 or 2 | Order headers |
SORDERQ | Yes if [M:PREP]ORITYP(I)=1 or 2 | Order line quantities |
SORDERP | Yes if [M:PREP]ORITYP(I)=1 or 2 and [F:SOH]SOHCAT<>4 | Order line prices |
SORDERC | Yes if [M:PREP]ORITYP(I)=1 or 2 et [F:SOH]SOHCAT=4 | Contract order by product |
STOREO | Yes if [M:PREP]ORITYP(I)=3 | Reorders |
STOALL | Yes if [M:PREP]ORITYP(I)=4 | Allocations |
|
|
|
CRE_PRE_SERNUM: Split of preparation lines if serial numbers in issue
This entry point is used to generate N preparation lines with a quantity of 1, based on the line of a preparation list that need to be prepared.
This entry point only applies when the preparation concerns a product with serial numbers managed in issue and if the allocated stock line is in packing unit with an 'shortage' issue mode.
It is called in the TRTPREPA processing
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is an open log file.
Different call cases
This entry point is called from the preparation plan when clicking 'Pick ticket' and from the preparation lists generation if 'Pick tickets generation' is selected.
It is called each time a STOPRED pick ticket line is written.
Operating mode
The product must be read with [F:PRW]ITMREF
If the product is managed with serial numbers in issue: [F:ITM]SERMGTCOD=2 and if the [F:PRW]PCU packing unit is set with a 'Shortage' issue mode. [F:ITM]PCU(n)=[F:PRW]PCU and [F:ITM]PCURUL(n)=2 then you must set variable GPE=1
ORD_PREP: Sort of lines to be prepared
This entry point is used to sort the table of lines to be prepared in the PREPLAN screen.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no log file.
Different call cases - Significant variables
This entry point is located in the SEARCH sub-program of the TRTPREPA processing.
It is called when clicking 'SEARCH' in the preparation plan after loading the lines to be picked that match the selection criteria.
It is used to sort the grid (block 7 row 40 of the PREPLAN screen)
CTRL_ITM Product data control on an order line
This entry point is used to control product data on an order line.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no log file.
Different call cases - Significant variables
This entry point is located in the SEARCH sub-program of the TRTPREPA processing
It is called during the reading loop on order lines and after the product reading
It can be used to reject the order line by testing order or product data.
The GPE variable must be set to 1
GPE = 1
Open tables
In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…).
Table | Significant content | Table Title |
SORDERQ | Yes | Sales orders - quantities |
SORDER | Yes | Sales orders - header |
ITMMASTER | Yes | Product |
AUTPRWSEL: Used to intervene on the pick tickets generation order
This entry point is used to take over the pick ticket generation order.
It is called in the TRTPREPA processing
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no log file.
Different call cases - Significant variables
This entry point is called in the preparation lists generation function:
It is used to define the reading order for the STOPREW/PRW work file.
The reading order defined in the EP can be considered if the GPE variable is set to 1.
GPE = 1
Open tables
In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…).
Table | Significant content | Table Title |
STOPREW | Yes | Preparation work file |
LIV_PRH: Use to prevent a pick ticket from becoming deliverable
This entry point is used to take control on the pick ticket header reading when clicking 'Deliverable' from the preparation plan.
It is used to make the ticket not deliverable.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no log file.
Different call cases - Significant variables
This entry point is called from the pick tickets workbench when clicking 'Deliverable'.
It is used to reject a pick ticket so that it cannot be delivered.
The GPE variable must be set to 1
GPE = 1
Open tables
In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…).
Table | Significant content | Table Title |
STOPREH | Yes | Pick ticket header |
ALI-SOQ-PREP
Use this entry point to take over after the loading of an order line in the preparation plan.
The loading can therefore be completed.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no log file.
Different call cases - Significant variables
This entry point is called from the pick ticket workbench when loading an order line.
It is therefore used to complete the loading of the order line into the PREPLAN [PREP] screen grid.
Open tables
In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…).
Table | Significant content | Table Title |
SORDERQ | Yes | Order line (quantity) |
SORDERP | Yes except open order | Order line (price) |
SORDERC | Yes if open order | Product line |
SORDER | Yes | Order header |