Purpose of the Document

The purpose of the document to provide some examples of data and settings that need to be additional
setup for Fit-to-Standard workshop if Treasury Management is one of the selected business processes to
be explored.

They are maintained in respective system via individual apps.

Hint: The document is created with Text Styles that allows for easy navigation. Check Navigation Pane
under View menu to see the list of examples.

Master Data Required or Related for Configuration or other Settings

Business Partners
If you want to create transactions with business partners, business partners with the assigned role
counterparty (TR0151 – Counterparty) are necessary. Within this role the company-code dependent
settings must be maintained and the authorizations for the relevant product and transactions type must
be allowed. Otherwise, it is not possible to enter a transaction with a business partner.

SAP Help Link:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/e5ec5859d8e54df98492d80564a734c0/
da53e5526913456aa0a4aeb849e4e789.html

Securities Master Data

Securities Master Data like Class Master Data (Manage Security Classes - FWZZ) must be created in
system directly. The security classes cannot be transported and therefore need to be maintained on
each system individually. As a prerequisite the relevant business partners must be created and
additionally the respective role (TR0150 – Issuer) must be assigned. 

The same approach is necessary for the Securities Account (Maintain Securities Account – TRS_SEC_ACC)
to manage and value your positions in the securities area. You can only create a securities account once
you have defined the depository bank (TR0150 – Depository Bank) as a business partner.

SAP Help Link:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/e5ec5859d8e54df98492d80564a734c0/
c118da531198434de10000000a174cb4.html 

Create/Import Banks and Bank Accounts

Before you start to use SAP S/4HANA Finance for cash management, you must set up the bank and bank
account master data. The set-up must be done directly in the productive environment, either manually
or via Excel import (bank accounts).
SAP Help Link:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/186460fdc35a4b64a713da9bb00deb1e/
a1758116d9b24d48a99e3fa61af5de89.html

https://help.sap.com/docs/SAP_S4HANA_CLOUD/186460fdc35a4b64a713da9bb00deb1e/
3e99cf54e81e6374e10000000a44538d.html

Correspondence Master Data

If the Correspondence Framework is being used, master data is required. Therefore, the following
settings must be maintained in system:

- Definition of Fixing References for the confirmation of NDFs using SWIFT MT300 (FTR_FIX_DEF)
- Definition of Values for Expiry Time for FX options (FTR_EXPIRY_TIME_DEF)
- Assign BIC (Bank Identifier Code) and External Securities Acc. ID to Business Partner
(FTR_BP_BIC)
- Assign Business Partner Group and Profiles (FTR_INT_ASSIGN & FTR_EXT_ASSIGN)

SAP Help Link:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/e5ec5859d8e54df98492d80564a734c0/
a6ea32ba287c4a18a6d5090e326283d6.html

Market Data
Market data can be transferred to the system from a file interface or via real-time data feed. You can
use the function for market data transfer from spreadsheets. In addition to the backend functions, you
can also use the SAP Fiori Launchpad to access the Import Market Data App for the data transfer, and
other apps for the manual entry. Dependent on your decision to import the respective market data, the
import needs to be done or checked directly on your productive system. Therefore, transaction TBD4 or
Fiori App Request Current Market Data – Data feed must be tested, and a batch job should be created if
required. If historical market data are relevant, then the manual upload additionally needs to be
executed.

Apps used:

 Import Market Data

 Import Foreign Exchange Rates
 Request Current Market Data – Datafeed

SAP Help Link:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/
e5ec5859d8e54df98492d80564a734c0/3c513ff5d5f1468d81dd84a7743256a2.html
Initialization
Initializing Cash Management
This activity is to set up transactional data that will be used by Cash Management applications. SAP
S/4HANA Finance for cash management consumes data from the One Exposure from Operations table
(database table FQM_FLOW). It contains cash management data such as memo records, and data from
other components like accounting, end-of-day bank statements, TRM, CML, FI-CA, and integrated data
from remote systems.

To use SAP S/4HANA Finance for cash management, perform the following data setup activities:

- Build key information in accounting documents (database table BSEG)

- Load data into One Exposure from Operations
- Load data from Treasury and Risk Management (TRM), Loans Management (FS-CML), Contract
Accounts Receivable and Payable (FI-CA), and integrated remote systems, into the One Exposure
from Operations hub.

Initializing Parallel Valuation Areas

The initialization process to generate new valuation areas in the Treasury subledger (Treasury Ledger)
must be done in each environment directly, otherwise it is not possible to enter new transactions
(TPM_INITIALIZE).

Settings needs to be entered using App in respective system

Traders and Trader Authorizations
After you have defined traders in the system directly you can use Define User Data app to assign the
traders to users, such as users in role Treasury Specialist - Front Office. Using the Manage Trader
Authorizations app, you can restrict the transactions a trader may conclude to the individual values.
Additionally, the maintenance of the transaction authorization needs to be done on every system
individually via Fiori App Manage Trader Authorizations or TBT1.

SAP Help Link:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/
e5ec5859d8e54df98492d80564a734c0/09bc501a83ef466b9df1adb8e5275431.html

Definition of Time Pattern for Hedging Areas

The time patterns that you define are relevant for the target quota table of the hedging area. These
settings are necessary for the Hedge Management Reporting via the Hedge Management Cockpit. This
information is required to be maintained on each system directly (TOE_TIME_PATTERN).

SAP Help Link:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/
e5ec5859d8e54df98492d80564a734c0/3e6b5358bae84442e10000000a4450e5.html

Definition of Hedging Areas

The hedging area is an entity that represents a section of your hedging policy. In the hedging area, you
define the level of granularity with which you want to monitor your foreign exchange risk. You also
specify in the hedging area which exposures and hedging instruments are relevant for the hedging area
(TOE_HEDGING_AREA). The hedging area is the basic master data of Hedge Management reporting and
needs to be maintained directly in the system. It controls the execution of the Hedge Management
Cockpit.

SAP Help Link:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/
e5ec5859d8e54df98492d80564a734c0/0f9ba95626c76b15e10000000a441470.html?q=Time%20pattern