On Behalf Reporting to EU Hub

Message Specification SAP Information Collaboration Hub for Life Sciences 2019-08-13

CUSTOMER

On Behalf Reporting to EU Hub 3PL for MAH

2 CUSTOMER © 2019 SAP SE or an SAP affiliate company. All rights reserved.

On Behalf Reporting to EU Hub Document History

Document History

Version Status Date Change

1.0 Released to Customer 7-Sep-18 Initial Release

1.1 Final 13-Aug-2019 Updated for namespace 20181

On Behalf Reporting to EU Hub Contents

CUSTOMER © 2019 SAP SE or an SAP affiliate company. All rights reserved. 3

Contents

1 About this Document .................................................................................................................... 4 1.1 Purpose and Scope ................................................................................................................................ 4 1.2 Target Audience ..................................................................................................................................... 4

1.2.1 Assumptions .......................................................................................................................... 4 1.3 Glossary .................................................................................................................................................. 4 1.4 Typographic Conventions ..................................................................................................................... 5

2 Introduction ................................................................................................................................... 7 2.1 European Hub Reporting ....................................................................................................................... 7 2.2 SAP Message Envelope ......................................................................................................................... 8 2.3 On Behalf Reporting .............................................................................................................................. 8 2.4 Prerequisites ......................................................................................................................................... 11 2.5 Business Process .................................................................................................................................. 11

2.5.1 Token and Certificates ......................................................................................................... 11 2.5.2 EU Requests ......................................................................................................................... 12 2.5.3 Responses ............................................................................................................................ 12

2.6 EMVO Versioning and Updates .......................................................................................................... 12

3 Message Overview ....................................................................................................................... 14 3.1 SAP Message Envelope ....................................................................................................................... 14 3.2 EU Message Format............................................................................................................................. 16

3.2.1 Product Pack State Update Request ................................................................................. 16 3.2.2 Product Pack State Update Response .............................................................................. 19 3.2.3 Restrictions Product Pack State Update ......................................................................... 20 3.2.4 Product Pack Verification Request ................................................................................... 20 3.2.5 Product Pack Verification Response ................................................................................. 22

4 Important Disclaimers and Legal Information ....................................................................... 24 4.1 Coding Samples ................................................................................................................................... 24 4.2 Accessibility .......................................................................................................................................... 24 4.3 Gender-Neutral Language................................................................................................................... 24 4.4 Internet Hyperlinks .............................................................................................................................. 24

Legal Disclaimer

The information in this document is confidential and proprietary to SAP and may not be disclosed without the permission of SAP


On Behalf Reporting to EU Hub About this Document

1 About this Document

1.1 Purpose and Scope

This document describes how Third Party Logistics business partners can report to the EU Hub on behalf of MAHs. The MAHs are customers of the SAP Information Collaboration Hub for Life Sciences, and the Third Party Logistics partners (3PLs) must onboard to the SAP Information Collaboration Hub for Life Sciences, known as SAP Info Hub.

1.2 Target Audience

This document is for Third Party Logistics Service Providers (3PLs) including: • Integration experts • Implementation teams

1.2.1 Assumptions

This document assumes readers are familiar with EMVS concepts and terminology, and with SAP’s EU Hub Regulatory Reporting service.

Related Information

• SAP Information Collaboration Hub for Life Sciences EU Hub Reporting • SAP Information Collaboration Hub for Life Sciences Help Portal

1.3 Glossary

Abbreviation Definition

3PL Third Party Logistics service provider

ATTP SAP Advanced Track and Trace for Pharmaceuticals

CMO Contract Manufacturing Organization

EDMC Electronic Drug Monitoring Code

https://help.sap.com/http.svc/rc/e3fbf5a214b44613a7ba28afd9b71355/1.0.0.0/en-US/SAP%20Regulatory%20Reporting%20for%20EU-Hub-1.2.pdf

https://help.sap.com/http.svc/rc/e3fbf5a214b44613a7ba28afd9b71355/1.0.0.0/en-US/SAP%20Regulatory%20Reporting%20for%20EU-Hub-1.2.pdf

https://help.sap.com/viewer/p/SAP_INFO_HUB_FOR_LIFE_SCIENCES_MAIN



Abbreviation Definition

EMVO European Medicines Verification Organization

EMVS European Medicines Verification System

EPC Electronic Product Code, often used to summarize different formats of unique identifiers

EPCIS Electronic Product Code Information Services - GS1 Standard, refer to http://www.gs1.org/epcis/epcis/1-1. This specification is based on EPCIS 1.1

EU Hub European Union Hub

FDA Food and Drug Administration

FMD Falsified Medecines Directive

GCP Global Company Prefix (GS1 Standard)

GLN Global Location Number (GS1 Standard)

GS1 Global Standardization Body

GTIN Global Trade Identification Number (GS1 Standard)

SAP Info Hub SAP Information Collaboration Hub for Life Sciences, formerly Pharma Network

MAH Marketing Authorization Holder

NDC National Drug Code

NHRN_DRN National Healthcare Reimbursement Number (NHRN, product identifier used in Brazil)

NTIN National Trade Item Number, special version of a GTIN where the “company prefix depicts a country. Used to bring country specific numbering schemes into the GTIN format.

PZN Pharmazentralnummer (Central Pharma Number, product identifier used in Germany)

SGTIN Serialized GTIN, special case of EPC

SSCC Serial Shipping Container Code

1.4 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.

http://www.gs1.org/epcis/epcis/1-1

http://www.gs1.org/



Type Style Description

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 .

On Behalf Reporting to EU Hub Introduction


2 Introduction

The SAP Information Collaboration Hub for Life Sciences is an innovative on-demand solution that connects pharmaceutical organizations and their supply chain partners on a secure network that is owned and managed by SAP. The SAP Information Collaboration Hub for Life Sciences supports the transfer and transformation of data between members of the pharmaceutical supply chain connected to the SAP Information Collaboration Hub for Life Sciences. Connected partners can exchange serialization messages across a secure and reliable network. The SAP Information Collaboration Hub for Life Sciences allows for the exchange of traceability data between pharmaceutical supply chain partners such as a Contract Manufacturer Organization (CMO), a Third Party Logistics Provider (3PL) and a Market Authorization Holder (MAH).

2.1 European Hub Reporting

Customers running SAP backend systems and SAP Advanced Track and Trace for Pharmaceuticals (ATTP), and customers using non-SAP backend systems can connect to the European Medicines Verification System (EMVS) through the SAP Information Collaboration Hub for Life Sciences by using an envelope to route the message to the EMVS.

EMVOSAP Customer

EMVSSystem

SAP Information Collaboration Hub for Life Sciences

Mes

sage

Han

dlin

g



2.2 SAP Message Envelope

The SAP message envelope is used to route messages. It is similar to the envelope of a letter that allows the Post Office to deliver a message without reading the content. The envelope includes the following: • Partner IDs to identify endpoints independently of the communication protocol • Message Type to identify the type of message, such as decommissioning • Version of the message interface • Message payload conent, which conforms to the EMVO message specification for pack update and pack

verification For further details of the message envelope, see Section 3.

2.3 On Behalf Reporting

Typically MAHs report directly to the EU Hub as shown in the following figure.

SEM Messages

MAH 3PL

Ackn

owle

dgem

ent

EU Hub

However, 3PLs can report on behalf of an MAH as shown in the following figure.



3PLMAHAcknowledgement

EU Hub

Acknowledgem

ent

A 3PL can communicate with the EU Hub using the MAH’s EU Hub gateway connection on the SAP Information Collaboration Hub for Life Sciences.



The following figure shows the interaction between the EU Hub and a 3PL through the MAH’s EU Hub connection without involving the MAH.

n Collaboration Life Sciences

Messages in figure: 1. Product Pack Update 2. ConfirmProductPackStateUpdateStatus 3. ProcessProductPackVerification 4. ConfirmProductPackVerificationStatus The EU Hub is not aware that the message does not come from the MAH. When a message is sent by a Business Partner to the EU Hub, the SAP Info Hub sends the response to the Business Partner and not to the MAH.



2.4 Prerequisites

A 3PL must: • Be able to receive response messages asynchronously • Use the EU Hub file format • Use the SAP Information Collaboration Hub for Life Sciences Envelope • Onboard to the SAP Information Collaboration Hub for Life Sciences through a B2B integration.

Note The SAP Information Collaboration Hub for Life Sciences does not check message payload content.

More Information

For information on 3PL onboarding, see the SAP Information Collaboration Hub for Life Sciences Preboarding Guide on the Help Portal.

2.5 Business Process

This section describes message creation and business impact. To connect to the EU Hub, an MAH must initially set up a secure communication channel. SAP performs this task for customers.

2.5.1 Token and Certificates

Before a 3PL can report to the EU Hub on behalf of an MAH, the MAH connection must be set up on the SAP Info Hub. The SAP Info Hub creates an MAH communication channel using an MAH specific certificate that the EMVO provides to the MAH. Each SAP EU customer has their own certificate and token that is stored by the SAP Info Hub. A 3PL sends the message payload to the SAP Info Hub. The SAP Info Hub adds the token, signs and encrypts the message payload, and sends the request to the EU Hub.

Note The token must be renewed every 24h-120h. SAP manages the token.

https://help.sap.com/viewer/p/SAP_INFO_HUB_FOR_LIFE_SCIENCES_MAIN



2.5.2 EU Requests

A 3PL can send a request to the EU Hub synchronously or asynchronously. When the SAP Info Hub receives the request message, the SAP Info Hub verifies the sender. The MAH must be authorized to communicate with the EMVO. The envelope is stored based on the MAH GLN, correlation ID, and other parameters. The SAP Info Hub then sends the request to the EU Hub without the envelope. The communication channel is closed even for synchronous communications. To summarize: 1. When a 3PL sends a request to the EU Hub, the communication channel is established and then closed. 2. The EU Hub processes the message and forwards the message to relevant national systems. 3. The EU Hub later sends a response to the 3PL.

2.5.3 Responses

The EU Hub sends responses to requests. For the Produck Pack State Update message, the EU Hub returns a response stating "success" for a successfully processed operation. This response arrives on the communication endpoint in the SAP Info Hub. The message is decrypted using the MAH certificate, and acknowledged to the EU Hub according to the EMVO specification. The SAP Info Hub: • Checks the message based on the correlation ID and MAH GLN. • Creates an envelope around the response, and sets the 3PL as the recipient using 3PL GLN. • Ends the response to the 3PL in the envelope.

2.6 EMVO Versioning and Updates

A 3PL must use the EMVO message format according to the requirements of the EU Hub. There is an interface available since the first release of the EU Hub (Interface 2016/1). From August 2018, the EMVO changed the approach. EMVO will not update existing interfaces but provide new EU Hub releases and new interfaces and namespaces (Interface 2018/1). The message content for the Product Pack State Update and Product Pack Verification messages will not change based on the content but the namespaces will. Both interfaces 2016/1 and 2018/1 are supported by the EU Hub until the EU Hub makes available a new release with an interface, which, for example, may be called 2020/1. 2016/1 will be deprecated, and MAHs and 3PLs must adopt the 2018/1 interface in a timly manner to stay compliant.



Note 3PLs must always align with the EU Hub’s message format that is currently supported by SAP. SAP Information Collaboration Hub for Life Sciences currently supports interface 2016/1 and 2018/1. New EU Hub releases that are supported by SAP are announced regularly by SAP.

Different versions are defined by new namespaces, new messages and functionality, and a different URL address. If functionality and content are not changed for the most relevant messages for On Behalf Reporting, SAP routes the URL based on the namespace of the request. The 3PL must only adapt the namespaces.


On Behalf Reporting to EU Hub Message Overview

3 Message Overview

This section outlines: • The SAP Message Envelope • The EU Hub message format with the update to 20181 namespace. Declarations are unchanged.

3.1 SAP Message Envelope

This section describes the SAP Message Envelope which encloses the message payload. This section includes examples of message fields and descriptions of use. In the examples, fields are shown in the following colors: • Light blue represents static data that is the same for all EMVS requests sent to the SAP Information

Collaboration Hub for Life Sciences. • Yellow represents conditional data. • Green represents variable data that is different for each request, for example, message ID to identify and

reconcile requests and corresponding responses.

Content Explanation Mandatory/Optional Conditional

<ich4ls:envelope version="2.4.1"

xmlns:ich4ls="http:// www.sap.com/sap_ich4ls/">

Root_Element M

<message

date="2017-08-18" time="21:02:42Z">

Date: creation date of the message envelope Time: creation time of the message envelope including time zone offset. (z=Zulu time or for example, +1:00 for an offset of + one hour

M

<id>0123456789ABC</id> Message ID: must be unique.

Note You must use the Correlation ID as Message ID.

M



Content Explanation Mandatory/Optional Conditional

<owner agency="GS1"

scheme="GLN">0123456789111</owner>

The owner of the message is the MAH, identified by the MAH’s GLN which is used to build communication channel. MAH provides this information to the Business Parnter. For EU Hub connections, SAP Information Collaboration Hub for Life Sciences only accepts GS1 GLNs.

M

</message> Close segment M

<sender agency="GS1"

scheme="GLN">0123456789222</sender>

Identifies the sender of the message. In the case of an EU-Hub connection, SAP Information Collaboration Hub for Life Sciences only accepts GS1 GLN.

M

<recipients>

<id agency="SAP"

scheme="RegReport">

emvo-medicines.eu</id>

</recipients>

Identifies one or more recipients of the message. In case of an EU-Hub connection, recipient must be “emvo-medicines.eu with agency = “SAP” and scheme = “RegReport”

M

<content format="EMVO"

type="RegulatoryReporting"

version="20181" encoding="XML">

The content segment describes the message in the envelope. For an EU Hub connection, SAP expects an EMVO format encoded as XML. The type must always be RegulatoryReporting for all EMVO Regulatory Reporting messages. The value “20181” is derived from the namespace.

M

<n0:ProcessProductBatchRecall

xmlns:n0="http://EMVS.EU/20161/"

xmlns:prx="urn:sap.com:proxy:Y3N:/1SAI

/TAS565276610CDCCD1FA3B2:740">

<n0:EMVSEnvelope>

<n0:Head>

…

This is an example of content that must be sent to the EU Hub. This section of the message stores the Request to the EU Hub and the EU Hub response.

C

</content> Close segment M

</ich4ls:envelope> Close segment M



3.2 EU Message Format

This section describes the EU Messages for the on behalf reporting scenario. This section only contains an example. For further information, contact your SAP representative for the WSDL definition of EU Hub messages.

3.2.1 Product Pack State Update Request

The Product Pack State Update Request is stored in the "content" statement of the message envelope.

Content from examples below Explanation Mandatory/Optional Conditional

<n0:ProcessProductPackStateUpdate

xmlns:n0=http://EMVS.EU/20181/>

Root_Element M

<n0:EMVSEnvelope> Root_Element M

<n0:Head> Root_Element M

<n1:CorrelationID

xmlns:n1="http://EMVS.EU/Common/20181/

">13DIGITGLN234005056B6A7EE1ED7BBF896F

34728200239857</n1:CorrelationID>

Correlation ID: must be unique. For on behalf reporting, ensure the sender GLN is part of this ID. The parts are: - 13 digit GLN - 27 digit alphanumeric

M

<n1:Timestamp


">2018-02-07T11:20:00Z</n1:Timestamp>

Date: creation date of the message Time: creation time of the message including time zone offset. (z=Zulu time). Only messages with a timestamp that includes today’s date and today’s time. Date and time must not be in the future.

M

</n0:Head> Close segment M

<n0:Body> Root_Element M

<n0:ProductPackStateUpdateRequest> Root_Element M

<n1:ProductCode scheme="GTIN"

xmlns:n1="http://EMVS.EU/Common/20181

/">14298382000029</n1:ProductCode>

The product code must be sent in GTIN format, and contains the 14 digits identification number of the product.

M

http://emvs.eu/20181/




<n1:BatchID


">EMVO_BATCH_2002</n1:BatchID>

Batch ID - for each Product - Batch - Status combination, a new message must be created.

M

<n1:BatchExpiryDate


">190102</n1:BatchExpiryDate>

Expiry date in the format YYMMDD.

M

<n1:PackList


">

Root_Element M

<n1:Pack sn="10000qHs78"/> List of items for which the status must be changed. Based on the EU Hub specification, list can contain up to one million numbers. For FREE_SAMPLE and SAMPLE status, only single requests are permitted.

M

</n1:PackList> Close segment M

<n0:InitialPackStatus>ACTIVE</n0:Initi

alPackStatus>

The initial pack status defines the state of an item before this business interaction. For on behalf reporting, the initial status is ACTIVE. In case there is uncertainty, a verfication can be sent first to get the initial status. For permitted status codes, see WSDL file. Contact your SAP representative.

M




<n0:NewPackStatus>LOCKED</n0:NewPackSt

atus>

New item status which can be: • ACTIVE • CHECKED-OUT • DESTROYED • EXPIRED • EXPORTED • FREE SAMPLE • LOCKED • RECALLED • SAMPLE • STOLEN • SUPPLIED • WITHDRAWN FREE SAMPLE and SAMPLE must be single requests.

M

</n0:ProductPackStateUpdateRequest> Close segment M

</n0:Body> Close segment M

</n0:EMVSEnvelope> Close segment M

</n0:ProcessProductPackStateUpdate> Close segment M



3.2.2 Product Pack State Update Response


<ConfirmProductPackStateUpdateStatus

xmlns="http://EMVS.EU/20181/"

xmlns:a="http://www.w3.org/2005/08/add

ressing"

xmlns:s="http://www.w3.org/2003/05/soa

p-envelope"

xmlns:u="http://docs.oasis-

open.org/wss/2004/01/oasis-200401-wss-

wssecurity-utility-1.0.xsd"

xmlns:xsd="http://www.w3.org/2001/XMLS

chema"

xmlns:xsi="http://www.w3.org/2001/XMLS

chema-instance">

Root_Element and name spaces M

<EMVSEnvelope> Root_Element M

<Head> Root_Element M

<CorrelationID


">13DIGITGLN234005056B6A7EE1ED7BBF896F


Same Correlation ID as in the request.

M

<n1:Timestamp

xmlns="http://EMVS.EU/Common/20181/">2

018-02-

07T13:42:04.2533531Z</n1:Timestamp>

Date and Time when the reponse was created by EU Hub.

M

</Head> Close segment M

<Body> Root_Element M

<ProductPackStateUpdateStatus> Root_Element M

<Status>SUCCESS</Status> The status defines if the request is confirmed by the NMVS. Status can be: - SUCCESS - FAIL - PARTIAL

M

<Errors/> Empty tag. M

</ProductPackStateUpdateStatus> Close segment M

</Body> Root_Element M




</EMVSEnvelope> Close segment M

</ConfirmProductPackStateUpdateStatus> Close segment M

3.2.3 Restrictions Product Pack State Update

For restrictions, see the EMVO Onboarding documentation for authorized status changes.

Note Only a single request is permitted for FREE_SAMPLE or SAMPLE status changes. This is planned to be changed from EMVO side in future releases.

3.2.4 Product Pack Verification Request


<n0:ProcessProductPackVerification

xmlns:n0=http://EMVS.EU/20181/>

Root_Element M

<n0:EMVSEnvelope> Root_Element M

<n0:Head> Root_Element M

<n1:CorrelationID


">13DIGITGLN234005056B6A7EE1ED7BAF896F


Correlation ID: must be unique. For on behalf reporting, ensure the sender Business partner GLN is part of this ID. The parts are: - 13 digit GLN - 27 digit alphanumeric

M

<n1:Timestamp


">2018-02-07T11:21:00Z</n1:Timestamp>

Date: creation date of the message Time: creation time of the message including time zone offset. (z=Zulu time). Only messages with a timestamp that includes today’s date and today’s time. Date and time must not be in the future.

M

http://emvs.eu/20181/




</n0:Head> Close segment M

<n0:Body> Root_Element M

<n0:ProductPackVerificationRequest> Root_Element M

<n1:ProductCode scheme="GTIN"

xmlns:n1="http://EMVS.EU/Common/20181

/">14298382000029</n1:ProductCode>

The product code must be sent in GTIN forma,t and contains the 14 digit identification number of the product.

M

<n1:BatchID


">EMVO_BATCH_2002</n1:BatchID>

Batch ID - each Product - Batch -Status combination, requires a new message.

M

<n1:BatchExpiryDate


">190102</n1:BatchExpiryDate>

Expiry date in the format YYMMDD.

M

<n1:PackList


">

Root_Element M

<n1:Pack sn="10000qHs78"/> List of items for which the status is requested.

M

</n1:PackList> Close segment M

</n0:ProductPackVerificationRequest> Close segment M

</n0:Body> Close segment M

</n0:EMVSEnvelope> Close segment M

</n0:ProcessProductPackStateUpdate> Close segment M



3.2.5 Product Pack Verification Response


<ConfirmProductPackVerificationStatus

xmlns="http://EMVS.EU/20181/"

xmlns:a="http://www.w3.org/2005/08/add

ressing"

xmlns:s="http://www.w3.org/2003/05/soa

p-envelope"

xmlns:u="http://docs.oasis-

open.org/wss/2004/01/oasis-200401-wss-

wssecurity-utility-1.0.xsd"

xmlns:xsd="http://www.w3.org/2001/XMLS

chema"

xmlns:xsi="http://www.w3.org/2001/XMLS

chema-instance">

Root_Element and name spaces M

<EMVSEnvelope> Root_Element M

<Head> Root_Element M

<CorrelationID


">13DIGITGLN234005056B6A7EE1ED7BAF896F


Same Correlation ID as in the request.

M

<n1:Timestamp

xmlns="http://EMVS.EU/Common/20181/">2

018-02-

07T13:42:04.2533531Z</n1:Timestamp>

Date and Time when the reponse was created by the EU Hub

M

</Head> Close segment M

<Body> Root_Element M

<ProductPackVerificationStatus> Root_Element M

<ProductCode

xmlns="http://EMVS.EU/Common/20181/"

scheme="GTIN">14298382000043</Product

Code>

Product code information M

<PackList

xmlns="http://EMVS.EU/Common/20181/">

Root_Element M

<Pack sn="10000MAvB1" state="ACTIVE"/> For each serial numer/item, the current status is displayed.

M

</PackList> Close segment M

</ProductPackVerificationStatus> Close segment M

</Body> Close segment M




</EMVSEnvelope> Close segment M

</ConfirmProductPackStateUpdateStatus> Close segment M


On Behalf Reporting to EU Hub Important Disclaimers and Legal Information

4 Important Disclaimers and Legal Information

4.1 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 will 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.

4.2 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 wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

4.3 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.

4.4 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 will 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).

http://help.sap.com/disclaimer/

On Behalf Reporting to EU Hub Important Disclaimers and Legal Information


www.sap.com/contactsap

© 2019 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. 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#trademark for additional trademark information and notices.

Material Number:

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

On Behalf Reporting to EU Hub

Documents

Transcript of On Behalf Reporting to EU Hub