Requests
Use this function to manage the customization setups on the purchase request entry screens.
A standard purchase request entry transaction is initialized when installing the software.
You can:
- Modify it
- Delete it
- Create a new one
You can set up several transactions for the purchase requests. Each transaction, identified by a code and a text description, is displayed in a selection window when opening the Purchase request function.
Prerequisite
Refer to documentation Implementation
Screen management
Header
Use the transaction header to:
- create new transaction codes,
- search for existing transactions to modify or delete.
Purchase request transaction
Transaction (field PTRNUM) |
Code used to identify the transaction set up. The setup of the entry transactions enables the user to fully set up the entry screens associated with a document (quote, invoice order, request for quotes etc.) or with a stock transaction type (receipt, issue etc.). For each document or stock transaction type, it is possible to define as many entry transactions as necessary, each one being identified by a code. Each transaction is used to define, both for fields located on the document header and fields entered in the lines, whether they must be:
Upon validation of this setup, dedicated entry screens are created, and then can be used by any user having been granted rights on the access code defined on this setup header.
|
Description (field DESAXX) |
Transaction description. |
Active (field ENAFLG) |
Use this field to activate or deactivate a transaction. |
Access code (field ACSCOD) |
This access code is used to restrict access to data by user or group of users. |
Group (field GFY) |
Tab Page 1
Use this tab to define different elements such as:
- The automatic printing of the purchase request note
- The type of quantity you want to enter
- The display of particular fields, the activation of particular actions
Purchase request form
Document (field DOCNAM) |
If the associated document check box is selected, enter the report code for the standard printed document. |
Auto print (field DOCFLG) |
Select this check box to automatically launch the printing of the document on entry completion. The automatic printing only takes place in creation mode. |
Line account entry
Input (field LEDTYPSCR) |
Grid Line accounts
Ledger type (field LEDTYPINT) |
This field specifies the ledger type(s) associated with the transaction. |
Method (field LEDTYPCOD) |
This field is used to specify whether the selected ledger type must be 'Invisible', 'To be entered' or 'Displayed'in the line accounts. |
Buttons
RFQs (field QRQBUT) |
Use this field to specify if this action must be activated or not in the screen generated from the setup of the entry transaction. |
Close (field CLEBUT) |
Use this field to specify if this action must be activated or not in the screen generated from the setup of the entry transaction. |
Order (field GENBUT) |
Use this field to specify if this action must be activated or not in the screen generated from the setup of the entry transaction. This action converts a purchase request into an order. |
Product lines grid
No. of fixed columns (field NBRCOL) |
The first N columns specified in this field remain visible on the screen when scrolling. |
Display
Project (field PJTHCOD) |
This parameter is used to define, for this entry transaction, whether the Project number must be:
|
Line amount - tax (field LINAMTFLG) |
Parameter that is used to define, for this entry transaction, if the ex-tax amount of an order, receipt or return line must be displayed or not. This information may prove useful when displaying, or modifying, an order, receipt or return. |
field LINAMTSCR |
Specify, for this entry transaction, if the field must be present in:
|
Closed (field CLEFLG) |
Parameter used to decide if the close indicator value must be displayed or not on the screen. This information must be used in display or in the modification of a line. |
field CLESCR |
Specify, for this entry transaction, if the field must be present in:
|
Signed (field APPFLG) |
Action - Four possible choices :
|
field APPSCR |
Specify, for this entry transaction, if the field must be present in:
|
Tab Page 2
Use this section to define the management method of specific headings within your entry screen, by deciding if these headings will be:
- Hidden: the field is not shown on the screen, but it can be initialized with default values, according to other parameters that control its update.
- Displayed: the field is displayed, but it cannot be accessed in entry mode. If parameters control the update of the heading, the default value is displayed but you cannot modify it.
- Entry: the field is shown on the screen and can be accessed in entry mode. Its value can be initialized with a modifiable default value.
Note on quantity management
Multiple units are available for the entry of your purchase requests (product Stock unit, Purchase unit and any other unit from the Units table).
The user must absolutely select the Entry mode for at least one of the proposed quantities. Regardless of your choice, the quantity in stock unit is always stored in the file (irrespective of whether it is entered or calculated from the purchase unit).
If you chose to enter the quantity in purchase unit without changing the unit, the displayed unit (not modifiable) is the one associated with the product.
If you want to change units at will upon entry, chose the entry in purchase unit with unit change. In that case, the quantity in stock unit is systematically calculated using the conversion coefficient between the chosen unit and the stock unit, if such a coefficient exists, or using value 1 otherwise.
Entry
Translated description (field ITMDESCOD) |
Parameter used to define, for this entry transaction, if the product description translated in the operator's language must be:
|
field ITMDESSCR |
Specify, for this entry transaction, if the field must be present in:
|
Standard description (field ITMDES1COD) |
Parameter used to define, for this entry transaction, if the standard product description must be:
|
field ITMDES1SCR |
Specify, for this entry transaction, if the field must be present in:
|
Product type (field ITMKNDCOD) |
Specify for this entry transaction if the Product type must be:
|
field ITMKNDSCR |
Specify, for this entry transaction, if the field must be present in:
|
Major version (field ECCCOD) |
Use this field to control entry or modification of the Major version number for a product. You can set this field to one of the following values:
|
field ECCSCR |
Specify, for this entry transaction, if the field must be present in:
|
Minor version (field ECCCODMIN) |
Use this field to control entry or modification of the Minor version number for a product. You can set this field to one of the following values:
|
field ECCSCRMIN |
Specify, for this entry transaction, if the field must be present in:
|
Receiving site (field RCPFCYCOD) |
Parameter that is used to define, for this entry transaction, if the site for the reception must be:
The default value assigned to the Reception site field is the request site (DA)/order entered in the header. |
field RCPFCYSCR |
Specify, for this entry transaction, if the field must be present in:
|
Supplier (field BPSCOD) |
This parameter is used to define, for this entry transaction, whether the supplier must be:
|
field BPSSCR |
Specify, for this entry transaction, if the field must be present in:
|
Project (field PJTCOD) |
This parameter is used to define, for this particular entry transaction, if the Project field must be:
Even if the project code can be entered using this setup, its entry is still prohibited if the document management is single-project (the PJTSNGDOC - Single-project documentparameter is set to Yes): in that case, the project code of the line automatically uses the value of the project code in the header. |
field PJTSCR |
Specify, for this entry transaction, if the field must be present in:
|
Order date (field ORDDATCOD) |
Setup used to define, for this entry transaction, if the theoretical order date must be:
|
field ORDDATSCR |
Specify, for this entry transaction, if the field must be present in:
|
Net price (field PRICOD) |
Setup used to define if, for this entry transaction, the net price must be:
|
field PRISCR |
Specify, for this entry transaction, if the field must be present in:
|
Purchase type (field PURTYPCOD) |
Setup that is used to define, for this entry transaction, if the purchase type must be:
It is possible to act on the presence of the purchase type (Purchase/Fixed Assets/Service). The purchase type is initialized to the purchase type of the original receipt or to the purchase type of the account associated with the product. |
field PURTYPSCR |
Specify, for this entry transaction, if the field must be present in:
|
PUR quantity (field QTYPUUCOD) |
Parameter used to define, for this entry transaction, if the quantity in purchase unit must be:
|
STK quantity (field QTYSTUCOD) |
Parameter used to define, for this entry transaction, if the quantity in stock units must be:
|
field QTYSTUSCR |
Specify, for this entry transaction, if the field must be present in:
|
Tax code 1 (field VAT1COD) |
This parameter used to define, for this entry transaction, if this tax code field must be:
|
field VAT1SCR |
Specify, for this entry transaction, if the field must be present in:
|
Tax code 2 (field VAT2COD) |
This parameter used to define, for this entry transaction, if this tax code field must be:
|
field VAT2SCR |
Specify, for this entry transaction, if the field must be present in:
|
Tax code 3 (field VAT3COD) |
This parameter used to define, for this entry transaction, if this tax code field must be:
|
field VAT3SCR |
Specify, for this entry transaction, if the field must be present in:
|
Receipt tax (field TAXRCPCOD) |
field TAXRCPSCR |
Specify, for this entry transaction, if the field must be present in:
|
Issue tax (field TAXISSCOD) |
field TAXISSSCR |
Specify, for this entry transaction, if the field must be present in:
|
Other tax 1 (field TAXOTH1COD) |
field TAXOTH1SCR |
Specify, for this entry transaction, if the field must be present in:
|
Other tax 2 (field TAXOTH2COD) |
field TAXOTH2SCR |
Specify, for this entry transaction, if the field must be present in:
|
Tab Analytical
In this function, the following fields cannot be accessed:
- Header sections,
- Stock movement sections,
- Line distribution.
Block number 1
Header dimensions (field HEACCECOD) |
Parameter used to define if, for this transaction, the analytical dimensions fields of the document header must be:
|
Distribution line (field DSPCOD) |
This setup is used to define, for this entry transaction, if the analytical distribution key at line and invoicing element level must be:
|
field DSPSCR |
Parameter used to define, for this entry transaction, if the field must be present in:
|
Stock movement dimensions (field STOCCECOD) |
Specify for this transaction if the analytical dimension fields related to stock movements must be:
|
Entry
field CCESCR |
Grid Dimension line
Dimension type (field DIE) |
You can enter an analytical dimension type code on each table line. |
Method (field CCECOD) |
Parameter used to define, for this entry transaction, if the analytical dimension must be:
|
Preloading dimensions |
Click the Preload dimensions action to load the default dimensions defined for a selected group of sites or companies. |
Reports
By default, the following reports are associated with this function :
PRTSCR : Screen print
This can be changed using a different setup.