Price List Update Definition

It is possible to define as many price list update processings as necessary. For that reason each processing must be identified by a revision code of 7 alphanumerical characters.

In order to avoid the excessive use of one specific processing, an access code can be assigned to each processing (see the documentation on Access codes).

The "Selection" block is used to select the price lists that will be concerned by the update processing.

Price list code

A price list code (see the documentation on Price list codes) MUST be entered. In effect the revision can only be parameterized for a set of price lists assigning the same price list conditions. A price list code is thus selected that defines the amount, the discounts and charges dealt with by the resulting price list records.

Price list records

The update processing will then be activated for the whole price list records defined under this code, except if ranges have been activated for these records.

Validity and modification possibilities

The validity date stipulated in this field matches the validity date of the price list records. In this way, only those records whose validity ranges contain the date stipulated in the selection will be dealt with.

The user can also decide, by checking the "Modifiable selection" option, that the selection on the price list records and their validity date will be accessible upon launching the update processing. Conversely, this information is frozen.

The "Processing" block is used to define the general processing type that will be executed during price list revision. Three general processing types will be submitted, implying a particular parameterization.

The first processing, "Record modification", is used to modify the whole price list records, or only a selection, that exist at the level of the price, discounts and charges dealt with in these recods. This function can be used, for instance, in case of a general or partial change in a price list policy.

The first processing, "Record copy" provides the same processing possibilities as the first one, except for the fact that the records of origin cannot be modified. They are copied and modifications can possibly be introduced to the copied records. The parameterization is identical to that of the first one. For instance, this function can be used in the case of the creation of price list records for new customers on the basis of already existing records.

The third processing, "Currency modification", is used to modify the display currency for all the price list records of only for a selection. The amounts present on the processed price list record are translated into a new currency. It is also possible to parameterize modifications on the price, discount and/or charges linked to the price list records (same parameterization as for the "Record modification" processing).

This type of processing can be used for instance:

• during the EURO transfer, when all the transactions for each BP, and each product, are valued in Euro.

• Upon creation of the pice list records for the foreign subsidiary of a customer managed in a currency other than the Euro, should the same price list policyas the parent company be applied to said subsidiary (first the price list records applied to the non Euro customer will be copied, then the currency dedicated to the subsidiary will be modified).

Depending on the requested type of processing, the dedicated area in the "Processing" section must be assigned.

The parameterization terms for each of these processings are explained hereafter. It is important to note that it is possible to enter new validity ranges for those records generated or modified by the processing. These dates can only be modified upon launching the processing if the "modifiable date" flag has been activated.

Record modification and Record copy

For a processing code parameterized with "Record modification" or "Record copy", most of the information entered for the processing to be executed is specified at line parameterization level (Lines button). The parameterization of the lines is dealt with in a paragraph further on.

Currency change

For a processing code parameterized with "Currency change", it is necessary to assign the "Currency change" section where the following elements will be mentioned:

• the former currency in which the amounts of the price list record were expressed.

• The new currency into which they should be converted.

• The exchange rate that will be used forthe conversion (see the documentation on the Currency exchange rates).

If additional modifications of the information on the price list record need to be parameterized, the same parameterization as for the "Record modification" or "Record copy" will also be used.

 

The "Processing variables" section is used to define a set of variables that will be used upon creation of the application conditions and/or the modifications to be made at price, discount and charge level. The variables are thus used when parameterizing the price list update line(s) (Lines button).

Any kind of variable can be defined.

For example:

• a "PRODUCT" variable that could take any product code value. It would then be possible to specify an application condition of the pice list update with resepct to this variable.

• a "DISCOUNT1" variable that could take any numerical value. It would then be possible to specify this variable as the value to be used when updating this discount.

These variables present the advantage of being displayed when the update processing is launched. It is then possible to modify the default value of these variables before launching a price list update. Conversely, if the definition of a condition is "hard-coded", or a fixed amount has been entered as price list update, it will not be possible to use it off the limits defined in the line parameterization.

The variable table is sub-divided into five columns:

• Variable
  A Variable code is defined in this field over 10 alpha-numerical characters. This is the code that will be used when elaborating the condition formulas for the price list application or modification.

• Title
  A title can be entered to easily identify the defined variable.

• Type
  The variable type is used to define the nature of said variable (see documentation Data type). For instance, for the "PRODUCT" variable, an ITM type (product reference) will be defined; for the "DISCOUNT1" variable, a DCB type (Decimal).

• Default value
  A default value can be stipulated to document this variable. Thus, upon launching the price list update processing, this value will be displayed. It remains modifiable.

For instance:

•  For the " PRODUCT" variable, the TOY value will be given.

• For the "DISCOUNT1" variable, the 10% value will be given.

Upon launching the processing, if these values are not modified, only the discounts applied to the sales operations of the TOY product will be initialized to 10%.

• Control table
  It is possible to assign a control table to the various variables (refer to the Control Table documentation). The entry of certain values can thus be prohibited.

Parameterization of the price list update lines

The line parameterization screen is subdivided into two parts:

• the parameterization header, with the line number, the title, the update application conditions.

• The updating table for the elements processed by the price list records (price, discount and charges, defined by the price list code).

As many update lines will be created as there are particular conditions for the application of the processing.

For instance: In the case of a price list update of type "Record modification"

For the moment, a common price list policy is applied to our 4 customers. The price list defines the price of the product at € 100 with a 10% discount.

The common price list policy needs to be revised. For customers 1 and 2, the major ones, what is aimed at is a price list defining the price of the product at € 90 with an 11% discount. For customers 3 and 4, occasional ones, what is aimed at is a price list defining the price of the product at € 110 with a 9% discount.

In order to manage this scenario, two price list update lines will need to be parameterized:

• Line 1: With a line header condition defining that only customers 1 and 2 are concerned. The new price and the new discount revised downwards will be specified in the table.

• Line 2: With a line header condition defining that only customers 3 and 4 are concerned. The new price and the new discount revised upwards will be specified in the table.

As a consequence, the parameterization of these price list updates requires the creation of at least one line.

In order to create a line, it is necessary to specify:

• Line number
  It is necessarily a number ranging from 1 to 99999999.

• Line title
  It is a title enabling the involved line to be quickly identified. This title is free.

• Condition
  It is also possible to parameterize a condition used to limit the application of the processing. This condition used the Adonix vocabulary. it can be built from:

The value of the fields present in the table of the various identifiers of the price list code. For instance: For a price list code whose identifier is the Product/Customer pair, it is possible to limit the application of the update to a specific product code ([F:ITM]ITMREF= "XXX") and/or to all the customers belonging to a given statistical range ([F:BPC]TSCCOD= "XXX").

The variables predefined in the parameterization header of the price list update.

Deletion or Modification of the price list record data

Two options are available concerning the price list processings (for the selection if parameterized).

• The deletion of the price list conditions, i.e. the various elements processed by the price list code.

• The modification of the values.

The deletion is activated via the dedicated flag. To modify values, the update table is documented. This table contains five columns:

• Title
  The titles of the lines in this table are automatically initialized based on the information entered at the level of the price list code, which is common to all the price list records processed by the price list update. A line is created for each discount, charge and price (if the price list code specifies that the price is documented by the price list).

• Modification type
  Several modifications can be parameterized:

  • Not modified: the price list column will not be concerned by the processing.

  • Variation in %: Application of a percentage to the value of the field of the Price or Discount or Charge column.

  • Variation in amount: Addition or substraction of a fixed value to/from the field value.

  • Assignment: the price list column will be initialized to a value defined by the price list update. If the column is already documented by an existing price list record, the processing will overwrite this value with the new one.

• Formula or constant
  This field is used to define the value that will be used for the rate or the amount during the update.
  The value can be defined by a constant (a "hard-coded" number) or by the variables of the processing, that were previously explained.
  If the rate or amount to be applied is decreasing, the constant or the formula must be preceded by a negative sign.

• Rounding & Rounding type
  The recalculation of the price list conditions can lead to results with too many decimals. It is possible to set a rule that will define the rounding type that should be applied to the result (to the nearest, down or up).
  The rounding type makes it possible to decide on the number of decimals requested for the rounding. Thus, it will be 1 for a rounding to the unit, 0.1 for a rounding to a decimal, 0.01 for a rounding to two decimals, etc.