Simulate Price Index Update

You can do a price index update on a leasing charge connected to a leasing line. You can either do this in 'Rental Agreement. Connect Additional Charge' (STS103) per leasing charge or as a mass update triggered from 'Leasing Price Index. Enter value' (LTS401).

When an index update is performed using (LTS401), all leasing charges with the same price index ID connected and valid periods for the date set in (LTS401) are updated, and the curves are recalculated.

If there are many leasing lines affected by such an update, there might be a need to simulate and review the update before confirming it. You can do this using the API LTS401MI.

The API consists of two transactions. One transaction to simulate and create records in table SWCHCU for the selection made and one transaction to list the records from this table.

This document describes how to do the simulation, using these two transactions.

Before you start

'Price index ID' must exist in 'Leasing Price Index. Open' (LTS400).

For records to be created in table SWCHCU, the selected price index ID must be connected to at least one leasing charge in (STS103) with periods equal or later than the set valid from date when running the simulated transaction.

Follow these steps

Follow these steps to create records in table SWCHCU, using simulated transaction:

  1. Start the API tool and search for LTS401MI and transaction SimulIndexUpd.

  2. The input fields for this transaction are the same as for a price index update from (LTS401). These fields are 'price index ID', 'valid from date', and 'price index value'.

    Enter a value in each field and press 'Run'.

    As a first action when running this transaction, any records already existing in table SWCHCU for the set price index ID are deleted. When that is done, new records are created in the table through a batch job according to the selection made.

    All leasing charges with the selected price index ID set in (STS103) and with periods in 'Rental Charge Curve. Open' (STS111) that have a valid from date equal or later than the selected valid from date create records in the table. Older periods do not create any records.

    This means, any leasing charge period that would be affected if an index update was instead done from (LTS401) with the same values, creates a record in table SWCHCU.

  3. A job number is given which can be checked in 'Job. Display History' (MNS320), to see when a job is completed. Ensure the job is completed before running the list transaction.

Follow these steps to view records in table SWCHCU, using list transaction:
Note: 

You can only view data that exists in table SWCHCU, that is, the simulated transaction must have been run for the selected price index ID to be able to view information in the list transaction.

Only the latest run for each price index ID is saved in the table.

  1. Start the API tool and search for LTS401MI and transaction LstSimulIndex.

  2. Enter a price index ID and press 'Run'.

    If a price index ID is set that does not have any records in table SWCHCU, an error message is displayed that a price index ID does not exist.

  3. When running this API, a list of all records that exist in table SWCHCU is presented for the set price index ID, created when this price index ID was last executed in the simulate transaction.

    Each record represents a period in (STS111) which is affected if the same price index update is performed in (LTS401).

    These fields are presented in the list:

    • 'Sequence number' of the API record

    • 'Price index ID' which was set as an input field

    • 'Valid from date' set in the simulated transaction, that is, from which date the simulation is done

    • 'Agreement number'

    • 'Agreement line number'

    • 'Line suffix' of the charge

    • 'Contract item' of the charge

    • 'Period', from (STS111)

    • 'Valid from date' for the period, from (STS111)

    • 'Valid to date' for the period, from (STS111)

    • 'Item number'

    • 'Serial number'

    • 'Fleet No'

    • Current 'Price index' value, from (STS103)

    • Current 'Charge' amount per period, from (STS111)

    • New 'Price index' value, set as an input field when running the simulate transaction

    • New simulated 'Charge' amount per period, based on set price index value

    • 'Currency'

    • 'Agreement Customer'

    • 'Agreement Customer Name '

    • 'Next Invoice Date'

    • 'Agreement Start Date'

    • 'Agreement End Date'

  4. If there are records that need to be corrected, you cannot do this in this function. Instead, you must do the change on each agreement line and leasing charge. You can change or remove the price index ID on the leasing charge in (STS103), if needed. When you do this, you can run the simulation and list transactions for the second time or to execute the price index update from (LTS401).

Related topics