Set-Up Instructions | PUBLIC

SAP S/4HANA
2023-09-12

Setting Up Advanced Payment Management (4MT)

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 SAP Watch List Screening Onboarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1 Maintain RFC Destination for Screening Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 Maintain RFC Destination for Screening Decision. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
3.3 Assign RFC Destination for Watch List Screening. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.4 Configure OAuth Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1 Ticket Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Setting Up Advanced Payment Management (4MT)

2 PUBLIC Content
1 Purpose

To enable the scope item SAP S/4HANA finance for advanced payment management with SAP Watch List
Screening, you need to carry out additional manual configuration steps to create required settings in the system
landscape that has already been installed. As these configuration steps are company-specific, they cannot be
delivered by SAP, and you need to make them in the productive system.

Setting Up Advanced Payment Management (4MT)

Purpose PUBLIC 3
2 Prerequisites

Before you start this configuration guide, please check your SAP S/4HANA on-premise system is installed and you
have a valid license for SAP Watch List Screening.

2.1 SAP Watch List Screening Onboarding

Please refer to this link and refer to the document Administration Guide for SAP Watch List Screening to set up SCP
for SAP Watch List Screening, and please also note down below parameters:

• Host Name [For both Screening and Screening Hits services]

• Port Number [For both Screening and Screening Hits services]
• Path
• Token Endpoint [For both Screening and Screening Hits services]
• OAuth 2.0 Client ID [For both Screening and Screening Hits services]
• Client Secret [For both Screening and Screening Hits services]
• Root certificate of SCP

Setting Up Advanced Payment Management (4MT)

4 PUBLIC Prerequisites
3 Configuration

3.1 Maintain RFC Destination for Screening Request

Procedure

1. Access the transaction using the following navigation option:

Transaction Code: SM59
2. In the Configuration of RFC Connections view, choose Create.
3. In the RFC Destination view, enter the following data:

Field Value

RFC Destination <the ID of RFC destination to screening request endpoint, for example,
SCREENING REQUEST>

Connection Type G

Description <the name of the RFC destination>

4. In the Technical Settings tab, enter the following data:

Field Value

Target Host <the host name of Screening service>

Port <the port number of Screening service>

Path Prefix /grc/watchlistScreening/screening/v2/screeningRequests

5. In the Log On & Security tab, enter the following data:

Field Value

Logon with User Do not use a User

Log on with Ticket Do not Send Log on Ticket

SSL Active

SSL Certificate DEFAULT SSL Client (Standard)

Setting Up Advanced Payment Management (4MT)

Configuration PUBLIC 5
6. Choose Save.

3.2 Maintain RFC Destination for Screening Decision

Procedure

1. Access the transaction using the following navigation option:

Transaction Code: SM59
2. In the Configuration of RFC Connections view, choose Create.
3. In the RFC Destination view, enter the following data:

Field Value

RFC Destination <the ID of RFC destination to screening request endpoint, for example,
SCREENING DECISION>

Connection Type G

Description <the name of the RFC destination>

4. In the Technical Settings tab, enter the following data:

Field Value

Target Host <the host name of Screening service>

Port <the port number of Screening service>

Path Prefix /grc/watchlistScreening/screeningHits/v1/screeningDecisions

5. In the Log On & Security tab, enter the following data:

Field Value

Logon with User Do not use a User

Log on with Ticket Do not Send Log on Ticket

SSL Active

SSL Certificate DEFAULT SSL Client (Standard)

6. Choose Save.

Setting Up Advanced Payment Management (4MT)

6 PUBLIC Configuration
3.3 Assign RFC Destination for Watch List Screening

Procedure

1. Access the transaction using the following navigation option:

IMG Path Financial Supply Chain Management Advanced

Payment Management External Interfaces SAP Watch
List Screening RFC configuration for Watchlist Screening

Transaction Code SPRO

2. In the Change View “RFC Destination for watchlist scenarios”: Choose New Entries and maintain the following
values:

ID RFC Destination

01 Screening Request <the ID of RFC created in step Maintain RFC Destination for Screening Request,
example SCREENING REQUEST>

02 Screening Decision <the ID of RFC created in step Maintain RFC Destination for Screening Decision,
example SCREENING DECISION>

3.4 Configure OAuth Clients

Procedure

1. Access the transaction using the following navigation option:

Transaction Code: OA2C_CONFIG
2. In the overview area, choose Create
3. Select profile /PF1/WLS_SCREENING_REQUEST from the input help in dialog box for the OAuth 2.0 Client
Profile field.
4. Also enter the profile in the Configuration Name field.
5. In the OAuth 2.0 Client ID field, enter the OAuth 2.0 Client ID of Screening service obtained from chapter SAP
Watch List Screening.
6. Confirm your entries with OK.
7. Then make the following entries in the detail area on the Administration tab page:
8. In the Client Secret field, under General Settings, enter the client secret of Screening service obtained from
chapter SAP Watch List Screening.
9. Under Authorization Server Settings, in the Authorization Endpoint field and Token Endpoint field both fill in the
Token Endpoint of Screening service obtained from chapter SAP Watch List Screening.

Setting Up Advanced Payment Management (4MT)

Configuration PUBLIC 7
10. Under Access Settings, select the following radio buttons:
1. Client Authentication: Form Fields
2. Resource Access Authentication: Headings Field
3. Selected Grant Type: Client Credentials
11. Save your entries.
12. In the overview area, choose Create.
13. Select the /PF1/WLS_DECISION_REQUEST profile from the input help in the dialog box for the OAuth 2.0
Client Profile field.
14. Also enter the profile in the Configuration Name field.
15. In the OAuth 2.0 Client ID field, enter the OAuth 2.0 Client ID of Screening Hits service obtained from chapter
SAP Watch List Screening
16. Confirm your entries with OK.
17. Then make the following entries in the detail area on the Administration tab page:
18. In the Client Secret field, under General Settings, enter the client secret of Screening Hits service obtained
from chapter SAP Watch List Screening.
19. Under Authorization Server Settings, in the Authorization Endpoint field and Token Endpoint field both fill in the
Token Endpoint of Screening Hits service obtained from chapter SAP Watch List Screening.
20.Under Access Settings, select the following radio buttons:
1. Client Authentication: Form Fields
2. Resource Access Authentication: Headings Field
3. Selected Grant Type: Client Credentials
21. Save your entries.

Setting Up Advanced Payment Management (4MT)

8 PUBLIC Configuration
4 Appendix

4.1 Ticket Component

In case of issues during the configuration, open an SAP support ticket for the following component: FIN-FSCM-PF

Setting Up Advanced Payment Management (4MT)

Appendix PUBLIC 9
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 an 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.

Setting Up Advanced Payment Management (4MT)

10 PUBLIC Important Disclaimers and Legal Information
Setting Up Advanced Payment Management (4MT)
Important Disclaimers and Legal Information PUBLIC 11
www.sap.com/contactsap

© 2023 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. 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.

THE BEST RUN