• Keine Ergebnisse gefunden

Process Integration Configuration Example for Onboarding Data

N/A
N/A
Protected

Academic year: 2022

Aktie "Process Integration Configuration Example for Onboarding Data"

Copied!
18
0
0

Wird geladen.... (Jetzt Volltext ansehen)

Volltext

(1)

SAP ERP HCM and SuccessFactors HCM Suite

Process Integration Configuration Example for Onboarding Data

Integration Add-On 3.0 SP02

(2)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 2

Validity

This document is for integration add-on 3.0 SP02 for SAP ERP HCM and

SuccessFactors HCM Suite.

(3)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 3

Introduction

• This document provides an example of the setup in the PI Integration Directory (PI IDR) needed for the integration scenario for onboarding data that is used in the hybrid integration of SAP ERP HCM and SuccessFactors HCM Suite.

• This document covers the communication channels that need to be configured

for the integration scenario for onboarding data.

(4)

PI Configuration for Begin

Session Service

(5)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 5

PI IDR – Configuration of Begin Session Service

Receiver Determination

The receiver determination for the Begin Session interface contains all objects needed to connect the following two interfaces:

• SFSFOnboardingBeginSession_Out

• SFSFOnboardingBeginSession_In

(6)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 6

PI IDR – Configuration of Begin Session Service

Interface Determination

The interface determination specifies the operation mapping to be used to connect

the two service interfaces.

(7)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 7

PI IDR – Configuration of Begin Session Service

Receiver Agreement

The receiver agreement specifies the communication channel to be used.

For the Begin Session service, be sure to use the communication channel with

SOAP Adapter. The corresponding template is SFSF_ONB_SOAP_ADAPTER.

(8)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 8

PI IDR – Configuration of Cancel Session Service

Receiver Determination, Interface Determination, and Receiver Agreement

The configuration for the Cancel

Session service is the same as

for the Begin Session service.

(9)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 9

PI IDR – Configuration of Get New Hire Record Service

Receiver Determination, Interface Determination, and Receiver Agreement

The configuration for the Get New

Hire Record service is the same

as for the Begin Session service.

(10)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 10

PI IDR – Configuration of OnboardingCandidateInfo

Receiver Determination, Interface Determination, and Receiver Agreement

The configuration for the

OnboardingCandidateInfo object is the same as for the Begin Session service, but the receiver agreement has a different

communication channel.

(11)

PI Configuration

Communication Channel

(12)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 12

PI IDR – Configuration of Communication Channel

Communication Channel for Begin Session, Cancel Session, and Get New Hire Record Services

This communication channel is to be used for the Begin Session, Cancel Session, and Get New Hire Record services. It can be created based on the template

SFSF_ONB_SOAP_ADAPTER.

The highlighted fields must be filled according to the system landscape.

(13)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 13

PI IDR – Configuration of Communication Channel

Communication Channel for Begin Session, Cancel Session, and Get New Hire Record Services

This shows the module configuration.

Use the parameters for

proxyHost and proxyPort if

needed.

(14)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 14

PI IDR – Configuration of Communication Channel

Communication Channel for OData Call OnboardingCandidateInfo

This communication channel is to be used for the Onboarding Candidate Info

service. It can be created based on the template SFSF_ONB_ODATA_ADAPTER.

The highlighted fields must be filled according to the system landscape.

(15)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 15

PI IDR – Configuration of Communication Channel

Communication Channel for OData Call OnboardingCandidateInfo

This shows the resource path configuration that needs to be maintained in the channel.

OnboardingCandidateInfo?$select=userId,readyToHire,managerId,kmsUserId,internalHire,hrManagerId,hi red,hireDate,fromExternalATS,candidateId,applicantId

In addition, you can specify other filter parameters to restrict the volume of data transfer to SAP ERP.

(16)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 16

PI IDR – Configuration of Communication Channel

Communication Channel for OData Call OnboardingCandidateInfo

This shows the advanced settings that need to be maintained in the channel. These settings are required if you want to use the filter option from import report.

Note: If a filter is passed dynamically, any filters defined in the channel configuration are not considered when calling the OData service.

If no filter is passed dynamically, the filters from the channel configuration are considered.

(17)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 17

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

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 SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

(18)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Customer 18

© 2014 SAP SE oder ein SAP-Konzernunternehmen.

Alle Rechte vorbehalten.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet.

SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP SE (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Ländern weltweit.

Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://global.sap.com/corporate-de/legal/copyright/index.epx.

Die von SAP SE oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.

Produkte können länderspezifische Unterschiede aufweisen.

Die vorliegenden Unterlagen werden von der SAP SE oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschließlich zu Informations- zwecken. Die SAP SE oder ihre Konzernunternehmen übernehmen keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in dieser Publikation. Die SAP SE oder ein SAP-Konzernunternehmen steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren.

Insbesondere sind die SAP SE oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehörigen Präsentation dargestellte Geschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu veröffentlichen. Diese Publikation oder eine zugehörige Präsentation, die Strategie und etwaige künftige Entwicklungen, Produkte und/oder Plattformen der SAP SE oder ihrer Konzern- unternehmen können von der SAP SE oder ihren Konzernunternehmen jederzeit und ohne Angabe von Gründen unangekündigt geändert werden.

Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von Material, Code oder Funktionen dar. Sämtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die die tatsächlichen Ergebnisse von den Erwartungen abweichen können. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder, zu dem sie getätigt wurden. Dem Leser wird empfohlen, diesen Aussagen kein übertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungen nicht auf sie zu stützen.

Referenzen

ÄHNLICHE DOKUMENTE

EBSD images with a colored overlay and an associated quartz c- axis orientation plot are indexed for each sample grid.. These c-axis orientation plots are oriented with their

We use more session type actions than channel-based session types, because there are more operations which can be performed: additionally to sending and receiving a method call,

Die Produzenten von E-Only-Journals müssen sich den Herausforderungen der Langzeitar- chivierung elektronischer Ressourcen in verstärktem Maße stellen, da hier keine Archivie-

11) X-shaped median apodeme on the frontal region: (0) absent; (1) present. Absent in Zorotypus weidneri. 12) Clypeus: (0) uniformly sclerotized; (1) with ante- and postclypeus.

This article has aimed to offer a discussion into Bitcoin price volatility by using an optimal GARCH model chosen among several extensions.. By doing so, the findings suggest an

inappropriate for development studies and how the same data can be better used.

During the warranty period, ALTOS, at its option will repair or replace components in the products that prove to be defective at no charge other than shipping and

The cointegration test, shown in Table 9, (see Engle & Granger, 1987; Engle and Yoo, 1987, Table 2), shows that in the two cases with monthly data (models 5 and 6),