How to Implement Mash Up to Show ECC Screen in SAP ...sapidp/...How to implement Mash up to show ECC screen in SAP Cloud for Customer 6 © 2015 SAP SE. All rights reserved. 2 SAP Cloud

© 2015 SAP SE. All rights reserved.

How-To Guide Document Version: 1511 2015.12.07

How to Implement Mash Up to Show ECC Screen in

SAP Cloud for Customer

How to implement Mash up to show ECC screen in SAP Cloud for Customer 2


Copyright

© 2015 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://global.sap.com/corporate-en/legal/copyright/index.epx#trademark 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.

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



Content 1 Introduction .................................................................................................................................................. 4

Business Scenario ......................................................................................................................................... 4

Background Information ................................................................................................................................ 4

Prerequisites .................................................................................................................................................. 4

2 SAP Cloud for Customer Configuration .................................................................................................... 6

Activate ERP Integration using Cloud Scoping ............................................................................................. 6

Setup Communication System ...................................................................................................................... 8

Create Communication Arrangements .......................................................................................................... 9

Setup URL MASHUP ................................................................................................................................... 12

Assign Tickets view to the Business User ................................................................................................... 14

Enable Mash up via personalization ............................................................................................................ 15

3 SAP ERP Configuration ............................................................................................................................ 19

BAdI implementation for Ticket reference and Logical system ................................................................... 19

Create a report in SAP ERP System ........................................................................................................... 21

Create transaction code for Report ............................................................................................................. 24

Output Determination .................................................................................................................................. 26

4 Middleware Configuration ........................................................................................................................ 27

SAP Process Integration ............................................................................................................................. 27

SAP HANA Cloud Integration ...................................................................................................................... 27



1 Introduction Business Scenario

This document describes how a Cloud for Service (Service on Demand) system and an ECC system can be set up to enable creation of a follow-up SD sales order from a Service on Demand ticket. Within ticket processing, a service agent wants to create a follow-up sales order with reference to the ticket. This might become necessary for different reasons, like the replacement of a defective part.

We assume that a B2C use case and at least one customer master record exists in the ECC system. The organizational data of this customer is maintained in the Cloud for Service system.

Background Information

This document details the steps required to enable bi-directional communication between SAP Cloud for Customer and SAP ERP systems, using SAP Process Integration/SAP Hana Cloud Integration as the integration middleware layer. Configuration scenarios designed for SAP Process Integration are enabled for configuration and deployment utilizing this document.

Prerequisites

SAP ERP The ERP system must contain the following ABAP components:

1. SAP_BASIS 700 SP18 or higher 2. SAP_APPL 600 SP15 or higher

- An ITS (Internet Transaction Server) is running for the ECC system. - The “webgui” service has been activated in transaction SICF (path sap/bc/gui/sap/its/webgui) - The service agent has access to the SAP ECC system. - Process Integration between the Cloud for Customer and ECC system instances has been set up using a PI or HCI system. The PI / HCI maps ECC outbound interface COD_SERVICE_REQUEST_CONF.ORDERS05 of namespace urn:sap-com:document:sap:idoc:messages to Cloud for Customer inbound interface ServiceRequestBulkProcessingConfirmationIn of namespace http://sap.com/xi/AP/CRM/Global.



Note: - “XI” denotes a PI or HCI system. SAP Cloud for Customer Initial setup and configuration was already performed in the tenant, as it is mentioned in the SAP Cloud for Customer Administrator Guide



2 SAP Cloud for Customer Configuration

Activate ERP Integration using Cloud Scoping

1. Connect to the SAP Cloud for Customer system using an internet browser and open the

Business Configuration tab.

2. In the Show dropdown, choose All Current Projects.

3. Select the project, and click Edit Project Scope.



4. Click Next

5. Click Next. Under Communication and Information Exchange Integration with External

Application and Solutions, select Integration with SAP ERP, Integration of Master Data and Integration into Sales, Service and Marketing Processes.

6. Click Next. Under Communication and information Exchange Integration with External Application and Solutions Integration into Sales, Services and Marketing Processes and scroll to group Service Requests. Select the question “Do you want to create follow up documents for service requests from

your cloud solution to an external application or solution?”

7. Click Next. In the dialog box that opens, click Yes and then click Finish.



Setup Communication System

1. Under the Administrator tab, click Communication Systems.

2. Click New to create a new communication system.

3. Enter the host name of the middleware system such as SAP HCI or SAP PI and check the option of SAP Business Suite.

4. Enter the information about the backend ERP system. It is important to note that all the information requested on the screen below is associated with the ERP system (Business System ID, IDOC logical system ID, SAP client, and so on.).

5. Click ActionsSet to Active.



6. Click Save and Close.

Create Communication Arrangements

1. Login to the SAP Cloud for Customer system.

2. Under the Administrator tab open Communication Arrangement For On-Premise Integration.

3. Under Select Communication System tab, select the integration details as shown below. Enter the

business system name of the PI system or HCI system, based on your integration middleware.



4. Under Communication System, select the SAP ERP System Instance ID and Code List Mapping value as SAP On Premise Integration.

5. Click Next.

6. Under Communication Arrangements tab, select the communication scenario Creation of Ticket

Follow-up document in SAP ERP. For more details, you can see the chapter Configure Communication Arrangements from the corresponding integration guide.

7. Under Inbound Communication Credentials, select the Authentication Method. For example in this case, SSL Client Certificate is selected. Click Edit Credentials.

8. In the Certificate tab, click Upload Certificate and choose the PI client Certificate or HCI Client

Certificate based on your integration middleware.



9. Click OK.

10. Click Finish.



11. Under Confirmation, click Close.

Setup URL MASHUP

1. Under the Administrator work center, choose MASHUP AUTHORING

2. Create a new URL MASHUP



3. For the Mashup Category select Productivity & Tools, and for Port Binding select Ticket information.

Enter the mashup name and description. Enter the URL in the https://<serverhostname>:<port>/sap/bc/gui/sap/its/webgui?sap-client=<client> format. Replace server and port with your backend SAP ERP backend information. After entering the URL, click Extract Parameters.

Note: - You will find the URL when you call transaction SICF in the backend SAP ERP system, press execute, and navigate to the tree default_host/sap/bc/gui/sap/its/webgui. Via right mouse click, choose “Test Service”.

4. Add the URL parameters (constants in angular brackets to be replaced) with their corresponding parameter bindings. Parameter bindings can be seen by using the value help button displayed in Parameter Bindings column.

URL Parameter Constant Example Parameter Binding

Remark

sap-client <ECC system client>

004

sap-language <user language>

EN Can be omitted

~OKCODE /08

~TRANSACTION ZCOD Transaction code created for the report.

p_title Report parameter (Part of Address)

p_logsys <Own logical system ID of the cloud for customer system as addressed by ECC>

0LO7BSV

Report parameter (Logical system). Logical system name can be found in any communication arrangement, under My Communication Data (My System field)



p_vgbel Ticket Report parameter (Part of Address). Use the value help displayed in Parameter Binding column.

p_name CustomerName Report parameter (Part of Address)

p_street CustomerAddressStreetName

Report parameter (Part of Address)

p_house CustomerAddressHouseNumber


p_cntry CustomerAddressCountryCode


p_zip CustomerAddressPostalCode


p_city CustomerAddressCityName


p_email CustomerEmail Report parameter (Part of Address)

p_kunnr External CustomerID

5. Choose Save and Close.

Assign Tickets view to the Business User

1. Under the Application and User Management workcenter, choose Business Users



2. Choose the business user and edit the Access Rights

3. Under Work Center and View Assignment, select the flag Assigned to User for Tickets View.

4. Click Save and confirm the dialog box. 5. Click Close.

Enable Mash up via personalization

1. Make the new URL mash up visible in the UI via personalization. For example, create a new ticket.



2. Navigate to Personalize This Screen, then to Mashups and Web Services displayed in the side bar that opens.



3. Select the new mash up and make it visible.



4. Save the changed personalization settings.



3 SAP ERP Configuration BAdI implementation for Ticket reference and Logical system

Note: - The code which is provided here should only serve as an example and may have to be adapted as per your needs.

1. Execute transaction code /nSE19. Under the Create Implementation section, enter the Enhancement Spot

name as ES_BADI_SD_SALES_BAPI. 2. Choose Create Implementation button and enter the Enhancement Implementation name and short text.

3. Choose the green arrow in the Create Enhancement Implementation window to save the BAdI

implementation. 4. Enter the following details in the Create BAdI Implementation window and choose enter:

5. Click Save 6. Expand the newly created definition and double click on Implementing Class



7. Double click on the method name and accept the dialog box with Yes

8. Enter the following lines of code between METHOD IF_BADI_SD_SALES_BAPI~CHANGE_INPUT and ENDMETHOD lines and choose Activate. DATA: lv_reference_document TYPE vgbel, lv_logsysb TYPE vbak-logsysb. CHECK cs_vbakkomx-updkz IS INITIAL OR cs_vbakkomx-updkz EQ 'I'. IMPORT gv_refdoc TO lv_reference_document gv_logsysb TO lv_logsysb FROM MEMORY ID 'ZCL_COD_BADI_ORDER_CREATE'. " ZCOD_ORDER_CREATE_VIA_DIA CHECK lv_reference_document IS NOT INITIAL. FREE MEMORY ID 'ZCL_COD_BADI_ORDER_CREATE'. MOVE: lv_reference_document TO cs_vbakkom-vgbel, '2' TO cs_vbakkom-vgtyp, lv_logsysb TO cs_vbakkom-logsysb.



Create a report in SAP ERP System

Note: - The code which is provided here should only serve as an example and may have to be adapted as per your needs.

1. Execute transaction /nSE38. Enter the report name as ZCOD_ORDER_CREATE_VIA_DIA and click Create

2. Enter the Title e.g., Report to Create a sales order with an external reference

3. Under Attributes, choose the input for the Type field as Executable program and input for the Status field as Test Program and click Save

4. Choose Local Object or enter Package name and click Save.



5. Delete all the lines from the ABAP Editor and paste the following lines of code:

*&---------------------------------------------------------------------* *& Report ZCOD_ORDER_CREATE_VIA_DIA *& *&---------------------------------------------------------------------* *& Create a sales order with an external reference *& Called from SAP Cloud for Service Ticket processing via URL Mashup *& The ticket reference (ID together with the originating logical system) *& is transported to an implementation of enhancement spot *& ES_BADI_SD_SALES_BAPI via memory *& *& *&---------------------------------------------------------------------* REPORT zcod_order_create_via_dia. PARAMETERS: p_kunnr LIKE kuagv-kunnr DEFAULT '100000', p_vgbel TYPE vgbel, p_slsorg TYPE vkorg , "DEFAULT 'CPB1', p_distch TYPE vtweg , "DEFAULT 'CB', p_divsn TYPE spart , "DEFAULT '00', p_title LIKE sza1_d0100-title_medi, p_name TYPE ad_name1, p_street LIKE addr1_data-street, p_house LIKE addr1_data-house_num1, p_cntry LIKE addr1_data-country, p_zip LIKE addr1_data-post_code1, p_city LIKE addr1_data-city1, p_region TYPE regio, p_email LIKE sza1_d0100-smtp_addr, p_langu LIKE addr1_data-langu, p_logsys LIKE vbak-logsysb. * Global declarations DATA: gs_sales_header_in TYPE bapisdhead1, gs_sales_partner TYPE bapipartnr, gt_sales_partner TYPE STANDARD TABLE OF bapipartnr, gt_sales_areas TYPE STANDARD TABLE OF bapiknvvky, gs_sales_area TYPE bapiknvvky,



gs_partneraddress TYPE bapiaddr1, gt_partneraddress TYPE STANDARD TABLE OF bapiaddr1, gv_sales_order_number LIKE bapivbeln-vbeln, gv_question(80) TYPE c, gv_answer TYPE c. IF ( p_slsorg IS INITIAL OR p_distch IS INITIAL OR p_divsn IS INITIAL ). * Get Customer Sales Area Details CALL FUNCTION 'BAPI_CUSTOMER_GETSALESAREAS' EXPORTING customerno = p_kunnr * IMPORTING * RETURN = TABLES salesareas = gt_sales_areas. IF gt_sales_areas IS NOT INITIAL. READ TABLE gt_sales_areas INTO gs_sales_area INDEX 1. MOVE: gs_sales_area-salesorg TO p_slsorg, gs_sales_area-distrchn TO p_distch, gs_sales_area-division TO p_divsn. ENDIF. ENDIF. MOVE: 'TA' TO gs_sales_header_in-doc_type, p_slsorg TO gs_sales_header_in-sales_org, p_distch TO gs_sales_header_in-distr_chan, p_divsn TO gs_sales_header_in-division. EXPORT gv_refdoc FROM p_vgbel gv_logsysb FROM p_logsys TO MEMORY ID 'ZCL_COD_BADI_ORDER_CREATE'. MOVE: p_kunnr TO gs_sales_partner-partn_numb, 'AG' TO gs_sales_partner-partn_role. MOVE: p_title TO gs_partneraddress-title, p_name TO gs_partneraddress-name, p_street TO gs_partneraddress-street, p_house TO gs_partneraddress-house_no, p_cntry TO gs_partneraddress-country, p_zip TO gs_partneraddress-postl_cod1, p_city TO gs_partneraddress-city, p_region TO gs_partneraddress-region, p_langu TO gs_partneraddress-langu, p_email TO gs_partneraddress-e_mail. MOVE: '1' TO gs_partneraddress-addr_no, '1' TO gs_sales_partner-addr_link. APPEND gs_sales_partner TO gt_sales_partner. APPEND gs_partneraddress TO gt_partneraddress. CALL FUNCTION 'BAPI_SALESDOCU_CREATEWITHDIA' EXPORTING sales_header_in = gs_sales_header_in IMPORTING salesdocument_ex = gv_sales_order_number



TABLES sales_partners = gt_sales_partner partneraddresses = gt_partneraddress. IF gv_sales_order_number IS NOT INITIAL. WRITE: gv_sales_order_number TO gv_question. CONCATENATE 'Sales order' gv_question 'has been created. Do you want to log off?' INTO gv_question SEPARATED BY space. CALL FUNCTION 'POPUP_TO_CONFIRM' EXPORTING text_question = gv_question IMPORTING answer = gv_answer EXCEPTIONS OTHERS = 1. IF gv_answer EQ '1'. CALL FUNCTION 'AUTHORITY_CHECK_C_FUNCTION' EXPORTING activity = 'CALL' function = 'SYST_LOGOFF' EXCEPTIONS no_authority = 04 OTHERS = 06. CHECK sy-subrc IS INITIAL. CALL 'SYST_LOGOFF'. ELSE. CALL TRANSACTION 'VA03' AND SKIP FIRST SCREEN. ENDIF. ENDIF. 6. Activate the source code by selecting all the inactive objects that will be shown in the objects list.

Create transaction code for Report

1. Execute transaction code /nSE93. Enter the transaction code as ZCOD and click Create



2. Enter the short text and choose the radio button Program and Selection screen (report transaction) and

click Continue.

3. Enter the program name as the name of the report ZCOD_ORDER_CREATE_VIA_DIA and choose the SAPGUI for HTML flag.



4. Click Save

Output Determination

For configuring the output determination, carry out the steps mentioned in the following chapters of the integration guide.

1. Go to Service Market Placehttps://service.sap.com/rds-cfs-erp

2. Choose Download Package

3. Open the Configuration documents and search for the chapters with the following names.

Maintain Output Type o Output type to be configured is COD3 in this case.

Maintain Output Determination Procedure o Make sure that determination procedure contains COD3 as described in the document.

Maintain Output Record o Follow the steps for output type COD3.

4. Automatically generate Integration settings for Data exchange -> Run through the wizard and Select Service Tickets checkbox and complete the execution of the report.



4 Middleware Configuration SAP Process Integration

Make sure that the following objects are configured as described in the integration guide.

SAP HANA Cloud Integration

Make sure that the IFLOW Update ticket from Follow-up Document

(com.sap.scenarios.erp2cod.servicerequest.confirmation) is configured. For more details, you can see the integration guide.

.

Documents

How to Implement Mash Up to Show ECC Screen in SAP ...sapidp/...How to implement Mash up to show ECC screen in SAP Cloud for Customer 6 © 2015 SAP SE. All rights reserved. 2 SAP Cloud