This function is used to start, in simulation or in real mode, one of the previously parameterized price list update processings.

Prerequisite

See also Refer to documentation Implementation

Screen management

 

An update processing is started from a single screen, via the selection of the concerned revised code. This revision code has been defined during the parameterization (definition) of the price list updates.

It is necessary to specify if the processing must be launched:

  • In simulation or in real mode. For that purpose, the Simulation Yes/No option must be chosen.
  • With display of the price list records. The Display Yes/No option is used to decide whether, for a processing launched in real mode, the updated price list records should be displayed or not. It is possible not to display every record. Then only the log file makes it possible to view the changes made.

The following fields are used to specify the selection criteria and modifiers. They are each considered below.

Record selection

It concerns the selection criteria of the price list records to be processed. Depending on the parameterization of the selected update code, it will be possible, or not, to update these criteria.

The selection can take place via:

  • A record range: a set of price list records limited by their respective numbers.
  • A validity date: all the price list records valid at this date
  • Variables, used in the condition formulas for the processing application.

Modification

This concerns criteria defining the processing action. It is thus possible to modify:

  • the validity dates of the modified or generated records (according to the parameterization of the selected update code).
  • The currency of origin, the new currency and the exchange rate to be used (in the case of a processing of "Currency modification" type).
  • Variables, used in the update formulas of the fields of price list records.

The OK button is used to launch the processing.

The End button is used to access the log file.

Entry screen

Block number 1

Code (field COD)

Code used to identify the price list revision.

A revision code identifies a setup giving access to the rules that modify the price lines for price lists and discounts.

To parametrize a revision code, a type, a price list and the price list records (of the specific price list) are defined, as well as tha calculation rules to be applied to the price and discount data.

Once the setup is specified, the user can access an execution screen in which the user can give the selection of records for revision and values for the variables that have been defined in the calculation formulas.

For instance: The record xxxxxx calid from 01/01/99 to 03/31/99 must be duplicated in order to create a valid price list record from 04/01/99 to 06/30/99.

for lines of the Product group (from the product record) that correspond to the selection, the basic price has increased by 2% and the Discount has increased from 1.5% to 7%.

for lines in FRF currency, the prices are rounded to the inferior franc.
field DES
Processing type (field TYP)

Processing

Simulation (field SIMFLG)

No help linked to this field.

View (field SEEFLG)

Record selection

Price list code (field PLI)
field PLIDES
From record (field PLISTRCRD)

Record number that allows the record to be identified in a unique way. This number is automatically generated or entered upon each creation of a price list record following the sequence number counter parameterization defined for the Sales price list records.

To record (field PLIENDCRD)
Valid on (field VLYDAT)

In order for the record to be processed, it must be valid at this date.
New start date (field PLISTRDAT)

This field defaults to the value defined in the field Validity start date in the price list update rules. Leave the default date displayed or select the date from which the new or updated price lists must be valid.
New end date (field PLIENDDAT)

Validity end date of the record under update.
To modify a record, if this date is not entered, the one from the record is kept.
For a change of currency, if this date is not entered, the new record keeps the validity end date of the original record.

Currency change

Old currency (field CUROLD)

Data that can be accesssed only if there is a change of currency.
All the lines of the record that have this currency code are retrieved in the new record

.
New currency (field CURNEW)

currency

Data that can be accesssed only if there is a change of currency.
In the record, the price list, discounts or expenses data are converted in this new currency.
Rate type (field CHGTYP)

This field is controlled by local menu and can take the following values: current exchange rate/monthly exchange rate/average exchange rate.

The exchange rate type proposed by default is the exchange rate type associated with the supplier entered in the order header. As long as the order has not been created, it can be modified except when a line with a cost structure has already been entered.

An exchange rate type is used to determine the currency exchange rate in the exchange rate table taking into account the order date. This information is used to determine the prices and discounts on the basis of the price lists authorizing the conversion between currencies.

If order lines have been entered, or during the copy of an order, a question will be posed to the user about whether to re-calculate the prices and discounts depending on the price lists. If the user decides not to apply the price lists, the prices and discounts will be simply converted into the new currency at the rate determined by the exchange rate type and the order date.

If the currency is equal to the company currency, the exchange rate type will not be accessible since it will have no influence in this context.

Grid Processing variables

Variable (field VARCOD)
Description (field VARDES)
Value (field VARVAL)

No help linked to this field.

Specific Buttons

Last Execution

The Last execution button is used to view the price list update launch screen as it was entered during the last operation.

Error messages

The only error messages are the generic ones.

Tables used

See also Refer to documentation Implementation