Role

Use

A VMS role serves as a central control element in VMS . You create roles in Customizing, feed them with data in the VMS basic data functions and then assign them to the users.

Prerequisites

You have created the VMS roles with key and description in Customizing for VMS under Define VMS Roles (transaction OVELO19).

Features

There are three types of role:

  • Organizational Role

    This is a role to which organizational data is assigned. Organizational data is dealer or importer data ( plant, sales organization, distribution channel, division, SD document type, customer, ship-to party , and payer ). A role for which the field Customer is filled with a value indicates a debtor, in other words a dealer.

    These fields are usually evaluated in the VMS Internet interface . If a dealer wants to create a sales order in the importer’s system via the Internet, the fields in the sales order are filled with the appropriate organizational data. The dealer cannot change this data.

    The Customer field is also evaluated in the SAP graphical user interface ( SAP GUI ). If there is an entry in this field, the dealer that has been entered can only see the end customers that he/she has created him/herself but not end customers of another dealer. If the field is empty, all the end customers are visible.

    Note Note

    If you work with the user parameters VELO_SOLDTO Customer, Sold-to party , VELO_SHIPTO Ship-to party and VELO_BILLING Bill-to party , you do not need to create a separate organizational role for each individual dealer. You only require one role for all your dealers. Each dealer is then identified by the user parameters as a specific dealer.

    End of the note.

    Furthermore, you can assign a vehicle search area and an original ordering party to the organizational role. These fields are required in category management. The vehicle search area controls which users are allowed to see which vehicles during the search.

    You can also assign a pricing procedure and a currency . These fields are required in SAP Internet Pricing and Configurator (SAP IPC) and in the Characteristic Value Assignment Screen . The prices are displayed in the currency specified. Furthermore, the currency field controls the currency in which the user sees the prices in the vehicle overview and in the detail data for the vehicle.

    The fields that affect purchasing are currently not evaluated and therefore have no significance. However, they can be included in BAdIs as and when required in order to meet customer requirements.

  • Vehicle Model Role

    This is a role to which vehicle models are assigned. This role determines which vehicles the system displays to the user in the vehicle model list.

    Example Example

    You are an importer and want to see and manage all vehicle models; dealer X sells only small cars, dealer Y only motorcycles.

    End of the example.

    A vehicle model can be assigned to more than one vehicle model role.

  • Configuration role

    This is a role that is assigned to a configuration change profile .

    Depending on the vehicle model, status and so on, the configuration role specifies which vehicle characteristics the system should make visible for the user and which changes the user is allowed to make to the vehicle characteristics.

    Recommendation Recommendation

    It is recommended that you create at least two configuration roles: one for yourself as importer and one for all your dealers. In this way you can be sure that you, as importer, are able to change more configurations than your dealers.

    End of the recommendation.

Activities

  1. Assign vehicle models to the vehicle model roles (transaction VELORM).

  2. Assign organizational data to the organizational roles (transaction VELORO).

  3. Optional: if desired, define configuration change profiles and, in the profile determination, define which profile can be used for which configuration roles (transaction VELOP).

  4. Assign roles to the users (transaction VELORU).

    You should assign exactly one organizational role, one configuration role and one or more vehicle model roles to a user.

    Caution Caution

    Use a role only ever in exactly one function. For example, only assign vehicle models to a vehicle model role and not organizational data. In this way, you achieve maximum flexibility when changes are made later.

    End of the caution.