Process SUBPPI: SUBPPI
PECFILTSUP: Additional filter in requirement selection
This entry point is located in the SUBPPI and SUBPPI2 processes selects the requirements in purchase requests, orders or delivery requests creation, generating a "PECFILTSUP" action.
The goal of this action is to give the possibility to set additional filters on the requirements to be processed.
Context and operating method
Transaction
There is no transaction in progress.
Log file
There is no open log file.
Different call cases
The call is made before the requirements selection processing after having entered the picking header elements.
Available variables and masks
The following variables are loaded at the time of the call to the "PECFILTSUP" action.
TYPFILT
Filter type :
- 1 = Filter on the purchase request line table PREQUISD [PSD]
- 2 = Filter on the on-hand order file ORDERS [ORD]
CRITERIA
Standard filter set on the PREQUISD or ORDERS table
CRITLNK
Standard filter set on the "Link" necessary for the search in the requirements
The variables given above must not be modified.
The following variables must be modified in order to influence the processing of the requirement selection.
CRITSUP
Additional filter on the PREQUISD table if TYPFILT=1 or ORDERS table if TYPFILT=2. The maximum length of the filter is 240 characters. If the filter is empty there will be no additional filter.
CRITLNK2
Additional filter on the ITMFACILIT table if TYPFILT=2. The maximum length of the filter is 240 characters. If the filter is empty there will be no additional filter.
Note: If the "Filter by buyer" parameter BUYFLT is set to 2 (Yes) the following filter will be automatically generated on the ITMFACILIT table: [F:ITF]BUY=[M:PPI2]ORDBUY or [F:ITF]BUY=""
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (in this precise case there is none).
Table |
Significant content |
Table Title |
PREQUISD |
Purchase request lines |
|
ORDERS |
Pending movements |
Miscellaneous remarks
If the additional filter is not correct, an information box will be displayed then this filter will be ignored.
PECBESOINS: Modification of the quantities to be considered
This entry point is located in the SUBPPI and SUBPPI2 processes selects the requirements in purchase requests, orders or delivery requests creation, generating a "PECBESOINS" action.
The goal of this action is to give the possibility of modifying the requirement quantity to be selected.
Context and operating method
Transaction
There is no transaction in progress.
Log file
There is no open log file.
Different call cases
The call is made for each requirement line found during the creation of a purchase request line, purchase order line or shipment request linked to an open purchase order contract.
Available variables and masks
The following variables are loaded at the time of the call to the "PECBESOINS" action.
TRAIT
Requirement loading type:
- 1 = From the purchase request line table PREQUISD [PSD]
- 2 = From the on-hand order file ORDERS [ORD]
ABREV
Screen mask abbreviation used ("PPI1" or "PPI2")
The [M:PPIx] screen mask is usable, the I variable indicates the grid line currently being loaded.
[M:PPIx]CODE
Process code:
- 1 = Selection of the "POS"
- 2 = Selection of the "POP"
- 3 = Selection of the "POS" and the "POP"
- 4 = Selection of the "SCF"
- 5 = Selection of the "POS" and the "POP" other than the purchase requests
- 6 = Purchase request selection
- 7 = Selection of the "TRS" and the "TRP"
The following file classes are loaded: [F:PSD] if TRAIT=1 or [F:ORD] if TRAIT=2
The variables and classes given above must not be modified.
The following variable must be modified in order to influence the processing of the requirement selection.
RMNQTY
Requirement quantity to be selected expressed in stock units.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (the current purchase request line is loaded...etc).
Table |
Significant content |
Table Title |
PREQUISD |
Yes if TRAIT=1 |
Purchase request lines |
ORDERS |
Yes if TRAIT=2 |
Pending movements |
Miscellaneous remarks
A null or negative value for RMNQTY has the meaning "no selection", the requirement line will not be loaded in the grid.