The definition of sales price lists is divided into several phases:
Use the Sales pricing setup function to define the customer pricing rules. These rules are based on criteria relating to the document current context and allow the definition of: price values, discounts, free products, commission factors applied to sales reps and additional amounts (all the fields included in the columns defined in the Price list structures setup can be assigned).
The price setting rules are applied to the management of quotes, orders and packing slips, not forgetting that these rules are only applied in creation or during the insertion of lines, but not when generated from another document (the commercial conditions are respected).
The user can define an unlimited number of customer 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:
These rules can be applied based on defined conditions:
Refer to documentation Implementation
The setup is spread over multiple tabs:
This tab is used to define the code, title and characteristics of the price list.
Price list
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.
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.
|
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. |
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. |
Structure
Structure code (field PLISTC) |
This field is used to enter a price list structure code. |
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. |
Type
Price list type (field PLITYP) |
This field defines the price list rule: Normal
Grouped
Prohibited
Component
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. 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. |
Customers (field PLIBPRCNR) |
When setting up a price, there are three types of customers: Group
Off-group
All
|
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.
|
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 |
ITMSALES |
Product - Sales |
ITMFACILIT |
Product - Sites |
BPARTNER |
BP |
BPCUSTOMER |
Customers |
BPCUSTMVT |
Customer transactions |
BPDLVCUST |
Ship-to customers |
SALESREP |
Sales reps |
SPRICLINK |
Header and footer elements of the document |
The order in which fields are entered can have an impact on the application of the price list line. If the Customer field (BPCNUM of table BPCUSTOMER) or the Site field (SALFCY of table SPRICLINK) is set up as a criterion before the Project code (PJTNUM) during the entry of price lists, the entered projects are filtered and controlled for this customer or site.
The Header and footer elements of a document (SPRICLINK) 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. It contains mainly the header and line elements that are common to all the documents (quotes, orders, packing slips, invoices) and that can be selected as price list search criteria (the country, geographic subdivision, carrier code, project number...)
In this table, it is possible to select fields used to establish the grouped price lists as a function of the type of line found:
Specification on versions:
For the SPRICLINK table, you cannot select the Major version (ECCVALMAJ) and Minor version (ECCVALMIN) fields. If you select one of these fields, an error message is displayed.
Specification on the Project code:
In the SPRICLINK table, two 'Project' fields are available:
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.
Grid Criteria
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. |
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. |
Use this tab to define how the prices and free products are processed.
Price
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
|
Base price field (field PRIFLD) |
This field is only available if the field Price processing is set to Coefficient or Calculation.
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.
|
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):
|
Criteria
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
No
If the price list type is Grouped, the grouped application conditions of the price list depends on a total of:
|
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
Conversion - / +tax (field ATICNVFLG) |
No
Yes
|
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.
|
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
|
Free
Free products (field FOCPRO) |
The possible values are: No
N for M:
Other Product
Order total
|
Free type (field FOCTYP) |
The possible values are: Threshold
Multiple
|
Sales rep commission
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
Initialization The commission base can be defined by the net price of the invoice line, the total margin for the invoice line or a set up calculation formula. The commission calculation is made at the time of invoicing. |
This tab displays the list of columns defined in the line structure setup (these columns can contain amounts or percentages).
Grid Charges/Discounts
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
|
You can assign null values using grouped price lists.
In order modification mode, even if the grouped price list determines a 0 value for a given invoicing element, this value is applied and maintained.
Example:
Let us consider a grouped price list defined as follows:
Validation |
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. |
In addition to the generic error messages, the following messages can appear during the entry :
This price list contains lines. Continue?This message is displayed on price list modification, if lines are indeed contained in the price list. In this case, the data risks being out of sync with the price list structure.
The major setup elements are modified (price list type, search criteria). It is recommended to delete the lines already entered. Do you wish to delete the lines entered?This message is displayed when the user modifies the header or the first price list tab for which the data has already been entered. Except in exceptional cases (for example to replace the bill-to customer code with the paying customer code), the data cannot be recovered, it is thus recommended to respond 'Yes' to the question (this is the default value).
The modification of the setup (price allocation, conversion conditions, free product processing) requires the deletion of lines already entered or at least they must be closely scrutinized. Do you wish to delete pricing lines?This message is displayed when an attempt is made to modify a price setting rule in the second tab where data has previously been entered. In this case, the price list data and structure could be out of sync. It is recommended to answer 'Yes' to the question (which is the default value).
The modification of the discount/charges columns requires the re-verification of the price list lines already entered. Do you wish to delete pricing lines?This message is displayed when the columns filled by the price list are modified in a price setting rule in the 3rd tab where data have previously been entered. In this case, certain added columns risk having a zero or incorrect value. The default value is No, but it is necessary to verify the price list lines.
Absence of the corresponding inter-company purchase price listThis warning message appears when an inter-company sales price list is created and there is no corresponding purchase price list.
The purchase price list with the same code is not inter-companyThis message is displayed when the reciprocal purchase price list for the inter-company sales price list is not of the type inter-company.