Integration Guide for SAP Supplier Problem- Solving

(1)

PUBLIC 2021-11-12

Integration Guide for SAP Supplier Problem- Solving

THE BEST RUN

(2)

Content

1 Integrating SAP Supplier Problem-Solving with SAP S/4HANA. . . . 3

2 Prerequisites. . . .4

3 Maintain Connection Data. . . . 5

3.1 Create RFC Destination for HTTP Connection. . . 5

How to Find the API Host URL. . . .5

3.2 Create OAuth 2.0 Client. . . .5

How to Find Authorization Server Data. . . 6

3.3 Configure QM Integration Scenario. . . .7

How to Find the UI Host URL. . . .7

3.4 Create Logical System and Assign Destination. . . .7

4 Configure Action Box for Quality Notifications. . . .9

4.1 Create Follow-Up Action. . . 9

4.2 Create Code Group and Code. . . 9

4.3 Define Functions for Action Box. . . 10

2 PUBLIC

Integration Guide for SAP Supplier Problem-Solving Content

(3)

1 Integrating SAP Supplier Problem- Solving with SAP S/4HANA

Purpose

This integration guide provides information about the settings you need to make in the SAP S/4HANA system to be able to trigger a problem-solving process in SAP Supplier Problem-Solving from a quality notification in SAP S/4HANA.

You can find the most current version of this integration guide on the SAP Help Portal under https://

help.sap.com/sps

Integration Guide for SAP Supplier Problem-Solving

Integrating SAP Supplier Problem-Solving with SAP S/4HANA PUBLIC 3

(4)

2 Prerequisites

To be able to integrate your SAP S/4HANA system with SAP Supplier Problem-Solving, the following prerequisites must be fulfilled:

● One of the following support packages is installed on your SAP S/4HANA system:

○ SAP S/4HANA 1809 SPS06

○ SAP S/4HANA 2020 FPS01

If you have not yet installed one of the support packages you can implement the following SAP Notes to install the required features:

1. First, you need to install SAP Note 2990907 . 2. Afterwards, install SAP Note 2991355 .

For SAP S/4HANA 1909 and SAP S/4HANA 2020 you should additionally install SAP Note 3019744 .

● You have configured the SAP Supplier Problem-Solving solution as described in the administration guide.

For more information, see Overview.

● To create problem-solving processes from quality notifications at the item level, you must have one of the following support packages installed in your SAP S/4HANA system:

If you haven't installed any of the support packages mentioned above, you can implement the SAP Note 3031099 .

● To enable fetching of business partners from IAS for D1 Step (Teams) of a problem-solving process, you must have one of the following support packages installed in your SAP S/4HANA system:

If you haven't installed any of the support packages mentioned above, you can implement the SAP Note 3053039 .

4 PUBLIC

Integration Guide for SAP Supplier Problem-Solving Prerequisites

(5)

3 Maintain Connection Data

3.1 Create RFC Destination for HTTP Connection

1. Open the app for defining RFC connections (transaction SM59).

2. Create a new destination with connection type G (HTTP Connection to External Server).

3. Enter a description, for example, Connection to SAP Supplier Problem Solving.

4. Enter the API URL for the host on which the SAP Supplier Problem-Solving system is running (without the protocol prefix https://). For more information how to find the API URL in the SAP Cloud Platform Cockpit, see How to Find the API Host URL [page 5].

5. Enter the port number 443.

6. Enter the following path prefix: /odata/v2/API_QM_SIP_SRV/A_SupplierIssueProcesses.

7. In the logon and security settings, activate SSL.

8. Save the RFC connection.

3.1.1 How to Find the API Host URL

In the RFC destination settings, you need to provide the API URL for the host on which the SAP Supplier Problem-Solving system is running. The following steps help you to find this URL.

1. Log on to the SAP BTP cockpit.

2. Under Subaccounts, select your SAP Supplier Problem-Solving subaccount.

3. Under Cloud Foundry Spaces , open the space for your SAP Supplier Problem-Solving subaccount.

4. Under Service Instances , select the instance for your SAP Supplier Problem-Solving service.

To create service instances and service keys, see Service Instance and Service Key 5. In the Service Keys section, open the keys view (under ... View ).

6. The attribute “sip_api” refers to the API host URL you need for the RFC destination. Copy the URL without https://.

3.2 Create OAuth 2.0 Client

1. Open the app for configuring OAuth 2.0 clients (transaction OA2C_CONFIG).

2. Create a new OAuth 2.0 client and enter the following data:

○ Select the OAuth 2.0 client profile QS8D_SUPPLIER_8D.

Maintain Connection Data PUBLIC 5

(6)

○ Keep the proposed configuration name QS8D_SUPPLIER_8D.

○ Enter the OAuth 2.0 client ID for your authorization server.

For more information how to find the client ID in the SAP Cloud Platform Cockpit, see How to Find Authorization Server Data [page 6].

3. In the detailed settings, enter the client secret of your authorization server.

For more information how to find the client ID in the SAP Cloud Platform Cockpit, see How to Find Authorization Server Data [page 6].

4. In the authorization server settings, enter the following data:

○ Authorization endpoint: <authorization server URL>/oauth/authorize

○ Token endpoint: <authorization server URL>/oauth/token

For more information how to find the authorization server URL in the SAP Cloud Platform Cockpit, see How to Find Authorization Server Data [page 6].

5. Make the following access settings:

○ For the client authentication, select Form Fields.

○ For the resource access authentication, select Header Fields.

○ For the selected grant type, select Client Credentials.

6. Save the new OAuth 2.0 client.

Further Information

OAuth 2.0 Client for AS ABAP

3.2.1 How to Find Authorization Server Data

In the OAuth 2.0 client settings, you need to provide some authorization server data for your SAP Supplier Problem-Solving subaccount. The following steps help you to find this data in the SAP BTP cockpit.

3. Under Cloud Foundry Spaces , open the space for your SAP Supplier Problem-Solving subaccount.

4. Under Service Instances , select the instance for your SAP Supplier Problem-Solving service.

To create service instances and service keys, see Service Instance and Service Key 5. In the Service Keys section, open the keys view (under ... View ).

In the keys view, the following attributes provide the necesssary information:

○ The ID for your authorization server is provided by the attribute “clientid”. This is needed for step 2 under Create OAuth 2.0 Client [page 5].

○ The client secret is provided by the attribute “clientsecret”. This is needed for step 3.

○ The authorization server URL is provided by the attribute “URL”. Copy the URL without https://.

This URL is needed for step 4.

6 PUBLIC

Integration Guide for SAP Supplier Problem-Solving Maintain Connection Data

(7)

3.3 Configure QM Integration Scenario

1. In Customizing for Quality Management (transaction QCC0), choose Environment Tools Configure QM Integration Scenarios .



Note

If this Customizing node is not available in your system you can open the corresponding view V_QINTEG_CONF in transaction SM30.

2. Add a new entry.

3. Enter the following data:

○ Enter the RFC destination you have defined under Create RFC Destination for HTTP Connection [page 5].

○ Enter the OAuth client profile and the configuration name you have defined under Create OAuth 2.0 Client [page 5].

○ Enter the UI host URL for the SAP Supplier Problem-Solving subaccount. For more information, see How to Find the UI Host URL [page 7].

○ Enter the following UI path: /cp.portal/site#StepBasedSupplierIssueProcess-manage?

sap-ui-app-id-hint=ui-customer

○ Set the integration scenario state to active, so that it can be used for triggering a supplier problem- solving process.

4. Save your settings.

3.3.1 How to Find the UI Host URL

In the QM integration scenario, you need to provide the UI host URL for your SAP Supplier Problem-Solving subaccount. The following steps help you to find this URL.

3. Under Instances and Subscriptions, search for your subscribed SAP Supplier Problem-Solving subaccount.

4. Choose Go to Application.

5. Log on to the system and copy the first part of the browser URL including “…ondemand.com”.

3.4 Create Logical System and Assign Destination

1. Open the app for defining logical systems (transaction BD54).

2. Create a new entry and enter the following data:

○ Enter a logical system, for example, S8DONSCP.

Maintain Connection Data PUBLIC 7

(8)

○ Enter a name for the logical system, for example, Supplier Problem-Solving Process on SCP.

3. Save the logical system.

4. Open the app for assigning RFC destinations to logical systems (transaction BD97).

5. Position the cursor on the logical system you have just created and choose More Standard Dialog Destination .

6. Select the RFC destination you have created under Create RFC Destination for HTTP Connection [page 5].

7. Save the assignment.

8 PUBLIC

Integration Guide for SAP Supplier Problem-Solving Maintain Connection Data

(9)

4 Configure Action Box for Quality Notifications

4.1 Create Follow-Up Action

In this step, you create a follow-up action for a task to trigger a supplier problem-solving process.

1. In Customizing for Quality Management (transaction QCC0), choose Quality Notifications Notification Processing Additional Notification Functions Define Follow-Up Actions for Tasks Define Follow-Up Actions for Tasks .

2. Add a new entry.

3. Enter the following data:

○ Enter a technical name for the follow-up action, for example, ZZS8DREQ.

○ For the object type, select Task for Notification by Functions.

○ Enter a short text, for example, Request Supplier Problem-Solving.

4. Save the follow-up action.

4.2 Create Code Group and Code

In this step, you create a code group and a code for a task (catalog 2) and assign the follow-up action you have created.

1. Open the Edit Code Groups app (transaction QS41).

2. Enter catalog 2 (Tasks) and a technical name for the new code group, for example, ZZS8DSCP.

3. Choose Continue.

4. Enter a short text for the code group, for example, Supplier Problem-Solving Process.

5. Set the status of the code group to Released.

6. Select the new entry and double-click on Codes in the dialog structure.

7. Add a new entry and enter the following data:

○ Code: 0001

○ Short text for code: Supplier Problem-Solving Requested

○ Follow-up action: Enter the follow-up action you have created under Create Follow-Up Action [page 9].

8. Save the data.

Configure Action Box for Quality Notifications PUBLIC 9

(10)

4.3 Define Functions for Action Box

In this step, you define three functions for the action box – one for requesting a problem-solving process, one for reviewing a problem-solving process, and another for requesting supplier problem item in SAP Supplier Problem-Solving.

1. In Customizing for Quality Management (transaction QCC0), choose Quality Notifications Notification Processing Additional Notification Functions Define Action Box Define Functions for Action Box . 2. Select notification type Q2 (Complaint Against Supplier) and double-click on Activities in the dialog

structure.

3. To create a function for reviewing a supplier problem-solving process, add a new entry and enter the following data:

1. Enter a technical name for the function (for example, X905) and a description (for example, Review Supplier Problem-Solving)

2. Enter the Notification Type as Q2 3. Enter a sort number, for example, 9979.

4. Set the usage to Any view ( change, display) and Notification.

5. For the documentation, select None.

6. Enter the function module QS8D_DISPLAY.

7. Select any icon you wish to be displayed for the activity in the action box. Add a quick info, for example, Review Supplier Problem-Solving Process.

8. Select Dependent follow-up function.

9. Save the new function and go back to the list of entries.

4. To create a function for requesting a supplier problem-solving process, add an additional new entry and enter the following data:.

1. Enter a technical name for the function (for example, X900) and a description (for example, Request Supplier Problem-Solving).

4. Set the usage to Any view (create, change ) and Notification.

5. For the documentation, select As task.

6. Enter the function module QS8D_REQUEST.

7. Select any icon you wish to be displayed for the activity in the action box. Add a quick info, for example, Request Supplier Problem-Solving Process.

8. For code group and code, use the value help to select the entries you have created under Create Code Group and Code [page 9].

9. Under Specific details for task select Completed.

10. Under Rules select Only performed once.

11. In the dialog structure, choose Dependent Follow-Up Functions and add a new entry.

12. Enter the function you have created in the step before, for example, X905.

13. Go back and save the second function.

5. To create a function for requesting supplier problem process for multiple defect items, add another entry and enter the following data:

1. Enter a technical name for the function (for example, X901) and a description (for example, Request Supplier Problem Item).

10 PUBLIC

Integration Guide for SAP Supplier Problem-Solving Configure Action Box for Quality Notifications

(11)

4. Set the usage to Any view (change, display) and Notification.

5. For the documentation, select As Task.

6. Enter the function module QS8D_REQUEST_ITEM.

7. Select any icon you wish to be displayed for the activity in the action box. Add a quick info, for example, Request Supplier Problem-Solving Item.

8. Enter the code group created in Create Code Group and Code [page 9].

9. Enter the code as 0001 or the one you have specified in Create Code Group and Code [page 9].

10. Set Specific Details for Task as Completed

11. Select Dependent Follow-Up Functions and add a new entry.

12. Enter the function you have created in the step before, for example, X905.

13. Save the new function.

Configure Action Box for Quality Notifications PUBLIC 11

(12)

Important Disclaimers and Legal Information

Hyperlinks

Some links are classified by an icon and/or a mouseover text. These links provide additional information.

About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.

The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code

Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language

SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders, and abilities.

12 PUBLIC

Integration Guide for SAP Supplier Problem-Solving Important Disclaimers and Legal Information

(13)

Important Disclaimers and Legal Information PUBLIC 13

(14)

www.sap.com/contactsap

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. The information contained herein may be changed without prior notice.

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 or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP 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.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.