Show TOC

Function documentationChanging Customer and Contract Data

 

You can use the following functions to make changes to customer and contract data, following a change request from the customer.

All functions are possible in Customizing for Electronic Toll Collection under Start of the navigation path Settings for User Interfaces Next navigation step Processes Next navigation step Define Processes End of the navigation path

Features

  • Change Primary Technical Resources

  • Change Additional Resources

  • Change Configuration

  • Maintain Customer Requested Locks

  • Cancel Contract

  • Change Prepayment Data

  • Top-Up Request Triggered by Customer

Activities

  • Change Primary Technical Resources (TC_CHANGE_TR / TC_CHANGE_TR)

    You use this function to change the primary technical resource defined in the assignment schema of the current contract. This can be the onboard unit (OBU) equipment or the license plate number (LPN). The system adjusts both the button to start the process and the view to capture the changes automatically according to the type of the primary resource you enter.

    • Change OBU Equipment

      If the OBU ID is the leading technical object used to identify a contract item, it may need to be changed.

      1. On the Change Technical Resource screen, enter the OBU Equipment ID.

      2. You can make this change time-dependent, by entering the time from which it applies.

        The respective time slices are reflected in the system and are considered for the billing process. To see all time slices, past and future changes, select the All Time Slices checkbox in the contract identification step.

    • Change LPN

      If the LPN is the leading technical object used to identify a contract item, it may need to be changed. You can make this change time-dependent, by entering the time from which it applies. For example, you can use this function if the customer is moving to a different town meaning that their vehicle requires a different LPN.

  • Change Additional Resources (TC_CHANGE_TR_ADD)

    You use additional resources as secondary identifiers for the technical resources. For example, the product can be configured with leading technical object OBU and the LPN as a secondary object. If the OBU is used in another vehicle, you must change the LPN as the additional resource. This change is not time dependent, because the additional resource has no influence on the price.

    Note Note

    If you add new resources to a contract, the system stores the date this change was made. If you remove resources during this process the system does not delete them; it stores the date up to which they had been valid.

    End of the note.

  • Change Configuration (TC_CHANGE_CONF1 / TC_CHANGE_CONF2)

    On the Change Configuration screen, you can change fields that might influence how the customer is handled or that influence the pricing of the contract, such as the Emission Class. For example, you change this value if a vehicle owner has installed an additional filter to their vehicle, thus changing the vehicle's emission class. Since this change can influence the price, it is time-dependent.

  • Maintain Customer Requested Locks

    For more information, see Maintenance of Customer Requested Locks.

  • Cancel Contract (TC_CANCEL)

    You can cancel a contract if, for example, a vehicle is no longer used. You can enter the cancellation with a specific request date or with immediate effect. However, the calculated cancellation date could be different from the one requested, depending on the environment and the status of the account.

    1. On the Cancel Contract screen, enter the Cancellation Request Date / Time and the Cancellation Reason.

    2. The system calculates the exact Cancellation Date, according to the Cancellation Request Date and the cancellation rules maintained in Customizing.

  • Change of Prepayment Data (TC_PREPAY)

    The initial payment data set up during order creation can be changed at a later date. You can change the top-up limit, the actual top-up amount charged and the payment method used for future top-ups. You can also change the procedure, for example, from automated top-up to manual top-up.

    Note Note

    This change becomes active immediately and will be considered for all future prepayments.

    End of the note.

  • Top-Up Process Triggered by Customer (TC_TOPUP_MANUAL)

    You use this process to capture top-up requests in the Interaction Center (IC) framework. The system creates an EDR for top-up, which allows you to change the default amount and payment data defined in the corresponding contract. Once the process is complete, the system sends the new EDR to the external system.

    If the EDR status is Pending for this contract, the system sets the status of this EDR to Obsolete. You can configure this process in terms of the EDR type that is used for the newly created EDR and the credit card check group, which defines if the entry of a CVV number is required for completing top-up requests using a credit card