TRTPREPA process: 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 and significant variables
This entry point is located in the SEARCH sub-program of the CALREO process.
It is called directly before reading the order files.
Use this entry point to define a new filter that applies to the SORDERQ, SORDER, and SORDERC files.
The filter is defined using the CRITSOQ alphanumeric field, which is available for this purpose and can contain up to 250 characters.
The accessible parameter is:
- CRITSOQ (250), filter on SORDERQ SORDER SORDERC
Open tables
In the table below, the significant content column indicates if 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.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
Depending on the movement type, there can be an open log file, as identified during a GTRACE test.
Different call cases
This entry point is systematically called.
Open tables
In the table below, the significant content column indicates if 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.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
Depending on the movement type, there can be an open log file, as identified during a GTRACE test.
Different call cases
This entry point is systematically called.
Open tables
In the table below, the significant content column indicates if 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 intervene before the work file is written for each subcontract order, reorder, or shortage line to be prepared.
It is used to populate data in the work file that will be used as shortage criteria, stored in the [F:PRW]WDATA2 field.
It is called in this 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 selecting 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, you need to load the required information in the WDATA2 field.
Example
[F:PRW]WDATA2 += [F:SOH]xxx
Important
The WDATA2 field can contain up to 250 characters, which are all available if a subcontract reorder or shortage is being prepared.
When preparing an order line, this field is already populated with the first address line, the postal code, the city and state of the ship-to customers and invoice. All spaces are removed from this data.
Open tables
In the table below, the significant content column indicates if 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 and [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: Splitting preparation lines if serial numbers in issue
Use this entry point to generate N preparation lines, each with a quantity of 1, based on the line of a preparation list that needs to be prepared.
This entry point applies only when the preparation concerns a product with serial numbers managed in issue and when the allocated stock line is in packing unit with a Shortage issue mode.
It is called in this 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 selecting Pick ticket and from the preparation list 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 [F:ITM]SERMGTCOD=2 issue, 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 the GPE variable must be set to 1: GPE = 1.
ORD_PREP: Sorting lines to be prepared
Use this entry point 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 this processing.
It is called when selecting SEARCH in the preparation plan after loading the lines to be picked that match the selection criteria.
It is used to sort the grid located in the PREPLAN screen, block 7 row 40.
CTRL_ITM: Controlling product data on an order line
Use this entry point 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 this processing.
It is called within the order line reading loop, after the product is read.
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 column indicates if 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: Controlling the pick ticket generation order
Use this entry point to take over the pick ticket generation order.
It is called in this 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 list generation function.
It is used to define the reading order for the STOPREW/PRW work file.
The reading order defined in the entry point can be considered if the GPE variable is set to 1: GPE = 1.
Open tables
In the table below, the significant content column indicates if the content matches the context (the current customer is loaded…).
| Table | Significant content | Table title |
|
STOPREW |
Yes |
Preparation work file |
LIV_PRH: Preventing a pick ticket from becoming deliverable
Use this entry point to take control on the pick ticket header reading when selecting Deliverable from the preparation plan.
You can use it 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 selecting 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 column indicates if the content matches the context (the current customer is loaded…).
|
Table |
Significant content |
Table title |
|
STOPREH |
Yes |
Pick ticket header |
ALI-SOQ-PREP: Completing order line loading in the preparation plan
Use this entry point to take over after the loading of an order line in the preparation plan.
Then, the loading can 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.
Then, you can use it to complete the loading of the order line into the PREPLAN [PREP] screen grid.
Open tables
In the table below, the significant content column indicates if 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 |
AFTWRIPRH: After writing pick ticket header
This entry point is called after the Write instruction for each new pick ticket header.
Context and operating method
Transaction
There is one transaction in progress.
Log file
Depending on the movement type, there can be an open log file, as identified during a GTRACE test.
Code context
This entry point is called when a pick ticket is generated from the Generate preparation lists and Preparation plan functions.
Available variables and masks
The STOPREH [PRH] table buffer is loaded.
Open tables
| Table | Significant content | Table title |
| STOPREW | Yes | Pick ticket work |
| STOPREH | Yes | Pick ticket header |