Administration Guide For SAP S/4HANA For Financial Products Subledger 1812

PUBLIC
Document Version: 1.0 – 2018-12-17
Administration Guide for SAP S/4HANA for

financial products subledger 1812
© 2018 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Useful Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Getting Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 About SAP S/4HANA for financial products subledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

2.1 Subledger Accounting for Financial Instruments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Subledger Accounting for Insurance Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 System Landscape for SAP S/4HANA for financial products subledger. . . . . . . . . . . . . . . . . . . . . . . 9
2.4 Overview of Required SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
3 Security Information for SAP S/4HANA for financial products subledger. . . . . . . . . . . . . . . . . 15

3.1 User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
User Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
User Administration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Authentication and Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
3.2 Role and Authorization Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Authorization Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Standard Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Critical Combinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
3.3 Network and Communication Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Communication Destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.4 Internet Communication Framework Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.5 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Consent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Read Access Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Information Retrieval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Deletion of Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Change Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Business Partner Data Protection Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.6 Security for Third-Party Applications or Other Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.7 Other Required Documents for Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4 Installing SAP S/4HANA for financial products subledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.1 Prerequisites for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2 Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Administration Guide for SAP S/4HANA for financial products subledger 1812
2 PUBLIC Content
4.3 Overall Installation Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Architecture Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5 Configuring SAP S/4HANA for financial products subledger. . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.1 Configuring Subledger Accounting for Financial Instruments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.2 Configuring Subledger Accounting for Insurance Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6 Operating SAP S/4HANA for financial products subledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6.1 Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.2 Periodic Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.3 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7 UI Technology Information for S/4HANA for financial products subledger. . . . . . . . . . . . . . . . 54
Content PUBLIC 3
1 About This Guide
This guide is the central starting point for the implementation of SAP S/4HANA for financial products
subledger. It tells you how to install and implement the Financial Products Subledger and also provides
security and operations information.
This guide addresses the following target audience:
● System administrators
● Technical consultants
● Key users
1.1 Document History
See what changes have been made to this document since it was first released.
 Note
The latest version of this document is available on SAP Help Portal at https://help.sap.com/S4FPSL.
Date Change More Information
December 17, 2018 Initial version
1.2 Useful Links
The following resources provide access to more information about general topics, such as software downloads
or customer incidents.
Resource Where to Find It
User assistance for SAP S/4HANA for financial products http://help.sap.com/S4FPSL
subledger
Information about creating customer incidents http://support.sap.com/incident
SAP Notes search http://support.sap.com/notes
SAP Software Download Center http://support.sap.com/swdc
4 PUBLIC About This Guide
Product Availability Matrix http://support.sap.com/pam
Get Involved Early https://support.sap.com/en/offerings-programs/get-in-

volved-early.html
Sizing https://www.sap.com/about/benchmark/sizing.html
Performance https://www.sap.com/about/benchmark/sizing/perform
ance.html
Information about support package stacks, latest software http://support.sap.com/sp-stacks

versions and patch level requirements
1.3 Getting Support
If you encounter any problems with SAP S/4HANA for financial products subledger, report an incident on
SAP Support Portal.
To report an incident, go to SAP Support Portal at http://support.sap.com/incident . The relevant

component is FS-FPS Financial Products Subledger.
About This Guide PUBLIC 5
2 About SAP S/4HANA for financial
products subledger
SAP S/4HANA for financial products subledger (also referred to here as Financial Products Subledger) is a
comprehensive subledger for financial products for banks, insurance and reinsurance companies, fintechs, and
other corporations. Deployed as an add-on to SAP S/4HANA, it is based on a highly simplified core and
designed for large data volumes, making use of SAP HANA capabilities. With SAP Fiori user experience and a
streamlined data model it is designed to run simple.
Combining financial and cost accounting, Financial Products Subledger allows you to produce multiple,
reconciled valuations for financial products.
The availability of some features may depend on your license agreement with SAP. Features that are not part of
the Financial Products Subledger might require a separate license. For further information, please contact
your SAP Account Executive.
Implementation Considerations
If you want to install the software components of SAP S/4HANA for financial products subledger in the
context of the implementation project for a broader solution such as subledger accounting for insurance
contracts, it is essential that you familiarize yourself with the content of the corresponding solution description
before beginning the installation.
Integration
The back-end instance SAP S/4HANA for financial products subledger contains the business logic and is an
add-on for SAP S/4HANA.
In addition, there is a front-end instance Financial Products Subledger UI, which contains Fiori applications as
an add-on for SAP Fiori Front-End Server.
You can choose to implement an embedded deployment with the back-end and front-end on the same server
or to implement a hub deployment. When you are implementing the hub deployment option, you use separate
servers for the back-end and front-end components in your landscape. You find further information for the
landscape planning and installation of Fiori applications in the corresponding SAP Fiori Implementation
Information .
6 PUBLIC About SAP S/4HANA for financial products subledger
2.1 Subledger Accounting for Financial Instruments
Banks and financial companies are regularly subject to accounting requirements in all jurisdictions. Companies
that operate internationally must observe the valuation principles developed by national authorities and
organizations as well as uniform accounting standards. The obligation to prepare an annual financial statement
requires periodization because a company has to present its financial position on the balance sheet date as
well as its economic development since the last balance sheet date.
Subledger Accounting for Financial Instruments offers you the following advantages:
● You can use several accounting standards simultaneously (multi-GAAP accounting).

● You can quickly and easily adapt to changes to the accounting standards.
● You gain an understanding of how the differences in valuation are due to different accounting standards
(delta accounting).
● You can use posting values for reporting purposes.
2.2 Subledger Accounting for Insurance Contracts
Insurance companies are regularly subject to accounting requirements in all jurisdictions. Companies that
operate internationally must observe the valuation principles developed by national authorities and
organizations as well as uniform accounting standards. The obligation to prepare an annual financial statement
requires periodization because a company has to present its financial position on the balance sheet date as
well as its economic development since the last balance sheet date.
For the insurance industry in particular, this results in many accrual and valuation problems because a large
number of transactions have to be mapped that are still pending at the end of the year. On the one hand
insurance contracts often have terms that extend over more than one accounting period, but on the other hand
losses are settled over several accounting periods or only occur long after the end of the contract. An open loss
settlement usually means that the final amount of the loss is uncertain. However, the time of payment or the
legality of the claim may also be uncertain.
Subledger Accounting for Insurance Contracts offers you the following advantages:
● You can use several accounting standards simultaneously (multi-GAAP accounting).

● You can quickly and easily adapt to changes to the accounting standards.
● You gain an understanding of how the differences in valuation are due to different accounting standards
(delta accounting).
● The granular mapping of the lifecycle stages of an insurance contract enables you to see how results
develop over time and to compare how your expected values differ from the values that were actually
incurred.
● You can use posting values for reporting purposes.
The most important steps are:
1. Contract data is transferred from the market data systems, and contract systems to the SAP system. At
the same time, the distribution functions for the expected losses, premiums, commissions, and insurance
payments are stored in the SAP system from the actuarial systems.
About SAP S/4HANA for financial products subledger PUBLIC 7
 Note
You can deliver estimated cash flows directly to the SAP system instead of contract data and actuarial
data. In this case, steps 2 and 3 are not required.
2. The SAP system starts the process of transferring all this information to Estimated Cash Flow Preparation
where the incoming cash flow information is processed and a best estimate cash flow (BECF) is
determined.
3. The cash flows determined in Estimated Cash Flow PreparationYou can use several accounting standards
simultaneously (multi-GAAP are written back to Financial Products Subledger as best estimate cash
flows and are stored there in the results data.
4. The SAP system generates and saves posting records based on the actual values of the postings and the
provided best estimate cash flows . The system first generates postings that map the distribution of the
cash flows by period, and then it generates additional postings that map the time value of money, the
adjustment for unexpected risks, and the revenue by period (delta accounting).
5. The SAP system generates general ledger documents and transfers these to the general ledger.
Components
To benefit from all the advantages of Subledger Accounting for Insurance Contracts, you can use the following
components:
Component Description Release/Support Package
Financial Products Subledger (FS-FPS) Postings are generated that map the SAP S/4HANA for financial products
distribution of the cash flows by period, subledger
the time value of money, the value ad
justment for unexpected risks, and the
revenue by period (delta accounting).
Estimated Cash Flow Preparation Actuarial models are assigned to the For example: SAP Profitability and
business volume and an estimate of the Performance Management
future cash flow is prepared depending
on the lifecycle stage of the contract.
More Information
● SAP S/4HANA for financial products subledger

● SAP Profitability and Performance Management
2.3 System Landscape for SAP S/4HANA for financial

products subledger
This section describes the technical system landscape and the software components involved.
Financial Products Subledger is an add-on to the SAP S/4HANA Core. You can install it in the following ways:
● One instance (recommended): You install the add-on as one instance together with SAP S/4HANA Core.
This results in lower hardware consumption and a higher standard of performance. Furthermore, you
benefit from the integration of Financial Products Subledger with SAP S/4HANA Core.
● Two instances: You configure two SAP NetWeaver instances - one with SAP S/4HANA Core and one with
SAP S/4HANA Core plus the add-on. Thus, you can balance the load on two separate stacks and have
more flexibility regarding system upgrades.
The following image gives an overview of the possible software stacks:
The following image gives an architectural overview of the relevant software components. The components
"Accountant Workplace" represents the software component UIFPSL, while Financial Products Subledger
represents the software component S4FPSL.
Back-End and Front-End
Back-End
Financial Products Subledger with its back-end applications is an add-on for SAP S/4HANA 1809. You must
install the following instance:
Instance Release SP Stack
SAP S/4HANA server SAP S/4HANA 1809 Initial Shipment Stack (ISS)
You can then install the following instance of Financial Products Subledger with its comprised software
components:
Comprised Software Com

Instance Release SP Stack ponent Versions
Financial Products Subledger SAP S/4HANA for financial Initial Shipment Stack (ISS) S4FPSL 100 (SP00)
products subledger 1812
S4FSFND 100 (SP00)
Front-End
The Financial Products Subledger with its front-end Fiori applications is an add-on for SAP Front-end Server
5.0. You can choose between an embedded deployment or a hub deployment and install corresponding
instances accordingly.
Deployment Scenario Instance Release SP Stack Comment
Embedded Financial Products SAP S/4HANA for fi- Initial Shipment Stack The required front-end
Subledger nancial products sub (ISS) server is part of the
ledger 1812 back-end software
stack
Hub SAP Frontend Server SAP Fiori Front-End Initial Shipment Stack
Server 5.0 (ISS)
7.51 or
SAP Frontend Server

7.52 or
SAP Frontend Server

7.53
You can then install the following instance of Financial Products Subledger with its comprised software
component.
Comprised Software Com

Instance Release SP Stack ponent Versions
Financial Products Subledger SAP S/4HANA for financial Initial Shipment Stack (ISS) UIFPSL 100 (SP00)
products subledger 1812
UI
Hardware and Software Requirements
The minimum system requirements for Financial Products Subledger are described in the SAP Note 2690404
for ABAP add-on S4FPSL, in SAP note 2690405 for ABAP add-on S4FSNFD and in SAP Note 2690406
for UIFPSL.
You can find further information one sizing at https://www.sap.com/about/benchmark/sizing.html .
2.4 Overview of Required SAP Notes
The following SAP Notes are essential for installing, upgrading, and operating SAP S/4HANA for financial
products subledger.
 Note
Make sure that you have the latest version of each SAP Note, which is available on SAP Support Portal at
http://support.sap.com/notes .
Before you start the installation, have a look at the Release Information Notes 2725310 and 2725350 .
SAP Note Number Title Description
2725310 Release information about S4FPSL100 Information on the add-on S4FPSL100

Support Packages and its Support Packages.
2725350 Release information about UIFPSL100 Information on software component

Support Packages version UIFPSL 100 and its Support
Packages.
2711006 S/4HANA for financial products sub How to install the Business Content for
ledger: Business Content Installation S/4HANA for financial products sub
ledger.
2729154 Financial Products Subledger: Esti How to install the Business Content for
mated Cashflow Preparation (ECP) integration of Estimated Cashflow Prep
Business Content Installation aration delivered with the S/4HANA Fi
nancial Products Subledger.
2722778 Configuration for integrating Financial You want to integrate Financial

Products Subledger with General Products Subledger with the General
Ledger Ledger.
2690404 Release strategy and Maintenance In Information on planning the installation,
formation for the ABAP add-on S4FPSL upgrades and support packages of the
ABAP add-on S4FPSL.
formation for the ABAP add-on upgrades and support packages of the
S4FSFND ABAP add-on S4FSFND.
formation for the ABAP add-on UIFPSL upgrades and support packages of the
ABAP add-on UIFPSL.
2710968 S/4HANA for financial products sub How to perform a system copy of a
ledger: Performing a system copy Financial Products Subledger system
including the required post-processing
steps.
SAP Note Number Title Description
Change of workflow system user and You upgraded your system to S/4HANA
2568271
On Premise 1709 or higher. In the Auto
workflow system jobs with S/4 HANA
matic Workflow Customizing (transac
On Premise 1709
tion SWU3), you notice that the status
is not green for "Edit Runtime Environ
ment".
2710975 S/4HANA for financial products sub How to carry out transports or client
ledger: Carry out a Client Copy or Cus copies in S/4HANA for financial prod
tomizing transports ucts subledger.
70228 Add-ons: Conditions and upgrade plan General information for add-ons.
ning
2722355 Partitioning of database tables For large data volumes the partitioning
of database tables is mandatory for
Financial Products Subledger. This sup
ports runtime optimization and data
volume management.
2709579 Change logging: How to-Guide for Changes to personal data can be traced
Financial Products Subledger and reviewed.
2725511 IRF Tool: Data collection displays field Data collected by IRF Framework dis
value instead of text for some charac plays field values for characteristics
teristics and key figures and key figures fields instead of corre
sponding texts.
2725637 IRF for ILM Objects in Financial The Information Retrieval Framework
Products Subledger allows to search for and retrieve per
sonal data of a specified data subject.
Anchor point of the search and data re
trieval are the Financial Products Sub
ledger ILM objects.
2098653 BP_VER: New database design for busi To enable more efficient access to ver
ness partner versioning in Bank Ana sioned business partner data, the data
lyzer model has been extended.
3 Security Information for SAP S/4HANA
for financial products subledger
This section deals with security topics relevant for SAP S/4HANA for financial products subledger.
3.1 User Management
This section provides an overview of how you manage and authenticate users in SAP S/4HANA for financial
products subledger.
Financial Products Subledger uses the user management and authentication mechanisms provided for SAP
S/4HANA. The security recommendations and guidelines for user administration and authentication as
described in the SAP S/4HANA Security Guide also apply to Financial Products Subledger.
3.1.1 User Types
This section describes the types of users relevant for SAP S/4HANA for financial products subledger.
User Type Description
Expert The expert is allowed to use the transactions in the Easy Ac
cess Menu Financial Products Subledger. This user type can
display Source Data and Results Data and is skilled to exe
cute CVPM processes.
Customizer The customizer is allowed to configure the Financial

Products Subledger system.
Administrator The administrator is allowed to administer the Financial

Products Subledger system beyond the business scope of
the expert and the customizer. This user type manages the
integration of Financial Products Subledger into the system
landscape, for example.
Security Information for SAP S/4HANA for financial products subledger PUBLIC 15
3.1.2 User Administration Tools
This section lists the tools available for user management and administration for SAP S/4HANA for financial
products subledger.
Tool Description Prerequisites
User and role maintenance with SAP For more information, see section User
Management in the Security Guide for
NetWeaver AS ABAP (Transactions
SAP S/4HANA, which can be found at
SU01, PFCG)
https://help.sap.com/viewer/p/
SAP_S4HANA_ON-PREMISE.
3.1.3 Authentication and Single Sign-On
This section describes how authentication and single sign-on for users are implemented in SAP S/4HANA for
financial products subledger.
Financial Products Subledger supports the Single Sign-On (SSO) mechanisms provided by SAP NetWeaver.
Therefore, the security recommendations and guidelines for user administration and authentication as
described in the SAP NetWeaver Security Guide also apply to Financial Products Subledger.
For more information, see SAP NetWeaver Security.
3.2 Role and Authorization Concept
This section describes the roles and authorizations available in SAP S/4HANA for financial products
subledger.
Financial Products Subledger uses the authorization concept provided by the SAP NetWeaver AS ABAP.
Therefore, the recommendations and guidelines for authorizations as described in the SAP NetWeaver AS
Security Guide ABAP also apply to Financial Products Subledger.
The SAP NetWeaver authorization concept is based on assigning authorizations to users based on roles. For
role maintenance, use the profile generator (transaction PFCG) on the AS ABAP.
 Note
For more information on how to create roles, see the role administration information in SAP NetWeaver
Security.
16 PUBLIC Security Information for SAP S/4HANA for financial products subledger
3.2.1 Authorization Objects
The section lists the most important security-relevant authorization objects that are used by SAP S/4HANA
for financial products subledger.
Authorization Object Field Field Description Object Description
F_BABR_REG /BA1/BRSRC Source System Smart AFI: Access in Register

Process Step
/BA1/LGENT Legal Entity
ACTVT Activity
F_BABR_BAS /BA1/BRSRC Source System Smart AFI: Basic Authoriza

tions in Accounting
ACC_SYSTEM Accounting System
ACTVT Activity
F_BABR_CLC /BA1/BRCLC Calculator Smart AFI: Calculator
/BA1/BRSRC Source System
ACTVT Activity
F_BABR_UI /BA1/APP Application (in Fiori or Smart AFI: Frontend (UI,

Work Center, ODATA, CDS
ODATA Context)
/BA1/BUSSG Views)
Segment for Segmental Re
/BA1/KOKRS
porting
/BA1/LGENT
Controlling Area
/BA1/ORGUT
Legal Entity
/BA1/PCTR
Organizational Unit
ACC_SYSTEM
Profit Center
ACTVT
Accounting System
Activity
F_BABR_GLC /BA1/LGENT Legal Entity Smart AFI: General Ledger

Connection
ACTVT Activity
F_BABR_ADJ /BA1/LGENT Legal Entity Smart AFI: Manual Adjust

ments and Workflow
/BA1/PCATG Process Category
ACTVT Activity
F_BAFC_PCD /BA1/FCPRC Process Step ID for Process Smart AFI: Process Control
ler
Controller
ACTVT
Activity
F_BABR_SCB ACTVT Activity Smart AFI: Subledger Coding

Block
F_FPS_TLS /BA1/TOOLS Tools Tool Methods, Utilities
ACTVT Activity
F_BAHW_RES /BA1/F0CH1 Characteristic Value 1 (for Results Data: Authorization

Authorization Field) for Result Object
/BA1/F0CH2
Characteristic Value 2 (for Required for the Results
/BA1/F0CH3
Authorization Field) Viewer and for the execution
/BA1/F0CH4 of CVPM process because of
Characteristic Value 3 (for
read and write access to the
/BA1/F0CH5 Authorization Field)
Results Data.
/BA1/F0CH6 Characteristic Value 4 (for
Authorization Field)
/BA1/F0CH7
/BA1/HWRDA
/BA1/HWRT
ACTVT Authorization Field)

Results Data Area
Result Type
Activity
F_BAFW_PM /BA1/F0CH1 Characteristic Value 1 (for CVPM Authorization Object

/BA1/F0CH2 You can use this authoriza
Characteristic Value 2 (for tion object to segregate du
/BA1/F0CH3
Authorization Field) ties regarding the execution
/BA1/F0CH4 of processes.
/BA1/F0CH5 Authorization Field)
/BA1/F0CH6 Characteristic Value 4 (for

/BA1/PAR
/BA1/PRO
/BA1/SEQ
ACTVT Authorization Field)
Process Partition
Analytical Process
Step Sequence
Activity
F_BAF3_GDS /BA1/F3SID ID of a Primary Data Source Authorization for General Pri

mary Data Sources
/BA1/F3STP Category of a Primary Data
Source
ACTVT
Activity
F_BAFF_ET /BA1/ETAPP Application Class for En Authorization for Enhance

hancement Tool Authoriza ment Tool
/BA1/ETTEC
tions
Includes the critical activities
ACTVT
Technical Control Parame for changing DDIC objects
ters - Control via Authoriza but without the DDIC author
tion ization itself.
Activity
F_BAF2_BTC /BA1/F2BTC Business Transaction Class Authorization for Business

Transaction Via BT Class
ACTVT Activity
F_BAF0_ADM ACTVT Activity Admin: RFC Destination and

Characteristic Registration
F_BAF1_AUG /BA1/F1AUG Authorization Group Authorization for Objects via

Authorization Group
ACTVT Activity
Authorization Objects for Business Partner
The table below shows the security relevant authorization objects that are used by the component Business
Partner for Financial Services in Financial Products Subledger.
Authorization Object Description
B_BUPA_ATT Business Partner: Authorization Types
B_BUPA_FDG Business Partner: Field Groups
B_BUPA_GRP Business Partner: Authorization Groups
B_BUPA_RLT Business Partner: BP Roles
B_BUPA_PGM FS Business Partner Custom Grouping
B_BUPR_BZT Business Partner Relationships: Relationship Categories
B_BUPR_FDG Business Partner Relationships: Field Groups
B_BUPA_CRI FS Business Partner: BP Role Cat./Differentiation Criterion
B_BUPA_CRS Business Partner: Credit Standing Data
B_BUPA_RAT Business Partner: Rating Procedures
B_BUPA_SLV Selection Variant for Total Commitment
B_CCARD Payment Cards
B_CLEANSE Business Partner: Data Cleansing
B_BUP_PCPT Business Partner: Purpose Complete
Additional Information:
● Employees, VIPs and other restricted groups of business partners should be secured by own groups.
Restrictions are possible using field AUGRP in table BUT000 (authorization object B_BUPA_GRP) or field
GROUP_FEATURE in table BP001 (authorization object B_BUPA_PGM).
You can use authorization object B_CCARD to grant different authorizations for creating, displaying or
changing payment card data. In CRM, you can use authorization object B_CARD_SEC (Authorization
Encryption Master) to control the encryption or decryption of payment card data.
For more information, see SAP Customer Relationship Management. Under section Application Help, choose
Basic Functions Payment Card Processing Security for Payment Card Data .
In addition, see the Security Guide under section Security.
● In the SAP GUI channel, you can use the authorization object B_BUPA_FDG for UI channel specific, detailed
checks at BDT field-group level.
● You can also check at a more detailed level in the service channel. To do so, you must define your own
authorization objects. The corresponding checks must be implemented in the enhancement BAdIs of the
Business Partner services.
● If you activate the SACF scenario FSBP_RATINGS (FS-BP: Scenario for Ratings and Credit Standing Data)
in the Workbench for Switchable Authorization Check Scenarios (transaction SACF), you can also use the
FS-BP authorization objects B_BUPA_RAT (Business Partner: Ratings) and B_BUPA_CRS (Business
Partner: Credit Standing Data).
● You can use authorization object S_TABU_NAM to control authorizations for settings in the Customizing
activity Set Rating Procedures and Ratings (maintenance view V_TP021).
Standard Authorization Groups in Tables
Direct table access for FS-BP tables (using transaction SE16, for example) is only possible with the following
authorization groups of authorization object S_TABU_DIS:
Authorization Group Description
BPOA Business Partner Application Data
BPOS Business Partner Control Tables
BPOC Business Partner Customizing Tables
BPAA Analytical Business Partner Application Data
BPAS Analytical Business Partner Control Tables
BPAC Analytical Business Partner Customizing Tables
Critical Combinations
The SAP_CA_BP_DEVELOPER_AG role contains * values for authorizations. These * authorizations are critical
because they allow unrestricted access to data or activities.
3.2.2 Standard Roles
This section describes the standard roles used by SAP S/4HANA for financial products subledger.
 Note
You can use these roles as template roles.
Role Description
SAP_FSP_CUSTOMIZER This role contains authorizations for maintaining the cus

tomizing for Subledger Accounting (/BA1/Subledger Ac
counting)
Role Description
SAP_FSP_EXPERT This role contains authorizations for the SAP Menu

Subledger for Financial Products.
Standard roles with extended authorizations for administrators

Role Description
SAP_BA1_ADM_BW This role contains administrator authorizations for BW.
SAP_BA1_ADM_FDB This role contains administrator authorizations for FDB.
SAP_BA1_ADM_RDL This role contains administrator authorizations for the Re

sults Data.
SAP_BA1_EXPERT_BW This role contains modeling and reporting authorizations for

BW.
SAP_BA1_EXPERT_FDB This role contains authorizations for maintaining the cus

tomizing for FDB
SAP_BA1_EXPERT_RDL This role contains authorizations for maintaining the cus

tomizing for the Results Data.
SAP_BA1_SHOW_BW This role contains display authorizations for BW.
SAP_BA1_SHOW_FDB This role contains display authorizations for FDB.
SAP_BA1_SHOW_RDL This role contains display authorizations for the Results

Data.
SAP_BA1_TECH_BW This role contains reporting authorizations for BW.
SAP_BA1_TECH_FDB This role contains application authorizations for FDB.
SAP_BA1_TECH_RDL This role contains application authorizations for the Results

Data.
SAP_BA1_USER_BW This role contains reporting authorizations for BW.
SAP_BA1_USER_FDB This role contains application authorizations for FDB.
SAP_BA1_USER_RDL This role contains application authorizations for the Results

Data.
Standard Roles for Business Partner
The Business Partner for Financial Products Subledger contains several user roles. These roles are given as
examples that must be adapted. Do not use them in your production system in the form in which they are
delivered.
Authorization objects used in these roles have been added manually. To create your own roles, you can use the
template roles or use transactions SU24/SU25 with transaction PFCG and dynamic role creation respectively.
You can display the roles available by using the Profile Generator (transaction PFCG) in the system. You can
also use the Profile Generator to create your own additional roles.
In a multi-system landscape for banking consisting of CRM, FSP and ERP instances, user management is
important. Different user groups exist and need authorizations according to their roles.
The following table shows the standard roles that are used by the Analytical Business Partner.
Role Description
SAP_BA_BP_FS_CUSTOMIZER Role to Customize Business Partners in Analytical Systems
SAP_BA_BP_FS_EXPERT Expert Role to Correct Business Partner Data in Analytical

Systems
If you need a user role to display analytical business partner data, you can use the display permissions of role
SAP_BA_BP_FS_EXPERT (permission for transaction BPV3).
3.2.3 Critical Combinations

This section describes combinations of roles and authorizations in SAP S/4HANA for financial products
subledger.
Financial Products Subledger (FPSL) runs on SAP S/4 HANA. Be careful when you combine FPSL roles with
non-FPSL roles. This may be required if you would like to configure an access to the general ledger in SAP S/
4HANA, for example. Maintain the authorization object S_RFC restrictively and do not provide it with *
authorizations.
The table below contains some of the most important authorization objects in Financial Products Subledger:
Authorization Object Use
F_BAFW_PM Processing data in the context of CVPM processes.
F_BAHW_RES Accessing the Results Data.
F_BAF1_AUTH or Accessing the Source Data.
F_BAF2_BTC
F_BABR* Specific to the accounting logic.
F_BAFC_PCD Process Controller
F_BAFF_ET Enhancement Tool for DDIC extensions in Source Data, Re

sults Data, and accounting.
You can use this authorization object to segregate duties re

garding the execution of processes.
Edit or change activities are generally critical.
Generally, you should not combine the authorizations of the specific FPSL template roles
SAP_FSP_CUSTOMIZER and SAP_FSP_EXPERT with the authorizations of the more general SAP_BA1*
template roles.
Related Information
System Landscape for SAP S/4HANA for financial products subledger [page 9]
3.3 Network and Communication Security
This section provides an overview of the network topology and communication protocols used by SAP S/
4HANA for financial products subledger.
The network topology for Financial Products Subledger is based on the topology used by SAP NetWeaver,
SAP HANA, and SAP S/4HANA. The security guidelines and recommendations described in the security guides
for these components also apply for the financial products subledger.
Related Information
System Landscape for SAP S/4HANA for financial products subledger [page 9]
https://help.sap.com/viewer/nwguidefinder
https://help.sap.com/viewer/p/SAP_HANA_PLATFORM
https://help.sap.com/viewer/p/SAP_S4HANA_ON-PREMISE
3.3.1 Communication Destinations
This section shows an overview of the communication destinations used by SAP S/4HANA for financial
products subledger.
Destination Delivered Type User, Authorizations Description
FPSL system No RFC Dialog User with au The usage is optional.
thorizations for RDL-
Result Viewer The destination is used
(F_BAHW_RES) or for the drill-through
Source Data (contracts from the FI-GL docu
F_BAF1_AUG, business
ment back to the FPSL
transactions
subledger documents
F_BAF2_BTC), Ac
counting Authoriza in the RDL Results
tions F_BABR_BAS Viewer.
and the GL connector
F_BABR_GLC
Destination Delivered Type User, Authorizations Description
FI-GL system No SOAP Technical System user, The usage is optional.

business authoriza
tions required for cre The destination is used
ating ledger docu for sending prepared
ments in FI-GL. general ledger docu
ments from the FS-
FPS system to the FI-
GL system. Service
Consumer is Financia
lInstrumentsAnalytica
lAccountingDocument
PreparationAccoun
tingDocumentNotifica
tionOut, (SWC
S4FPSL, http://
sap.com/xi/BA/
Global ), service pro
vider is AccountingDo
cumentERPBulkNotifi
cation_In (SWC
S4CORE, http://
sap.com/xi/APPL/SE/
Global)
3.4 Internet Communication Framework Security
This section describes how SAP S/4HANA for financial products subledger uses Internet Communication
Framework (ICF) services.
Only activate those services that are needed for the applications running in your system.
For the Workplace for Financial Accountants and Actuaries, the following ICF services are required:
● /default_host/sap/bc/ui5_ui5/ba1/acd
● /default_host/sap/bc/ui5_ui5/ba1/cil
● /default_host/sap/opu/odata/sap/fps_assg_chg_drvrs_srv
● /default_host/sap/opu/odata/sap/fps_chg_ins_liab_srv
Use the transaction SICF to activate these services.
If your firewall(s) use URL filtering, also note the URLs used for the services and adjust your firewall settings
accordingly.
For more information, see the available user assistance for SAP NetWeaver. To find the relevant documents, go
to SAP Help Portal at http://help.sap.com/nw and open the product page for your SAP NetWeaver release.
Search for "activating and deactivating ICF services" and "ICF security".
3.5 Data Protection and Privacy
This section provides information about how SAP S/4HANA for financial products subledger complies with
data protection requirements.
You can find an overview of the system landscape and the architecture components in section System
Landscape for SAP S/4HANA for financial products subledger [page 9].
3.5.1 Introduction
Data protection is associated with numerous legal requirements and privacy concerns. In addition to
compliance with general data protection and privacy acts, it is necessary to consider compliance with industry-
specific legislation in different countries. SAP provides specific features and functions to support compliance
with regard to relevant legal requirements, including data protection. SAP does not give any advice on whether
these features and functions are the best method to support company, industry, regional, or country-specific
requirements. Furthermore, this information should not be taken as advice or a recommendation regarding
additional features that would be required in specific IT environments. Decisions related to data protection
must be made on a case-by-case basis, taking into consideration the given system landscape and the
applicable legal requirements.
 Note
SAP does not provide legal advice in any form. SAP software supports data protection compliance by
providing security features and specific data protection-relevant functions, such as simplified blocking and
deletion of personal data. In many cases, compliance with applicable data protection and privacy laws will
not be covered by a product feature. Definitions and other terms used in this document are not taken from
a particular legal source.
 Caution
The extent to which data protection is supported by technical means depends on secure system operation.
Network security, security note implementation, adequate logging of system changes, and appropriate
usage of the system are the basic technical requirements for compliance with data privacy legislation and
other legislation.
Generic Fields
You need to make sure that no personal data enters the system in an uncontrolled or non-purpose related way,
for example, in free-text fields, through APIs, or customer extensions. Note that these are not subject to the
read access logging (RAL) example configuration.
 Note
Take into account that the Application Log may contain personal data in an unstructured way, i.e. in the
message fields. The protocol may contain the Bank Account Number (or Contract ID respectively) or the
Business Partner ID, for example.
The application log is accessible for example via the CVPM monitor or transaction SLG1. In addition, test
runs of CVPM processes display protocols and detail logs instantly.
3.5.2 Glossary
The following terms are general to SAP products. Not all terms may be relevant for this SAP product.
Term Definition
Blocking A method of restricting access to data for which the primary

business purpose has ended.
Consent The action of the data subject confirming that the usage of
his or her personal data shall be allowed for a given purpose.
A consent functionality allows the storage of a consent re
cord in relation to a specific purpose and shows if a data
subject has granted, withdrawn, or denied consent.
Data subject An identified or identifiable natural person. An identifiable

natural person is one who can be identified, directly or indi
rectly, in particular by reference to an identifier such as a
name, an identification number, location data, an online
identifier or to one or more factors specific to the physical,
physiological, genetic, mental, economic, cultural, or social
identity of that natural person.
Deletion Deletion of personal data so that the data is no longer avail

able.
End of business Date where the business with a data subject ends, for exam
ple, the order is completed, the subscription is canceled, or
the last bill is settled.
End of purpose (EoP) End of purpose and start of blocking period. The point in
time when the primary processing purpose ends, for exam
ple, a contract is fulfilled.
Term Definition
End of purpose (EoP) check A method of identifying the point in time for a data set when
the processing of personal data is no longer required for the
primary business purpose. After the EoP has been reached,
the data is blocked and can only be accessed by users with
special authorization, for example, tax auditors.
Personal data Any information relating to an identified or identifiable natu

ral person (a data subject).
Purpose The information that specifies the reason and the goal for
the processing of a specific set of personal data. As a rule,
the purpose references the relevant legal basis for the proc
essing of personal data.
Residence period The period of time between the end of business and the end
of purpose (EoP) for a data set during which the data re
mains in the database and can be used in case of subse
quent processes related to the original purpose. At the end
of the longest configured residence period, the data is
blocked or deleted. The residence period is part of the over
all retention period.
Retention period The period of time between the end of the last business ac
tivity involving a specific object (for example, a business
partner) and the deletion of the corresponding data, subject
to applicable laws. The retention period is a combination of
the residence period and the blocking period.
Sensitive personal data A category of personal data that usually includes the follow
ing type of information:
● Special categories of personal data, such as data reveal

ing racial or ethnic origin, political opinions, religious or
philosophical beliefs, trade union membership, genetic
data, biometric data, data concerning health or sex life
or sexual orientation.
● Personal data subject to professional secrecy
● Personal data relating to criminal or administrative of
fenses
● Personal data concerning insurances and bank or credit
card accounts
Where-used check (WUC) A process designed to ensure data integrity in the case of
potential blocking of business partner data. An application's
where-used check (WUC) determines if there is any depend
ent data for a certain business partner in the database. If de
pendent data exists, this means the data is still required for
business activities. Therefore, the blocking of business part
ners referenced in the data is prevented.
3.5.3 Consent
SAP S/4HANA for financial products subledger does not provide functionality that allows data subjects to
give and withdraw consent to collect and process their personal data. SAP assumes that the user (for example,
an SAP customer collecting data) has consent from its data subject (a natural person such as a customer,
contact, or account) to collect or transfer data to the solution.
 Note
Financial Products Subledger supports you in the context of fulfilling regulatory requirements and multi-
dimensional management analysis and reporting.
With respect to data protection and privacy be careful to ensure that data that were collected based on
different legitimate purposes are separated.
 Example
Do not mix contractual and legally required data together with data that require an end user’s consent
in the subledger document. Instead, contractual data can be stored at the level of the financial contract
in the Source Data, whereas consensual amendments can be stored, for example, in specific result
types in the Results Data for reporting purposes.
3.5.4 Read Access Logging
Read access logging (RAL) is used to monitor and log read access to sensitive data. Data may be categorized
as sensitive by law, by external company policy, or by internal company policy. Read access logging enables you
to answer questions about who accessed particular data within a specified time frame. Here are some
examples of such questions:
● Who accessed the data of a given business entity, for example a bank account?
● Who accessed personal data, for example of a business partner?
● Which employee accessed personal information, for example religion?
● Which accounts or business partners were accessed by which users?
Read access logging is currently available in, but not limited to the following channels:
● Remote Function Calls (sRFC, aRFC, tRFC, qRFC, bgFRC)

● Dynpro (dynpro fields, ALV Grid, ABAP List, F4)
● Web Dynpro
● Web services
● Gateway (for OData)
The template below shows how these fields are logged and may be combined with additional fields in the
following business contexts.
Configuration Fields Logged Business Context
FPS_ASSG_CHG_DRVRS_SRV Contract ID Assignment of contracts to change rea

sons in the Workplace for Financial Ac
countants and Actuaries
FPSL_RDLVW_ALV Contract ID Result Data - Result Viewer
BA_BT_DISPLAY Contract ID Display of Business Transactions
Business Partner ID
BA_FT_DISPLAY Contract ID Display of Financial Transaction / Fi

nancial Contract
Read Access Logging for Business Partner
Read Access Logging is supported in the service channel for the Financial Services Business Partner starting
with NetWeaver release SAP_ABA 7.40. The following LOG domains are available in transaction
SRALMANAGER:
Domain Description
FS_BP_INTERNAL_ID Business Partner Number
FS_BP_UUID Business Partner GUID
FS_BP_IDENTIFICATION_ID Business Partner Identification Number
FS_BP_IDENTIFICATION_TYPE_CODE Business Partner Identification Type
Sample configurations are available for the following service operations:
● Retrieve Business Partner

● Update Business Partner
● Inform Business Partner
3.5.5 Information Retrieval
Data subjects have the right to receive information regarding their personal data that is being processed. The
information retrieval feature supports you in complying with the relevant legal requirements for data protection
by allowing you to search for and retrieve all personal data for a specified data subject. The search results are
displayed in a comprehensive and structured list containing all personal data of the data subject specified,
organized according to the purpose for which the data was collected and processed.
For information on reporting, the Information Retrieval Framework can be used. The guide mentioned under
More Information explains how you create a purpose, which enables the data retrieval process, and how you
display the consolidated data of the business partner.
You can retrieve the information by using the following ILM objects when you create a purpose:
● BA1_F1_040 (Financial Products Subledger: Archiving of Financial Transactions)

● BA1_F1_041 (Financial Products Subledger: Archiving of Financial Instruments)
● BA1_F2_035 (Financial Products Subledger: Business Transaction)
Results data area (RDL) and result type do not have their own fixed ILM objects (the respective ILM objects are
generated and cannot be used here directly). Therefore, the RDL tables must be added to the IRF models for
financial transactions and financial instruments.
More information
For information on how to configure and use the IRF models, see SAP Note 2725637 , which contains the
guide IRF Data Model Configuration for FPSL ILM Objects.
SAP Note 2725511 - IRF Tool: Data collection displays field value instead of text for some characteristics and
key figures
SAP Note 2725637 - IRF for ILM Objects in Financial Products Subledger
For information on the information retrieval framework, see the SAP Help Portal at SAP NetWeaver 7.5. Under
Application Help choose SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management
Information Retrieval Framework .
For more information on data archiving and deletion, see the SAP Help Portal at https://help.sap.com/S4FPSL.
Access the Application Help under Product Assistance and choose Infrastructure (FS-FPS-IF) Data
Archiving and Deletion in Financial Products Subledger .
3.5.6 Deletion of Personal Data
Simplified Blocking and Deletion
When considering compliance with data protection regulations, it is also necessary to consider compliance
with industry-specific legislation in different countries. A typical potential scenario in certain countries is that
personal data shall be deleted after the specified, explicit, and legitimate purpose for the processing of
personal data has ended, but only as long as no other retention periods are defined in legislation, for example,
retention periods for financial documents. Legal requirements in certain scenarios or countries also often
require blocking of data in cases where the specified, explicit, and legitimate purposes for the processing of
this data have ended, however, the data still has to be retained in the database due to other legally mandated
retention periods. In some scenarios, personal data also includes referenced data. Therefore, the challenge for
deletion and blocking is first to handle referenced data and finally other data, such as business partner data.
Deletion of Personal Data
The processing of personal data is subject to applicable laws related to the deletion of this data when the
specified, explicit, and legitimate purpose for processing this personal data has expired. If there is no longer a
legitimate purpose that requires the retention and use of personal data, it must be deleted. When deleting data
in a data set, all referenced objects related to that data set must be deleted as well. Industry-specific legislation
in different countries also needs to be taken into consideration in addition to general data protection laws. After
the expiration of the longest retention period, the data must be deleted.
This SAP product might process data (personal data) that is subject to the data protection laws applicable in
specific countries as described in SAP Note 1825544 .
Deletion
To enable even complex scenarios, SAP simplifies existing deletion functionalities to cover data objects that are
personal data by default. For this purpose, SAP uses SAP Information Lifecycle Management (ILM) to help you
set up a compliant information lifecycle management process in an efficient and flexible manner. The functions
that support the simplified blocking and deletion of personal data are not delivered in one large
implementation, but in several waves. Scenarios or products that are not specified in SAP Note 1825608
(central Business Partner) and SAP Note 2007926 (ERP Customer and Vendor) are not yet subject to
simplified blocking and deletion. Nevertheless, it is also possible to destroy personal data for these scenarios or
products. In these cases, you have to use an existing archival or deletion functionality or implement individual
retention management of relevant business data throughout its entire lifecycle. The ILM component supports
the entire software lifecycle including storage, retention, blocking, and deletion of data.
This SAP product uses SAP ILM to support the deletion of personal data as described in the following sections:
End-of-Purpose Check
An end of purpose (EoP) check determines whether data is still relevant for business activities based on the
retention period defined for the data. The retention period is part of the overall lifecycle of personal data which
consists of the following phases:
● Business activity: The relevant data is used in ongoing business, for example contract creation, delivery or
payment.
● Residence period: The relevant data remains in the database and can be used in case of subsequent
processes related to the original purpose, for example reporting obligations.
● Blocking period: The relevant data needs to be retained for legal reasons. During the blocking period,
business users of SAP applications are prevented from displaying and using this data; it can only be
processed in case of mandatory legal provisions.
● Deletion: The data is deleted and no longer exists in the database.
For Business Partner the following EoP report is available: BUPA_PREPARE_EOP.
Blocking
Blocking of data can impact system behavior in the following ways:
● Display: The system does not display blocked data.

● Change: It is not possible to change a business object that contains blocked data.
● Create: It is not possible to create a business object that contains blocked data
● Copy/Follow-Up: It is not possible to copy a business object or perform follow-up activities for a business
object that contains blocked data.
● Search: It is not possible to search for blocked data or to search for a business object using blocked data in
the search criteria.
It is possible to display blocked data if a user has special authorization; however, it is still not possible to create,
change, copy, or perform follow-up activities on blocked data.
The blocking of data is handled in two different ways:
● ILM-enabled archiving: Archiving blocks the processing of data completely as soon as the data is removed
from the application tables.
You can configure the system in such a way that it supports a read access from the application into the
archive. We do not recommend this because this may slow down the runtime performance. If you choose
to use this feature, make sure that it is compliant with your data protection and privacy regulations.
● Masking: This is a mainly a UI functionality (e.g. SAP GUI or ALV) which does not prevent data from being
used in mass data processing (e.g. via CVPM processes) that leads to information production (e.g. the
creation of subledger documents in the results data).
Configuration: Simplified Blocking and Deletion for Business Partner
You configure the settings related to the blocking and deletion of business partner master data in Customizing
for Cross-Application Components under Data Protection.
● Define the settings for authorization management under Data Protection Authorization
Management .
● Define the settings for blocking in Customizing for Cross-Application Components under Data Protection
Blocking and Unblocking Business Partner .
More Information
For more information on data archiving and deletion, see the SAP Help Portal at https://help.sap.com/S4FPSL.
Access the Application Help under Product Assistance and choose Infrastructure (FS-FPS-IF) Data
Archiving and Deletion in Financial Products Subledger .
For more information on blocking and deletion of personal data, see the SAP Help Portal at https://
help.sap.com/S4FPSL. Access the Application Help under Product Assistance and choose Basic Settings
Blocking and Deletion of Personal Data in Financial Products Subledger .
3.5.7 Change Log
Change Log
Personal data is subject to frequent changes. Therefore, for review purposes or as a result of legal regulations,
it may be necessary to track the changes made to this data. When these changes are logged, you should be
able to check which employee made which change, the date and time, the previous value, and the current
value, depending on the configuration. It is also possible to analyze errors in this way.
Defining Fields to be Logged

SAP S/4HANA for financial products subledger processes personal data of, for example, business partners
and financial contracts that are involved in change requests and activities. If any changes are made regarding
the business partner such personal data, the system logs the following information on personal data per
change request and activity:
● The user who changed data

● The date and time of the change
● The change type (update, insert, deletion, single field documentation)
● The identifying keys and their values of the data records
● The heading name for the attribute that was changed
Most business objects, like the analytical business partner or the financial contract, are master data with a
specific versioning scheme that does not change or overwrite data but that always creates new data records in
the respective database tables. Therefore, in contrast to several other SAP products and applications, SAP S/
4HANA for financial products subledger does not log the changes via Change Documents, but the system
holds a full version history of the business objects unless they are archived.
For more information, see SAP Note 2709579 - Change logging: How to-Guide for Financial Products
Subledger.
See Also
For more information on change documents see the documentation at http://help.sap.com/netweaver. Choose
the relevant SAP NetWeaver version and open the following documentation:
● Under Application Help, go to SAP NetWeaver Library: Function-Oriented View Application Server ABAP
Other Services Services for Application Developers Change Documents .
● Open the SAP NetWeaver Security Guide and go to Security Aspects for Lifecycle Management
Auditing and Logging .
Personal data is subject to frequent changes. Therefore, for review purposes or as a result of legal regulations,
it may be necessary to track the changes made to this data. When these changes are logged, you should be
able to check which employee made which change, the date and time, the previous value, and the current
value, depending on the configuration. It is also possible to analyze errors in this way.
3.5.8 Business Partner Data Protection Scenario
The business partner data protection scenario checks whether the residence period for a business partner is
over and the end of business purpose has been reached. It also enables the destruction of business partner
data after the legally required retention period.
Between the end of the residence period and the end of the retention period the access to business partner
data is limited for regular users (blocking period).
If privileged users such as data protection administrators need to access business partner data during the
blocking period, the role SAP_CA_BP_DISPLAY_FS or SAP_CA_BP_MAINTAIN_FS can be used as templates.
In addition, the authorization object B_BUP_PCPT must be considered. See template role
SAP_CA_BP_DP_ADMIN that allows the blocking and unblocking of business partners as well as access to
blocked business partners.
If you activate the SACF scenario FSBP_RATINGS (FS-BP: Scenario for Ratings and Credit Standing Data) in
the Workbench for Switchable Authorization Check Scenarios (transaction SACF), the following FS-BP
authorization objects are also available:
● B_BUPA_RAT (Business Partner: Ratings)

You can use this authorization object to check whether a user has the authorization to create, change,
display, or delete rating procedures. For each rating procedure, you can differentiate between an
authorization for a permitted period or an authorization for any period. The prerequisite for this is that you
have made the settings for the periods in Customizing under SAP Business Partner for Financial Services
Settings for Financial Services General Settings Ratings/Credit Standing Ratings Set Rating
Procedures and Ratings .
● B_BUPA_CRS (Business Partner: Credit Standing Data)
You can use this authorization object to check whether a user has the authorization to display and change
credit standing data.
3.6 Security for Third-Party Applications or Other
Components
This section describes security aspects of third-party applications used in SAP S/4HANA for financial
products subledger.
The Estimated Cashflow Preparation (ECP) is executed in the third-party component SAP Profitability and
Performance Management (FS-PER).
Outside of the FPSL context, do not use FS-PER functionality ( SAP Easy Access Menu Financial Products
Subledger Preparatory Processing ).
 Note
Do not allow RFC calls to the FS-PER RFCs via authorization object S_RFC.
For more information, see the Administration Guide and Application Help at SAP Profitability and Performance
Management.
3.7 Other Required Documents for Security
This section provides an overview of other security-related documents.
SAP S/4HANA for financial products subledger is based on SAP S/4HANA. This means that the
corresponding security guides also apply.
Security Guide for SAP S/4 HANA Go to http://help.sap.com/s4hana and find the Security
Guide in section Product Documentation.
Security Guide for SAP HANA Got to https://help.sap.com/viewer/product/

SAP_HANA_PLATFORM/2.0.02/en-US and find the Security
Guide in section Security.
4 Installing SAP S/4HANA for financial
products subledger
This section provides information about how to prepare for installation and what to do before and after the
installation of SAP S/4HANA for financial products subledger.
4.1 Prerequisites for Installation
This section lists the prerequisites that must be met before you start installation.
4.2 Pre-Installation Tasks
This section describes tasks that must be completed before you start the installation of SAP S/4HANA for
Before you install SAP S/4HANA for financial products subledger 1812, note that this add-on cannot be
uninstalled. You cannot remove it from a system. See SAP Note 2690404 for more information about
further restrictions that are caused by installing an add-on and that relate to the upgrade and maintenance of
your SAP system.
There are two options for installing the Financial Products Subledger back-end:
1. If your SAP S/4HANA 1809 system already exists, you plan a maintenance transaction with Maintenance
Planner to install SAP S/4HANA for financial products subledger 1812 in addition.
2. If you plan a new system, you can install SAP S/4HANA 1809 and SAP S/4HANA for financial products
subledger 1812 together in one maintenance transaction of Maintenance Planner.
In both cases you use Maintenance Planner to plan your system landscape and generate a stack XML file
based on the required product versions and instances. In Maintenance Planner, you select and download the
installation files.
Choose the Add-on Product Version S/4HANA FIN PROD SUBLEDGER 1812:
● Instance Financial Products Subledger for the main component S4FPSL 100
● Instance Financial Products Subledger UI for the UI component UIFPSL 100
For more information on Maintenance Planner, see SAP Help Portal at https://help.sap.com/viewer/p/
MAINTENANCE_PLANNER.
Alternatively, you can install components using the SAP Add-On Installation Tool (transaction SAINT).
Installing SAP S/4HANA for financial products subledger PUBLIC 37
4.3 Overall Installation Sequence
This section provides detailed instructions for installing SAP S/4HANA for financial products subledger.
Installation
Based on the stack XML file and your Maintenance Planner transaction, you execute the plan and perform the
installation.
For more information on Maintenance Planner and Execute Plan, see the SAP Help Portal at Maintenance
Planner, where you can find the Maintenance Planner User Guide in section Other. Refer to section 8 "Execute
Plan".
Implementation
You can implement the add-on using Software Update Manager (SUM). For more information, see the SAP
Help Portal at Software Update Manager .
Alternatively, you can implement it using SAP Add-On Installation Tool (SAINT) and the stack XML. For more
information, see the SAP Help Portal at SAP Add-On Installation Tool and Support Package Manager, where
you can find the documentation under section Application Help.
4.3.1 Architecture Overview
A Financial Products Subledger system consists of (at least) two logical clients:
Logical Client Use
One Tool BW client Provides services to the Financial Products Subledger cli
ents such as a characteristics repository for primary objects
in the Source Data.
One or more Financial Products Subledger clients Use the functionality offered by the Tool BW. As several fi-
nancial products subledger clients may use one Tool BW cli
ent, the data stored in the Tool BW has to be separated by
the source clients. This is done using the source system ID
(characteristic 0SOURSYSTEM).
You can use the same physical client for both the Tool BW client and the Financial Products Subledger client.
During system setup, you must assign a source system ID to be used in BW to every financial products
subledger client.
38 PUBLIC Installing SAP S/4HANA for financial products subledger
4.3.2 Post-Installation Tasks
This section describes tasks that should be completed after you've finished installing SAP S/4HANA for
Perform the following steps before entering any customizing settings or installing Business Content:
● Change the system settings

● Set up the Tool BW client
● Set up the system landscape
4.3.2.1 Namespace Settings
To ensure that the system runs correctly, set the following namespaces to "modifiable" using transaction
SCTS_RSWBO004:
● /BA1/ modifiable
○ Namespace of InfoObjects assigned to a fix characteristic (/BA1/C..), SAP key figure (/BA1/K...).
○ InfoObjects assigned to fix characteristics will be generated on demand in the characteristic monitor
using function Create InfoObject or Update InfoObject.
○ The InfoObjects assigned to SAP key figures will be generated on demand in the key figure monitor
using function Generate InfoObject.
● /B20/ modifiable
○ Namespace of generated DDIC objects of an InfoObject in namespace /BA1/.
○ Must be modifiable during the generation of InfoObjects assigned to Fix Characteristics in the
characteristic monitor or the generation of InfoObjects assigned to SAP key figures in the key figure
monitor.
● /BA1C/ modifiable
○ Namespace of InfoObjects assigned to a Business Content characteristic or key figure.
○ Must be modifiable during generation of InfoObjects in namespace /BA1C/ in the characteristic
monitor or key figure monitor.
● /B20C/ modifiable
○ Namespace of generated DDIC objects of InfoObjects in namespace /BA1C/.
○ Must be modifiable during generation of InfoObjects in namespace /BA1C/ in the characteristic
monitor or key figure monitor.
● /BIC/ modifiable
○ Namespace of generated DDIC objects of InfoObjects without prefix.
○ Must be modifiable during generation of InfoObjects generation of InfoObjects without prefix in the
characteristic monitor or key figure monitor.
 Note
You can set the namespaces /BA1/, /B20/, /BA1C/, /B20C/, /BIC/ not modifiable in
systems (e.g. the production system), if you transport the manually created or generated InfoObjects
from the development system to the target system.
● /1SGS/ Not modifiable
Namespace for DDIC objects and reports generated by tools of the segmentation service.
● /1BA/ Not modifiable
Namespace for DDIC objects and reports generated by tools of the financial products subledger.
● /1FB/ Not modifiable
Namespace for DDIC objects generated by tools of the FINBASIS.
● /BI0/ Not modifiable
Namespace for generated DDIC objects of InfoObjects of BI content in namespace 0.
● /BA1S/ Not modifiable
Namespace for generated objects of XI mapping.
4.3.2.2 System Parameters
Adjust them to the specific system environment and data volume.
4.3.2.3 Setting Up the Tool BW Client
After the technical implementation of SAP S/4HANA 1809 create a BW standard client. Note that a BW client
cannot be set up in client 000. Create a new one or use the existing client as the Tool BW client and assign a
logical system to it using transaction SCC4.
1. Create a background user in the BW client using transaction SU01 and assign the following profiles:
○ S_BI-WHM_RFC
○ S_BI-WX_RFC
2. Call up transaction SE16 and enter table name RSADMINA. Create a new entry with following settings:
○ BW_USER: Enter the background user created above.
○ BWMANDT: Enter the BW client ID.
○ Leave all other fields unchanged.
3. Initialize the BW as follows:
○ Call up transaction RSA1.
 Note
When you start the transaction for the first time, you need to make some initial settings. In the
process, the system displays several message dialog boxes. Confirm all of them.
○ Verify that the BW source system connection is active. To do so, choose Modeling Source
System and check the respective logical system (the one that has been entered in SCC4 as logical
system).
4.3.2.4 Setting Up the Financial Products Subledger Client
After you have configured the Tool BW, you must configure the financial products subledger client. For this, you
can create a new client or use the Tool BW client.
Setting up the logical FPSL client in the physical Tool BW client:
● Check if an RFC destination exists with the same name as the logical system that is assigned to the BW
client.
○ RFC destination exists: Enhance the profile of the background user and add role SAP_FSP_EXPERT.
○ RFC not created yet: Execute steps 3 and 4.
Setting up a new FPSL client:
1. Create a new client and assign a logical system to it using transaction SCC4.
2. Make a client copy from client 000 to the new client with profile SAP_CUST or SAP_ALL using transaction
SCCL
 Note
No post processing is necessary, i.e. you do not need to execute transaction /BA1/AT_INIT in the new
client.
3. Create a background user in the financial products subledger client using transaction SU01. Assign the
following roles and profiles to the background user:
SAP_FSP_EXPERT (single role)
S_BI-WHM_RFC (profile)
For security reasons, you should copy the role to a Z role first. Assign these Z roles to the user instead of
the SAP role.
However, you must assign the profile directly.
4. Create an RFC destination using transaction SM59. Use the same name as the logical system that is
assigned to the FPSL client. Make the following settings:
○ Technical Settings tab page:
No settings are necessary. Do not enter a system.
○ Logon and Security tab page:
Enter the following data:
○ ID of the financial products subledger client
○ Background user
○ Assigned password
4.3.2.5 Business Partner Settings
Report FSBP_MAINTAIN_IDTYPE_MAPPING creates the mapping for new identification categories and types in
customizing for table BUT0ID (ID numbers) for existing identification number categories for table BPID001 (ID
numbers) and saves the assignments.
 Note
Once the results of the report have been saved, the assignments between identification categories and
types determined by the report cannot be changed. Changes to these assignments can cause errors during
the subsequent data conversion.
Activate Business Function CA_FSBP_MIGRATION_ID (transaction SFW5) to create the customizing. This is
described in SAP Note 1556353 .
Once you have created customizing for identification numbers, the system displays the additional partner
numbers from table BPID001 in online processing mode as identification numbers. For more information, see
the report documentation of FSBP_MAINTAIN_IDTYPE_MAPPING (transaction SA38).
Financial Products Subledger (software component S4FPSL) is an add-on that is installed on an S/4HANA
instance. Within such an installation there are two different business objects available for the business partner:
● operational Business Partner (oBP), maintained in transaction BP

● analytical Business Partner (aBP), maintained in transactions BPV1 (create), BPV2 (change), BPV3
(display)
If a client should only be used for the analytical Business partner, you can define it as aBP-only in Customizing
for SAP Banking under Settings for Financial Services Settings for Financial Products Subledger Technical
Settings Activate Business Partner for Analytical Applications Only . This prevents confusion and data
inconsistencies.
More Information
See SAP Note 1556353 : BP_AID: Checklist for migration of "Additional Partner Numbers"
See SAP Note 2098653 : BP_VER: New database design for business partner versioning
4.3.2.6 Create an Entry in the System Landscape Table
Go to the Customizing for Financial Products Subledger and choose Basic Settings Global Settings
Define System Landscape for Financial Products Subledger .
Create a new entry and make the following settings:
● System ID: The system ID and the client define a core client that is assigned to BW system. Enter the
system ID.
● Switch: By default, the append generation is set to the mode Standard Append Generation. For more
information, read the F1 help of the field.
● Namespace: Namespace for transportable objects of the enhancement tool. Set the namespace to Z or Y,
or your own transportable customer namespace.
In the sub dialog Active Clients, make the following settings:
● Client: See System ID. Enter the financial products subledger client ID.
● Main Client:
Indicates the client which is usually used for the transport of client independent objects, such as appends
of the enhancement tool and InfoObjects for characteristics and key figures.
The main client is relevant as soon as a conflict of the meta data is detected with the cross-client
customizing definition of characteristics or key figures. In this case, you can only generate the InfoObject in
the main client.
 Note
If the Tool BW client is also an FPSL client, mark this client as the main client.
Otherwise mark the client that is usually used for customizing transports.
● Source System ID:

The source system ID is used to separate the data of different FPSL clients in the Tool BW. A source system
ID consists of two alphanumeric characters.
 Note
Enter a source system ID in this field.
 Recommendation
We strongly recommend that you use different source system IDs for all clients across the FPSL system
landscape (in all systems including development, test, and production).
● Staging BI:
Enter the system name of the BI client from which the Data Loading Process (DLP) of the FPSL loads data.
The staging BI system might be a separate system or the tool BI client of the FPSL system. If the latter is
the case, leave this field empty. The system then does not have to use Remote Function Calls (RFC) to read
data from the BI in Data Load Layer processes, which increases performance.
● FPSL Client (FPSL Core System Client):
Enter the logical system name of the FPSL client. This information is required in the Data Loading Process
(DLP) to get data about change pointers, which is done in an RFC to the correct target client.
If the DLP is not used, this field has no effect and can therefore be left empty.
● DLP Target Client (Data Loading Process Target Client):
If you supply data to the FPSL using the Data Loading Process, the system creates change pointers in the
BI and stores them in the FPSL system. You can use this checkbox to determine in which FPSL clients the
system stores the change pointers.
The system only uses this information, if no explicit source system ID is transferred when the change
pointer is updated in the DLP. This means that all the selected clients are provided with the data by means
of the DLP. This is important for the delivery of market data that is relevant for more than one client.
If the DLP is not used, this field has no effect and can therefore be left empty.
4.3.2.7 Execute Initial Configuration
To execute the initial configuration, go to the customizing of Financial Products Subledger under Basic
Settings Global Settings Run Initial Configuration .
There are two options for performing the initial configuration.
● In a client with a new installation of Financial Products Subledger or an upgrade to a new release, choose
Run in New Installation or Release Upgrade Mode.
● For installing a Support or Feature Package, choose Run in Support Package Upgrade Mode.
If errors occur during initial configuration, analyze the application log.
5 Configuring SAP S/4HANA for financial
products subledger
This section describes how to configure SAP S/4HANA for financial products subledger.
With Business Content we provide a pre-configured system that can be used by your team members involved
in your implementation project to familiarize themselves with the system architecture and functions. The
examples, templates, and solutions provided with the Business Content enable you to create prototypes easily,
and speed up the implementation process. Business Content contains sample customizing for end-to-end
processing of data for Subledger Accounting for Financial Instruments and Subledger Accounting for Insurance
Contracts.
The Business Content is delivered via Business Configuration Sets (BC sets), piece lists, and content for SAP
NetWeaver Business Warehouse (BW). Once you have activated the Business Content, you can access the
related customizing settings in your system.
 Note
Business Content is not intended to replace an implementation project and is not suitable for productive
use without individual adaptations. Therefore it cannot replace an implementation project.
5.1 Configuring Subledger Accounting for Financial

Instruments
After you have installed Financial Products Subledger and performed the post-installation tasks, you can
activate the Business Content for Subledger Accounting for Financial Instruments.
To do this, follow the instructions described in SAP Note 2711006 .
5.2 Configuring Subledger Accounting for Insurance

Contracts
After you have installed Financial Products Subledger and performed the post-installation tasks, you can
activate the Business Content for Subledger Accounting for Insurance Contracts.
You can use the Estimated Cash Flow Preparation provided as content for SAP Profitability and Performance
Management to estimate cash flows. Therefore, you must install SAP Profitability and Performance
Management in addition to Financial Products Subledger.
Configuring SAP S/4HANA for financial products subledger PUBLIC 45
Prerequisites
Refer to the Administration Guide for SAP Profitability and Performance Management, which you can find at
SAP Profitability and Performance Management.
● You have completed the post-installation steps described under Installation Information
Implementation Sequence Post Installation Steps .
● You have followed the instructions described under Sample Content Information Install the Finance
and Risk Data Platform Integrated Estimated Cash Flow Preparation Sample Content in Other SAP
Profitability and Performance Management Clients in Your System .
Procedure
1. Activate Business Content for Financial Products Subledger: Follow the instructions described in SAP Note
2711006 .
2. Make sure you have completed the post-installation steps for Financial Products Subledger in the ASU
list, as described in SAP Note 2729154 .
3. Activate Business Content for Estimated Cash Flow Preparation: Follow the instructions described in SAP
Note 2650963 .
46 PUBLIC Configuring SAP S/4HANA for financial products subledger
6 Operating SAP S/4HANA for financial
products subledger
This section contains general information about how to operate Financial Products Subledger.
Financial Products Subledger is based on SAP S/4HANA. For general operations information, see the
Operations Guide for SAP S/4HANA (go to http://help.sap.com/s4hana.
Specific information for Financial Products Subledger
Monitoring
For more information, see Monitoring [page 48].
Trace and Log Files
There are application log objects that are specific for Financial Products Subledger. The central objects and
start with the prefix /BA1.
Workload Monitors
Parallel processing and packaging settings affect the processing time and the usage of the hardware resources.
You can use monitoring tools like MassMan and the report RBANK_PP_MONITOR to verify the parallel
processing and package size settings that lead to the expected throughput of a mass process.
Administration and Management
● Technical Configuration
Financial Products Subledger does not recommend custom code changes. They are considered as
modifications and are not supported. There are tools to perform changes without modifications, such as
the standard BAdIs.
● Periodic Tasks
For more information, see Periodic Tasks [page 49].
Troubleshooting
For more information, see Troubleshooting [page 51].
Support Desk Management
The FS-FPS application component (including their subcomponents) is relevant for Financial Products
Subledger and should be used to report problems via CSS.
Operating SAP S/4HANA for financial products subledger PUBLIC 47
6.1 Monitoring
This section describes monitoring tasks for SAP S/4HANA for financial products subledger.
Interface Monitoring
For the analysis of services used by Financial Products Subledger, you can use the Postprocessing Office
(PPO) or the Error and Conflict Handler (ECH)You can access interface monitors for analyzing problems with
interfaces such as RFC, IDoc, and HTTP using transactions SMQ1 (Outbound Queue) and SMQ2 (Inbound
Queue).
For more information, go to http://help.sap.com/s4fpsl, enter Error Handling in Financial Services or

Postprocessing Office into the search bar, press Enter , and open the search result with the corresponding title.
You can access these functions from the SAP Easy Access screen by choosing Cross-Application Components.
Data Delivery to Financial Products Subledger
RFC Enabled Function Modules

There is a collection of remote function call enabled function modules (RFCs) that are APIs, which are used to
create data in Financial Products Subledger.
RFCs are only an interface and not a process. They return only standardized messages that document the
status of the process you are executing. The calling process is responsible for creating an appropriate log and
reacting appropriately to the response of the RFCs. The calling process is also the owner of the logical unit of
work (LUW) and the transaction handling (commit or rollback).
Therefore, no monitoring for these interface calls is available in Financial Products Subledger.
Services (SOAP)
As part of service enablement, the interfaces to Financial Products Subledger are implemented as services.
The infrastructure is responsible for the handling of services. The infrastructure is the active component and is
responsible for the logging of information, the transaction management and the necessary monitoring
capabilities. The SAP infrastructure component for handling messages is Process Integration (PI), which
contains the following monitoring tools:
● Technical monitoring: SXMB_MONI

● Technical monitoring for WS services: SRT_MONI
● Technical monitoring for WS services: sequence monitor: SRT_MONIS
● Error and conflict handling: ECH_MONI_SEL
● Error and conflict handling (/SAPPO/PPO2)
These tools are not specific to Financial Products Subledger and common descriptions are therefore
available. While implementing the service usage, you must ensure that the monitors are connected to an
48 PUBLIC Operating SAP S/4HANA for financial products subledger
alerting mechanism so that an operator / responsible person is immediately informed (by SMS or e-mail for
example) in case of an incident.
Data Loading
Data can be loaded to Financial Products Subledger using embedded BW functionality.
For more information about data loading topics, go to http://help.sap.com/s4fpsl, enter Data Loading Process
into the search bar, press Enter , and open the search result with that title.
The data load process owns a process type, which can be included in a BW process chain. The process loads
data according to existing change pointers. The change pointers always document the current status of each
object to be loaded. The change pointers are also used to restart the process again to handle the objects with
errors.
Data Growth and Data Archiving Monitors

For more information about the archiving processes in Financial Products Subledger, go to http://
help.sap.com/s4fpsl, enter Archiving with ILM-Enabled Archiving Objects into the search bar, press Enter , and
open the search result with that title.
Database Monitoring
After the database tables have initially been partitioned during the installation process and according to
consulting note 2722355 , the partitioning of the tables must be adjusted accordingly as time proceeds. A lot
of tables is partitioned based on the posting date, and partitions may have been created for just one or tw fiscal
years into the future. Therefore new partitions must be created on a regular basis. Since tables must often be
partitioned without having an OTHERS-partition, it is indispensable to make sure that the required partitions
always exist (for example with regard to posting dates). Otherwise processes that try to write in such non-
existing partitions will abort.
In addition the data volume growth in the partitions must regularly be checked. Since the initial partitioning was
done based on assumptions about data volume growth these assumptions may need to be adjusted. Data
volume growth may be faster than expected and a finer partitioning may be required.
Apart from this the normal health checks of a database have to be applied, see the Operations Guide for SAP
S/4HANA.
6.2 Periodic Tasks
This section describes periodic tasks that must be completed for SAP S/4HANA for financial products
subledger.
This section lists the most important tasks to be performed by the administrator regularly.
 Note
The periodic tasks listed here help to keep your SAP system stable.
These tasks are not critical for system availability. Avoid running additional tasks when the system is stalled
by an overload of work processes and needs to be restarted.
Checks in Financial Products Subledger
Periodic tasks include reports on the daily processing of accounts and business transactions. The sequence in
which you run these reports, and their interdependencies, depend on the configuration of your system. You
have to define the order in which the system runs the reports, and how the reports interrelate, according to
your business needs.
You can find additional information about periodic tasks for the components in Financial Products Subledger
on SAP Help Portal at http://help.sap.com/s4fpsl.
Scheduled Periodic Tasks

This section describes all automatable tasks that have to run periodically to keep the application running
smoothly. These tasks may be required at component level and are therefore relevant in each scenario that
uses the component. Other tasks may be relevant for specific business scenarios only. It is important that you
monitor the successful execution of these tasks on a regular basis.
Program Name / Task Recommended Frequency Description
Archiving (ILM) For more information about the archiv

ing processes in Financial Products
Subledger, go to http://help.sap.com/
s4fpsl, enter Archiving with ILM-Ena
bled Archiving Objects into the search
bar, press Enter , and open the search
result with that title.
Report RBANK_DELETE_RUNS see SAP Note 1439952 This reports deletes RBANK_PP_MONI
TOR process data.
Manual Periodic Tasks

This section describes all manual tasks that have to be run periodically to ensure that the application runs
smoothly over time. You need to execute manual tasks yourself as opposed to the scheduled tasks listed above
that you can automate by using a task scheduler program. These tasks may be required at component level
and are therefore relevant in every scenario that uses the component. Other tasks may be relevant for certain
business scenarios only. It is important that you monitor the execution of these tasks on a regular basis.
Manual Periodic Tasks

Program Name / Task Description
Transaction /BA1/FW_PROCMON Monitors all current jobs for CVPM processes. You can also
archive the data, display more information for each job (run
status, detailed log, statistics, interdependencies of runs),
abort corrupt jobs and restart jobs (if the CVPM process
uses the step controller /BA1/CL_AL_FW_STEP_CONTROL).
Transaction RSPC Process Chain Maintenance
6.3 Troubleshooting
This section describes troubleshooting for Financial Products Subledger.
For general information, see the corresponding chapter in the Operations Guide for SAP S/4HANA.
Sending of General Ledger Documents
If a problem occurs during the sending process of a general ledger document, you can send this document
again.
For more information, go to http://help.sap.com/s4fpsl, enter General Ledger Connection into the search bar,
press Enter , and open the search result with that title.
Specific Problem Analysis
Some problems may arise from specific processes within Financial Products Subledger. The following
sections provide information about how to analyze and solve these problems.
Communication with Services

For the analysis of services used by Financial Products Subledger, you can use the Postprocessing Office
(PPO) or the Error and Conflict Handler (ECH) (see Monitoring [page 48]).
The system stores messages that could not be processed completely in the ECH, which is integrated in the
PPO. With this integration you can configure a workflow that forwards errors to an administrator to handle the
problem.
In the event of a configuration error, a change in the application configuration can be applied and the message
can be reprocessed locally. In the event of data errors, the issue has to be solved in the sending system
because the data errors must be corrected.
Generated Objects
Some functions require objects that are generated when you copy clients, while postprocessing using a client
copy or when you save/activate Customizing objects. Automatic generation takes place without checking data
for consistency. To check whether the client was copied successfully, the data in the source client and target
client has to be compared.
If object generation fails, you can manually start the following reports that create the necessary objects or give
an overview of all generated objects:
● Check report for Customizing and the configuration of source data

This check routine identifies inconsistencies in Customizing and activation of generated objects. In
Customizing for Financial Products Subledger, choose Source Data Configuration Check .
● Characteristics and Key Figures
○ Check current status of characteristics and correct errors:
In Customizing for Financial Products Subledger, choose Basic Settings Settings for Metadata
Characteristics Characteristics Characteristic Monitor .
○ Check current status of key figures and correct errors:
In Customizing for Financial Products Subledger, choose Basic Settings Settings for Metadata
Key Figures Characteristics Key Figure Monitor .
Calculation and Valuation Process Manager (CVPM)

The CVPM is the central infrastructure component in Financial Products Subledger.
● Depending on the step controller, there are different reorganization reports:

○ Step controller /BA1/CL_AL_FW_STEP_CONTROL: /BA1/AL_FW_DELETE_RUN_FROM_CLU deletes
data packages from cluster data base '/BA1/R6_TAB_CLUS' that are written before and after an
aggregation for example.
○ Step controller /BA1/CL_AL_FW_STEP_CONTROL_DPF: For all the CVPM processes that have an
aggregation or a repackaging step, use transaction /BA1/R6_DPF_REORG instead to clear the cluster
DB.
● CVPM Process Monitor (transaction /BA1/FW_PROCMON): You use transaction /BA1/FW_PROCMON to
monitor all current jobs for CVPM processes. You can also archive the data, display more information for
each job (run status, detailed log, statistics, interdependencies of runs), abort corrupt jobs and restart jobs
(if the CVPM process uses the step controller /BA1/CL_AL_FW_STEP_CONTROL).
● Restart function for CVPM processes:
○ All CVPM processes: If you define that the generation of run groups for a particular CVPM process is
optional, and the sequence defined in Customizing is a simple sequence that does not contain any
aggregation or repackaging steps, the parallel processing framework (PPF) provides a restart function
for failed packages of the job in question (the status of these runs is set to incomplete). That is, if the
same process is restarted using the same process parameters, only the failed packages of the
incomplete run are processed again.
○ For CVPM processes using the step controller /BA1/CL_AL_FW_STEP_CONTROL: You can enter
settings in Customizing to define that these processes can be restarted on a single record basis (which
is not provided with the PPF) at synchronization points (after worklist creation, before/after
aggregation, and after repackaging). In this case, you can use the process monitor to restart the jobs
(transaction /BA1/FW_PROCMON).
Module Editor Tool

The after-import and post-processing methods of the Module Editor attempt to generate all active and inactive
module versions in the system. Deactivated versions are not generated. This is a requirement of the test
functions provided by this tool.
If the source client contains inconsistent modules, their activation fails in the target client. You can use
report /BA1/P3_REGENERATE to activate individual modules or start mass activation. If the activation fails, it
might be due to incomplete or inconsistent Customizing. You must analyze these modules in the source client.
The report has a No Generation flag. If you set this flag, the report simply checks whether the modules need to
be generated.
Problems While Postprocessing

A reconciliation report checks the consistent delivery of positions and business transactions for Financial
Products Subledger. If there are differences, business transactions can be automatically generated to make
corrections and solve discrepancies.
Data Volume
SAP S/4HANA for financial products subledger has a full versioning strategy for most of its objects that
increases the data volume. The data volume can be reduced by archiving the data as soon as possible.
For more information, go to http://help.sap.com/s4fpsl, enter Data Archiving and Deletion in Financial Products
Subledger into the search bar, press Enter , and open the search result with that title.
7 UI Technology Information for S/4HANA
for financial products subledger
 Note
This section deals with UI technology topics relevant for SAP S/4HANA for financial products subledger,
especially the use of Fiori apps and is intended for system administrators and technical consultants.
With Financial Products Subledger, the workplace for financial accountants and actuaries is accessible in the
SAP Fiori launchpad.
Using the launchpad, you can call up all apps for which you have been granted access.
Financial Products Subledger is based on SAP S/4HANA. For general information about UI technology in SAP
S/4HANA, see the UI Technology Guide for SAP S/4HANA 1809 (go to http://help.sap.com/s4hana).
 Note
Not all the information contained in the UI Technology Guide for SAP S/4HANA 1809 is applicable for the
apps in Financial Products Subledger, for example the information about Fiori search and extensibility.
App Implementation
For the implementation of the app in Financial Products Subledger, you need information from the app-
specific implementation documentation, such as technical names of services, roles, and so on.
You can find this information in the SAP Fiori apps reference library at:
● Changes in Insurance Liabilities app: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/

index.html?appId=F3685
● Assign Change Reasons – Insurance Contracts app: https://fioriappslibrary.hana.ondemand.com/sap/fix/
externalViewer/index.html?appId=F3686
54 PUBLIC UI Technology Information for S/4HANA for financial products subledger
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.
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.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
Important Disclaimers and Legal Information PUBLIC 55
www.sap.com/contactsap
© 2018 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

Administration Guide For SAP S/4HANA For Financial Products Subledger 1812

Uploaded by

Copyright:

Available Formats

Administration Guide For SAP S/4HANA For Financial Products Subledger 1812

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Administration Guide For SAP S/4HANA For Financial Products Subledger 1812

Uploaded by

Copyright:

Available Formats

PUBLIC

Document Version: 1.0 – 2018-12-17

Administration Guide for SAP S/4HANA for

THE BEST RUN

1 About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 About SAP S/4HANA for financial products subledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

3 Security Information for SAP S/4HANA for financial products subledger. . . . . . . . . . . . . . . . . 15

4 Installing SAP S/4HANA for financial products subledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5 Configuring SAP S/4HANA for financial products subledger. . . . . . . . . . . . . . . . . . . . . . . . . . 45

6 Operating SAP S/4HANA for financial products subledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

7 UI Technology Information for S/4HANA for financial products subledger. . . . . . . . . . . . . . . . 54

This guide addresses the following target audience:

1.1 Document History

Date Change More Information

December 17, 2018 Initial version

1.2 Useful Links

Resource Where to Find It

User assistance for SAP S/4HANA for financial products http://help.sap.com/S4FPSL

Information about creating customer incidents http://support.sap.com/incident

SAP Notes search http://support.sap.com/notes

SAP Software Download Center http://support.sap.com/swdc

Product Availability Matrix http://support.sap.com/pam

Get Involved Early https://support.sap.com/en/offerings-programs/get-in-

Information about support package stacks, latest software http://support.sap.com/sp-stacks

1.3 Getting Support

To report an incident, go to SAP Support Portal at http://support.sap.com/incident . The relevant

● You can use several accounting standards simultaneously (multi-GAAP accounting).

2.2 Subledger Accounting for Insurance Contracts

● You can use several accounting standards simultaneously (multi-GAAP accounting).

The most important steps are:

● SAP S/4HANA for financial products subledger

2.3 System Landscape for SAP S/4HANA for financial

Instance Release SP Stack

Comprised Software Com­

Deployment Scenario Instance Release SP Stack Comment

SAP Frontend Server

SAP Frontend Server

Comprised Software Com­

Hardware and Software Requirements

You can find further information one sizing at https://www.sap.com/about/benchmark/sizing.html .

SAP Note Number Title Description

2725310 Release information about S4FPSL100 Information on the add-on S4FPSL100

2725350 Release information about UIFPSL100 Information on software component

2722778 Configuration for integrating Financial You want to integrate Financial

3.1 User Management

3.1.1 User Types

User Type Description

Customizer The customizer is allowed to configure the Financial

Administrator The administrator is allowed to administer the Financial

Tool Description Prerequisites

3.1.3 Authentication and Single Sign-On

For more information, see SAP NetWeaver Security.

3.2 Role and Authorization Concept

Authorization Object Field Field Description Object Description

F_BABR_REG /BA1/BRSRC Source System Smart AFI: Access in Register

F_BABR_BAS /BA1/BRSRC Source System Smart AFI: Basic Authoriza­

ACC_SYSTEM Accounting System

F_BABR_CLC /BA1/BRCLC Calculator Smart AFI: Calculator

/BA1/BRSRC Source System

Comprised Software Com

Comprised Software Com

F_BABR_BAS /BA1/BRSRC Source System Smart AFI: Basic Authoriza

F_BABR_ADJ /BA1/LGENT Legal Entity Smart AFI: Manual Adjust

F_BAF3_GDS /BA1/F3SID ID of a Primary Data Source Authorization for General Pri

F_BAFF_ET /BA1/ETAPP Application Class for En Authorization for Enhance

SAP_FSP_CUSTOMIZER This role contains authorizations for maintaining the cus

SAP_BA1_ADM_RDL This role contains administrator authorizations for the Re

SAP_BA1_EXPERT_FDB This role contains authorizations for maintaining the cus

SAP_BA1_EXPERT_RDL This role contains authorizations for maintaining the cus