Vendor and Customer

Use

  • The customer is the business partner to whom the vehicle is to be sold (debtor).

    This is usually the dealer in the importer scenario supported by VMS. It may, however, also be an end customer , for example, a car rental/hire company that wants to buy an entire fleet of cars from the importer, or an employee of the importer who wants to buy a vehicle directly from the importer.

    Note Note

    You can manage one-time customers , for example the employees of the importer, using a CpD one-time suspense/collective account in the customer master record.

    End of the note.

  • The vendor is the business partner from whom the vehicle is procured (creditor).

    In the importer scenario supported by VMS, this is usually the manufacturer (OEM). In cases where there is multi-level procurement, it may be an intermediate vendor, for example a distribution center.

    When a used vehicle is being exchanged for cash, the vendor can also be, for example, a rent-a car company or any other person. Such a business partner may also be managed at the same time as a customer in the system.

    Note Note

    You can manage one-time vendors , for example the previous owner when exchanging a vehicle for cash, using a CpD one-time suspense/collective account in the customer master record.

    End of the note.

You require this master data for the following activities:

  • the execution of specific actions (the vendor, for example for the action ORD1 Create purchase order , the customer, for example, for the action CUOR Create sales order )

  • the assignment of the organizational data to VMS roles, transaction VELORO (customer)

  • the entry of the manufacturer in the material master record in the purchasing view (vendor)

Activities

You must enter some master data when you create vendors and customers since not all the required data can be set on the VMS action interface.

  • Choose transaction XK01 to create a vendor centrally.

    Enter the required general data, purchasing data and company code data. For VMS the following data for the vendor is particularly important:

    • Location

    • Payment conditions

    • Incoterms (international commercial terms)

    • Purchase order currency

    • Purchasing group (alternatively also in the purchasing info. record)

    • Indicator for goods-receipt-based invoice verification (alternatively also in the purchasing info. record)

      This indicator is not necessary if you are not working with goods-receipt-based invoice verification.

      Caution Caution

      Create a purchasing info. record manually for each vendor. Leave the field Valuation type under Purchasing organization 1 empty. Do not use the Customizing setting (Customizing for Materials Management ) under Start of the navigation path Purchasing Next navigation step Environment Data Next navigation step Define Default Values for Buyers End of the navigation path , indicator InfoUpdate – Purchase order ), which defines that a purchasing info. record is created automatically when a purchase order is created. The field Valuation Type is filled when this Customizing setting has been made. This leads to problems when you want to create vehicles.

      End of the caution.

  • Choose transaction XD01 to create a customer centrally.

    Enter the required general data, sales area data and company code data. For VMS the following data for the customer is particularly important:

    • Location

    • Currency

    • Incoterms (international commercial terms)

    • Payment conditions

    • Shipping conditions

    • Account assignment group

    • Tax code

You also have to enter a reconciliation account and bank details in the company code data for vendors and customers.

See also: