Pricing Parameters
The definition of supplier price lists consists in four stages:
- setting up the invoicing elements to define the different invoice footers that can influence the price setting of a business partner,
See the Invoicing elements documentation for further information. - setting up the structure codes to define the different discount and charge columns that can be applied to a particular business partner,
See the documentation on the price list structure for further information. - setting up the price list codes to define the various price setting rules that can apply to each structure code.
- the input of the price list records, defining the actual values of the product price, discounts and charges, for each price list code.
See the documentation on the price list entry for further information.
This function is the third major stage in the price list setup cycle. You use this function to set the supplier price setting rules, which are rules used for determining the values of prices, discounts, and other amounts (all the column fields of the price list structure setup can be used).
The price setting rules are applied to the management of purchase requests, orders and receipts, remembering that these rules are only applied in creation or during the insertion of lines, but not when generated from another document (the sales conditions are complied with in this case). Except for purchase requests, which can be recalculated if necessary (which is the case where a group of purchase requests are chosen).
The user can define an unlimited number of supplier price setting rules, each being identified by a 6-character code. Each rule is associated with a priority that allows the establishing of a hierarchy with respect to other rules and a reason code that makes it possible to indicate the origin of the values found during a price list search.
The result of this setup makes it possible, for each price list code, to automatically create inquiry and update screens for price lists that will contain the correct columns. The price list search algorithm takes into account the price setting rule, and the user can then load the price list database.
A large number of rules can be set up, thus making it possible to define:
- prices or charges and discounts,
- the amounts at the line that can be defined by the line structure setup (as a percentage or amount, with the sign -/+).
These rules can be applied based on defined conditions:
- for each line individually (depending or not on the quantity),
- for a group of lines with the same characteristics (depending on the quantities or aggregated prices).
Prerequisites
Refer to documentation Implementation
Screen management
The setup is spread over multiple tabs:
- Criteria: determines the linked criteria which are used to detect when a a price list line applies, by associating a price list code to a structure code.
- Price: determines the general rules of price processing.
- Charges / discounts: determines the charges and discounts to be considered in the price list.
Header
Price list code (field PLI) |
Code used to identify the price list rule. A price list code identifies a setup giving access to the rules that determine the price, discounts or other elements linked to the price lists. In order to set up a price list code, it is necessary to define its type, the list of fields used to specify when a price list line can be applied, and the list of fields assigned by the line. Once this has been set up, the user can access the price list line entry screens. In these screens, the user can enter both the criteria values and the corresponding values. For example: Definition of two discounts by Product group-Customer code combination. The Product group (from the product record) and Customer code (from the customer record) fields are considered as criteria for the setup. The Discount1 and Discount2 fields display the values assigned by the price list rule. In this case, the price list line entry screen contains a total of four columns. |
field DESAXX |
This long description is used as a title in screens and reports. By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language. The connection language must be defined as a default language for thefolder. |
Structure code (field PLISTC) |
This field is used to enter a price list structure code. |
Active (field PLIENAFLG) |
Indicator used to activate or not the presence of this price list in the suggestions. When a price list is declared to be 'Inactive', it is no longer used during price search.
See the documentation on the Price list activation for more information. |
Suppliers (field PLIBPRCNR) |
When setting up a price, there are two types of suppliers: Group
Off-group
|
Price list type (field PLITYP) |
This field defines the price list rule: Normal This price list defines a group of conditions valuated on the line, according to the conditions linked with the context (supplier or customer, order header...). Grouped
The grouped price list, if applied, does not take into account the priority rules of the standard price lists or the initialization done by these price lists (however, the priority rules apply between grouped price lists). |
Search group (field PLISEA) |
The search groups are used for the association of logical price list sets, which are evaluated by priority within the same group. |
Priority (field PIO) |
Indicator used to assign a priority to the pricing in order to enable its classification in the search order. Price lists are processed in the increasing order. Specificity of grouped price lists Standard price lists can be applied in cascade if the price list is based on different discount columns and charges columns. |
Reason (field PRIREN) |
The Reason is a local menu code associated with a price list rule.
A dedicated setup makes it possible to define a default value for the reasons when the price is modified manually.
See the documentation on the Price list reasons for more information. |
Tab Criteria
Use this tab to define the different fields in the on-line tables where the values will determine the application of the price setting on the line.
The following tables are available:
Table |
Table Title |
ITMMASTER |
Products |
ITMFACILIT |
Product - site |
ITMBPS |
Products / Suppliers |
BPARTNER |
BP |
BPSUPPLIER |
Suppliers |
BPSUPPMVT |
Supplier transactions |
PPRICLINK |
Header and footer elements of the document |
ITMSALES |
Products / Sales (for inter-company price lists) |
BPCUSTOMER |
Customers (for inter-company price lists) |
BPCUSTMVT |
Customer transactions (for inter-company price lists) |
BPDLVCUST |
Delivered customers (for inter-company price lists) |
The Header and footer elements of a document (PPRICLINK) has no real existence in the database. This is a data structure in which the document header and line elements used for the price list search are stored. The elements concerned essentially include header elements and line elements common to all the documents (Purchase requests, orders, receipts) selected as price list search criteria (carrier code, delivery mode, supplier/product statistical groups, etc.).
Specification on the Project code:
In the PPRICLINK table, two Project fields are available:
- The PJT - Project field, authorizing the selection of a unique Project reference or of a project reference linked to a task code and/or a budget code at the price list entry level,
- The PJTNUM - Project number field, only authorizing the entry of a 'global' project, with no mention of the task code or budget code, at the price list entry level.
When the price list setup defines a price list line related to the PJT field, the price list search only applies to the project code or to the project code + task code and/or budget code association defined at the price list entry level. This makes it possible to define price list conditions by task or budget code.
When the price list setup defines a price list line related to the PJTNUM field, the price list search applies to the project code, whether it is linked to a task code or budget code. This makes it possible to define a price list condition, regardless of the task or budget used.
Inter-company price lists: it is possible to define different prices for certain companies of the group which purchase from other companies of the group. For this setup, the ITMSALES, BPCUSTOMER, BPCUSTMVT and BPDLVCUST tables have been added. The PPRICLINK table has been modified to include the sales site and the sales company associated with the inter-company supplier.
It is possible to define a price list per sales company for different purchasing companies:
For a sales company, the price list can be defined with the:
- Sales company: SPRICLINK/CPY.
- Customer: BPCUSTOMER/BPCNUM.
- Product: ITMMASTER/ITMREF.
For a purchase company, the price list can be defined with the:
- Sales company: PPRICLINK/CPY.
- Customer: BPCUSTOMER/BPCNUM (this is the customer associated with the purchasing site)
- Product: ITMMASTER/ITMREF.
Grid
N (field NOLIG) |
Table (field FIL) |
It is the available table on which price list rules can be applied. |
Table description (field INTFIC) |
This field reproduces the long title of the selected table. |
Field (field FLD) |
It is the name of the field used as as criterion. It belongs to the table previously entered. |
Length (field CRILEN) |
This field specifies the length of the field selected. This criterion is involved in the determination of the maximum length of the elements that can be used. The total length of the criteria is limited to 50 characters, but can be set up. The index, if the field has multiple occurrences, can be specified. |
Dimension type code (field CRIDIE) |
It is the value of the analytical dimension code to take into account for the CCE analytical dimension fields. |
Index (field CRIIND) |
This is the value of the index to be taken into account for multi-sized fields. |
Criterion title (field CRIDES) |
This title is displayed in the column header for the screens created using this setup. |
Link (field LIEN) |
This field is used to add a column with the long or short title during inquiry, e.g. company name, product decription, etc. |
Tab Unit Price
Use this tab to define the price processing.
Block number 1
Price processing (field PRIPRO) |
Use this field to define if the price list assigns a unitary price to the line, and if so, how: No
Value A price is entered into the price list, and the line unitary price takes this value if the price list line is applicable. Value for no
Coefficient
Calculation
For the Coefficient or Calculation, use the following tables when searching for a price for a sales document: ITMSALES, ITMMVT, and ITMCOST. During setup, the VLTTOT field in the IMTCOST table is used to take the standard cost in the formula (Base price field) as an element of the gross price. |
Base price field (field PRIFLD) |
If the Price processing is 'Coefficient': If the Price processing is 'Calculation': |
Update zero price (field UPDNULPRI) |
The Update zero price check box only applies to grouped price lists where the Price processing is set to 'Value' or 'Coefficient'. When the box is checked, the system forces the gross price of the list on product lines with a null gross price. Contrary to the usual logic of grouped price lists, the null price will not be considered as the best price. This rule is the same when the price set up for the grouped price list (Price field in the Price lists entry function) is null: a null value (price, discount or charge) never replaces the entered line value, whether the Update zero price check box is selected or not. For other grouped price lists, the process remains the following (Update zero price box selected or not):
|
Block number 2
Price - / +tax (field PRITYP) |
This indicator is used to determine whether the prices of the products are expressed ex-tax or tax inclusive. It has no implication on the price list search in purchases. |
Price/Quantity (field PRIQTYFLG) |
If the price list type is Normal, the field can take several types of value: Yes
There is no consistency controls on the quantity brackets between the various lines of the price list record during entry.
No
If the price list type is Grouped, the grouped application conditions of the price list depends on a total of:
|
Currency (field CUR) |
This is the currency code controlled in the currency table. |
Block number 3
Conversion - / +tax (field ATICNVFLG) |
No
Yes
|
Unit conversion (field UOMCNVFLG) |
No
Yes
The unit conversion cannot be applied for the grouped price lists. |
Currency conversion (field CURCNVFLG) |
Indicator used to decide whether or not an automatic conversion of the price list will take place in the document currency. No
Yes
|
Tab Charges / Discounts
This tab displays the list of columns defined in the line structure setup (these columns can contain amounts or percentages).
Grid
Description (field COLDES) |
This field takes the title of the discount or of the charges coming from the price list structure. |
Charge/Discount processing (field DISCRGPRO) |
This field can be used to manage the charges and discounts defined in the price list structure. Yes
No
Initialization
The option to initialize a discount in the price list applies only to the same price list types. There is no dependency between the grouped and normal price list types. |
Specific Buttons
Posting |
Click this action once you have completed the entry to save the setup and trigger the screen generation. |
Copy
Click this action to copy the setup from or to a folder. Block number 1
Block number 2
|