Pricing Parameters

• 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.

• Description (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.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

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.

• 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.

• 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
Priorities apply. If a grouped price list applies to a document line, the other grouped price lists cannot apply.

Standard price lists can be applied in cascade if the price list is based on different discount columns and charges columns.

• Structure code (field PLISTC)

This field is used to enter a price list structure code.
This code determines the sales conditions managed for each purchase document line ('Discounts and Charges' field).
The structure code is defined for one or several companies. At least one price list code must be set up for each structure code used by at least one BP.
 When aprice list structureis changed, the new structure must include the previous one.

• Company (field PLICPY)

Different companies can share the same price list structure. The company code is used to associate a price list structure to a single company.

If the Company code field is empty, the price list setup will be applied to all the companies that share the same price list structure.

• 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

This price list is used to assign specific conditions for a group of lines, according to the conditions linked with the context (supplier or customer, order header...),
The calculation processing of the grouped price list can be automatic, requested upon creation or when modifying the orders according to criteria specified in the following parameters:

• PURGRUDIS - Invoke group pricing (ACH chapter, PRI group).
• GRPPRI - Group price management (VEN chapter, PRI group).

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).
As a principle, the grouped price list applies the amount and/or the discounts/charges most favorable to the buyer. For the same order line, the gross price can originate from a normal price list record, the discounts and charges of the grouped price list record, if they exist,

The grouped conditions are processed at the end of the entry of the order or document lines.

Prohibited

The criteria for this price list determine the sales prohibition conditions applied to a product. This price list is called upon entry of the product reference.

Component

The BOM reference must be a part of the criteria.
During the setup of the rules for the determination of the product prices in the sales BOMs (component prices, the options or the variants in the commercial kits), it is necessary to enter:

• the application criteria of the price list (applying to BOM components),
• the kit code (PNTITMREF field in the SPRICLINK table).

If this field is not specified in the setup, the component prices is valid for all the BOM where they are used. These prices associated to each component line value the whole BOM in the document.

• 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.
After the search group evaluation, the price list coming from the price group that is the most favorable for the customer is taken into account, based on the calculated net price.

It is possible to define up to 10 search groups (0.9). if no group is determined (all the price lists have a value of zero), the priority apply to all the price lists.
 Search groups do not apply to grouped price lists

• Customers (field PLIBPRCNR)

When setting up a price, there are three types of customers:

Group

A price only concerns the customers of the group (inter-site customers).
In that case, a price setup with an identical code must be created in both modules (Purchasing and Sales) in order to make sure that the discounts and the charges are consistent. It implies that the price list structure of the inter-site supplier is the same as the sales price list structure of the company representing the supplier.
Entering the prices is only carried out on the Sales side. The Group purchasing price lists will then point to the sales price lists.
To define the inter-company customers, it is possible to refer to the customer management function (sales).
When the Customers field is set to Group, some types of price lists (forbidden price lists, components price lists) cannot be applied.

Off-group

The price list concerns all the customers who are not inter-site,

All

The price list concerns all the customers.

• Reason (field PRIREN)

The Reason is a local menu code associated with a price list rule.
During the price list search, this reason is assigned to each value of the document line (quote, order, delivery notes, invoice etc.) using this price list.
This is used for:

• identifying the origin of a sales condition,
• conducting additional checks (for instance, prohibit in some cases the modification of the said reason and/or the modification of prices and discounts).

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.

• Table (field FIL)

Indicates the available table to which price list rules can be applied.

• Table description (field INTFIC)

This field indicates the long title of the selected table.

• Field (field FLD)

It is the name of the field used as a criterion. It belongs to the table previously entered.
A warning message is displayed to mention that the theoretical total length of the criteria exceeds the maximum length authorized to set up the price lists.

• 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.
The value of the analytical dimension must be included in the GDIE table.
This analytical dimension code replaces the indexes from 0 to 8 of the versions prior to the 6.0

• Index (field CRIIND)

This is the value of the index to be taken into account for multi-sized fields.
 The index value is equal to '0' for the first occurrence, it is equal to '1' for the second, etc.
For instance, for a field with 9 occurrences, indices range from '0' to '8'.

• 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.

• 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

The price is not defined by the price list.

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

This option is used to enter a price that corresponds to W products X being the divisor. Three columns are entered in the price list: a price, a unit, and a price divisor.

Coefficient

The price is defined in the form of a coefficient that is applied to the value of a field in one of the product, product/sales, product/cost or product movement records.
The code needs to be entered in the Basic price field. You use the selection window to view all the fields in the data dictionary for the ITMMASTER, ITMSALES, ITMMVT and ITMCOST tables. For example, if you need to define the price in relation to the base price of the product record, use the field code: [F:ITS]BASPRI.

Calculation

The price is defined in the form of a calculation formula (numerical expression) entered in the Basic price field. The fields in the online tables and a certain number of variables can be used.

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)

This field is only available if the field Price processing is set to Coefficient or Calculation.

• When it is set to Coefficient, the price is determined by a coefficient. The coefficient is applied to a specified numeric field in a table that can be used to determine the price. The table can be from the following list of tables:
  • ITMCOST (Products-costs)
  • ITMMVT (Product-site movements)
  • ITMSALES (Products-Sales)For example, if the price should be defined as a factor of the base price in the Products-sales record (table ITMSALES), enter [F:ITS]BASPRI.
• When it is set to Calculation, the price is determined by a formula. You enter the formula as a numerical expression that can include constants, operators, functions, and multiple online tables.

Click Formula analyzer from the Actions icon to create the required coefficient or formula. During setup, the VLTTOT field in the IMTCOST table is used to take the standard cost in the formula as an element of the gross price.

If calculating prices based on the Products-costs table (ITMCOST), the default cost is the standard cost. To use a different cost you must use the entry point TARIFS of the TRTPRICE processing (Data base module). You can use TARIFS to select a cost type by setting up the Cost type field (CSTTYP) in the Sales price list search table (SPRICLINK).

• 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):

• Applying a grouped price list makes it possible to individually force the value corresponding to the set up price, provided that this value presents more benefits for the customer. Otherwise, the initial value of the line is kept.
• The setup of the grouped price list consists in:
• the gross price,
• and/or discounts (in amount and/or percentage),
• and/or charges (in amount and/or percentage).
• Discounts and charges of the grouped price list can be used instead of their respective zero values on lines, but gross prices are submitted to the Update zero price check box.
  

• Price - / +tax (field PRITYP)

The prices and charges/discounts in amount are entered ex-tax or tax-incl. in the lines of the Price list function. When searching for a price list, the lines of this price list are used according to the value of the Ex-tax/Tax-incl. conversion code and the call currency of the document.

• Price/Quantity (field PRIQTYFLG)

If the price list type is Normal, the field can take several types of value:

Yes

In addition to the price list criteria, an unit and quantity classes must:
The line is taken into account only if:
- All the criteria are met
- The quantity (converted if the quantity conversation is authorized for this price list) is set between the minimum and maximum ranges

There is no consistency controls on the quantity brackets between the various lines of the price list record during entry.

No

Only the price list criteria are taken into account.

If the price list type is Grouped, the grouped application conditions of the price list depends on a total of:

• Gross prices (gross price ranges)
• Net prices (net price ranges)
• Quantities on all the rows that meet the grouped criteria (quantity ranges).

• Currency (field CUR)

used to assign a fixed currency code if all the lines entered with this price rule share the same currency. If this field is empty, it is necessary to enter the corresponding currency code for each price list line.

• Conversion - / +tax (field ATICNVFLG)

No

If the document price is different than the price list, the price list is not used.

Yes

If the document entry is carried out with a price type different than that of the price list, the price list amounts are converted following the tax codes.

• Unit conversion (field UOMCNVFLG)

No

If the sales unit is different to that of the price list line, the price list is not used.

Yes

If the sales unit is different, the quantity and amount criteria for the price list are converted according to the unit conversion rates table.
If no conversion is set up for the sales and price list units in this table, the price list amounts are considered using a conversion rate of 1.

• 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.
This indicator can take the following values:

No

If the entry currency of the document is different from that of the price list line, the latter is not taken into account,

Yes

If the entry currency of the document is different from that of the price list line, the amounts for this price list line are automatically converted into the document currency at the rate which is applicable on the document date.

• Free products (field FOCPRO)

The possible values are:

No

This price list does not define free product conditions.

N for M:

Allocation of a free quantity of the same product

Other Product

Allocation of another free product

Order total

Only valid for a grouped price list. It is used to assign a free quantity depending on the totaling conditions (quantities or amounts) of the document lines and according to the order total.This order total depends on the parameter entered in the field.

The calculation of the free quantity is based on the free type.

• Free type (field FOCTYP)

The possible values are:

Threshold

Allocation of the free product when the threshold is reached. If the threshold is exceeded, it is necessary to assign the corresponding free quantity.

Multiple

Allocation of the free product by product ranges (beyond the threshold).
Example: beyond 10 units, one free product is allocated every 5 units.

• Commission factor (field COMPRO)

This field displays the multiplying coefficient of the commission rate. It is applied to the representatives rates 1 and 2.

No

This price list does not have an impact on the rate.

Initialization

The coefficient is set with weighing factor to '1'.

• 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

The column is displayed and can be modified in the Price list entry function.

No

The column is not displayed in the Price list entry function.

Initialization

If the charges and discounts are set to Initialization, no value is indicated in the Price list entry function even in the case of a price list with less priority. This field is initialized to 0.

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.