1883966-60011-SAP COM 0333 ConfigGuide

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 10

Set-Up Instructions for Implementing a Scope Item

S/4 HANA Cloud Edition 1808


August 2018
English

Market Data for Treasury and Risk Management (1XN)


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.
Example Output 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, F 2 or E N T E R .

ERROR: REFERENCE SOURCE NOT FOUND Market Data for Treasury and Risk Management (1XN)
2 © 2017 SAP SE or an SAP affiliate company. All rights reserved. Table of Contents
Document History

Revision Date Change

1.0 <2018-04-18> Create version for review

Market Data for Treasury and Risk Management (1XN) ERROR: REFERENCE SOURCE NOT FOUND
Document History © 2017 SAP SE or an SAP affiliate company. All rights reserved. 3
Table of Contents

1 Purpose

2 Preparation
2.1 Required Information
2.2 Prerequisites

3 Configuration

4 Communication Arrangement
4.1 Create Technical Communication User
4.2 Create Communication System
4.3 Create Communication Arrangement

ERROR: REFERENCE SOURCE NOT FOUND Market Data for Treasury and Risk Management (1XN)
4 © 2017 SAP SE or an SAP affiliate company. All rights reserved. Table of Contents
1 Purpose

This document describes additional configuration steps that have to be carried out by customers in order to activate the S/4
HANA integration scenario Treasury Posting Journal Integration (SAP_COM_0333). As these configuration steps are customer-
specific, they cannot be delivered by SAP, and must be carried out by the customer.

Market Data for Treasury and Risk Management (1XN) ERROR: REFERENCE SOURCE NOT FOUND
Communication Arrangement © 2017 SAP SE or an SAP affiliate company. All rights reserved. 5
2 Preparation

2.1 Required Information


During the course of the activities described in this guide, you will be required to enter or provide system-specific information.
To ensure a smooth and efficient integration to SAP S/4HANA, we recommend that you have the information listed in the table
below at hand prior to starting the integration process.

Information Required:
SAML Local identity provider certificate of Jam instance Recommendation: Create a zip file

SAML Local identity provider issuer of certificate of Jam


instance

Communication user ID starting with CC

SAP S/4HANA cloud system

2.2 Prerequisites
None

ERROR: REFERENCE SOURCE NOT FOUND Market Data for Treasury and Risk Management (1XN)
6 © 2017 SAP SE or an SAP affiliate company. All rights reserved. Communication Arrangement
3 Configuration

The following sections describe all settings required for this scope item. These can be divided into four main groups:
 Prerequisite settings that have to be checked and which are delivered by SAP
 Communication arrangement set-up

Market Data for Treasury and Risk Management (1XN) ERROR: REFERENCE SOURCE NOT FOUND
Communication Arrangement © 2017 SAP SE or an SAP affiliate company. All rights reserved. 7
4 Communication Arrangement

A communication arrangement needs to be activated in SAP S/4HANA for communication with web services.

The communication arrangement is named SAP_COM_0333 .

4.1 Create Technical Communication User

Prerequisite

In order to carry out the following activity, a business user with a business role must exist. The business role must contain the
business catalog SAP_CORE_BC_COM (Communication Management). For example, the business role
SAP_BR_ADMINISTRATOR (Administrator) is required.

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA cloud system.
2. Select the Maintain Communication Users tile.
3. Choose New to create a new user.
4. Enter a description for the user.
5. Assign a password for the user.
6. Choose Create.
7. Make a note of user data. This is required when you create the communication arrangement.

4.2 Create Communication System

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA cloud system.
2. Select the Communication Systems tile.
3. Choose New to create a new system.
4. Enter a system ID and a system name.
5. Choose Create.
6. Enter information regarding the system you wish to integrate in the Technical Data section.
7. Choose Save.

ERROR: REFERENCE SOURCE NOT FOUND Market Data for Treasury and Risk Management (1XN)
8 © 2017 SAP SE or an SAP affiliate company. All rights reserved. Communication Arrangement
4.3 Create Communication Arrangement

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloudsystem.


2. Select the Communication Arrangements tile.
3. Choose New to create a new communication arrangement.
4. Select SAP_COM_0333 (Treasury Posting Journal Integration).
5. Adapt the Arrangement Name if required.
6. Choose Create.
7. In the Common Data section, select the Communication System from the input help that was created in the Create
Communication System section.
8. The technical user that was created in the Create Technical Communication User section is automatically added to the
Inbound Communication section.
9. Choose Save.

The communication arrangement has been activated.

Market Data for Treasury and Risk Management (1XN) ERROR: REFERENCE SOURCE NOT FOUND
Communication Arrangement © 2017 SAP SE or an SAP affiliate company. All rights reserved. 9
www.sap.com/contactsap

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

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy