Configuration Guide SAP S4HANA Cloud Enterprise Edition

8/17/2019 Configuration Guide SAP S4HANA Cloud Enterprise Edition

http://slidepdf.com/reader/full/configuration-guide-sap-s4hana-cloud-enterprise-edition 1/78



2 CUSTOMER

SAP Cloud for Customer Integration with

SAP S/ 4 HANA Cloud Enterprise Edition using HANA Cloud Integration (HCI)

Typographic Conventions

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.

Exampl eOutput 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.





CUSTOMER

Error Reference source not found. 3

Document History

Revision Date Change

1.0 2015-05-20 Configuration Guide created

2.0 2015-11-30 Updated for November release

3.0 2016-03-09 Updated for March release





4 CUSTOMER

Table of Contents

1SAP Cloud for Customer Integration with SAP S/ 4 HANA Cloud Enterprise Edition using HANA Cloud

Integration (HCI) 6

2Configuration in SAP Cloud for Customer 7

2.1 Scoping 7

2.1.1 First Log in with Initial User 7

2.1.2 Scoping with Initial User 7

2.2 Fine Tuning 13

2.2.1 Confirm Milestone: Design Accepted and User 13

2.2.1.1 Confirm Milestone: Design Accepted 13

2.2.1.2 Create Administrator with Initial User 14

2.2.1.3 Lock Initial User with the Newly Created Administrator 18

2.2.1.4 Define Business Roles 19

2.2.2 Master Data Preparation Manually 22

2.2.2.1 J ob Definition 22

2.2.2.2 Add Activities into Project for Integration 23

2.2.2.3 Define Organizational Structure 24

2.2.2.4 Define Employees 30

2.2.2.5 Define Distribution Channel 33

2.2.2.6 Define Division for Product 34

2.2.2.7 Define Product Categories 34

2.2.3 Set Up Communication System 37

2.2.4 Adjust MashUp URL 38

2.2.5 ID Mapping 39

2.2.6 Configure Communication Arrangement 412.2.6.1 Mass Configuration of Communication Arrangements. 41

2.3 Configure Organizational Work Distribution in SAP Cloud for Customer 46

2.4 Manual Code List Mapping in Cloud for Customer system 47

3Configuration in SAP S/ 4HANA 49

3.1 Define Communication User 49

3.2 Create Key User 50

3.3 Maintain Communication Arrangements 51

3.4 How to get the S/ 4HANA System URL 54

3.5 Business Configuration in S/ 4HANA 54

3.5.1 Configure Your Solution 54

3.5.2 Message Monitoring 56

4Configuration in HANA Cloud Integration 58

4.1 View prepackaged iFlows using SAP HCI Web UI 58

4.2 Configure Communication User Credentials from SAP HCI to SAP Cloud for Customer 58

4.2.1 Deploy Cloud Credential Artifacts 59

4.3 Configure Communication User Credentials from SAP HCI to SAP S/ 4 HANA 60

4.3.1 Deploy S/ 4 HANA Credential Artifacts 60

4.4 How to get the HCI Runtime URL 61

4.5 How to get the HCI client certificate 62

4.6 Configure and Deploy the iFlow Using SAP Web UI 62

5Data Loading 67

5.1 Initial Data Load from S/ 4 HANA 67





CUSTOMER


5.1.1 Add Business role to Key User 67

5.1.2 Customer Master/ Relationships 68

5.1.3 Material Master 70

5.2 Delta Load for Business Partners/ Relationships and Material 70

5.2.1 Add Business roles to Key User 71

5.2.2 Maintain Customer Master/ Relationships 71

5.2.3 Maintain Material Master 72

6Message Monitoring in SAP S/ 4 HANA 75

6.1 Add Business role to Key User 75

6.2 Monitor Messages 76





6 CUSTOMER

1 SAP Cloud for Customer Integration with

SAP S/ 4 HANA Cloud Enterprise Editionusing HANA Cloud Integration (HCI)

The purpose of this document is to describe the general configuration steps required to manually set up the

configuration within the system landscape that has already been installed.

This document describes the procedure to configure the Integration between SAP S/4HANA Cloud Enterprise

Edition and SAP Cloud for Customer using SAP HANA Cloud Integration.

Before you start working through this document, ensure that you have downloaded the most recent version of this

document available on SAP Service Marketplace

Important:

If you have any queries or feedback on this document, please create a ticket for the CSN component SV-RDS-CFC

http://service.sap.com/cloud4customer

http://service.sap.com/cloud4customer





CUSTOMER


2 Configuration in SAP Cloud for Customer

· The empty 1602 Cloud for Customer tenant should be available with initial user/ password.

· When an empty tenant is available, the tenant owner gets an e-mail from Cloud Management Service. The e-

mail contains tenant - access and support information. The initial user with password can be found in the

access information. To make certain configuration, the first step is to do scoping with the initial user.

2.1 Scoping

2.1.1First Log in with Initial User

1. Open the Frontend Access tenant URL in Web browser

i.

ii. Example: https:/ /<host_name>.XXXX.XXXXXX.com

2. Input the initial user and password,

3. Select your logon language, by default it is English .

4. ChooseLog On ; change the password in the dialog box.

5. Select I want m y SAP application to use the Microsoft Silverlight app lication stor age in the dialog box.

6. ChooseOK.

7. ChooseYes .

2.1.2Scoping with Initial User

1. Choose Work Center View :

Work Center BUSINESS CONFIGURATION

View IMPLEMENTATION PROJECTS

2. Select First Implementation project.

3. ChooseEdit Project Scope button.





8 CUSTOMER

4. In theCountry and Type of Business step, ChooseEdit Countries.

5. AddUS to the Selected Countries and ChooseOK .

6. ChooseNext.





CUSTOMER


7. In the Implementation Focus step, The Implementation Focus SAP Cloud for Customer is Selected, Choose

Next

Implementation Focus Selected

SAP Cloud for Customer Checked

8. In theScoping Step, Maintain the following values and chooseNext :

Scoping Element L1 Scoping Element L2 Scoping Element L3

Sales

Account and Activity

Management

Account Management

Act ivity Management

Communication for Account and

Act ivity Management.

Analysis for Account and Activity

Management

Sales

Product and Service Portfolio

for Sales

<all>

Expand the scoping element and

check the sub element “Sell

Standard Products ”.





10 CUSTOMER

Scoping Element L1 Scoping Element L2 Scoping Element L3

Sales New Business

<all> except Sales Lead

Management(obsolete)

Sales Lead Management <all>

Sales

Sales Planning (SAP Cloud for

Customer) <all>

Business Performance

Management <all> <all>

Communication and

Information Exchange Business Process Management <all>

Communication andInformation Exchange

Integration with ExternalApplications and Solutions Int egration wit h SAP ERP

Communication and

Information Exchange

Integration with External

Applications and Solutions Integration of Master Data

Communication and

Information Exchange

Integration with External

Applications and Solutions

Integr ation into Sales, Service,

and Market ing Process

General Business Data Business Partners <all>

General Business Data Employees and Service Agents <all>

General Business Data Products Product Category hierarchy

General Business Data Products Materials

General Business Data

Products Communication for Product

master Data

General Business Data Products Analysis for Product M aster Data

General Business Data Product and Service Pricing <all>

Built-in Services and

Support <all> <all>

Note

Scoping depends on the business needs. Some of the Elements are selected automatically due tobusiness logic. This is needed for Communication and Information Exchange.

9. ChooseNext .

10. In theQuestions Step, navigate using the following path.

Comm unication and Information Exchange àIntegration with External App lications and Solutions à

11. Select theScoping element , On the Right Pane maintain the following values.





CUSTOMER


12. Mark In Scope for below Elements

Scoping Element Business Option

Integration of Master Data Do you want to replicate business partner data from an external

application or solution to your cloud solution?

Integration of Master Data Do you want to replicate product data from an external application or

solution to your cloud solution?

Integration into Sales, Service,

and Marketing Processes

Do you want to create follow up documents for opportunities from

your cloud solution to an external application or solution?





12 CUSTOMER

a.

b.

13. ChooseNext.

14. ChooseYes on the pop-up to confirm the values selected in the Questions step.

15. Review the Scoping Setting and ChooseFinish to complete the Scoping.

16. On theConfirmation step, chooseClose .





CUSTOMER


2.2 Fine Tuning

2.2.1Confirm Milestone: Design Accepted and User

2.2.1.1 Confirm Milestone: Design Accepted

1. In below Work Center,



2. Select the titleFirst Implementation project.

3. ChooseOpen Activity List

4. On thePrepare Tab, ChooseConfirm Milestone: Design Accepted .

5. In the page, selectDesign Accept ed and ChooseConfirm .





14 CUSTOMER

6. On the Prompt, ChooseOK to continue.

7. ChooseConfirm .

8. ChooseClose .

Caution

System may take 30 minutes to complete this task in the background. Wait until The Confirm Milestone

status will change to Confirmed with Confirmed On and Confirmed By updated

2.2.1.2 Create Administrator with Initial User

1. Navigate to the below Work Center.



2. Select the titleFirst Implementation project , ChooseOpen Activity List

3. On thePrepare Tab, ChooseDefine Administrators for Project Team





CUSTOMER


4. ChooseCreate Service Agents, Maintain the following values,

Field Value

First Name ADMIN

Last Name PROJ ECT

Phone <The Project Administrator or Contact’s Phone>

E-Mail <The Project Administrator or Contact’s E-Mail>

5. ChooseSave , and ChooseRequest User.





16 CUSTOMER

6. ChooseClose.

7. Close these Opened Pages.

8. Now log out and then log in the system again with project initial user.

9. Go to below Work Center and ChooseGo.

Work Center APPLICATION AND USER MANAGEMENT

View BUSINESS USERS

10. Select the User ID.

Example

PROJECTADMIN7000000

11. Go toEdit àAttributes , maintain the following values.

Field Value

User ID <USERID> For example: PROJ ECTADMIN

Password <Password>

12. Choose Edit Access Right s, ChooseYes to save the attributes change.

a.

13. In theEDIT ACCESS RIGHTS screen, select tabWORK CENTER AND VIEW ASSIGNMENT and make below

assignment by selecting the checkbox.





CUSTOMER


Work Center/ View ID Work Center / View Name

SEODADMINWCF Administrator

IST_APPLICATIONUSERMANAGEMENT Application and User Management

BC_BUSINESSCONFIGURATION Business Configuration

BUSINESSPARTNERS_WCF Business Partners

MASSDATAMAINTAINANCE_WCF Mass Data Maintenance

MOM_ORGANIZATIONALMANAGEMENT Organizational Management

CODPARTNERWC Partners

CODPEOPLE People

COD_PRODUCTDATA Products

CI_CUSTOMER_CONTROL_CENTER Service Control Center

DATA_INTEGRATION Data Integration

a.

14. ChooseSave twice

15. ChooseLog Off on the top right corner and Choose Yes.





18 CUSTOMER

2.2.1.3 Lock Initial User with the Newly CreatedAdministrator

1. Choose Restart Application or log on again

2. Input the administrator user and password created, and Choose Log On.

Field Value

User ID <USER ID> For example: PROJECTADMIN

Password <Password>

3. Change the password then log on.

4. Navigate to the below Work Center view



5. Select First Implementation project

6. ChooseOpen Activity List.

7. ChooseDefine Administrators for Project Team in Prepare.





CUSTOMER


8. ChooseLock Initial User.

9 . ChooseLock User.

10. ChooseOK and close the opened pages.

2.2.1.4 Define Business Roles

1. Navigate to below Work Center.

Work Center ADMINISTRATOR

View GENERAL SETTINGS

2. Select Business Roles





20 CUSTOMER

3. ChooseNew àBusiness Role :

Tab Field Value

GENERAL Business Role ID SALES_ROLE

GENERAL Business Role Name Sales Rep

GENERAL Description Role for Sales Rep

4. Choose the TabWORK CENTER AND VIEW ASSIGNMENTS.

5. Select below assignment.





CUSTOMER


Tab Work Center/ View ID Work Center/ View Name

WORK CENTER AND

VIEW ASSIGNMENTS

CODACCOUNTWCV

COD_CONTACT_WCV

Customers -> Accounts

Customers -> Contacts

WORK CENTER AND

VIEW ASSIGNMENTS

COD_PRODUCTDATA

COD_MATERIAL

Products

Products -> Products

WORK CENTER AND

VIEW ASSIGNMENTS

COD_SALES_WCF

COD_OPPORTUNITY_WCVIEW

COD_MKT_PROSPECT_WC

COD_MARKETINGLEAD

Sales

Sales -> Opportunities

Sales -> Leads

Sales -> Sales Leads

WORK CENTER AND

VIEW ASSIGNMENTS

COD_ACTIVITIES Activities

WORK CENTER AND

VIEW ASSIGNMENTS

PEOPLE Employees

6. Select Action àActivate.

7. Save and Close the business roles page.





22 CUSTOMER

2.2.2 Master Data Preparation Manually

2.2.2.1 Job Definition




Note

Some Work Centers are not displayed on the UI, Use the Tab menu on the top- right corner to select

from the list.

2. Under the section Company, choose Job Definition.

3. ChooseNew and input Job Name and Job ID.

4. ChooseSAVE then chooseNEW.

5. Repeat the previous two steps for the following entries.





CUSTOMER


Example

Job Name Job ID

Chief executive officer CEO

Sales Representative SALESREP

Sales Manager SALESMGNR

Sales Director SALESDTR

6. Close the page.

2.2.2.2 Add Activities into Project for Integration

1. Navigate to the following Work Center View.



2. ChooseOpen Activity List .

3. ChooseFine-Tune tab.

4. SelectAll Act ivities in theShow field and ChooseGo

5. Add below activities to the project scope by selecting them and Choose Add to Project





24 CUSTOMER

Activities Activity Group

Distribution Channel Sales

Division Sales

Code List Mapping for integration with

External Applications and Solutions

Communication and Information Exchange

6. ChooseClose .

2.2.2.3 Define Organizational Structure




2. ChooseOrg Struct ures.

3. ChooseEdit then switch to Planning Area

4. Input the effective-from dat a and ChooseOK





CUSTOMER


5. ChooseNew àOrg Structur e to define Company

Tab Field Value

General Org Unit ID <Org Unit ID>

For example:1000

General Org Unit Name <Org Unit Name>For example: SOD_INT_ERP

General Working Day Calendar 2-USA with 5 working days (Mon-Fri)

Definitions Company Checked

Definitions Country of Registration <Country> For example: US – United

States

Definitions Reporting Line Unit Checked

Addresses Country <Country> For example: US – United

States





26 CUSTOMER





CUSTOMER


6. ChooseSave .

7. Select Company defined above

8. ChooseNew àOrg Unit to define Sales organization under this company.

9. Repeat the previous 2 steps for other Org Unit with different Org Unit ID and Name.

Example

Org Unit ID Org Unit Name

S1000 Dom. Sales Org

S1010 Dom. Sales Org 2

S1100 Int. Sales Org

S1110 Int. Sales Org 2

10. Create sub org unit for S1000, Select S1000 Org Unit, and ChooseNew àOrg Unit to define Sales Org under

this Org. Repeat this step for the values in below 3 tables.

Example

Tab Field Value

General Org Unit ID S100010

General Org Unit Name Direct Sales


Tab Field Value

General Org Unit ID <Org Unit ID> S0001

General Org Unit Name Sales Org. 0001

General Working Day Calendar 2-USA with 5 working days

(Mon-Fri)


Functions Sales Organization Checked





28 CUSTOMER


Functions Sales Checked

Tab Field Value


General Org Unit Name Wholesale




Tab Field Value


General Org Unit Name Other Sales




11. Create sub org unit for S1100, Select the S1100, and ChooseNew àOrg Unit to define Sale Org under this org.

Repeat this step for the values in below 3 tables.

Example

Tab Field Value


General Org Unit Name Direct Sales








CUSTOMER


Tab Field Value


General Org Unit Name Wholesale




Tab Field Value


General Org Unit Name Other Sales




12. ChooseCheck à Check All , if no issue, Choose Activate à Activate All and close the org structure page.





30 CUSTOMER

Note

All the above value or information depend on customer's real business, and thus has to be related

accordingly.

2.2.2.4 Define Employees

1. In below Work Center View



2. ChooseEmployees





CUSTOMER


3. ChooseNew àEmployee , maintain below values and Choose Save and Close

Field Value

First Name Direct Sales

Last Name Dom

Organization Unit S100010 - Direct Sales

J ob ID SALESREP - Sales Representative

4. ChooseSave and Close .





32 CUSTOMER

5. ChooseUsers àBusiness Users under Adm inistrat or àGeneral Sett ings.

6. ChooseGo , Select User ID related to the Employee just created

For example: DOMDIRECTD SALES1

7. In the next screen, ChooseEdit àAttributes

Field Value

User ID DOMDIRECTSALES

Password <Password>

8. ChooseEdit Access Rights ; ChooseYes to save the changes

9. Assign role to the user as below

Business Role ID Assigned to User

SALES_ROLE Checked





CUSTOMER


10. ChooseSave and Yes to the Confirmation pop up.

2.2.2.5 Define Distribution Channel




2. ChooseOpen Activity List .3. ChooseFine-Tune.

4. ChooseDistribution Channel in the table.

5. ChooseAdd Row .

6. InputDistribution Channel andDescription, maintain the following distribution channels.

Example

Distribution Channel Description

Z1 Direct sale Z1





34 CUSTOMER

Z2 Wholesale Z2

Z3 Other sales Z3

7. ChooseSave and Close .

2.2.2.6 Define Division for Product




2. ChooseOpen Activity List .3. ChooseFine-Tune

4. ChooseDivision from the Activity table.

5. ChooseAdd Row and maintain the following values.

Division Description

01 Product Division 01



6. ChooseSave and Close

2.2.2.7 Define Product Categories






CUSTOMER




2. ChooseProduct Categories

3. ChooseNew Hierarchy

4. Define ROOT Category

5. For others, first Choose ROOT, then ChooseAction àAdd Subcategory , fills the value like below, and Select

Product Assignment Allowed .

Note

Product Category ID can be maintained on the left, the Production Category and Product Assignment

Allowed can be maintained on the right.

Product Category ID is the Material group available in S/ 4 HANA system.





36 CUSTOMER

Example

Product Category ID Product Category

ROOT ROOT

1 Material group 1

2 Material group 2

YBD01 Product Group D01

YBF01 Product Group F01

YBF02 Product Group F02

YBR01 Product Group R01





YBS01 Product Group S01

YBS02 Product Group S02

YBSVM1 Spare parts

YBSVS1 SP-Services

YBT01 Product Group T01

YBZ01 Product Group Z01







CUSTOMER


6. ChooseSave and Close.

2.2.3 Set Up Communication System




2. ChooseCommunication Systems in the Integration division

3. ChooseNew to define Communication System, maintain as following.

Note

Host Name is the value of Worker Node without prefixHttps:/ / .

Enter the information about the backend S/ 4 HANA system. It is important to note that all the

information requested on the screen below is associated with the S/ 4 HANA system (logical system

name, SAP client, and so on) with the exception of the host name, which should be the hostname of the

worker node of SAP HCI system. In addition, make sure to check the option of “SAP Business Suite”. See

chapter Maintain Communication Arrangements to know the System Instance ID, Business System ID,

and IDOC Logical System ID.

4. Maintain the person responsible for system maintenance in the TECHNICAL CONTACT.





38 CUSTOMER

5. ChooseSave and then ChooseActions àSet t o Active.

6. ChooseClose.

2.2.4 Adjust MashUp URL



View MASHUP AUTHORING

2. Click the Mashup link, with Mashup ID SM00036 (S/ 4 HANA Sales Order View).

3. Select Edit URL under URL Information and enter the below URL. Replace the serverhostname and port details

with the SAP S/ 4HANA system details.

https:/ / <serverhostname>:<port>/ sap/bc/ ui5_ui5/ui2/ ushell/ shells/ abap/ FioriLaunchpad.html





CUSTOMER


4. ChooseSave andClose .

5. ChooseActivate .

2.2.5 ID Mapping


Work Center APPLICATION AND USER MANAGEMENT

View ID MAPPING FOR INTEGRATION

2. ChooseEdit ID Mapping for Integration.

3. SelectERP Sales Organizat ions from the drop-down for the fieldMapping of .

4. Select System Instance ID and ChooseGo .

5. Maintain as the following values.

Note

Below this is the mapping between Cloud for Customer and S/ 4 HANA organization structure

External ID values should be available in SAP S/ 4HANA system. Refer Business Configuration in S/ 4

HANA section for details.

ID External ID

S0001 0001

S1000 1000

S1010 1010

S1100 1100

S1110 1110

6. ChooseSave





40 CUSTOMER

7. ChooseERP Product Cat egories

8. Select System Instance ID and ChooseGo .

9. Maintain the following values.

Note

External ID values should be available in SAP S/ 4HANA system. Refer Business Configuration in S/ 4

HANA section for details.

ID External ID

1 01

2 02

ROOT

YBD01 YBD01





CUSTOMER


… …

YWEM YWEM

10. ChooseSave

11. Maintain the above mapping for Employees between SAP S/ 4HANA system and SAP Cloud for Customer.

2.2.6 Configure Communication Arrangement

2.2.6.1 Mass Configuration of CommunicationArrangements.

1. To create multiple communication arrangements, go toAdministrator àComm unication Arrangement for On-

Premise Integration common task.

Work Center ADMI NI STRATOR

View Communi cat i on Ar r angement For On- Pr emi se I ntegrat i on





42 CUSTOMER

2. InSelect Comm unication System step, maintain the SAP backend integration system and middleware. As wellas the System Instance ID and Code List Mapping of SAP on Premise Integration.

3. In the step 1 Select Communication System,

o Under INTEGRATION DETAILS chooseSAP ERP System for Integration with and HCI for Integration

Middleware .

o Under COMMUNICATION SYSTEM maintain theSystem Instance ID of the SAP S/ 4HANA system and

choose Code List Mapping asSAP On-Premise Integration.

4. ClickNext.

5. InCommunication Arrangements , select the communication scenarios mentioned in the table below. These

are relevant for your project scope.

Communication Scenario

Material Replication from SAP Business Suite

Creation of Opportunity Follow Up Document in SAP Business Suite





CUSTOMER


Business Partner Replication from SAP ERP

Note

In case you do not see any of the configuration scenarios, re-check the project scoping to add the

necessary scoping elements.

6. The Inbound and Outbound tabs are displayed,

7. On the Inbound tab, forApplication Protoco l selectWeb Service from the drop down.

8. ClickNext .

9. In step 3 COMMUNICATION CREDENTIALS ,

o Select Authentication Method as SSL Client Certificate .

o ClickEdit Credentials .

10. On theCertificate tab, chooseUpload Certificat e .





44 CUSTOMER

11. Choose the HCI Client Certificate.

12. ClickOK.





CUSTOMER


13. ForOUTBOUND COMMUNICATION CREDENTIALS clickDownload . The client certificate downloaded here has

to be installed in the HCI system.

14. Enter a name for Cloud for Customer Client Certificate x.509(example C4CSSLClient.cer) and choose Save.

Note

This certificate has to be uploaded while configuring HCI iFlow.

15. ClickFinish.

16. ClickClose.

You may need to check the arrangements details if required.





46 CUSTOMER

2.3 Configure Organizational Work Distribution in SAP Cloudfor Customer


Work Center ADMINISTROR


2. ChooseOrganizational Work Distribut ion

3. ChooseRelevant Distr ibut ion Channels and ChooseEdit ,

4. ChooseAdd Rule to maintain the rules given in the table below.





CUSTOMER


Example

Name Org Unit Responsible

Distribution Channel is Direct sale Z1 SG_100 –Sales Group 100

5. ChooseSave and Close

2.4 Manual Code List Mapping in Cloud for Customer system



View IMPLEMENTATION PROJ ECTS

2. ChooseOpen Activity List.

3. ChooseFine-Tune Tab.

4. ChooseCode List Mapping for Integration with External Applications and solutions in the Table.

5. ChooseMaintain Code List Mapping .

Note

The code list mapping UI contains the following 3 tables which are hierarchical:





48 CUSTOMER

A. Local data type: This shows the data types available in the Cloud for customer system. Here we select data

type for which the code list needs to be mapped.

B. Code list mapping rule: Here we set the code list mapping rules for the data type selected in the above table. There are 2 rules possible:

Local and Remote codes are equal: This rule can be used when the values in the Cloud for customer system and

the ones in the ERP system are the same. If this rule is selected, there is no need to do any mapping for the code

values.

Map Individual values: This rule can be used when the values in the Cloud for Customer system and the ones in the

ERP system are different. If this rule is selected, the individual code values for the data type need to be mapped

with values in the ERP system. An example and the list of ERP tables corresponding to the local data types in

mentioned in the next steps.

C. Code List mapping: Map each code value (only the required ones) for the local data type from Cloud for

customer system with the corresponding values in the ERP system.

6. In theCode List Mapping Definition section, select the row withLocal Data Type Name to configure the code

list values.

7. In theCode List Mapp ing Rule section, maintainMapping Rule .

Note

In theCode List M apping section if you are unable to change existing value, delete the entries and create

new ones.

8. In Code List Mapping section, ClickAdd Row to add new rows in the code list mapping table

9. ClickValue selection in the field Local Code to get the pop up with the list of values.

Note

The steps to enter the mappings is available in the table below with an example.

Field Value Example

Local Code <Code represented by the Cloud for

Customer System>

For the local code type

“BusinessPartnerFunctionTypeC

ode” With value “0003”

Description <Description of what the code represents> Local code value “0003” has a

description “Sales Manager” in

Cloud for Customer.

External Code <Code as maintained in the backend S/ 4

HANA system>

Refer the Business configuration

chapter in SAP S/ 4HANA section.

Inbound Default < If this is checked the Inbound value is

considered as default>

(*)

Outbound Default < If this is checked the Outbound value is

considered as default >

(**)

(*) In case where each External code is mapped to multiple Internal codes

(**) In case where each Internal code is mapped to multiple External codes.





CUSTOMER


3 Configuration in SAP S/ 4HANA

3.1 Define Communication User

Overview

Communication user defined in S/ 4 HANA system is used for inbound communication and processing messages

in the system. Technically, the user is used to call OData services in S/ 4 HANA from HCI.

Prerequisites

Administrator user should have the catalog role ID SAP_BCR_CORE_IAM assigned in SAP S4HANA system.

Procedure

1. Access the SAP S4HANA system and log in as an Administrator.

2. ChooseMaintain Communication Users in Identity and Access Management.

3. ChooseCreate .

4. On the Next screen, maintain the following values and Choose Create.

User Data

User Name <user name> for example: CODINTEG

Description S4HANA Communication User

Password <password>

Communication Scenario





50 CUSTOMER

Field Name Value

Logistics - SAP Cloud for

Customer

Checked

5. ClickCreate .

3.2 Create Key User

Overview

Key User in S/ 4HANA System: - is used for monitoring the inbound and outbound messages. Also used for initial

data loads from SAP S/ 4HANA system into SAP Cloud for Customer system.

Procedure

1. Access the SAP S/ 4HANA system and log in as an Administrator.

2. ChooseMaintain Business Users in Identity and Access Management

3. ChooseCreate.

4. On theUser Maintenance: Init ial scr een,enter the following values:

Field Name Value

User KEYUSER

5. ChooseCreate .

6. On theMaint ain User screen , maintain the following values and Choose Save.

Address tab page

Last Name <user name> for example: KEYUSER

E-Mail <valid E-Mail Address>

Comm.Meth Remote Mail

7. Logon data tab page





CUSTOMER


User Type Dialog User

Password <password>

8. Roles tab page

Field Name Value

Role XXXXXXXXXXXXXXXXXX

9. ClickSave .

10. Login into SAP S/ 4HANA system with KEYUSER and initial password.

11. Change the initial password to productive password.

3.3 Maintain Communication Arrangements

Overview

The Communication arrangement in S/ 4 HANA system defines all relevant information for the communication

with HCI. For example, it contains the communication system, inbound and outbound authentication.

Prerequisites

In the SAP S/ 4 HANA system, the administrator user has the catalog role ID SAP_BCR_CORE_COM.

Tips on how to gather required information

Host Name See chapter How to get the fully qualified HCI runtime URL.

Port It is 443 always.

Path You get it from the following place once the iFlow Replicate Business

Partner from SAP Business Suite is deployed. See Configure andDeploy iFlows using SAP HCI Web UI

In the HCI Web UI navigate to Monitor. Click on the Started tile. Search

for the iFlow Replicate Business Partner from SAP Business Suite. Click

on status Started. The second part of the listed endpoint is the needed

service end point. Example: / cxf/XXX/C4C/ XXXXX

Outbound Authentication

(Basic Authentication):

Username and password

Typically, it is the p-user (SCN user) or s-user (SMP user).

The role ESBmessaging.send should be assigned to the p- or s-user.

Please refer to Overview of Authorization Groups in SAP HCI.

http://dwdf213.wdf.sap.corp/SAaP_SolnPrj/0934_C4C_S4_Cloud/02_Deliverables/03_Delivery_and_Production/1_Implementation_Content/2_Config_Guides/javascriptvoid(0);





https://uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/93810d568bee49c6b3d7b5065a30b0ff/LATEST/en-US/frameset.html?2937e5ca6ef448cfb21451a2461cc2a6.html










52 CUSTOMER

Procedure

Log on to your SAP S/ 4 HANA system as an administrator who has required authorization.

Choose the Maintain Communication Arrangements tile.

Within the App “Maintain Communication Arrangements” check if an arrangement for scenario SAP_COM_0025

already exists. If not, click on the “Create” button.

Select the communication scenario ID SAP_COM_0025 through value help, and enter the following mandatory

parameters:

Communication System ID: Enter a meaningful ID for your Cloud for Customer tenant.

Communication System Name: Enter a meaningful description for your Cloud for Customer tenant.

Logical System: Not needed.

Host Name: Full qualified host name of your HCI system. See chapter How to get the HCI Runtime URL

Port: Port number of the HCI system which is always 443





CUSTOMER


Note down the S/ 4 HANA tenant ID which is displayed under My System. This will be used in chapter Set Up

Communication System. This should be used in the fields like System Instance ID, Business System ID, IDOC

logical system ID while defining the communication system in SAP Cloud for Customer.

After filling the mandatory fields, press “Enter” and new parameters will appear.

Enter the other parameters:

Inbound Basic Authentication: Select the communication user from the value help that you have created in

chapter Define Communication User.

Outbound Basic Authentication: User and password of the user in HCI system.

Path: Services end point URL in HCI system.

Take a note for the logical system ID (Field: “My System”). You will find the information in the General Data block:

Save the Communication Arrangement.





54 CUSTOMER

3.4 How to get the S/ 4HANA System URL

The S/ 4HANA System URL is included in the S/ 4HANA provisioning e-mail which was provided from SAP (email

sender: SAP s4scc) and includes system access and administrative information.

Note down the system access URL for business users.

3.5 Business Configuration in S/ 4HANA

Purpose

o Configure Your Solution

o Sales Order type

o Org data

o The IMGs which are not available as part of Configure Your solution

o Check the message monitoring in C4C and S4H and configure the Code list mapping, ID mapping in C4C.

3.5.1Configure Your Solution

Purpose

This section describes how to check the Sales Organization, Sales order type values maintained in the SAP

S/ 4HANA system. These values should be mapped with the values in SAP Cloud for Customer for the messages

to flow correctly.

Procedure

1. Access the SAP S/ 4HANA system by logging in as Administrator user

2. Access the tile Manage Your Solution in End to End Implementation Experience - Implementation Cockpit.

3. Choose Configure Your Solution.





CUSTOMER


4. For the entry SalesOrganization-Configure, selectStart .

5. Check the Sales Organization value maintained here and ensure the same value is mapped with the Sales

Organization data in SAP Cloud for Customer. Below screenshot shows an example value of Sales

Organization.

6. ChooseBack .

7. Similarly, check the values maintained for Distribution Channel and Sales Document Type.





56 CUSTOMER

3.5.2 Message Monitoring

Purpose

The procedure describes how to monitor the inbound messages into SAP S/4HANA system and correct the

errors by manually maintaining the code-list mapping and ID mapping in SAP Cloud for Customer system.

Procedure

1. Access the SAP S/ 4HANA system using the Key User.

2. ChooseMessage Dashboard SAP IAF in Communication

3. The Interface Monitor page launches.

4. Use theCalendar Monitor to select the date range to view the triggered messages and chooseSearch .

5. In theResult List , view the messages and check for the log details.





CUSTOMER


6. Select the entry you wish to check the log for.





58 CUSTOMER

4 Configuration in HANA Cloud Integration

Note

SAP provides prepackaged, generic integration content called integration flows (iFlows) for the

integration of SAP Cloud for Customer with SAP S/ 4HANA using SAP HANA Cloud Integration.

Prerequisites

To be able to import and deploy iFlows, you need the AuthGroup.IntegrationDeveloper role assigned in your

tenant.

4.1 View prepackaged iFlows using SAP HCI Web UI

1. Access the web UI URL from the provisioning e-mail. It should be in the format:

https:/ / <hcitenant>.hana.ondemand.com/ itspaces.

2. View all pre-packaged integration flows delivered by SAP in the Discover tab.

3. Click on the package SAP Cloud for Customer Integration with SAP S/ 4HANA Cloud Enterprise Edition.

4. For each integration flow, click on the Actions icon to download and view relevant metadata.

4.2 Configure Communication User Credentials from SAP HCIto SAP Cloud for Customer

https:/ / proddps.hana.ondemand.com/ dps/ d/ preview/ 93810d568bee49c6b3d7b5065a30b0ff/ 2015.08/ en-

US/ frameset.html?af0d632c2f5741249cd2b595e8c58d5f.html

https://proddps.hana.ondemand.com/dps/d/preview/93810d568bee49c6b3d7b5065a30b0ff/2015.08/en-US/frameset.html?af0d632c2f5741249cd2b595e8c58d5f.html








CUSTOMER


http:/ / scn.sap.com/community/ cloud-for-customer/blog/ 2014/ 09/ 14/ hana-cloud-integration-hci--

application-edition-learning-series--part-6

4.2.1Deploy Cloud Credential Artifacts

1. Open HCI Web UI URL for example https:/ / XXXXXXXXX.hana.ondemand.com/ itspaces.

2. Navigate to Monitor Menu.

3. Choose Security Material under Manage Security Material and choose Add.

4. In the next pop-up window, Enter Name, exampleC4C_Basic. Enter a description and User, Password of the

SAP Cloud for Customer which should be created in SAP HCI system. Choose Ok.

http://scn.sap.com/community/cloud-for-customer/blog/2014/09/14/hana-cloud-integration-hci--application-edition-learning-series--part-6








60 CUSTOMER

5. ClickOK when it finishes the deployment of the artifact.

6. The artifact will be seen in theArtifacts view.

4.3 Configure Communication User Credentials from SAP HCIto SAP S/ 4 HANA

https:/ / proddps.hana.ondemand.com/ dps/ d/ preview/ 93810d568bee49c6b3d7b5065a30b0ff/ 2015.08/ en-

US/ frameset.html?a65a337912ca47dfb3ac7dbe9d86b6fe.html

4.3.1Deploy S/ 4 HANA Credential Artifacts

1. Open HCI Web UI URL for example https:/ / XXXXXXXXX.hana.ondemand.com/ itspaces.

2. Navigate to Monitor Menu.

3. Choose Security Material under Manage Security Material and choose Add.

https://proddps.hana.ondemand.com/dps/d/preview/93810d568bee49c6b3d7b5065a30b0ff/2015.08/en-US/frameset.html?a65a337912ca47dfb3ac7dbe9d86b6fe.html








CUSTOMER


4. In the next pop-up window, Enter Name, exampleERP_Basic. Enter a description and User, Password of the

SAP S4HANA system example theCODINTEG user created above. ChooseOk .

5. ClickOK when it finishes the deployment of the artifact.

6. The artifact will be seen in the Artifacts view.

4.4 How to get the HCI Runtime URL

The HCI Runtime URL is included in the HCI provisioning e-mail.

Alternatively you can get it from the following place once the iFlow Replicate Business Partner from SAP Business

Suite is deployed. See Configure and Deploy iFlows using SAP HCI Web UI.





62 CUSTOMER

In the HCI Web UI navigate to Monitor. Click on the Started tile. Search for the iFlow Replicate Business Partner

from SAP Business Suite. Click on status Started. The first part of the listed endpoint is the needed HCI tenant

runtime URL. Example https:/ / <tenant>-iflmap.hana.ondemand.com

4.5 How to get the HCI client certificate

In the HCI provisioning e-mail follow the link under Certificate Information. In the resulting screen choose X509

Certificate with option Binary CER. Download it to your local machine.

4.6 Configure and Deploy the iFlow Using SAP Web UI

Note

If you have re-deployed key store (system.jks) in your HCI tenant, you need to re-deploy all the iFlows to

avoid the caching issues.

1. Connect to the tenant management node of the HCI system with the URL http:/ / <tenant management

node>/ itspaces

2. Hover your mouse on the content package, for example: SAP Cloud for Customer Integration with S/ 4HANA

Cloud Enterprise Edition (select the required version) and chooseCopy to Workspace.

3. If the Integration package is being created first time, then you would see the message ‘Integration Package

Created’. If not, you will see the below pop-up asking to either create a new copy of the package or to

overwrite the existing integration package content.





CUSTOMER


4. Select theDesign mode to configure the iFlows.

5. Select the Integration Package copied.





64 CUSTOMER

6. All the iFlows will be shown/ listed in the right side of the page.

7. Select the iFlows described in the table below and chooseActions button in the right and select Configure .

iFlows to be configured

Replicate Business Partner

from SAP Business Suite

Business Partner Replication from

SAP Business Suite





CUSTOMER


Replicate Business Partner

Relationship from SAP

Business Suite

Business Partner Replication from

SAP Business Suite

Replicate Material from SAP

Business Suite

Material Replication from SAP

Business Suite

Create Opportunity Follow

Up Document in SAP

Business Suite

Creation of Opportunity Follow Up

Document in SAP Business Suite

Note

You can either configure a single iFlow or do a mass configuration by checking multiple artifacts

8. Confirm the Information message by choosingOK .

9. Configure the sender system (in this example C4C) and receiver syst em (in this example S/ 4 HANA) details.

10. Under C4C, Choose Sender Authentication as Certificate based authentication from the dropdown menu.

11. Import the SAP Cloud for Customer communication arrangement X.509 certificate usingBrowse button.





66 CUSTOMER

12. For the receiver details, enter the host name of the reverse proxy server and port of the S/ 4 HANA system.

Provide the client details of the S/ 4 HANA system, service and binding if available for the iFlow and choose

Receiver Authentication as Basic Authentication. Enter Credentials Name as the deployed artifact name of

the SAP S/ 4HANA System. Example, ERP_Basic

NoteCheck with your system administrator for the Reverse proxy host details.

For the iFlows, which has receiver as COD, the Host of CoD is the URL of Cloud for Customer system without

HTTPS prefix, i.e, my307315.vlab.sapbydesign.com. In Sender, select Authentication Type as Basic

Authentication .

13. ChooseDeploy .

14. The integration flows are deployed in the HCI tenant.

15. To see the deployed artifacts, CheckMonitor -> Integration Content Monitor .





CUSTOMER


5 Data Loading

5.1 Initial Data Load from S/ 4 HANA

Purpose

This section describes how to execute the initial data load of material and customer master data from your SAP

S/ 4HANA system to the SAP Cloud for Customer system.

PFCG roleSAP_BCR_CMD_PR_ADMIN_PC is required for Initial load operation.

5.1.1Add Business role to Key User

Procedure


2. ChooseMaint ain Catalog Roles in Identity and Access Management.

3. Enter Catalog Role ID SAP_BCR_CMD_PR_ADMIN_PC and press Enter.

4. Select the row entry and chooseEdit .





68 CUSTOMER

5. ChooseAdd User .

6. Enter Key User in theUser Name field and press Enter .

7. Select the User ID and chooseOK .

8. ChooseSave .

9. ChooseBack Twice.

5.1.2Customer Master/ Relationships

1. Access the SAP S4HANA system and log in as Key User.

2. Open the tileExecute Data Replication in Master Data-Product Administration.

3. In Replication Model, select value$S4HTOC4C$, Outbound Implementation as 986_3 and select Manual as

the Replication Mode.

4. ChooseManual Replication Filter Criteria button to select the Business Partner





CUSTOMER


5. Enter the Business Partner details, you wish to replicate to SAP Cloud for Customer.

6. ChooseSave .

7. ChooseExecute to replicate the Business Partner to SAP Cloud for Customer.





70 CUSTOMER

5.1.3Material Master

1. Access the SAP S4HANA system and log in as Key User.

1. Open the tileSend Mat erial in Master Data-Product Administration

2. Enter Message Type as MATMAS_CFS, Logical system as the SAP Cloud for Customer tenant ID and Material

to be sent.

3. Check fieldSend Mater ial in Full and chooseExecute .

Note

IDOCs are sent out asynchronously triggered by a report/ job. The frequency of the job run is set to 15 min.

Related Transaction SJOBREPO

J ob Name: APS_COM_CA_EXEC_IDOC

5.2 Delta Load for Business Partners/ Relationships andMaterial

Purpose

This section describes how to execute the delta data load of material and customer master data from your SAP

S/ 4HANA system to the SAP Cloud for Customer system.

PFCG roles SAP_BCR_CMD_BP_MAINT_PC and SAP_BCR_CMD_PR_MAINT_PC are required for Delta load

operation.





CUSTOMER


5.2.1Add Business roles to Key User



3. Enter Catalog Role ID SAP_BCR_CMD_BP_MAINT_PC and press Enter .


5. ChooseAdd User .

6. Enter Key User in theUser Name field and press Enter.


8. ChooseSave .


10. Repeat the above steps for adding Role SAP_BCR_CMD_PR_MAINT_PC to Key User.

5.2.2 Maintain Customer Master/ Relationships

1. Access the SAP S4HANA system and log in as a Key User.

2. Open tileMaintain Business Partn er in Master Data-Business Partner.





72 CUSTOMER

3. Enter Business Partner details, you wish to modify and replicate to SAP Cloud for Customer

4. ChooseStart .

5. ChooseEdit .

6. Change the necessary Business partner details and chooseSave .

5.2.3 Maintain Material Master

1. Access the SAP S4HANA system and log in as a Key User.

2. Open tileChange Material in Master Data-Product.





CUSTOMER


3. ChooseStart .

4. Select the Material using the input help

5. ChooseSelect View( s)

6. Select the required or All Views and chooseContinue .

7. Select theSales Org . details if required and chooseContinue .





74 CUSTOMER

8. Maintain the required changes and chooseSave .

DELTA LOAD J OB is not working





CUSTOMER


6 Message Monitoring in SAP S/ 4 HANA

6.1 Add Business role to Key User

Procedure

1. Access the SAP S/ 4HANA system and log in as an Administrator.


3. Enter Catalog Role ID SAP_BCR_CA_COM_PC and press Enter .


5. ChooseAdd User .





76 CUSTOMER

6. Enter Key User in theUser Name field and press Enter .


8. ChooseSave .


10. Choose Recipients of a User

11. Search for the user (for example: KEYUSER) to whom the monitoring should work

12. Choose New Entries if you are already not on the New Entries Screen

13. Choose Value help in NS (Namespace) column and select / SDCFC.

14. Choose value help in Recipient for Alert column and select SDCFC_ALL.

15. Select Overview and Tech. Usr checkboxes.

16. Save the entries.

6.2 Monitor Messages

1. Access the SAP S/ 4HANA system and log in as Key User.

2. ChooseMessage Dashboard SAP IAF in Communication

.

3. The Interface Monitor page launches.





CUSTOMER


4. Use theCalendar Monitor to select the date range to view the triggered messages and chooseSearch .

5. In theResult List , view the messages and check for the log details.

6. Select the entry you wish to check the log for.





Copyrights, Trademarks, and Disclaimers

© 2016 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 expresspermission 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 for additional trademark information

and notices.

Configuration Guide SAP S4HANA Cloud Enterprise Edition

Documents

Transcript of Configuration Guide SAP S4HANA Cloud Enterprise Edition