Technical Integration

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_di46c2/helpdata/EN/a1/8ac43ace7a3b46e10000000a114084/content.htm
Created on March 24, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 6

Table of content
1 Technical Integration
1.1 Linking the IPC
1.2 Vehicle IDoc VEHCLE01
1.2.1 Calling the Status Monitor for the Vehicle IDoc
1.3 Connection to SAP Business Information Warehouse (BW)
1.4 Connection to Supply Chain Event Management (SCEM)

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 6

1 Technical Integration
Features
VMS is completely integrated into the SAP application components MM, SD, CS and FI/CO.
You can implement VMS together with APO (SAP Advanced Planner and Optimizer) as a planning system and with BW (SAP Business Information
Warehouse) as a reporting system for analysis and evaluation purposes.
Furthermore, VMS is linked to the IPC (Internet Pricing and Configuration) for vehicle configuration and pricing.
Message determination
is also part of the technical integration. It allows you to send and receive IDocs (intermediate documents) via EDI (electronic data interchange).

1.1 Linking the IPC

Use
The IPC (Internet Pricing and Configuration) is a New Dimension product of SAP that is used to configure vehicles in the Vehicle Management System as well
as for price determination.
The IPC is a software package that is installed separately and then linked to the Vehicle Management System.

Prerequisites
Before you link the IPC to VMS, execute the IPC standalone scenario as described in the IPC documentation. The IPC standalone scenario works with a
Java servlet user interface.
As soon as the IPC standalone scenario is u and running with the example database that is delivered, you must use the IPC data loader to assist you in
downloading data from your SAP DI system to a new and empty IPC database. This procedure is also explained in the IPC documentation.

Procedure
The linking of the IPC standalone scenario to the VMS takes place in two steps:
Create an RFC (remote function call) destination. You must create an RFC destination for each client of the SAP DI system to which you want an IPC to be
linked.
Enter these RFC destinations in the appropriate Customizing table. You must also make this entry in the Customizing table for each client.
Creating an RFC Destination
Call transaction SM59.
Choose Create .
Enter a name (for example,
IPC_050) for the RFC destination via which you want the IPC to be linked to client 050.
Choose the connection type T (TCP/IP connection) and enter a description. Then choose Enter .
Choose Explicit host in the frame Start on.
Under Explicit host in the field Program , enter the following:
/servlet/com.sap.ipc.servlet.IPCServlet/.
In the field Target host , enter the name and the port number of the Web server with which you want your IPC installation to be called (for example,
www.myserver.com:1080).
Choose Save as HostName.
Save your entries.
Entering the RFC Destination in the Customizing Table
Call transaction SM30.
Enter the table name IPCDEST in the Table/View field and choose
Maintain .
Make an entry in the table with the following values:
Field Parameter :
SAPCRM_SPC_ITS
Field Destination : name of the RFC destination you have created (for example, IPC_050).

Result
The IPC is now linked to the Vehicle Management System and you can use it to configure vehicles.

1.2 Vehicle IDoc VEHCLE01

Definition
The vehicle IDoc VEHCLE01 is part of VMS. It serves to transfer vehicle data between manufacturer and importer or between different sales organizations. It
can be an inbound or an outbound IDoc.
For more information, see the standard documentation

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 6

Processing of IDocs.

Use
The inbound IDoc serves mainly as a communication means between the manufacturer and yourself as importer. The manufacturer can confirm your vehicle
order via the IDoc and update the vehicle status ( in production , in transit etc.) regularly with current production data. To do this, VMS evaluates the
Customizing table for transaction OVELO5 ( Define External Status ): it finds an action and a plant for the organization channel and the external status. As soon as
the system performs this action, the vehicle is set to the internal status stored in the appropriate action matrix.
You can display inbound IDocs using the standard transactions WE02 or the VMS transaction VELOM
Status Monitor for Vehicle IDoc.
The outbound IDoc is linked to VMS message control (see VMS Customizing). As importer, you can send faxes, e-mails and IDocs containing the vehicle
data to subordinate or superior sales organizations using action MSSO. The system then uses the plant and the action to find an organization channel and an
external status in the above-named Customizing table and writes these to the IDoc. If the recipient of the IDoc also uses VMS, he/she can evaluate this data and
process it automatically using the same Customizing table in his/her own VMS.
You can display outbound IDocs using the standard transaction WE05.

Outbound and inbound IDocs use the same Customizing table (transaction OVELO5) and read it once forwards and once backwards. Please
ensure that the table only contains clear and precise entries. If the outbound IDoc finds ambiguous entries, the data is sent but it cannot be
processed any further on the receiving side and a warning message appears.

Structure
The vehicle IDoc VEHCLE01 contains the following segments:
E1VLCK1 vehicle identification: required segment, number 1 (organization channel, external status, vehicle ID, internal/external vehicle number, vehicle
identification number)
E1VLCK2 vehicle data: optional segment, number 1 (vehicle model, plant, storage location, vendor, customer, end customer, visibility, availability,
address, production date, delivery date, vehicle use, sales campaign, gross list price, currency, vehicle search area, original ordering party, access
authorization)
E1VLCC1 configuration data: optional segment, number 1
E1VLCC2 instance data: optional segment, number n
E1VLCC3 partof data: optional segment, number n
E1VLCC4 characteristic value assignment: optional segment, number n
E1VLCA1 additional data: optional segment, number n (qualifier, qualifier characteristics)
E1EDS01 general totals segment: required segment, number 1
The fields Organization channel , External status and one of the vehicle numbers must be filled in segment E1VLCK1 for inbound IDocs and in segment
E1VLCK2 the field Vehicle model (only for Create actions).
The inbound vehicle IDoc has message type VLCCPO ( vehicle: purchase order confirmation/status tracking ), the outbound vehicle IDoc has message type
VLCVDT ( vehicle detail data ).

Example for an Inbound IDoc

As importer, you receive a purchase order confirmation that contains a small configuration change from manufacturer X (for example, the vehicle is a different color
than in the purchase order). The external status is Purchase order confirmed with change . In Customizing you have assigned the action Change purchase order
to the external status Purchase order confirmed with change and the organization channel XY. As soon as you confirm the configuration change, the system
performs this action. The vehicle receives the internal status Purchase order confirmed and the purchase order is changed accordingly.

1.2.1 Calling the Status Monitor for the Vehicle IDoc

Use
You can use the status monitor to display incoming vehicle IDocs. You can also see exactly which vehicle data has changed and you can accept or reject the
changes manually.

You can display logs for the status monitor with transaction VELOP01 or by choosing
You can delete the logs with transaction SLG2 (object VMS_IDOC).

Hist. Logs in the selection screen of the status monitor.

Procedure
Choose transaction VELOM Status Monitor for Vehicle IDoc .
The selection screen for the status monitor appears.
Choose an organization channel.
The values proposed when you choose F4 (combination of organization channel and external status) come from the Customizing transaction OVELO5 Define
External Status .
Choose a period of time, one or more IDoc statuses and further selection parameters, if required.
Only the following IDoc statuses are possible:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 6

51 (IDoc has not been posted since an error occurred; red traffic lights)
52 (IDoc has not been posted since changes have been made that must be confirmed; amber traffic lights)
53 (IDoc has been posted; green traffic lights)
Select the field Execute Immediately if you want the action (that has been assigned to the external status of a vehicle) to be performed straightaway. The
IDoc status 52 changes to 53. Select this field only if you are sure that you want to accept all the changes.
Deselect the field if you want to trigger this process manually by selecting the desired IDocs from the list and choosing
Choose

Accept .

A screen displaying the selected IDocs appears. You see different data in different colors for each IDoc with status 51 or 52: the pale area displays configuration
characteristics, the yellow area the qualifiers and the blue area the vehicle data. Only the new or the changed data is displayed; new and old values are
displayed next to one another so that you can compare them.
Select the desired IDocs with status 52 and accept the IDoc data with

Accept or reject the data with

Reject .

You can branch to the general IDoc monitor by double clicking on the IDoc number (transaction BD87) - all the IDoc processing functions are then
at your disposal.

Result
If you accept the IDocs, the action that is assigned to the external status of the vehicles is performed, and the vehicles are set to their internal status that is in the
appropriate action matrix. Vehicle data and documents are changed appropriately.
Irrespective of whether you have accepted or rejected the changes, the IDoc status changes from 52 to 53.

If you are sure that vehicle data in IDocs is to be accepted automatically as soon as the IDoc takes effect, you can define this directly in
Customizing (transaction OVELO5).

1.3 Connection to SAP Business Information Warehouse (BW)

Use
The SAP Business Information Warehouse allows you to analyze and evaluate data from operative R/3 applications, from any other business applications and
from external data sources such as databases, online services and the Internet. You use queries to analyze the data. Queries target specific views on the data
according to the individual issues in question. Every authorized person can use these queries to access both historical and current data in any desired
summarized or detailed form.
The connection of VMS to SAP Business Information Warehouse allows you to evaluate vehicle data according to different business issues and in any depth you
wish.
You can find further information in the standard documentation for the SAP Business Information Warehouse.

Features
Three VMS extractors are available on the side of the DI system. You can use these extractors independently of one another to extract the following data to the
appropriate DataSources and this make it available to the BW system for evaluation and analysis purposes:
The most important vehicle attributes (all vehicle numbers, vehicle model, supplier, customer, action control, primary and secondary stati, availability
status, gross list price, planned production date, planned delivery date etc.) (extractor VELO26_VLC_BW_GA)
The configuration characteristics of the vehicles, for example, color, engine, special features etc. (extractor VELO26_VLC_BW_GC) and the texts for
the appropriate values (extractor VELO26_VLC_BW_GCT)
You can map the special VMS configuration characteristics to BW characteristics. A class with characteristics is assigned to each vehicle model
in VMS; each characteristic has a specific number of possible characteristic values (see also:
Creating Vehicle Configurations). So that you can compare the characteristics of vehicles, it is helpful to map these specific characteristics dependent on vehicle
model to more general vehicle-independent characteristics (example: the vehicle-dependent VMS characteristics Exterior color_SAPCar and Exterior
color_SAPRover can be mapped to the BW characteristic Exterior color ). This BW characteristic then contains all possible characteristic values.
In this way, queries for BW characteristics are possible across all vehicle models (example: how many red vehicles have I sold in the last two months?) A further
advantage of mapping is that you can control which and how many characteristics should be relevant to BW. As a result, BW reporting is more efficient.
Queries can relate to vehicle data and configuration characteristics and can, for example, answer the following question: how many 90 horsepower vehicles of
vehicle model SAPCar have I, as importer, sold to dealer Smith within a specific period of time?

Activities
Map VMS configuration characteristics to BW characteristics (transaction VELOBWC Assign Class Characteristics to BW Characteristics ).
Create your own queries in BW.

Example
Here are some possible questions you could ask when you create new VMS queries:
How many vehicles with which configuration characteristics have I sold to dealer Smith? Such a question provides valuable data for a new sales forecast.
Which dealers have I sold the most vehicles to?
From which vehicle model have I sold the most vehicles?
How popular is air-conditioning, heating under the seats etc.?

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 5 of 6

1.4 Connection to Supply Chain Event Management (SCEM)

This functionality only has the status "Controlled Availability" (CA). In other words, you can only use it after consultation with SAP.

Use
Supply Chain Event Management (SCEM) principally allows you to define specific expected events for a business process (for example, transport) or business
object (for example, sales order) and use rules to define which actions (for example, change of status) should be connected to which event. At the same time you
can define planned, baseline dates for the events. If the appropriate event is then confirmed with an actual time for this process or object, the status is changed,
for example, and the planned scheduling for the following events is updated. In this way you can monitor each step of the logistics chain, refer to critical situations
with alerts and be proactive by sending the appropriate messages.
Above all, the connection between VMS and Supply Chain Event Management allows you to log and constantly monitor actions that you call in VMS with
reference to specific vehicles. This means that you can always provide your dealers with the latest information on process being made in production and transport,
track down delays and initiate appropriate measures in good time.

Prerequisites
You have installed the plug-in that connects the DI system to the SCEM system. This plug-in contains several transactions for SCEM administrators. You
can use these transactions to set up the connection between the two systems. Together with the plug-in, the VMS functions named below are delivered in a
condensed form.

If you have not installed the plug-in, the following functions are not available to you.
You have installed an SCEM system.

Features
Customizing
In Customizing you can define for each action whether it should be relevant to SCEM or not. If you define an action as relevant to SCEM, an event handler is
created for the vehicle for which you perform the action. If an event handler already exists for this vehicle, the information parameters for this event handler are
updated. An event handler is the SCEM version of the vehicle as application object in DI, which allows you to process confirmed events for this application object
in SCEM.
Action EMMI
Action

Description

Prerequisites

What does the action do?

Notes

EMMI

Report events for SCEM

An event handler for the

vehicle must exist in SCEM.

Reports events for the event

handler in SCEM, which is
assigned to a vehicle in DI.

This action is normally

performed in SCEM (using a
transaction or scanner) or
started via a BAPI/IDoc.

You can find further information under

Actions.
Displaying SCEM Information
You call SCEM information for a vehicle via transaction VELO, tab page Detail and then pushbutton
following tab pages then appears:

SCEM under Vehicle Data . A screen with the

Expected Events
: list of the expected events defined in SCEM for the application object vehicle with planned and actual scheduling. The planned scheduling is based on
the planned production date. Events that have already been reported are shown by the icon .
Event Messages
: list of the events already reported for this vehicle.
Error Messages
: list of the error messages that have occurred in connection with the event messages.
Status Display
: list of the possible stati defined in SCEM with the status values as they are due to the events that have been reported for this vehicle.
Searching for SCEM Information
You have two more search views at your disposal in the vehicle search when you are searching for SCEM information:
Event Manager: search for vehicles with SCEM parameters such as application object type, set of rules, status profile, profile of expected events,
administrative data and transport data.

Messages and status

: search for vehicles with a specific SCEM status, specific event or error messages
You can find further information under Vehicle Search.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 6 of 6