System Processes in Electronic Toll Collection

 

The following processes are carried out by the system:

Features

  • Release of contract

    Contracts are released in two steps:

    1. During the create process, the status Accepted by Customer (I2300) is set. This happens if the user chooses Save (not Save with Status 'Open' ) and all checks are passed successfully.

    2. If the status of a contract is Accepted by Customer but not yet Released (I1004), the system executes the process of the category TCE1.

      Note Note

      The implementation for this process decides if the status Released should be set or not. You can replace the standard implementation, for example if you want the system to perform further checks before releasing the contract.

      End of the note.

      The standard implementation of process TCE1 is process TC_RELEASE_SYST. This implementation checks if the status Released is allowed by the business transaction settings. If so, it checks if there are EDRs with status Open for the current contract and releases them. The system sets the status to Released and triggers the distribution of the new contract by setting a special log entry.

  • Creation of initial top-up EDRs

    The system creates an initial EDR if the following conditions are fulfilled:

    • The contract is a prepaid one

    • An appropriate EDR type is specified in the process

    If the CVV check requires an authorization of the amount, the system only creates the EDR if the authorization can be executed successfully. If not, the system displays an error message, asking you to complete the data.

  • Distribution

    Once you have saved an ETC contract with no errors and it has therefore been automatically accepted, the contract details are sent to the SAP NetWeaver Exchange Infrastructure (XI) for distribution. Using the XI dispatching and mapping capabilities, the contract is distributed to all other systems that require this information. This could be for purposes such as fraud detection, rating, billing and so on. As a result, every process implementation that changes the contract details can determine if the information is relevant for the downstream systems, and can then trigger the distribution of the changes. For more information on the distribution mechanisms, see ETC Contract Distribution.