You are on page 1of 18

PUBLIC

2018-03-21

Asset Intelligence Network Integration


Content

1 Asset Intelligence Network Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3


1.1 Configuration Guide for Asset Intelligence Network Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 AIN Navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Configuration Guide for AIN Navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
1.3 Linking EAM Technical Objects to AIN Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Configuration Guide for Linking EAM Technical Objects to AIN Models. . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 AIN Equipment Creation and Synchronization to EAM Technical Objects. . . . . . . . . . . . . . . . . . . . . . . . .8
Configuration Guide for AIN Equipment Creation and Synchronization. . . . . . . . . . . . . . . . . . . . . . . .9
1.5 Document Creation and Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Configuration Guide for Document Creation and Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6 Notification Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Configuration Guide for Notification Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.7 Work Order Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuration Guide for Work Order Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Asset Intelligence Network Integration


2 PUBLIC Content
1 Asset Intelligence Network Integration

The Asset Intelligence Network (AIN) product provides a collaborative network for manufacturers and customers.
You can set a manufacturer as your partner and can monitor its models and the statuses of the models.

Use

If you integrate AIN with the Enterprise Asset Management (EAM) product, you can directly reach the AIN platform
from EAM and integrate your technical objects with their details into AIN as well. This way, your technical objects
become part of the AIN global registry.

Features

● AIN navigation
● Linking of EAM technical objects to AIN models
● Document creation and synchronization
● AIN equipment creation and synchronization for EAM objects
● Notification replication
● Work order replication

Note
All features have their own configuration procedures which you need to execute before you can start to use
them. For more information about this, see the configuration guide in the description documentation.

For more information about Asset Intelligence Network, see SAP Asset Intelligence Network.

Asset Intelligence Network Integration


Asset Intelligence Network Integration PUBLIC 3
1.1 Configuration Guide for Asset Intelligence Network
Integration

To integrate Asset Intelligence Network with EAM, you need to create your own RFC connection, and make settings
in the technical and general configuration.

Procedure

1. Create a new RFC destination in transaction SM59.


a. Define the following parameters:
○ RFC Destination: AIN_CONNECTION
○ Connection Type: Select the G (HTTP Connection to External Server) option.
○ Host at Technical Settings Target System Settings : Provide your AIN system host details, for
example, <account_ID>.hana.ondemand.com.

Note
Optional: You can set up your RFC connection to use SSL certificates if you maintain the certificates in
the SAP system.

a. Optional: Enable the OAuth 2.0 protocol for the communication between the SAP ERP system and the AIN
system. In transaction SM30, provide the following in view AIN_V_TEC_CONFIG:
○ AIN_AUTHENTICATION_MODE: OAUTH
○ AIN_OAUTH_PROFILE: Provide the name of the OAuth 2.0 client profile which you created.

Note
You must execute the security configuration of Asset Intelligence Network as well if you wish to
enable authentication based on client certificate or the OAuth 2.0 protocol. You can find
information about this under SAP Cloud Platform Security Keystore Service Enabling Client
Certificate Authentication and SAP Cloud Platform Security OAuth 2.0 Service OAuth 2.0
Configuration .

2. In transaction SM30, provide your RFC configuration name in view AIN_V_TEC_CONFIG.


3. Maintain the AIN_SYSTEM_NAME parameter in the same view by entering the name of the system which has a
connection to AIN.

Results

You have successfully connected Asset Intelligence Network to EAM.

Asset Intelligence Network Integration


4 PUBLIC Asset Intelligence Network Integration
1.2 AIN Navigation

With the new features of the Find Technical Object application, you can navigate directly to the AIN platform and
check your technical object there. You can access the feature with the Maintenance Planner role.

Features

● You can filter the technical objects that are synchronized with Asset Intelligence Network (AIN). If you click
Adapt Filters in the Find Technical Object application and select More Filters under the Technical Object section
at the bottom, you can select the Technical Obj. Is Synchronized with AIN option and define the conditions of
the filter.
● You can display the synchronized technical objects in AIN. If you click a technical object link, you can see the
navigation URL which you have created, and you can navigate to AIN.

1.2.1 Configuration Guide for AIN Navigation

To use Asset Intelligence Network navigation, configure SAP Fiori Launchpad Designer.

Procedure

1. Launch SAP Fiori Launchpad Designer.


2. Search for the business catalog SAP_EAM_BC_AIN_INT.
3. Configure the target mapping in SAP Fiori Launchpad Designer on layer CUST.
a. Go to the Target Mappings option of the catalog and select the entry with the following settings: Semantic
Object: MaintenanceObject, Action: displayInAssetIntelNtwk.
b. Click the Configure button.
c. Change the URL part +INSERT_YOUR_AIN_FLP_URL+ to your own Fiori Launchpad access.
d. Delete the RemoveAfterURLSetup parameter.
e. Finally, save the target mapping.

Results

You have successfully configured Asset Intelligence Network navigation.

Asset Intelligence Network Integration


Asset Intelligence Network Integration PUBLIC 5
1.3 Linking EAM Technical Objects to AIN Models

With SAP GUI transactions, you can link EAM technical objects to AIN models.

Context

With the transactions AIN_MAPPER or SE38/SA38, you can execute the AIN_MODEL_MAPPER program. This
program determines the potential AIN model matches for the EAM objects. After this, you can select the AIN
model you need and create a link between the AIN model and the EAM object. Proceed as follows:

Procedure

1. Select Equipment or Functional Location as selection criterion.


2. Define the ID of the equipment or functional location. You can also optionally define further technical object
data.
3. Select Skip AIN-linked Objects if you want to exclude those technical objects which already have mappings to
an AIN model.
4. Select Matched based on Const. Type and define a construction type if you want to check potential matches
based on the construction type provided.
5. Select the row of the AIN model that you want to link to your EAM technical object.
6. Click the Link Model icon in the toolbar.

Note
You can also unlink this connection by clicking the Delink Model icon.

The program can search either based on construction type, or manufacturer and model number together. If
you do not select the above-mentioned construction type checkbox, the program executes your search based
on only the latter. If you select the search based on construction type, the program also attempts to find an
AIN model based on the manufacturer part number and the vendor name from the construction material. If
you search based on the manufacturer and model number, the match will be successful only in those cases
where at least the model number exists.

Asset Intelligence Network Integration


6 PUBLIC Asset Intelligence Network Integration
1.3.1 Configuration Guide for Linking EAM Technical Objects to
AIN Models

To display details of the AIN models linked to EAM technical objects, you need to create some classes and
characteristics.

Procedure

1. Create the SAP_AIN_01 characteristic with transaction CT04 (Create Characteristic).

○ Description: AIN: Model


○ Data Type: Select the Character Format option.
○ Number of Chars: 40
○ Value Assignment: Leave this on the Single Value option.
○ Case Sensitive: Select this option.
2. Create the SAP_AIN_02 characteristic with the same transaction.

○ Description: AIN: Manufacturer


○ Data Type: Select the Character Format option.
○ Number of Chars: 40
○ Value Assignment: Leave this on the Single Value option.
○ Case Sensitive: Select this option.

Note
We recommend that you create a characteristic group called SAP_AIN and allocate it to the AIN
characteristics. You can do this with the Customizing SAP Customizing Implementation Guide Product
Safety and Stewardship Basic Data and Tools Specification Management Specification Database
Structure Classification System Settings Characteristics Define Characteristic Groups . After
creating the characteristic group, you can select it in CT04 for Char. Group.

3. For the class types 002 Equipment and 003 Functional location, define a ZSAP_AIN class with transaction
CL01 (Create Class).

○ Description: SAP AIN class for linking EAM to AIN


○ Same classification: Leave this on the Do not check option.

Note
We recommend that you create a class group called SAP_AIN and allocate this to this class and to all future
AIN classes. You can do this with the Customizing SAP Customizing Implementation Guide Cross-
Application Components Classification System Classes Define Class Groups . After creating the
class group, you can select it in CL02 for Class group.

Asset Intelligence Network Integration


Asset Intelligence Network Integration PUBLIC 7
Note
If you cannot define the class as a class already exists for any of these class types, go to the Customizing
SAP Customizing Implementation Guide Logistics - General Product Lifecycle Management (PLM)
Classification Classes Maintain Object Types and Class Types and check the Multiple classification
function to enable multiple classes.

4. Assign the SAP_AIN_01 and SAP_AIN_02 characteristics to the ZSAP_AIN class under the Chars. tab.

Note
We recommend you to set all of your previously defined AIN characteristics as Not Ready for Input under
Addnl data Procedure for Value Assignment so these will not be available during the synchronization
process.

Results

You have successfully configured linking EAM technical objects to AIN models.

1.4 AIN Equipment Creation and Synchronization to EAM


Technical Objects

With SAP GUI transactions, you can create AIN equipments and synchronize them with EAM technical objects.

Importing AIN Model and AIN Equipment Templates


With the transaction SE38/SA38, you can execute the AIN_TEMPLATES_PULL program. This program imports AIN
model templates and equipment templates together with its belonging AIN attributes to EAM. You need to enter a
valid AIN template name and the system directly imports the template. After the system finishes the import
process, you can see the template in the configuration with transaction AIN_EQUI_CONFIG in Model Templates or
Equipment Templates. After importing the templates, you can map the EAM characteristics to the AIN attributes.

Creating and Synchronizing an Equipment


With the transaction AIN_EQUI_SYNC or SE38/SA38, you can execute the AIN_EQUIPMENT_MAPPER program.
With providing an EAM technical object name, you can create a new AIN equipment for this technical object or you
can link an existing AIN model and equipment. You can use the following options after selecting the proper row:

● Link Model: You can select an AIN model which you can link to the EAM technical object.
● Propose Equipment: You can have a list of matching AIN equipments for the EAM technical object either based
on the name of the technical object (INTERNALID option) or its manufacturer serial number (SERIALNUMBER
option).
● Link Equipment: You can link an EAM technical object to an existing AIN equipment.
● De-Link Equipment: You can unlink an EAM technical object to an existing AIN equipment.

Asset Intelligence Network Integration


8 PUBLIC Asset Intelligence Network Integration
● Create Equipment: You can create an AIN equipment from the selected EAM technical object with the same
name. This option is available for those EAM technical objects which have link to an AIN model.
● Create Equipment without Model: You can create an AIN equipment from the selected EAM technical object
with the same name. This option is available for those EAM technical objects which have no link to an AIN
model.
● Sync Data: You can synchronize the data between the two systems based on the mapping configurations. You
can check and set the mapping configurations in transaction SM30 with view AIN_V_EQ_HDR_MAP for the
equipment header and in transaction AIN_EQUI_CONFIG for characteristics. The system synchronizes the
field attributes, characteristics and the technical object/equipment hierarchy between the two systems.
● View Log: You can view your actions for equipment creation and data synchronization.

1.4.1 Configuration Guide for AIN Equipment Creation and


Synchronization

To be able to create and synchronize an AIN equipment, you must set the general and mapping configurations and
you need to create some classes and characteristics.

Procedure

1. Set the general configuration.

In transaction SM30, set the following for view AIN_V_GEN_CONFIG:


○ AIN_LEAN_EQUIPMENT: Setting whether you can create an AIN equipment without a model or not. If you
enter X, you will be able to create these equipments.
○ AIN_SYNC_HIERARCHY: Setting whether the system synchronizes the AIN equipment hierarchy with
EAM. If you enter X, you allow synchronization.
○ AIN_HIERARCHY_MASTER: Defining whether the system takes the AIN or the EAM hierarchy into account
during synchronization. The possible values are EAM and AIN.
○ AIN_EQUI_SOURCEBPROLE: Defining the business role of the AIN equipment (1 - For my operations, 2 -
For Service, 3 - For Customer).
○ AIN_EQUI_LIFECYCLE: Defining whether an AIN equipment is planned or actual (1 - Planned, 2 - Actual).
Check the mapping differences between the two systems at .
2. Set the mapping configuration.

In transaction SM30, search for the view AIN_V_EQ_HDR_MAP and define the mapping between AIN equipment
headers and EAM technical object fields. You can find a default mapping configuration which you can
personalize.

In transaction SM34 at view cluster AIN_VC_TMPL_MAP, or in transaction AIN_EQUI_CONFIG, define the


mapping between AIN equipment fields and EAM technical object fields.

Model Templates

You can map the AIN model template attributes to EAM equipment characteristics, EAM functional location
characteristics, and you can also provide a default AIN equipment template.

Asset Intelligence Network Integration


Asset Intelligence Network Integration PUBLIC 9
○ Equipment Characteristics Mapping: You can map AIN model attributes to EAM equipment characteristics.
This way, the system overwrites the defined EAM values to the AIN model values.
○ Functional Location Characteristics Mapping: You can map AIN model attributes to EAM functional
location characteristics. This way, the system overwrites the defined EAM values to the AIN model values.
○ Default Equipment Templates: You can define a default AIN equipment template for the AIN model
template. If you do not define a default equipment template, you will need to select the relevant AIN
equipment template when you copy from AIN.

Equipment Templates

You can map the AIN equipment template attributes to EAM equipment characteristics and EAM functional
location characteristics.
○ Equipment Characteristics Mapping: You can map AIN equipment template attributes to EAM equipment
characteristics. This way, the system overwrites the defined EAM values to the AIN equipment template
values if you select Owrite EAM, or it overwrites the AIN equipment template values to the defined EAM
values if you select Owrite AIN. You need to make this setting for each value separately.
○ Functional Location Characteristics Mapping: You can map AIN equipment template attributes to EAM
functional location characteristics. This way, the system overwrites the defined EAM values to the AIN
equipment template values if you select Owrite EAM, or it overwrites the AIN equipment template values
to the defined EAM values if you select Owrite AIN. You need to make this setting for each value separately.
3. Define the necessary characteristics.

Create the SAP_AIN_01, SAP_AIN_02 and also the SAP_AIN_03 characteristics with transaction CT04
(Create Characteristic). For this, see the Procedure section of Configuration Guide for Linking EAM Technical
Objects to AIN Models [page 7] for SAP_AIN_01 and SAP_AIN_02, and define the following for SAP_AIN_03:
○ Description: AIN: Equipment
○ Data Type: Select the Character Format option.
○ Number of Chars: 40
○ Value Assignment: Leave this on the Single Value option.
○ Case Sensitive: Select this option.
4. Define the ZSAP_AIN class.
a. Follow the instructions in the Prodecure section of Configuration Guide for Linking EAM Technical Objects
to AIN Models [page 7].
a. Assign the SAP_AIN_03 characteristic as well to the ZSAP_AIN class under the Chars. tab.

Results

You have successfully configured AIN equipment creation and synchronization.

Asset Intelligence Network Integration


10 PUBLIC Asset Intelligence Network Integration
1.5 Document Creation and Synchronization

With SAP GUI transactions, you can copy document attachments from AIN to EAM and EAM to AIN. You can run
this feature in the background as well.

You can use transactions AIN_DMS or SE38/SA38 to execute the AIN_DMS_PULL program. This program
synchronizes the AIN and EAM documents. If you select Equipment or Functional Location as selection criterium
and define the ID of the technical object, you can select from the following options:

● Pull Model Documents from AIN: The EAM technical object must contain a link to the AIN model (see Linking
EAM Technical Objects to AIN Models [page 6]). The program checks the documents attached to the model
and updates the EAM technical object with the delta. It may create new documents for the EAM technical
object, update or remove documents.
● Push Equipment Documents to AIN: The EAM technical object must contain a link to the AIN equipment. The
program checks the documents attached to the EAM technical object and updates the AIN equipment with
the delta. It may create new documents for the AIN equipment, update or remove documents.
● Pull Equipment Documents from AIN: The EAM technical object must contain a link to the AIN equipment. The
program checks the documents attached to the AIN equipment and updates the EAM technical object with
the delta. It may create new documents for the EAM technical object, update or remove documents.

If the document synchronization is successful, you see a Document Updated status. If no change has taken place,
you see the No changes to update status. You can also see whether the reason why the synchronization did not
take place is because the AIN and the EAM items are not linked.

The system stores both the AIN model and equipment documents in DMS DIR records and creates a DMS DIR
record for each AIN equipment and model. The system stores the document attachments linked to the DMS DIR
record and links the DMS DIR records to the EAM technical objects.

1.5.1 Configuration Guide for Document Creation and


Synchronization

To be able to create and synchronize AIN and EAM documents, you must define document types, set the general
configuration, and create some classes and characteristics.

Procedure

1. Optional:In the Customizing SAP Customizing Implementation Guide Cross-Application Components


Document Management Control Data Define Document Types , define two new document types: one for
AIN model and another for AIN equipment documents (for example, AIN and AEQ).

Step 1 is optional as you can use your existing document type to store both model and equipment documents.
If you wish to have a separate document type to store AIN model and equipment documents, you can create a
new one in the given Customizing.
Define document status

Asset Intelligence Network Integration


Asset Intelligence Network Integration PUBLIC 11
If you create new document types, we recommend you to add a default initial status Ifor the document type
and set it as released.
Define object links

You need to add the EQUI (Equipment Master) and the IFLOT (Functional Location) objects to your object list.
2. In transaction SM30, add configurations to the view AIN_V_GEN_CONFIG.
○ AIN_MODEL_DMS_TYPE: This is the DMS document type for the AIN model documents (for example, AIN).
○ AIN_EQUI_DMS_TYPE: This is the DMS document type for the AIN equipment documents (for example,
AEQ).
○ AIN_DMS_STORAGE_TYPE: This is the storage category for storing the AIN documents (for example,
DMS_C1_ST).
○ AIN_DEFAULT_LANGUAGE: This is the default language of creating a document in AIN (for example, en).
3. Define the necessary characteristics.

Create the SAP_AIN_01, SAP_AIN_02 and also the SAP_AIN_03 characteristics with transaction CT04
(Create Characteristic). For this, see the Procedure section of Configuration Guide for Linking EAM Technical
Objects to AIN Models [page 7] for SAP_AIN_01 and SAP_AIN_02, and define the following for SAP_AIN_03:
○ Description: AIN: Equipment
○ Data Type: Select the Character Format option.
○ Number of Chars: 40
○ Value Assignment: Leave this on the Single Value option.
○ Case Sensitive: Select this option.
4. For the class type 017 Document Management , define a ZSAP_AIN class with transaction CL01 (Create
Class).
a. Click the Create button.
b. Description: SAP AIN class for linking DMS rec to AIN
c. Same classification: Leave this on the Do not check option.

Note
We recommend that you create a class group called SAP_AIN and allocate this to this class and to all future
AIN classes. You can do this with the Customizing SAP Customizing Implementation Guide Cross-
Application Components Classification System Classes Define Class Groups . After creating the
class group, you can select it in CL02 for Class group.

Note
If you cannot define the class as a class already exists for any of these class types, go to the Maintain Object
Types and Class Types IMG activity at SAP Customizing Implementation Guide Logistics - General
Product Lifecycle Management (PLM) Classification Classes and check the Multiple classification
function to enable multiple classes.

Asset Intelligence Network Integration


12 PUBLIC Asset Intelligence Network Integration
Results

You have successfully configured document creation and synchronization.

1.6 Notification Replication

With SAP GUI transactions, you can push maintenance notifications from EAM to AIN and vice versa. You are
advised to run this feature in the background.

Replication from EAM to AIN

With the transactions AIN_NOTI_POST or SE38/SA38, you can execute the AIN_NOTIFICATION_POST program.

You need to define the related equipment of the maintenance notification, and also provide some filter values for
the maintenenace notification.

Replication from AIN to EAM

With the transactions AIN_NOTI_PULL or SE38/SA38, you can execute the AIN_NOTIFICATION_PULL program.
The program pulls those notifications from the SAP Cloud Platform which were initially created in AIN. You can
filter the notifications for creation date.

If you select an AIN notification attribute and click the Create Notifications button, you can replicate some of its
attributes into a new maintenance notification. The system displays the synchronization result in the selected row
and also stores it in the application log framework for the AIN_INT object and NOTI subobject. The newly created
maintenance notification has the initial status OSNO (Outstanding notification).

Note
If you run the program in the background, the system takes the filter conditions into account just like in the case
of foreground running.

1.6.1 Configuration Guide for Notification Replication

To be able to push maintenance notifications from EAM to AIN and vice versa, you must set the mapping
configuration.

In transaction SM30, search for the view AIN_V_VALUE_MAP and define the mapping between the EAM and AIN
maintenance notification fields.

Asset Intelligence Network Integration


Asset Intelligence Network Integration PUBLIC 13
AIN values are predefined by the system, whereas EAM values are customizable. You can see in the table below
which AIN values belong to the EAM fields. You must use these AIN values for mapping.

Table 1: Predefined AIN Values

Field Name Field Description AIN Value Description

NOTITYPE Notification Type M1 Maintenance

M2 Breakdown

PRIORITY Priority 5 Low

10 Medium

15 High

20 Very High

25 Emergency

STATUS Status NEW New

PBD Published

CPT Completed

1.7 Work Order Replication

With SAP GUI transactions, you can push work orders from EAM to AIN. You are advised to run this feature in the
background.

With the transactions AIN_ORDER_POST or SE38/SA38, you can execute the AIN_WORKORDER_POST program.

You need to define the related equipment of the work order, and also provide some filter values for the work order.

1.7.1 Configuration Guide for Work Order Replication

To be able to push work orders from EAM to AIN, you must set the mapping configuration.

In transaction SM30, search for the view AIN_V_VALUE_MAP and define the mapping between the EAM and AIN
work order fields.

AIN values are predefined by the system, whereas EAM values are customizable. You can see in the table below
which AIN values belong to the EAM fields. You must use these AIN values for mapping.

Asset Intelligence Network Integration


14 PUBLIC Asset Intelligence Network Integration
Table 2: Predefined AIN Values

EAM Field Name Field Description AIN Value Description

ORDERTYPE Order Type 1 Breakdown

2 Inspections

3 Installation

4 Planned

5 Disposal

6 Operations

PRIORITY Priority 5 Low

10 Medium

15 High

20 Very High

25 Emergency

STATUS Status NEW New

PBD Published

CPT Completed

CSD Closed

Asset Intelligence Network Integration


Asset Intelligence Network Integration PUBLIC 15
Important Disclaimers and Legal Information

Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.

Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not
apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see:
http://help.sap.com/disclaimer).

Asset Intelligence Network Integration


16 PUBLIC Important Disclaimers and Legal Information
Asset Intelligence Network Integration
Important Disclaimers and Legal Information PUBLIC 17
go.sap.com/registration/
contact.html

© 2017 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.
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.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.