June 2014
English
PI Design Objects within Enterprise Service Repository (SF1)
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany / Building Block Configuration Guide
SAP Best Practices PI Design Objects within Enterprise Service Repository (SF1): Config. Guide
Copyright
© 2014 SAP AG 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 AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Icons
/ Caution
/ Example
/ Note
/ Recommendation
/ Syntax
Typographic Conventions
Type Style / DescriptionExample text / Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
Cross-references to other documentation.
Example text / Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT / Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text / Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
EXAMPLE TEXT / Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.
Example text / Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text> / Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
Content
1 Purpose 5
2 Preparation 5
2.1 Prerequisites 5
2.2 Limitations 6
3 Configuration 6
3.1 Importing Design Objects in SAP Enterprise Service Repository 6
3.1.1 Downloading RDS Package at SAP Software Download Center 6
3.1.2 Importing Design Objects 6
3.2 Designing Object Templates 7
3.2.1 Communication Channel Templates 7
3.2.2 Integration Scenarios 8
3.2.3 Interface Objects for Workforce Analytics 9
3.3 Mapping Enhancements in SAP Enterprise Service Repository 9
PI Design Objects within Enterprise Service Repository
1 Purpose
The purpose of this document is to describe the general configuration steps required to manually download the XI Content of this Rapid Deployment Solution from the SAP Service Marketplace, and to import it into the Enterprise Service Repository. This should be performed within a system landscape that has already been installed using the corresponding installation or configuration guides for installation.
2 Preparation
2.1 Prerequisites
Before you start installing this scenario, you must install the prerequisite building blocks. For more information, see the Building Block Prerequisites Matrix for this Packaged Solution. You will find this document in the content library, attached to the Step-by-Step Guide.
For implementing the RDS for SAP ERP Human Capital Management and SuccessFactors Business Execution with SAP NetWeaver Process Orchestration, a running SAP NetWeaver PI 7.1 with EHP 1 (or higher; refer to the Software Requirements document for all required versions) system must be accessible, including adequate permissions (additional to role SAP_XI_IR_SERV_USER to access Integration Repository, role SAP_XI_ADMINISTRATOR or SAP_XI_CONTENT_ORGANIZER is needed to import the ESR-content).
On the ERP side, an SAP ERP 6.0 EHP2 system with the corresponding SPS is the minimum requirement. The ERP system must be configured as a business system in your System Landscape Directory. For more information on registering a business system into the SLD, see Set up System Landscape on the SAP Help Portal or refer to Registering the SAP ERP System in the SLD of the PI System. After including the ERP system in the SLD, the necessary business systems must be assigned in your Integration Directory. For more information, see SAP NetWeaver 7.3 Defining Communication Components on the SAP Help Portal.
To use this Rapid Deployment Solution, the Integration add-on 2.0 for SAP ERP Human Capital Management and SuccessFactors Business Execution is a prerequisite. The SAP NetWeaver Process Orchestration Secure connectivity Add-on is only needed if you want to implement the Workforce Analytics scenario, since the add-on provides SFTP and PGP functionalities needed for this purpose.
The integration add-on for SAP ERP Human Capital Management (SAP ERP HCM) and SuccessFactors Business Execution (SuccessFactors BizX) enables the integration for employee and organizational data, as well as for Analytical data transferred from SAP ERP HCM to SuccessFactors Workforce Analytics to support workforce planning, analytics, and Talent Management processes. Therefore, customers need a SuccessFactors tenant as well as a fully functional connectivity (over HTTPs and (S)FTP) as a prerequisite to establish a successful data integration work between SAP ERP HCM and SuccessFactors.
Furthermore, the processes Compensation Management (Pay for Performance) and Recruiting (Attract to Hire) are also integrated.
The integration of the three scenarios basic employee data, Compensation Management and Workforce analytics were already delivered with the previous add-on version 1.0. This new add-on version 2.0 additionally implements the Recruiting integration scenario on top of the others existing processes.
The configuration Guide SF6 describes how the integration add-on for SAP ERP Human Capital Management (SAP ERP HCM) and SuccessFactors Business Execution (SuccessFactors BizX) can be upgraded or installed.
The configuration Guide SF3 describes how The SAP NetWeaver Process Orchestration Secure connectivity Add-on can be installed.
Please also refer to both guides to figure out how you can check if the add-ons are already installed in your landscape.
2.2 Limitations
This Packaged Solution covers the following specific HR scenarios:
· Basic Employee Data (User)
· Compensation Data (Comp),
· Workforce Analytics (WFA) and
· Recruiting Data
This content is not ready to be used in a productive environment. This Packaged Solution must be tested in a test system in the customer-specific scenario.
3 Configuration
The following section describes the complete settings for this building block and for the following steps:
· Import Design Objects in Enterprise Service Repository (ESR)
· PI Enterprise Service Repository (ESR) Mapping Customizing
3.1 Importing Design Objects in SAP Enterprise Service Repository
3.1.1 Downloading RDS Package at SAP Software Download Center
Procedure
This Packaged Solution works with SAP standard objects.
1. Go to the necessary objects in the Software Download Center (http://service.sap.com/swdc).
2. Go to the top navigation bar: Software Downloads / Software Download Center.
3. Go to the left navigation bar: Installation and Upgrades / A – Z Index.
4. In the middle, choose R, and then choose SAP Rapid Deployment solutions.
5. In the opened subtree, choose SAP ERP HCM Integration for SuccessFactors rapid-deployment solution.
6. Choose XI CONTENT RDS SF HCM 2.0, and then #Database independent
7. Download the zip file (SAP Download Manager is required).
3.1.2 Importing Design Objects
Prerequisites
Check if the necessary software component (SFIHCM01 600 and SFIHCM02 600) of the Integration add-on 2.0 for SAP ERP Human Capital Management and SuccessFactors Business Execution is in the ESR. If not, then they must be downloaded and imported from the SAP Software Marketplace or updated from the SLD.
Make sure that you have checked the SAP Note 1578675 since it is necessary for the AXIS Framework (see SAP Notes section in the Quick Guide).
Update functionality / Tools ® Update Products/Main Instances…Make sure that the software components fulfill the required prerequisites. The software components SFIHCM01 600 and SFIHCM02 600 must be in the PI Enterprise Service Repository before importing the Design Objects. If not, then refer to the Administrator's Guide Integration Add-On HCM - SF BizX 2.0 to learn how to download and import the content in the ESR.
Procedure
1. Open the SAP NetWeaver PI Landing Page:
PI Landing Page / http://<pi_hostname>:<pi_http_port>/dir2. In the PI Tools area, open the SAP NetWeaver Enterprise Service Builder within the Enterprise Service Repository (ESR) area using the link.
3. Select the ESR Connectivity profile and start (if prompted).
When you start the ESR for the first time, it may take several attempts to initialize the tool.
3. In the ESR, go to the Import Design Objects section.
Menu navigation / Tools ® Import Design Objects…4. Select Client as the source system.
5. Select the downloaded tpz file (zip file you have previously downloaded) and choose Import….
6. Agree to the Import Design Objects warning message by choosing Import.
7. Afterwards, you should see the ESR objects displayed as a new software component version RDS SF HCM 2.0 under the software component RDS SF HCM. If the software component is not displayed, refresh your Design Object tree.
3.2 Designing Object Templates
This Packaged Solution has additional templates included that help set up the configuration for the HCM-SFSF Integration faster. These Design Object templates are delivered on top of the Integration Add-On XI Content SFIHCM02 and are available in the RDS Software Component RDS SF HCM (RDS SF HCM ® RDS SF HCM 2.0 ®http://sap.com/xi/RDS_SF_HCM ® Communication Channel Template).
3.2.1 Communication Channel Templates
Use
From a technical point of view, communication channel templates are own ESR object types. The usage is not mandatory since customers can manually create communication channels or generate standard communication channels in PI directory. Moreover, communication channels are technically not required for most sender channels.
There are three reasons why we strictly recommend creating and shipping communication channel templates and also assigning them to scenarios:
1. If you assign communication channel templates to a scenario, customers can easily see which adapter is used by the sender or expected by the receiver without reading the documentation.
2. If your scenario requires special attribute, values for the communication channels (such as security settings) can facilitate the customer’s configuration by already adding these values. Customers should not be forced to maintain values by copying and pasting from the documentation.
3. Customers might be unsure which adapter they should use, in case they have an AEX (see the following section) installed instead of a PI dual stack. For this purpose, we recommend creating communication channel templates for both variants (ABAP adapter and Java adapter in case they differ) and assigning the communication channel for the standard PI dual stacks adapter by default. In the documentation, you should mention this topic.
In summary, adding communication channel templates to a scenario completes the picture of a business process, facilitates the configuration at customer side, and therefore reduces TCO.
This Packaged Solution consists of various Communication Channel Templates for all scenarios:
Basic Employee, Recruiting Data and Compensation Data / · HCM_SOAPSender· HCM_SOAPReceiver
· HCM_SOAPSender_AAE
· SFSF_SOAPReceiver
· SFSF_SOAPReceiver_Axis
Workforce Analytics Data / · HCM_FTPSender
· SFSF_SFTPReceiver
If you want to use the Communication Channel Templates please make sure, that SAP BASIS 7.31 content is imported into your Enterprise Service Repository as the templates are based on that.
You can obtain that at the Software Download Center (http://service.sap.com/swdc). SAP Content ® ESR Content (XI Content) ® XI CONTENT SAP_BASIS ® XI CONTENT SAP_BASIS 7.3.
3.2.2 Integration Scenarios
Use
Process integration scenarios depict the message exchange and process flow of collaborative processes in a simple graphical notation. A scenario is the entry point in ESR for customers when they want to inform themselves about a business process. With one simple picture, they get a first impression on how the process works – without reading any documentation. If customers want detailed information, they can even drill-down from the scenario to all dependent and related objects like mappings or services (forward navigation).
The Process Integration Scenario simplifies the configuration of a scenario, in this case: Basic EmployeeDataSynchronization,CompensationDataSynchronization and RecruitingDataSynchronization . The Actions displayed in the Swim lanes of the Process Integration Scenario represent a message flow within the integration scenario with a unique sender and receiver interface. To connect actions, and to map between 1:1 relations of the interfaces, operation mappings are used.
Procedure
1. In the Enterprise Service Repository (ESR), open the software component RDS_SF_HCM Version 2.0.
2. Go to the namespace http://sap.com/xi/RDS_SF_HCM/IC, open the Process Integration Scenario node, to view the Objects for this Packaged Solution:
Basic Employee / · EmployeeDataSynchronization· EmployeeDataSynchronization_AAE
Compensation Data / · CompensationDataSynchronization
· CompensationDataSynchronization_AAE
Recruiting Data / · RecruitingDataSynchronization
· RecruitingDataSynchronization_AAE
All scenarios are set with the fitting Operations Mappings and Communication Channel Templates. The Process Integration scenario with the _AAE-ending are set for Integrated Configuration. Customers can use these scenarios to export their configurations with the Model Configurator. This step is described in the PI general configuration within Integration Directory building block (SF2).