Integration Guide - SAP Help Portal

INTERNAL

Integration Guide SAP Digital Vehicle Hub with SAP Vehicle Management System

2

Typographic Conventions

Type Style Description Example Words or characters quoted from the screen. These include field names, screen titles,

pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents.

Example Emphasized words or expressions. EXAMPLE Technical names of system objects. These include report names, program names, transaction

codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .

3

Document History

Version Date Change 1.0 (2010) 2020-10-08 Initial published version 1.1 (2102) 2021-02-21 Integration is enhanced with standard integration flows (for example, replication of

attributes, replication of status, replication of location and replication of equipment templates from SAP Vehicle Management System to SAP Digital Vehicle Hub)

2.0 (2105) 2021-05-21 SAP S/4HANA release relevant details added in required sections 2108 2021-08-22 No changes 2111 2021-11-14 No changes 2202 2022-02-20 No changes 2205 2022-05-22 No changes

TABLE OF CONTENTS

1 INTEGRATION WITH DIGITAL VEHICLE HUB ...................................................... 6 1.1 About SAP Digital Vehicle Hub .............................................................................. 6 1.2 Basic Integration Process ...................................................................................... 6

2 PREREQUISITES ..................................................................................................... 8

3 INTEGRATION STEPS ............................................................................................. 9 3.1 Steps in SAP S/4 HANA .......................................................................................... 9 3.1.1 Define Logical System ............................................................................................ 9 3.1.2 Maintain Target System .......................................................................................... 9 3.1.2.1 SAP S/4HANA 2020 FPS01 ..................................................................................... 9 3.1.2.2 SAP S/4HANA 2020 FPS00 ..................................................................................... 9 3.1.3 Maintain Integration-Relevant Actions .................................................................. 9 3.1.4 Maintain Vehicle Model and SAP Digital Vehicle Hub Model Mapping ............ 10 3.1.4.1 SAP S/4HANA 2020 FPS01 ................................................................................... 10 3.1.4.2 SAP S/4HANA 2020 FPS00 ................................................................................... 10 3.1.5 Maintain Vehicle Attribute to SAP Digital Vehicle Hub Attributes Mapping .... 11 3.1.5.1 SAP S/4HANA 2020 FPS01 ................................................................................... 11 3.1.5.2 SAP S/4HANA 2020 FPS00 ................................................................................... 15 3.1.5.3 Search Helps .......................................................................................................... 17 3.1.5.4 Prefix Maintenance .................................................................................................. 18 3.1.6 Initial Load of Vehicles ......................................................................................... 19 3.1.7 Delta Load of Vehicles .......................................................................................... 19 3.1.8 Initial Load of Classification, Vehicle Location and Status .............................. 20 3.1.8.1 Vehicle Status ......................................................................................................... 20 3.1.8.2 Vehicle Location ..................................................................................................... 20 3.1.8.3 Characteristics ........................................................................................................ 20 3.1.8.4 Variant Class .......................................................................................................... 21 3.1.8.5 Call Back Mechanism to Update Attributes ............................................................ 21 3.2 Steps in SAP Cloud Integration ........................................................................... 21 3.2.1 Configure JMS Queue ........................................................................................... 21 3.2.2 Accessing Integration Content ............................................................................ 22 3.2.3 Maintaining User Credentials ............................................................................... 22 3.2.4 Configuring Integration Flows ............................................................................. 22 3.2.4.1 Replicate Vehicles from SAP S/4 HANA ................................................................ 22 3.2.4.2 Replicate Vehicles to SAP Digital Vehicle Hub ...................................................... 25 3.2.4.3 Replicate Vehicle Attributes from SAP S/4HANA .................................................. 28 3.2.4.4 Replicate Vehicle Attributes to SAP Digital Vehicle Hub........................................ 29 3.2.4.5 Replicate Vehicle Location from SAP S4HANA ...................................................... 33 3.2.4.6 Replicate Vehicle Location to SAP Digital Vehicle Hub ......................................... 34 3.2.4.7 Replicate Vehicle Source System Status from SAP S4HANA ............................... 37 3.2.4.8 Replicate Vehicle Source System Status to SAP Digital Vehicle Hub ................... 38 3.2.4.9 Replicate Vehicle Templates from SAP S4HANA .................................................. 41 3.2.4.10 Replicate Vehicle Templates to SAP Digital Vehicle Hub ....................................... 43

3.3 Error Mail Notification ........................................................................................... 47 3.4 Troubleshooting and Log ..................................................................................... 47 3.4.1 Context ................................................................................................................... 47 3.4.2 Procedure ............................................................................................................... 48

4 APPENDIX .............................................................................................................. 49

1 INTEGRATION WITH DIGITAL VEHICLE HUB

This integration guide provides configuration steps to integrate the Vehicle Management System on SAP S/4 HANA with SAP Digital Vehicle Hub on SAP Business Technology Platform.

For more information about the integration of Vehicle Management System with SAP Digital Vehicle Hub, see Integration to SAP Digital Vehicle Hub.

1.1 About SAP Digital Vehicle Hub

SAP Digital Vehicle Hub represents the digital twin of a vehicle, which interacts seamlessly with the automotive and mobility value chain in the cloud. It serves as a central registry for managing all types of vehicle-related master, transactional, and usage data. The information is built and shared between internal and external business partners to enable and handle collaborative business models and processes along the automotive and mobility value chain.

The aim of SAP Digital Vehicle Hub is to enable a central repository for vehicles and vehicle-related information. This repository acts as a foundation for searching and analyzing the entire vehicle fleet.

SAP Digital Vehicle Hub serves as a scalable platform to store vehicle information, using APIs to connect to various systems like legacy systems, distributor systems, dealer systems or any other third-party systems.

As a network hub, SAP Digital Vehicle Hub enables the sharing of vehicle data between OEMs, distributors, dealers, third-party service providers and all other network parties, based on an extensive authorization concept.

1.2 Basic Integration Process

The integration process includes replication of the following information from Vehicle Management System to SAP Digital Vehicle Hub:

1. Replication of vehicle information and related information such as:

o Vehicle configuration

o Vehicle statuses

o Vehicle purchase orders

o Vehicle sales orders

o Vehicle incoming and outgoing invoices

2. Replication of classification information such as:

o Characteristics

o Variant Class

3. Replication of vehicle location information

4. Replication of vehicle status information

For SAP S/4HANA 2020 FPS00 release, the following integration flows are available:

Vehicle replication Replicate vehicle(s) from SAP S/4 HANA Vehicle Management System to SAP Cloud Integration

JMS Queue. Transfer vehicle(s) from SAP Cloud Integration JMS Queue to SAP Digital Vehicle Hub

For SAP S/4HANA 2020 FPS01 release, the following integration flows are available:

Characteristic Replication Replicate characteristic(s) from SAP S4 HANA Vehicle Management System to SAP Cloud

Integration JMS Queue Transfer characteristic(s) from SAP Cloud Integration JMS Queue to SAP Digital Vehicle Hub

Variant Class Replication Replicate variant classes from SAP S4 HANA Vehicle Management System to SAP Cloud

Integration JMS Queue Transfer variant classes from SAP Cloud Integration JMS Queue to SAP Digital Vehicle Hub

Vehicle Location Replication Replicate vehicle location(s) from SAP S4 HANA Vehicle Management System to SAP Cloud

Integration JMS Queue Transfer vehicle location(s) from SAP Cloud Integration JMS Queue to SAP Digital Vehicle Hub

Vehicle Status Replication Replicate vehicle status from SAP S4 HANA Vehicle Management System to SAP Cloud

Integration JMS Queue Transfer vehicle status from SAP Cloud Integration JMS Queue to SAP Digital Vehicle Hub

Usage of JMS in SAP Business Technology Platform Integration:

The integration process uses the JMS adapter in SAP Cloud Integration for message processing via queues and retry mechanisms when errors occur. For more information, see JMS Adapter.

2 PREREQUISITES

The prerequisites for the integration are as follows: SAP S/4HANA

You have an SAP S/4HANA on-premise 2020 system or higher. You have implemented the following SAP Notes:

Component Release Note Number IS-A-VMS S/4HANA FPS01 3031622 IS-A-VMS S/4HANA FPS01 3029021 IS-A-VMS S/4HANA FPS01 3029007 IS-A-VMS S/4HANA FPS01 3028656 IS-A-VMS S/4HANA FPS01 3020975 IS-A-VMS S/4HANA FPS01 3010251 IS-A-VMS S/4HANA FPS01 3008441 IS-A-VMS S/4HANA FPS01 3046668 IS-A-VMS S/4HANA FPS01 3009008 IS-A-VMS S/4HANA FPS01 2993289 IS-A-VMS S/4HANA FPS00 2949130 IS-A-VMS S/4HANA FPS00 2958457 IS-A-VMS S/4HANA FPS00 2957704 IS-A-VMS S/4HANA FPS00 2969438 IS-A-VMS S/4HANA FPS00 2975474

SAP Cloud Integration You have subscribed to SAP Cloud Integration.

SAP Digital Vehicle Hub You have subscribed to SAP Digital Vehicle Hub application. For SAP S/4HANA 2020 FPS00 release, the following information must already exist in SAP

Digital Vehicle Hub during vehicle replication:

o Model: This is the model of a vehicle. If model information is sent from Vehicle Management System, then the corresponding model must exist in SAP Digital Vehicle Hub.

o Equipment template and Attributes: This corresponds to the variant class and associated characteristics in Vehicle Management System. If custom characteristics are sent from Vehicle Management System, then the corresponding equipment template and associated attributes must exist in SAP Digital Vehicle Hub.

o Location: This is the location for a vehicle. If location information is sent from Vehicle Management System, then the corresponding location must exit in SAP Digital Vehicle Hub.

o Status Attributes: This corresponds to the statuses associated with a vehicle in Vehicle Management System. If status information is sent from Vehicle Management System, then the corresponding attributes and associated codelists (with status values) must exist in SAP Digital Vehicle Hub.

3 INTEGRATION STEPS

3.1 Steps in SAP S/4 HANA

3.1.1 Define Logical System

Define the logical system for SAP Cloud Integration by entering an RFC destination of type G. For more information, see Maintaining RFC Destinations.

Note:

o While creating the RFC destination, maintain only the host information. Do not use the prefix. You can use the path prefix only to test the connection.

o For SAP S/4HANA 2020 FPS00, maintain the path prefix information as: /vehicle.

o For SAP S/4HANA 2020 FPS01, do not maintain any path prefix information. You can use the path prefix only to test the connection.

3.1.2 Maintain Target System

3.1.2.1 SAP S/4HANA 2020 FPS01 Navigate to SPRO-> Logistic Execution-> Vehicle Management System-> Integration

with Digital Vehicle Hub-> General Settings-> Maintain SAP Business Technology Platform System Details

Choose Execute and enter the target system that you configured in the previous step. Choose Save to save your entries.

3.1.2.2 SAP S/4HANA 2020 FPS00 Navigate to SPRO-> Logistic Execution-> Vehicle Management System-> Integration

with Digital Vehicle Hub-> General Settings-> Maintain Target System

Choose Execute and enter the target system that you configured in the previous step. Choose Save to save your entries.

3.1.3 Maintain Integration-Relevant Actions

Navigate to SPRO-> Logistic Execution-> Vehicle Management System-> Integration with Digital Vehicle Hub-> General Settings-> Maintain Integration -relevant Actions

Maintain integration-relevant actions only for the delta load of vehicles. You set the following actions to Enable:

Example Action Action Description Enable CHCO Change Sales Order X CONF Confirm Purchase Order CREA Create Vehicle (Configurable) X

Actions that have been set to Enable can be performed using the transaction VELO. Save your entries and choose Execute. You can perform all these actions using the transaction

VELO.

3.1.4 Maintain Vehicle Model and SAP Digital Vehicle Hub Model Mapping

3.1.4.1 SAP S/4HANA 2020 FPS01

Navigate to SPRO-> SAP Reference IMG-> Logistic Execution-> Vehicle Management System-> Integration with Digital Vehicle Hub-> Integration with Digital Vehicle Hub-> Vehicle Transfer-> Maintain Vehicle Model to DVH Mapping.

Maintain Vehicle Model to SAP Digital Vehicle Hub Model. Vehicle Model refers to a material in Vehicle Management System and Digital Vehicle Hub Model refers to a model in SAP Digital Vehicle Hub.

Example Vehicle Model Digital Vehicle Hub Model Material_A Model_A Material_B Model_B

After defining your mapping, save the settings.

Note

o This is an optional activity which is required when a material in Vehicle Management System is sent as the model of a vehicle in SAP Digital Vehicle Hub.

o Only one vehicle model can be mapped to one SAP Digital Vehicle Hub model. The vehicle will be created in DVH, with the model maintained in SAP Digital Vehicle Hub Model section of the mapping.

o The model maintained in SAP Digital Vehicle Hub Model section of the mapping must already exist in SAP Digital Vehicle Hub.

3.1.4.2 SAP S/4HANA 2020 FPS00

Navigate to SPRO-> SAP Reference IMG-> Logistic Execution-> Vehicle Management System-> Integration with Digital Vehicle Hub-> Integration with Digital Vehicle Hub-> Vehicle Transfer-> Maintain Vehicle Model to DVH Model.


Example Vehicle Model Digital Vehicle Hub Model Material_A Model_A Material_B Model_B

After defining your mapping, save the settings.

Note

o This is an optional activity which is required when a material in Vehicle Management System is sent as the model of a vehicle in SAP Digital Vehicle Hub.

o Only one vehicle model can be mapped to one SAP Digital Vehicle Hub model. The vehicle will be created in DVH, with the model maintained in SAP Digital Vehicle Hub Model section of the mapping.

o The model maintained in SAP Digital Vehicle Hub Model section of the mapping must already exist in SAP Digital Vehicle Hub.

3.1.5 Maintain Vehicle Attribute to SAP Digital Vehicle Hub Attributes Mapping

3.1.5.1 SAP S/4HANA 2020 FPS01

Navigate to SPRO-> Logistic Execution-> Vehicle Management System-> Integration with Digital Vehicle Hub-> Vehicle Transfer-> Maintain Vehicle Attribute Mapping with DVH Attributes.

This view will have separate sections to maintain configuration for:

o Vehicle Model to Target Template Mapping and

o Vehicle Status

3.1.5.1.1 Maintain Vehicle Model to Target Template Mapping


Note o This is a mandatory activity and is required to create a vehicle in SAP Digital Vehicle Hub.

o The target equipment template must already exist in SAP Digital Vehicle Hub.

o One vehicle model can be mapped to ‘N’ number of target templates.

Example Vehicle Model Digital Vehicle Hub Model Material_A DVH_ET_VEHICLE_SPECIFICATION Material_B CUSTOM_TEMPLATE

Consider that Material A has the following two classes:

Class A

Class B Separate sections for standard template attributes and custom template attributes are available for

the view Vehicle Model to Equipment Template Mapping. For a specific mapping entry, select any view from the parent view Vehicle Model to Equipment

Template Mapping.

Standard Template Attributes

You can maintain the mapping between attributes of Vehicle Management System and standard pre-delivered attributes of SAP Digital Vehicle Hub.

Target Template

Source Object

Source object Name

Source Attribute

Target Attribute Group

Target Attribute

Template_A Variant Class

Class_A Characteristic_A StatusGroup DVH_EXTERIOR_COLOR




Class_A Characteristic_A StatusGroup DVH_RIM_SIZE


Class_A Characteristic_A StatusGroup DVH_ODOMETER_READING




Class_A Characteristic_A StatusGroup DVH_INTERIOR_COLOR

Suppose DVH_ET_VEHICLE_SPECIFICATION is the standard pre-delivered equipment template, if you choose Source Object as Variant Class, then Source Object Name would be class name. Maintain a Source Attribute which is the characteristic of a class and the corresponding Target Attribute of the standard pre-delivered equipment template.

Search help for Source Attribute will show all the characteristics of the class and search help for Target Attribute will show all attributes associated with the standard pre-delivered equipment template.

To enable search helps for Target Attribute, perform the activities mentioned in section 3.1.5.3

Note

The following are the standard SAP artifacts provided with SAP Digital Vehicle Hub that corresponds to the target template, group and attributes.

Equipment Template Attribute Group Attribute DVH_ET_VEHICLE_SPECIFICATION

DVH_AG_VEHICLE_SPECIFICATION

DVH_INTERIOR_COLOR Interior Color DVH_EXTERIOR_COLOR Exterior Color DVH_UPHOLSTERY_COLOR Upholstery Color DVH_UPHOLSTERY Upholstery DVH_USED_VEHICLE Used Vehicle DVH_ODOMETER_READING

Odometer Reading DVH_HOLOLOGATION_NUMBER Homologation Number DVH_RIM_SIZE Rim Size Front DVH_WHEEL_TYPE Wheel Type DVH_TIRE_SIZE Tire Size Front DVH_TIRE_SIZE Tire Size Rear DVH_GEAR_BOX Gear Box DVH_RIM_SIZE_REAR Rim Size Rear DVH_STEERING TYPE Steering Type

Custom Template Attributes:

You can maintain the mapping between attributes of Vehicle Management System and user created attributes of SAP Digital Vehicle Hub.

Target Template Source Object

Source object Name

Source Attribute


Target Attribute

CUSTOM_TEMPLATE Variant Class

Class_B Characteristic _W

CUST_ATTR_GRP CUST_ATTRIBUTE

Suppose, CUSTOM_TEMPLATE is the custom created equipment template. If you choose Source

Object as Variant Class, then Source Object Name would be class name. Maintain a Source Attribute which is the characteristic of a class and the corresponding Target Attribute of the custom created equipment template.

Search help for Source Attribute will show all characteristics from the corresponding Source Object which is the class in VMS and search help for Target Template, Target Attribute Group, Target Attribute will show the corresponding artifacts from SAP Digital Vehicle Hub.

To enable search helps for Target columns, perform the activities mentioned in section 3.1.5.3

Note

o Target Template refers to the equipment templates (standard and custom) created in SAP Digital Vehicle Hub.

o Source Object refers to a database table or variant class

o Source Object Name will display either the name of the variant class or the database table depending on the choice.

o Source Attribute refers to characteristics of the class or field name of the database table.

o Target Attribute Group signifies the attribute group ID created in SAP Digital Vehicle Hub

o Target Attribute signifies the attribute ID created in SAP Digital Vehicle Hub

3.1.5.1.2 Vehicle Status

A vehicle in Vehicle Management System has two statuses in parallel: a primary status and a secondary status. You define the status values in Vehicle Management System configuration.

Both the statuses of a vehicle can be transferred to SAP Digital Vehicle Hub correspondingly. To enable the status transfer, the entries corresponding to the primary status (MMSTA) and secondary status (SDSTA) must be entered as follows (example values shown):

Target Template Source Object

Source Object Name

Source Attributes


Target Attribute

CUSTOM_TEMPLATE

Vehicle VLCVEHICLE

MMSTA StatusGroup

VMS_PRIMARY_STATUS

CUSTOM_TEMPLATE

Vehicle VLCVEHICLE

SDSTA StatusGroup

VMS_PRIMARY_STATUS

Note

o The target template, the target attribute group and the target attribute must be defined in SAP Digital Vehicle Hub.

o For the status values, a code list must be created in SAP Digital Vehicle Hub which is assigned to the two attributes for primary and secondary status.

Example

For primary status attribute defined in SAP Digital Vehicle Hub:

Example

For status code list defined in SAP Digital Vehicle Hub:

3.1.5.2 SAP S/4HANA 2020 FPS00

Navigate to SPRO-> SAP Reference IMG -> Logistic Execution-> Vehicle Management System-> Integration with Digital Vehicle Hub-> Integration with Digital Vehicle Hub -> Vehicle Transfer-> Maintain Vehicle Attribute Mapping with DVH Attributes.

This view will have separate sections to maintain configuration for:

o Vehicle Model to Target Template Mapping and

o Vehicle Status

Maintain Vehicle Model and Target Template mapping in the maintenance view. Vehicle Model refers to a material in Vehicle Management System and Target Template refers to an equipment template in SAP Digital Vehicle Hub.

Note o This is a mandatory activity and is required to create a vehicle in SAP Digital Vehicle Hub.

o The target equipment template must already exist in SAP Digital Vehicle Hub.

o One vehicle model can be mapped to ‘N’ number of target templates.

Example Vehicle Model Target Template Material_A DVH_ET_VEHICLE_SPECIFICATION Material_B CUSTOM_TEMPLATE

Consider that Material A has the following two classes:

Class A

Class B A single section for standard template attributes and custom template attributes is available for the

view Vehicle Model to Equipment Template Mapping.

Note

o This section can also be used to maintain the mapping for vehicle status.

o The target template, the target attribute group and the target attribute must be defined in SAP Digital Vehicle Hub.

o For the status values, a code list must be created in SAP Digital Vehicle Hub which is assigned to the two attributes for primary and secondary status.

For a specific mapping entry, select the view Vehicle Model to Equipment Template Mapping. The configuration can be maintained as shown below:

Example Target Template Sour

ce Object

Source Object Name

Source Attribute

Target Attribute group

Target Attribute

DVH_ET_VEHICLE_SPECIFICATION

Variant Class

Class_A EXT_COLOR


DVH_EXTERIOR_COLOR


Variant Class

Class_A INT_COLOR


DVH_INTERIOR_COLOR


Variant Class

Class_A RIM_SIZE


DVH_RIM_SIZE

CUSTOM_TEMPLATE Variant Class

Class_B VMS_CUST_C

CUST_GROUP CUST_ATTRIBUTE

CUSTOM_TEMPLATE Vehicle

VLCVEHICLE

MMSTA StatusGroup VMS_PRIMARY_STATUS

CUSTOM_TEMPLATE Vehicle

VLCVEHICLE

SDSTA StatusGroup VMS_SECONDARY_STATUS

Note

o Target Template refers to the equipment templates (standard and custom) created in SAP Digital Vehicle Hub.

o Source Object refers to a database table or variant class

o Source Object Name will display either the name of the variant class or the database table depending on the choice.

o Source Attribute refers to characteristics of the class or field name of the database table.

o Target Attribute Group signifies the attribute group ID created in SAP Digital Vehicle Hub.

o Target Attribute signifies the attribute ID created in SAP Digital Vehicle Hub.

3.1.5.3 Search Helps

Note This is an optional activity and is enabled from SAP S/4HANA 2020 FPS01 release.

You can enable entries in the mapping table with search helps. When you select search help for Target Template, Target Attribute Group and Target

Attribute in custom template mapping view and status mapping view, the corresponding artifacts from SAP Digital Vehicle Hub will be displayed.

To enable search helps, the following activities must be performed:

3.1.5.3.1 Create Logical System

Create a new logical system corresponding to SAP Digital Vehicle Hub. The host details of the logical system will point to the resource URL for accessing equipment templates, attribute groups and attributes from SAP Digital Vehicle Hub.

You can find the URL from the service key instance by navigating from Subaccount -> Spaces -> Service Instances -> (select relevant service instance) -> Service Keys -> (select relevant service key)

Client Credentials Parameters Application URL endpoints.ain-service

For more information, see Accessing APIs of SAP Intelligent Asset Management Solutions.

3.1.5.3.2 Create OAuth 2.0 Client Profile and Configuration

Create OAuth2.0 client profile from SE80 as follows: Start the object navigator (transaction SE80). Choose Development Object in the dropdown list. To create a development object in the SAP namespace, choose Create OAuth 2.0 Client

Profile in the context menu of the object name. Enter the object name in the Client Profile field of the popup. For example,

‘ZOAUTH_CLIENT_PROFILE’. Choose the type of service provider as HANA_CLOUD_PLATFORM. The Scope section is optional. Activate the profile.

Create OAuth2.0 client as follows: Navigate to OA2C_CONFIG transaction to configure the OAuth2.0. Choose Create.

Select ZOAUTH_CLIENT_PROFILE as the OAuth2.0 Client Profile and provide the Client ID. Maintain the Client Secret. Provide the Token Endpoint. Enter the Client Authentication as Basic, Resource Access Authentication as Header Field and

select grant type as Client Credentials. Choose Save. The OAuth2.0 configuration name is EXAMPLE_OAUTH_CLIENT_PROFILE

Note

o To proceed with the configuration steps, ensure that OAuth 2.0 Client ID, Client Secret, Token endpoint are available, as these are mandatory.

o The service key instance can be accessed by navigating from the BTP Subaccount -> Spaces -> Service Instances -> (select relevant service instance) -> Service Keys ->

(select relevant service key).

Client Credentials Parameters Client ID uaa.clientid Client Secret uaa.cleintsecret Token URL uaa.url+'oauth/token'

For more information, see Creating an OAuth Client Profile in the AS ABAP and Configuring an OAuth 2.0 Client in the AS ABAP.

3.1.5.3.3 Maintain Target System for SAP Digital Vehicle Hub

Navigate to SPRO-> SAP Reference IMG-> Logistic Execution-> Vehicle Management System-> Integration with SAP Digital Vehicle Hub-> General Settings-> Maintain Target System for SAP Digital Vehicle Hub.

3.1.5.4 Prefix Maintenance

Note o This is an optional activity and is enabled from SAP S/4HANA 2020 FPS01 release.

o You can maintain the prefix, suffix, and separator for Attribute, Code-list, Attribute Group, Equipment Template, Model Template, Location and Model. You can also select the object type from the drop-down menu.

o Navigate to SPRO-> SAP Reference IMG-> Logistic Execution-> Vehicle Management System-> Integration with SAP Digital Vehicle Hub->General Setting->Define SAP

Digital Vehicle Hub Name.

Note

o Object type, Model Template, and Models are currently not supported in Vehicle Management System. The ‘-’ and ‘_’ are the supported separators as per SAP Asset Intelligence Network guidelines. Prefix and suffix support any combination of a-z,0-9,A-Z,- and _. After maintaining the mapping, save the settings.

o Note that creating a vehicle of a given Vehicle Model will create an equipment on SAP Digital Vehicle Hub with reference to the mentioned Equipment Template(s). One vehicle model can be mapped to ‘N’ number of target template(s).

3.1.6 Initial Load of Vehicles

A customer who had purchased the license for SAP Digital Vehicle Hub will have the possibility to replicate the existing set of vehicles from SAP S/4 HANA Vehicle Management System to SAP Digital Vehicle Hub.

You can execute the report RVLC_DVH_INTEGRATION or use transaction VELO for the replication of vehicles.

The following selection criteria is available to select the vehicles to be replicated: Choose Execute in the top left-hand corner, and a screen appears with a message that vehicle was

successfully sent to SAP Digital Vehicle Hub.

Note

o The report is invoked only if a target system has been maintained and only for those vehicles whose material has been mapped to a valid equipment template. The report sends only those attributes and characteristics that are mapped as described in section 3.1.5.

o Execution of the report can be scheduled to run in the background.

3.1.7 Delta Load of Vehicles

Whenever a new vehicle is created or an existing vehicle is changed, the information needs to be replicated to SAP Digital Vehicle Hub.

You can use transaction VELO to perform delta load for this.

Prerequisite: See section 3.1.3 for information about defining integration-relevant actions. An action must be marked as an integration-relevant action so that the creation or update of a

vehicle via actions is replicated to SAP Digital Vehicle Hub. The replication process checks the existence of a valid target system before triggering the

replication. It will only be triggered for those vehicles whose material has been mapped to a valid equipment template. The action sends only those attributes and characteristics that have been mapped as described in section 3.1.6.

3.1.8 Initial Load of Classification, Vehicle Location and Status

Note

This feature is available from SAP S/4HANA 2020 FPS01 release for replication of classification information, vehicle location and status to SAP Digital Vehicle Hub.

To access the initial load report: Navigate to SPRO -> SAP Area Logistic -> Logistic Execution -> Vehicle Management

System -> Integration with SAP Digital Vehicle Hub -> Initial Load of Master Data to SAP Digital Vehicle Hub or

Use the transaction code VELOMI You can schedule the report execution to run in the background.

3.1.8.1 Vehicle Status

Choose the Vehicle Status radio button. Enter the necessary selection criteria. Choose the Execute button (on the top left corner).

3.1.8.2 Vehicle Location

Choose the Vehicle Location radio button. Enter the necessary selection criteria. Choose the Execute button (on the top left corner).

3.1.8.3 Characteristics

Choose the Characteristics radio button. Enter the necessary selection criteria. Choose the Execute button (on the top left corner).

3.1.8.4 Variant Class

All the characteristics (attributes) of the variant class should be available in SAP Digital Vehicle Hub, otherwise variant class replication will fail. This is a prerequisite.

Choose the Variant Class radio button. Enter the necessary selection criteria. Choose the Execute button (on the top left corner).

3.1.8.5 Call Back Mechanism to Update Attributes

All the characteristics (attributes) of the variant class should be available in SAP Digital Vehicle Hub,and must follow the naming format defined in the SAP S/4HANA system. Executing Update Vehicle Attribute:

Choose the Update Vehicle Attributes radio button. Enter the necessary selection criteria. Choose the Execute button (on the top left corner). On successful execution, system displays the

success message. To ensure that the vehicle replication considers the automatically created mapping, assign the

vehicle model to the newly created equipment template under SPRO-> Logistic Execution-> Vehicle Management System-> Integration with Digital Vehicle Hub-> Integration with Digital Vehicle Hub-> Vehicle Transfer-> Maintain Vehicle Attribute Mapping with SAP DVH Attributes.

3.2 Steps in SAP Cloud Integration

Prerequisites: You have the CONFIGURATION_DELETE or CONFIGURATION_EDIT role assigned to your user ID. You have access to the SAP Cloud Integration Web UI account. You have the link to access the Integration Flow.

3.2.1 Configure JMS Queue

To be able to use JMS queues for storing messages, you first need to activate the message broker for your cloud integration tenant. If you have an Enterprise Edition license you can do this for your tenant in Cloud Integration Provisioning via Provision Broker. You can then see the active message broker and its details. You can now start using the JMS adapter to configure your scenario.

This is described in detail in the blog ‘Activating and Managing Enterprise Messaging Capabilities’. For more information about JMS Adapters, see JMS Adapter.

3.2.2 Accessing Integration Content

Log on to your SAP Business Technology Platform Integration Web UI. On the SAP Business Technology Platform Integration landing page, choose Discover. Choose the package SAP S/4 HANA Integration with SAP Digital Vehicle 2010. Choose Copy. Choose the Design tab from the side panel. Choose the copied package, navigate to the Artifacts tab. Choose Actions Deploy for all the

required artifacts that you want to establish an integration with. The Integration Flow is deployed to the SAP Business Technology Platform integration system.

To check the deployment status, choose the Monitor tab on the side panel and verify the data in the Manage Integration Content section.

3.2.3 Maintaining User Credentials

Log on to your SAP Business Technology Platform Integration Web UI. In the navigation tree, choose Overview. Choose the Security Material tile in the Manage Security section. Choose Add. Select OAuth2 Credentials. Specify the following fields in the Add OAuth2 Credential dialog box.

Property Value Name <preferred name> Grant Type Client Credentials Description <preferred description> Token Service URL <url from Service Key> Client ID <clientid from Service Key> Client Secret <clientsecret from Service Key> Client Authentication Send as Request Header

Note

o The service key creation for SAP Digital Vehicle Hub is a prerequisite for this step. For more information, see Creating Service Keys.

o Choose Deploy.

3.2.4 Configuring Integration Flows

Once you have access to the integration package, you must configure the externalized parameters and deploy them for the integration flows.

3.2.4.1 Replicate Vehicles from SAP S/4 HANA

Choose the integration flow and select the Configure option. The following parameters must be specified:

o Configure for sender SAP_S4HANA

Example

o Configure for receiver SAP_CPI

Example

o More configuration parameters for the type All Parameters

Example

o More configuration parameters for the type General Splitter

Example o More configuration parameters for the type Integration Process

Example o More configuration parameters for the type Integration Flow

Example

3.2.4.2 Replicate Vehicles to SAP Digital Vehicle Hub

Choose the integration flow and select the “Configure” option. The following parameters must be specified: o Configure for Sender SAP_CI

Example

o Configure for receiver SAP_DVH_VEHICLE_GET

Example

o Configure for receiver mail

Example

Note

An email is sent to the configured email IDs if error occurs during execution of the integration flow. The email contains details about the error.

o Configure for receiver SAP_DVH_VEHICLE

Example

o More configuration parameters for the type All Parameters

Example

Note

o The messages will remain in the JMS queue for manual retry. The message will be retained in queue in accordance to the configuration for the parameter Maximum_Error_Retry

o Messages from the JMS Queue are removed once the maximum number of automatic retries by JMS is exceeded as configured for the parameter Maximum_Error_Retry.

o If you require the messages to remain in the JMS queue for a manual retry, you can use a high value for the parameter Maximum_Error_Retry

o More configuration parameters for Type Route

Example

o More configuration parameters for the type Integration Process

Example o More configuration parameters for the type Integration Flow

Example

3.2.4.3 Replicate Vehicle Attributes from SAP S/4HANA

Choose the integration flow and select Configure. The following parameters must be specified:

o Configure for sender SAP_S4HANA

Example

o Configure for receiver SAP_CI

Example

o Configure for More All Parameters

Example

o Configure for More General Splitter

Example

3.2.4.4 Replicate Vehicle Attributes to SAP Digital Vehicle Hub

o Configure for sender SAP_CI

Example

o Configure for receiver SAP_DVH_CODELIST_GET

Example

o Configure for receiver Mail

Example

o Configure for receiver SAP_DVH_ATTRIBUTE_POST

Example

o Configure for receiver SAP_DVH

Example

o Configure for more Route

Example

o Configure for more All Parameter

Example

o Configure for more Local Integration Process

Example

3.2.4.5 Replicate Vehicle Location from SAP S4HANA o Configure for sender SAP_S4HANA

Example

o Configure for receiver SAP_CPI

Example

o Configure for More All Parameter

Example o Configure for More General Splitter

Example

3.2.4.6 Replicate Vehicle Location to SAP Digital Vehicle Hub o Configure for Sender SAP_CPI

Example

o Configure for Receiver SAP_DVH

Example

o Configure for Receiver Mail

Example


Example

o Configure for More Route

Example o Configure for More Local Integration Process

Example

3.2.4.7 Replicate Vehicle Source System Status from SAP S4HANA o Configure for Sender SAP_S4HANA

Example

o Configure for Receiver SAP_CPI

Example


Example

o Configure for More General Splitter

Example

3.2.4.8 Replicate Vehicle Source System Status to SAP Digital Vehicle Hub o Configure for Sender SAP_CPI

Example


Example

o Configure for Receiver SAP_DVH_CODELIST_GET

Example

o Configure for Receiver SAP_DVH_CODELIST_POST

Example o Configure for Receiver SAP_AIN

Example o Configure for More All Parameters

Example


Example o Configure for More Local Integration Process

Example

3.2.4.9 Replicate Vehicle Templates from SAP S4HANA o Configure for Sender SAP_S4HANA

Example

o Configure for Receiver SAP_CPI

Example o Configure for More All Parameter

Example o Configure for More General Splitter

Example

3.2.4.10 Replicate Vehicle Templates to SAP Digital Vehicle Hub o Configure for Sender SAP_CI

Example


Example


Example

o Configure for Receiver SAP_DVH_TEMPLATE_DELETE

Example o Configure for Receiver SAP_DVH_ATTRIBUTE_GROUP_POST

Example

o Configure for Receiver SAP_DVH_TEMPLATE_POST

Example

o Configure for Receiver SAP_DVH_TEMPLATE_GET

Example

o Configure for Receiver SAP_DVH_DELETE_ATTRIBUTE_GROUP_DELETE

Example

o Configure for Receiver SAP_DVH_ATTRIBUTE_GROUP_GET

Example

o Configure for Receiver SAP_DVH_TEMPLATE

Example


Example

o Configure for Receiver Mail_Invalid_Attribute

Example

3.3 Error Mail Notification

All integration flows in this integration package can send error mail notifications for errors that occur during process execution. A mail is sent to the configured email IDs as soon an error occurs during execution of the integration flow. The mail will contain the details of the error.

You can configure the SMTP server to be used and the email IDs for sending and receiving the error message in the mail adapter connected to the exception sub-process in each integration flow in the package.

3.4 Troubleshooting and Log

3.4.1 Context

In the SAP Business Cloud Integration web UI, you can analyze the deployed integration flows in the Monitoring section.

3.4.2 Procedure

To carry out the activity, open your SAP Cloud Integration tenant web UI, for example, https://<your SAP Business Technology Platform Integration tenant URL>/itspaces.

In the Tenant menu, choose Monitor, then Monitor Message Processing. On the Overview screen, choose the tile with the message status you wish to analyze. On the left, select the integration flow you wish to analyze. Access the Message Processing Log from the Log tabs.

49

4 APPENDIX

Caution

<Put your caution here>

Example

<Put your example here>

Note

<Put your note here>

Recommendation

<Put your recommendation here>

Syntax

<Put your syntax here>

www.sap.com/contactsap © 2021 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 or an SAP affiliate company. 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 or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.

Documents

Integration Guide - SAP Help Portal