SAP ABAP IMG Activity VLC_CRM_INTEGRATOR (BAdI: Integration Between VMS and CRM)
Hierarchy
☛ ECC-DIMP (Software Component) DIMP
   ⤷ IS-A-VMS (Application Component) Vehicle Management System
     ⤷ ISAUTO_VLC (Package) Vehicle Management System (VMS)
IMG Activity
ID VLC_CRM_INTEGRATOR BAdI: Integration Between VMS and CRM  
Transaction Code S_KA5_12001327   (empty) 
Created on 20021129    
Customizing Attributes VLC_CRM_INTEGRATOR   BAdI: Integration Between VMS and CRM 
Customizing Activity VLC_CRM_INTEGRATOR   BAdI: Integration Between VMS and CRM 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name VLC_CRM_INTEGRATOR    

Use

This business add-in (BAdI) is used in the Vehicle Management System (IS-A-VMS) component.

Using this BAdI, you can transfer vehicles from the VMS to SAP Customer Relationship Management (SAP CRM). It is always run if you execute an action, which involves vehicle data being transferred into CRM (see Customizing for the actions). In the case of action CRMV for example, all vehicle relevant data is transferred to CRM (vehicle data, configuration data, history entries, link to business partners such as dealer and end customer).

The BAdI is also used, if you load vehicles from the VMS during the initial-load into CRM. In CRM, you can also store additional attributes for the individual object "vehicle" using set types. In the VMS you can do the same thing using an extension of table VLCVEHICLE. Using this BAdI you can transfer additional VMS data into CRM.

It is also possible, using this BAdI, to determine which vehicles and data you want to transfer.

The BAdI has the following methods:

  • PREPARE_COMPLETEVEHICLE_CRM
    Using this method, the VMS vehicle is mapped with the individual object "Vehicle" in CRM. If customer-specific Customizing exists in CRM, that is different to the Customizing delivered, you can make enhancements. For example, if you have assigned another catagory in CRM and assigned your VMS vehicles to this catagory.
  • PREPARE_VEHICLE_BUPAREL_CRM
    Using this method, the link between the vehicle and the dealer or end customer in VMS is mapped with the partner relationship.
  • PREPARE_VEHICLE_HISTORY_CRM
    Using this method, the VMS vehicle history is mapped with the event history from the individual object in CRM. The following possibilities exist:
    • You specify which actions in VMS should be mapped with which history-relevant event in CRM.
    • You can prepare document extracts that should be transferred to CRM.
    • If you have enhanced the vehicle history in VMS, you can transfer this additonal data to CRM.
  • PREPARE_VEHICLE_IOLINK_CRM
    Using this method, the sales documents for the vehicle in VMS are mapped with the business processes within the make-to-order-scenario (MTO) in CRM. You can also maintain the determination of the CRM business transaction.
  • SEND_COMPLETEVEHICLE_TO_CRM
    This method is run, if you execute action CRMV . In the default implementation, vehicle data, configuration data, history entries, as well as the link with the dealers and end customers are transferred. Using a different implementation, you could, for example just transfer vehicle data.
  • SEND_NEW_HISTORY_TO_CRM
    As soon as the vehicle has been transferred to CRM, you can transfer history records for the actions, which are relevant for the CRM business transactions. The actions that are relevant for CRM are generally indentified in Customizing for the actions in the VMS. This can, however, also be maintained using this method.
  • SEND_VEHICLE_1O_LINK_TO_CRM
    This method is relevant for the MTO scenario. In this scenario, the sales order for the vehicle is created in CRM. A new vehicle is created in the VMS and linked to this sales order; this vehicle is then transferred to CRM for processing of the aftersales processing. As soon as the vehicle has been transferred to CRM, you can also transfer the link of the vehicle to the relevant sales order, which was used to create the order.

Requirements

You must use a CRM PlugIn with release level 2003.1 or higher.

In Customizing for the VMS, you must set the CRM-relevant indicator for the CRM-relevant actions to ensure that the BAdI is called.

During the implementation you must ensure that the PREPARE methods are implemented. If this is not the case, the SEND methods will not work correctly.

Standard settings

The BAdI has a default implementation in which the VMS vehicle is mapped with the individual object "vehicle" in CRM.

Activities

Procedure for Implementing a BAdI

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG VLC_CRM_INTEGRATOR 0 KA50000029 Vehicle Management System 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20021219 
SAP Release Created in 471