0% found this document useful (0 votes)

20 views

FPSL Adminguide en

Uploaded by

DurgaPrasad

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

20 views

FPSL Adminguide en

Uploaded by

DurgaPrasad

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 62

PUBLIC

Document Version: 1.0 – 2022-11-16

Administration Guide for SAP S/4HANA for

Financial Products Subledger 1812 Support
Package Stack 6
© 2022 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 System Landscape for SAP S/4HANA for Financial Products Subledger. . . . . . . . . . . . . . . . . . . . . . .7
2.2 Overview of Required SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Security Information for SAP S/4HANA for Financial Products Subledger. . . . . . . . . . . . . . . . 12

3.1 User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
User Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
User Administration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Authentication and Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
3.2 Role and Authorization Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Authorization Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Standard Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Critical Combinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3 Network and Communication Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Communication Destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.4 Internet Communication Framework Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.5 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Consent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Read Access Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Information Retrieval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Deletion of Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Change Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
3.6 Security for Third-Party Applications or Other Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.7 Other Required Documents for Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4 Installing SAP S/4HANA for Financial Products Subledger. . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4.1 Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.2 Overall Installation Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Architecture Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
2 PUBLIC Content
5 Updating SAP S/4HANA for Financial Products Subledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6 Setting Up a Financial Products Subledger Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

6.1 Business Partner Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.2 Create an Entry in the System Landscape Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.3 Execute Initial Configuration for Subledger Accounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

7 Configuring SAP S/4HANA for Financial Products Subledger. . . . . . . . . . . . . . . . . . . . . . . . . 49

7.1 Configuring Subledger Accounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.2 Configuring Estimated Cash Flow Preparation for Use with Subledger Accounting. . . . . . . . . . . . . . 50

8 Operating SAP S/4HANA for Financial Products Subledger. . . . . . . . . . . . . . . . . . . . . . . . . . . 51

8.1 Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.2 Periodic Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.3 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.4 Reports for Development and Test Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

9 UI Technology Information for SAP S/4HANA for Financial Products Subledger. . . . . . . . . . . 58

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
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 or SAP S/4HANA, financial posting gateway. 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.

Version Date Description

1.0 November 16, 2022 Initial version for SAP S/4HANA for
financial products subledger 1812
SPS06

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 https://help.sap.com/s4fpsl

subledger

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

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

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
4 PUBLIC About This Guide
Resource Where to Find It

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

Product Availability Matrix https://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 https://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 https://support.sap.com/incident . The relevant

component is FS-FPS Financial Products Subledger or FI-AF-FPG Financial Posting Gateway.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
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 or SAP S/4HANA, financial posting gateway 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.

For more information, see the Product Page for SAP S/4HANA for financial products subledger.

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. These Fiori apllications are not relevant for SAP S/4HANA, financial
posting gateway.

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 .

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
6 PUBLIC About SAP S/4HANA for Financial Products Subledger
2.1 System Landscape for SAP S/4HANA for Financial
Products Subledger

This section describes the technical system landscape and the software components involved.

SAP S/4HANA for financial products subledger (S4FPSL) is an add-on to the SAP S/4HANA core.

System Landscape

If you use Subledger Accounting for Insurance Contracts, you can also deploy Estimated Cash Flow
Preparation (ECP) on the same instance. SAP Analytics Cloud (SAC), Business Warehouse (BW), and other
SAP or third-party systems must be deployed separately.

The overall system landscape can look like this:

For more information about the minimal and maximal system landscape in Financial Products Subledger, see
SAP Note 2990348 .

Back End and Front End

For SAP S/4HANA for financial products subledger, you can choose between a single-instance installation
(one software stack) and a dual instance installation (two software stacks) as illustrated below.

In a single-instance deployment, you deploy the back end and front end together, whereas in a dual instance
installation, you deploy them separately.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
About SAP S/4HANA for Financial Products Subledger PUBLIC 7
Back End

Financial Products Subledger with its back-end applications is an add-on for SAP S/4HANA 1809 or SAP S/
4HANA 1909 or SAP S/4HANA 2020. You must install the following instance:

Instance Release

SAP S/4HANA server • SAP S/4HANA 1809

• SAP S/4HANA 1909
• SAP S/4HANA 2020

You can then install the following instance of Financial Products Subledger with its comprised software
components:

Comprised Software Component Ver

Instance Release sions

Financial Products Subledger SAP S/4HANA for financial products S4FPSL 100
subledger 1812
S4FSFND 100

Front End

Financial Products Subledger with its front-end SAP Fiori applications is an add-on for SAP Fiori front-end
server 5.0 or 6.0 or SAP FIORI FES 2020 FOR S/4HANA

Deployment Scenario Instance Release Comment

Embedded Financial Products Subledger SAP S/4HANA for financial The required front-end server
products subledger 1812 is part of the back-end soft
ware stack.

Hub SAP Front-End Server 7.52 or SAP Fiori Front-End Server

5.0
SAP Front-End Server 7.53

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
8 PUBLIC About SAP S/4HANA for Financial Products Subledger
Deployment Scenario Instance Release Comment

Hub SAP Front-End Server 7.52 or SAP Fiori Front-End Server

6.0
SAP Front-End Server 7.53 or

SAP Front-End Server 7.54 or

Hub SAP Front-End Server 7.52 SAP FIORI FES 2020 FOR S/
4HANA
(Hub) or

SAP Front-End Server 7.53 or

SAP Front-End Server 7.54 or

SAP Front-End Server 7.55 or

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

Comprised Software Component Ver

Instance Release sions

Financial Products Subledger UI SAP S/4HANA for financial products UIFPSL 100
subledger 1812

Hardware and Software Requirements

The minimum system requirements for Financial Products Subledger are described in SAP Note 2690404
for ABAP add-on S4FPSL, in SAP Note 2690405 for ABAP add-on S4FSFND, and in SAP Note 2690406
for UIFPSL.

You can find more information about sizing at https://www.sap.com/about/benchmark/sizing.expert-

sizing.html#expert-sizing .

2.2 Overview of Required SAP Notes

The following SAP Notes are essential for installing, upgrading, and operating SAP S/4HANA for financial
products subledger.

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 .

 Note

Before you start the installation, have a look at the Release Information Notes 2725310 and 2725350 .

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
About SAP S/4HANA for Financial Products Subledger PUBLIC 9
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 UIFPSL100 and its support
packages.

1668882 Note Assistant: Important Notes for Allows you to automatically implement
SAP_BASIS note corrections in your ABAP systems
730,731,740,750,751,752,753,754,755,75
6

2711006 S/4HANA for financial products sub How to install Business Content for SAP
ledger: Business Content Installation S/4HANA for financial products sub
ledger.

2729154 Financial Products Subledger: Esti How to install Business Content for the
mated Cashflow Preparation (ECP) integration of Estimated Cashflow Prep
Business Content Installation aration, delivered with SAP S/4HANA
for financial 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.

2690405 Release Strategy and Maintenance In Information on planning the installation,
formation for the ABAP add-on upgrades and support packages of the
S4FSFND ABAP add-on S4FSFND.

2690406 Release Strategy and Maintenance In Information on planning the installation,
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.

Change of workflow system user and You upgraded your system to SAP S/
2568271
4HANA On Premise 1709 or higher. In
workflow system jobs with S/4 HANA
the Automatic Workflow Customizing
On Premise 1709
(transaction SWU3), you notice that the
status is not green for "Edit Runtime
Environment".

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.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
10 PUBLIC About SAP S/4HANA for Financial Products Subledger
SAP Note Number Title Description

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 you to search for and retrieve
personal data for a specified data sub
ject. The Financial Products Subledger
ILM objects are the anchor point for the
search and data retrieval.

2874355 How to Monitor and Operate S4FPSL To avoid a decrease in runtime perform
ance and to maintain high quality data
processing, you need to monitor the
system status on a daily basis.

2798428 Data Tiering in SAP S/4HANA for finan- Guidance on how to setup a native stor
cial products subledger, banking edi age extension for Financial Products
tion / Smart AFI Subledger, banking edition.

2637010 Smart AFI / FPSL banking edition - Guidance on how to setup a scale-out
Multi-Node Support setup for Financial Product Subledger,
banking edition.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
About SAP S/4HANA for Financial Products Subledger PUBLIC 11
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 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.

These user types do not exist in the system automatically. You can create and configure your own user types,
such as the following examples:

User Type Description

Expert The expert is allowed to use the transactions in the SAP Easy
Access Menu for Financial Products Subledger. This user
type can display source data and results data and is able to
execute 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.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
12 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
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

User and role maintenance with SAP NetWeaver AS ABAP For more information, see the User Management section in
the Security Guide for SAP S/4HANA at https://
(Transactions SU01, PFCG)
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 is 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 SAP NetWeaver AS ABAP.
Therefore, the recommendations and guidelines for authorizations 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 about how to create roles, see the role administration information at SAP NetWeaver
Security.

This 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 FPSL: Access in Register

Process Step
/BA1/LGENT Legal Entity

ACTVT Activity

F_BABR_BAS /BA1/BRSRC Source System FPSL: Basic Authorizations in

Accounting
/BA1/LGENT Legal Entity

ACC_SYSTEM Accounting System  Recommenda

tion
ACTVT Activity
We strongly recommend
that you fill the database
table field
LEGAL_ENTITY for con
tracts and securities ac
counts. Otherwise, the
extensive authorization
check for the legal entity
in master data and
transaction data using
authorization object
F_BABR_BAS is not sup
ported (see also Critical
Combinations [page
20]).

F_BABR_CLC /BA1/BRCLC Calculator FPSL: Calculator

/BA1/BRSRC Source System

/BA1/LGENT Legal Entity

ACC_SYSTEM Accounting System

ACTVT Activity

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
14 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
Authorization Object Field Field Description Object Description

F_BABR_UI /BA1/APP Application (in Fiori or FPSL: Frontend (UI, Work

ODATA Context) Center, ODATA, CDS Views)
/BA1/BUSSG
Segment for Segmental Re F_BABR_UI is the most im
/BA1/KOKRS
porting portant authorization object
/BA1/LGENT for the CDS views in the Vir
Controlling Area
tual Data Model.
/BA1/ORGUT
Legal Entity
/BA1/PCTR
Organizational Unit
ACC_SYSTEM
Profit Center
ACTVT
Accounting System

Activity

F_BABR_GLC /BA1/LGENT Legal Entity FPSL: General Ledger Con

nection
ACTVT Activity

F_BABR_ADJ /BA1/LGENT Legal Entity FPSL: Manual Adjustments

and Workflow
/BA1/PCATG Process Category

ACC_SYSTEM Accounting System

ACTVT Activity

F_BAFC_PCD /BA1/FCPRC Process Step ID for Process FPSL: Process Controller

Controller
ACTVT
Activity

F_BABR_SCB ACTVT Activity FPSL: Subledger Coding

Block
ACC_SYSTEM Accounting System

/BA1/LGENT Legal Entity

F_BABR_FPS /BA1/ACCSC Accounting Scenario FPSL: Forecasting, Planning

and Simulation
/BA1/FPSST Status of Scenario Results

/BA1/NBSCN New Business Scenario

ACTVT Activity

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 to enable
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
Characteristic Value 5 (for
/BA1/HWRDA
Authorization Field)
/BA1/HWRT
Characteristic Value 6 (for
ACTVT Authorization Field)

Characteristic Value 7 (for

Authorization Field)

Results Data Area

Result Type

Activity

F_BAFW_PM /BA1/F0CH1 Characteristic Value 1 (for CVPM Authorization Object

Authorization Field)
/BA1/F0CH2 You can use this authoriza
Characteristic Value 2 (for tion object to separate tasks
/BA1/F0CH3
Authorization Field) involved in the execution of
/BA1/F0CH4 processes.
Characteristic Value 3 (for
/BA1/F0CH5 Authorization Field)

/BA1/F0CH6 Characteristic Value 4 (for

Authorization Field)
/BA1/PAR
Characteristic Value 5 (for
/BA1/PRO
Authorization Field)
/BA1/SEQ
Characteristic Value 6 (for
ACTVT Authorization Field)

Process Partition

Analytical Process

Step Sequence

Activity

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
16 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
Authorization Object Field Field Description Object Description

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 actual DDIC au
tion thorization.

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

F_BAFJ_PRO ACTVT Authorization Object for ECP

For more information about

/BA1/CR0SR
processes related to ECP, see
Security for Third-Party Ap
plications or Other Compo
nents [page 34].

Authorization Objects for Business Partner

Financial Products Subledger (software component S4FPSL) is an add-on that is installed on an SAP S/4HANA
instance. There are two different business objects available for the business partner in this type of installation:

• Recommended: SAP Business Partner, maintained in transaction BP

• Analytical Business Partner (aBP), maintained in transactions BPV1 (Create), BPV2 (Change), BPV3
(Display)

 Recommendation

We stongly recommend that you use SAP Business Partner.

For more information about the authorization objects for SAP Business Partner, see Authorization
Management.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Security Information for SAP S/4HANA for Financial Products Subledger PUBLIC 17
If you are still using the analytical business partner, the table below shows the security-relevant authorization
objects that are used by the Business Partner for Financial Services component 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 need to be secured by separate 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.

 Note

This information is specific to Business Partner only. Financial Products Subledger does not provide any
card-specific security requirements. Moreover, information such as credit card numbers must not be
stored in the Financial Products Subledger database.

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 Application Help, choose Basic
Functions Payment Card Processing Security for Payment Card Data .

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
18 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
In addition, see the Security Guide under 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 using 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.

Authorization for Data Access Interface

When generating views for the Data Access Interface, enable authorization checks in Customizing for Financial
Products Subledger under Infrastructure Data Access Interface Enable Authorization Checks in DAI .

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.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Security Information for SAP S/4HANA for Financial Products Subledger PUBLIC 19
Role Description

SAP_FPS_CUSTOMIZER This role contains authorizations for making Customizing

settings for Subledger Accounting (/BA1/Subledger Ac
counting).

SAP_FPS_EXP_FINANCIAL_ACCTNT This role contains authorizations for the SAP Easy Access
Menu for Financial Products Subledger.

SAP_FPS_EXP_FINANCIAL_ECP This role contains authorizations for the SAP Easy Access
Menu for Financial Products Subledger Preparatory
Processing .

SAP_FPS_EXP_FINANCIAL_PLANNER This role contains authorizations for the SAP Easy Access

Menu for Financial Products Subledger Forecasting,

Planning, and Simulation .

SAP_FPS_EXP_VDM_REPORTING This role contains authorizations for using CDS views of the
Virtual Data Model for Financial Products Subledger.

An administrator or a technical user can have all of the roles listed, together with specific profiles for
Customizing transports or BW as described in Setting Up a Financial Products Subledger Client [page 44].

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/4HANA. Be careful when you combine FPSL roles with
non-FPSL roles. This might be necessary if you want to configure access to the General Ledger in SAP S/
4HANA, for example. Define the authorization object S_RFC restrictively and do not provide it with wildcard (*)
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. Wildcard

authorizations (starting with *) in the Analytical Process
field /BA1/PRO are critical.

F_BAHW_RES Accessing results data

F_BAF1_AUG or Accessing source data

F_BAF2_BTC

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
20 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
Authorization Object Use

F_BABR* Specific to the accounting logic.

F_BABR_BAS is used to check the legal entity (/BA1/LGENT

- Legal Entity) in source data, results data, and CVPM proc
esses.

The legal entity in the source data must be entered in the da
tabase field LEGAL_ENTITY for financial contracts. Other
wise authorization checks on the legal entity cannot be sup
ported properly.

 Note
F_BABR_BAS is the most important authorization object
for checking the legal entity. To a large extent, this check
is based on the field LEGAL_ENTITY in the financial con
tract in the source data. Therefore, we strongly recom
mended that when you load financial contracts, the da
tabase field LEGAL_ENTITY is filled. (Do not enter a le
gal entity by using entries from other fields that are
mapped to the characteristic Legal Entity /BA1/
C55LGENT in the Subledger Coding Block). This also ap
plies to the definition of securities accounts and portfo
lios in the source data. To be clear: An entry in the the
field LEGAL_ENTITY is mandatory; not only for support
ing the proper execution of accounting processes but
also for authorization checks in value helps, database
access and process execution.

In addition, F_BABR_UI is the most important authorization

object for CDS views of the Virtual Data Model.

F_BAFC_PCD Process Controller

F_BAFF_ET Enhancement Tool for DDIC extensions in source data, re

sults data, and accounting.

Only relevant for system administrators and power users:

Edit or change activities are generally required.

F_FPS_TLS Used in several technical tool reports, such as where-used

lists, code generation for derivation and mapping routines,
or ASU-delivery functions

Related Information

System Landscape for SAP S/4HANA for Financial Products Subledger [page 7]

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 to the Financial Products Subledger.

Related Information

System Landscape for SAP S/4HANA for Financial Products Subledger [page 7]
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

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
22 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
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 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 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 user assistance for SAP NetWeaver. To find the relevant documents, go to SAP
Help Portal at https://help.sap.com/nw and open the product page for your SAP NetWeaver release. Search for
"activating and deactivating ICF services" and "ICF security".

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 7].

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, which are documented in these templates
along with the assumptions that have been guiding the implementation in the software. By nature of legal
requirements the conclusion whether these features are covering customer specific demands as well as the
conclusion whether additional measures have to be taken is solely with the customer.

 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.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
24 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
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

Term Definition

Artificial Intelligence (AI) The simulation of human intelligence processes by machines

and computer systems – typically by learning, coming to its
own conclusions, appearing to understand complex content,
engaging in natural dialogs with people, enhancing human
cognitive performance (also known as cognitive computing)
or replacing people on execution of nonroutine tasks. Appli
cations include autonomous vehicles, automatic speech rec
ognition and generation and detecting novel concepts and
abstractions (useful for detecting potential new risks and
aiding humans to quickly understand very large bodies of
ever-changing information)

Automated Decision Making The ability to make decisions by technological means with
out human involvement.

Blocking A method of restricting access to data for which the primary

business purpose has ended.

Business Purpose The legal, contractual, or in other form justified reason for
the processing of personal data to complete an end-to-end
business process. The personal data used to complete the
process is predefined in a purpose, which is defined by the
data controller. The process must be defined before the per
sonal data required to fulfill the purpose can be determined.

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 Any information relating to an identified or identifiable natu

ral person ("data subject"). An identifiable natural person is
one who can be identified, directly or indirectly, 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, men
tal, economic, cultural, or social identity of that natural per
son.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Security Information for SAP S/4HANA for Financial Products Subledger PUBLIC 25
Term Definition

Deletion Deletion of personal data so that the data is no longer avail

able.

End of Business Defines the end of active business and the start of residence
time and retention period.

End of Purpose (EoP) The point in time when the processing of a set of personal
data is no longer required for the primary business purpose,
for example, when a contract is fulfilled. After the EoP has
been reached, the data is blocked and can only be accessed
by users with special authorizations (for example, tax audi
tors).

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

Processing of Personal Data Processing means any operation or set of operations which
is performed on personal data or on sets of personal data,
whether or not by automated means, such as collection, re
cording, organisation, structuring, storage, adaptation or al
teration, retrieval, consultation, use, disclosure by transmis
sion, dissemination or otherwise making available, align
ment or combination, restriction, erasure or destruction.

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.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
26 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
Term Definition

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

Technical and organizational measures (TOM) Some basic requirements that support data protection and
privacy are often referred to as technical and organizational
measures (TOM). The following topics are related to data
protection and privacy and require appropriate TOMs, for ex
ample:

• Access control: Authentication features

• Authorizations: Authorization concept
• Read access logging
• Transmission control / Communication security
• Input control / Change logging
• Availability control
• Separation by purpose: Is subject to the organizational
model implemented and must be applied as part of the
authorization concept.

3.5.3 Consent

SAP S/4HANA for financial products subledger or SAP S/4HANA, financial posting gateway 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.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Security Information for SAP S/4HANA for Financial Products Subledger PUBLIC 27
 Note

Financial Products Subledger supports you in the context of fulfilling regulatory requirements and multi-
dimensional management analysis and reporting.

3.5.4 Read Access Logging

Read Access Logging is considered as an additional safeguard in the protection of personal data, because it
helps to identify potential illegitimate access to personal data. Read access to sensitive personal data is
partially based on legislation, and it is subject to logging functionality. Read access logging (RAL) is used to
monitor and log read access to sensitive personal data that was disclosed via user interface, which can be
extended to read access to other personal data. Data may be categorized as sensitive by law, by external
company policy, or by internal company policy. When these read accesses are logged, you should be able check
which user accessed personal data on which access channel and the date and time, depending on the
configuration. Read access logging enables you to answer questions about who accessed particular data within
a specified time frame. That logging also includes downloading attachments or files, logs for such events shall
contain information to identify the attachment. Additionally, as for Read Access Logging across system
boundaries, the respective “access” shall be logged as soon as sensitive personal data crosses the boundary
from a trusted to an un-trusted area. 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?

Furthermore, log records can be viewed and queried, but access to them is restricted by adequate
authorizations. The personal data for which read access shall be logged and the retention period of logs, can be
configured.

Read access logging is currently available in, but not limited to the following channels:

• Remote Function Calls (sRFC, aRFC, tRFC, qRFC, bgFRC)

• Dynpro
• 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.

• BW channel (for analytical queries of the Virtual Data Model)

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

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
28 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
Configuration Fields Logged Business Context

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 / finan-

cial contract

Read Access Logging for Business Partner

• Recommended: SAP Business Partner, maintained in transaction BP

• Analytical Business Partner (aBP), maintained in transactions BPV1 (Create), BPV2 (Change), BPV3
(Display)

 Recommendation

We strongly recommend that you use SAP Business Partner.

For more information about SAP Business Partner, see SAP Business Partner.

If you are still using the analytical business partner, read access logging is supported in the service channel for
the Financial Services Business Partner as of 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

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.

 Note

The entry point for the Information retrieval report is the Business Partner ID of the central 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 .

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
30 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
3.5.6 Deletion of Personal Data

Simplified Blocking and Deletion

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 irrecoverably.
Blocking is necessary when the original retention period has expired but additional applicable extended and
overruling (mandated by law) retention periods are still in place. After the expiration of the longest retention
period, the data must be deleted.

Deletion of Personal Data

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 if 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. Sometimes, transactional data are personal data with relation to a master data object, e.g. a sales
order with reference to a business partner. Therefore, the challenge for deletion and blocking is first to handle
transactional data and finally other data, such as business partner data.

This SAP product might process data (personal data) that is subject to the data protection laws applicable in
specific countries as described in 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.

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.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
32 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
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 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

Creation and change of personal data need to be documented. 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 user made which change, the date and time, the previous value, and the
current value, depending on the configuration. Furthermore, log records can be viewed and queried, but access
to them is restricted by adequate authorizations. The personal data for which changes shall be logged and the
retention period of logs, can be configured..

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:

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Security Information for SAP S/4HANA for Financial Products Subledger PUBLIC 33
• 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 https://help.sap.com/nw . 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.6 Security for Third-Party Applications or Other

Components

This section describes security aspects relating to third-party applications used in SAP S/4HANA for financial
products subledger.

Integration with Financial Services Data Management (FSDM): Data

Federation

The integration with SAP Financial Services Data Management (FSDM) through data federation is based on
generated HANA SQL views.

These SQL views do not provide information about data that is blocked (in the context of business partner
blocking and DPP). Therefore, data federation must be used for read-only purposes only. It must not be used
for data extraction because it cannot notify a data consumer about the end of the lifecycle of a data object in

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
34 PUBLIC Security Information for SAP S/4HANA for Financial Products Subledger
Financial Products Subledger. Since the SQL views do not prevent blocked data from being displayed if the data
objects are related to a blocked central business partner, any business objects in Financial Products Subledger
that need to be blocked must be blocked using ILM-enabled archiving.

In addition, the SQL views do not explicitly show the purpose of data processing that is specified within
Financial Products Subledger. The data consumer must ensure that the legitimate purpose of data processing
is being adhered to.

Integration with Estimated Cashflow Preparation (ECP), not relevant for SAP
S/4HANA, financial posting gateway

Estimated Cashflow Preparation (ECP) is executed in the third-party component SAP Profitability and
Performance Management (FS-PER).

Only use the FS-PER functions within Financial Products Subledger ( SAP Easy Access Menu Financial
Products Subledger Preparatory Processing ). You control which users are authorized to run the processes
under the subnode Best Estimated Cash Flows (which calls the ECP functionality) using the CVPM
authorization object described in section Authorization Objects [page 14] (see also template role
SAP_FPS_EXP_FINANCIAL_ECP). To enable a role to use these functions, enter a value, such as/BA1/RFJ*,
for the Analytical Process attribute in the authorization object.

Financial Products Subledger supports preparatory processes for Expected Cash Flows. These processes
follow the naming convention /BA1/RFJ_* for CVPM processes: The transaction codes start with /BA1/FJ.
These processes partially call functions from component FS-PER. Most of the processes use the Source
System as report granularity. These processes mainly use the authorization objects F_BAFJ_PRO and
F_BAFW_PM, and they do not make checks on the legal entity.

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 security
guides relevant for SAP S/4HANA also apply.

Resource Where to Find It

Security Guide for SAP S/4 HANA At https://help.sap.com/s4hana, under Product

Documentation.

Security Guide for SAP HANA At https://help.sap.com/hana, under Security.

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.

Financial Products Subledger is based on SAP S/4HANA. For general installation information, see the
Installation Guide for SAP S/4HANA at https://help.sap.com/s4hana.

4.1 Pre-Installation Tasks

There are two options for installing the Financial Products Subledger back-end:

1. If your SAP S/4HANA 1809 (or 1909 or 2020) 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 (or 1909 or 2020) and SAP S/4HANA for
financial products subledger 1812 together in one maintenance transaction in 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. You select and download the installation files in
Maintenance Planner.

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 about Maintenance Planner, see https://help.sap.com/viewer/p/

MAINTENANCE_PLANNER.

Alternatively, you can install components using the SAP Add-On Installation Tool (transaction SAINT).

4.2 Overall Installation Sequence

1. Installation

Execute the plan and perform the installation based on the stack XML file and your Maintenance Planner
transaction.

For more information about Maintenance Planner and Execute Plan, see the "Execute Plan" section of the
Maintenance Planner User Guide on SAP Help Portal at Maintenance Planner. You will find the Maintenance
Planner User Guide under Other.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
36 PUBLIC Installing SAP S/4HANA for Financial Products Subledger
2. Implementation

You can implement the add-on using Software Update Manager (SUM). For more information, see Software
Update Manager .

Alternatively, you can implement the add-on using SAP Add-On Installation Tool (SAINT) and the stack XML.
For more information, see SAP Add-On Installation Tool and Support Package Manager. You will find the
documentation under Application Help.

3. Completion

To complete the installation, see Release Information Note 2725310 .

4.2.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.

 Note
This is an auxiliary client that is required because the cli
ent concept is not known to BW. There can be only one
BW client in one system. Once you have chosen a BW
client, you can no longer change it.

One or more Financial Products Subledger clients This is the application client in which Financial Products
Subledger functions are used.

It uses the functionality offered by the Tool BW. As several

Financial Products Subledger clients can use one Tool BW
client, the data stored in the Tool BW must be separated ac
cording to source client.

For this reason,you need to assign a source system ID (char

acteristic 0SOURSYSTEM) for use in BW to each Financial
Products Subledger client when you set up the system.

 Note

We do not recommend using the same physical client for the Tool BW client and the Financial Products
Subledger client.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Installing SAP S/4HANA for Financial Products Subledger PUBLIC 37
4.2.2 Post-Installation Tasks

Complete the following steps before making any Customizing settings or installing Business Content:

• Change the system settings

• Set up the Tool BW client
• Set up a Financial Products Subledger client

4.2.2.1 Namespace Settings

To ensure that the system runs correctly, set the following namespaces to modifiable or not modifiable using
transaction SCTS_RSWBO004:

Modifiable
Set the following namespaces for characteristics and key figures that are created in Customizing to
modifiable:

• /B20/
• /B20C/
• /BA1/
• /BA1C/
• /BIC/

These namespaces are used for generated objects for the Tool BW. They need to be modifiable when
InfoObjects are created manually or generated in the characteristic or key figure monitor, and when you
activate the DLL content.

 Note

This is also applies to characteristics and key figures contained in Business Content.

Additional information about the namespaces used:

• /B20/ (modifiable)
• Namespace of generated DDIC objects of InfoObjects in namespace /BA1/.
• These need to be modifiable when you generate InfoObjects for fixed characteristics in the
characteristic monitor or when you generate of InfoObjects for SAP key figures in the key figure
monitor.
• /B20C/ (modifiable)
• Namespace of generated DDIC objects of InfoObjects in namespace /BA1C/.
These need to be modifiable when you generate InfoObjects in namespace /BA1C/ in the
characteristic monitor or key figure monitor.
• /BA1/ (modifiable)
• Namespace of InfoObjects generated for a fixed characteristic (/BA1/C..), SAP key figure (/BA1/K...).
• InfoObjects for fixed characteristics are generated on demand in the characteristic monitor using
the Create InfoObject or Update InfoObject function.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
38 PUBLIC Installing SAP S/4HANA for Financial Products Subledger
• InfoObjects for SAP key figures are generated on demand in the key figure monitor using the
Generate InfoObject function.
• Activation of BI Content for Data Loading Process
• /BA1C/ (modifiable)
• Namespace of InfoObjects generated for a Business Content characteristic or key figure.
These need to be modifiable when you generate InfoObjects in namespace /BA1C/ in the
characteristic monitor or key figure monitor.
• /BIC/ (modifiable)
• Namespace of generated DDIC objects of InfoObjects without prefix.
These need to be modifiable when you generate InfoObjects without prefix in the characteristic
monitor or key figure monitor.
• /BI0/ (not modifiable)
• Namespace for generated DDIC objects of InfoObjects from BI content in namespace 0
• /1BA/ (not modifiable)
• Namespace for DDIC objects and reports generated by Financial Products Subledger
• /1SGS/ (not modifiable)
• Namespace for DDIC objects and reports generated by the segmentation service

4.2.2.2 System Parameters

Adjust the system parameters to the specific system environment and data volume.

4.2.2.3 Setting Up a Tool BW Client

Financial Products Subledger uses functionality that is provided by BW embedded in S/4HANA. Therefore, you
need to set up a local BW client in FPSL, which is called the Tool BW client.

After the technical installation of Financial Products Subledger, create a BW standard client. Note that a BW
client cannot be set up in client 000. Instead, create a new client or use an 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 relevant profiles.
For more information, see Authorization Profile for Background Users.

 Note

In this case, the profiles for both the BW system and the source system are relevant.

2. Initialize BW as follows:
• Call up transaction RSA1.

 Note

When you start the transaction for the first time, you need to make some initial settings. During the
process, the system displays several message dialog boxes. Confirm all of them.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Installing SAP S/4HANA for Financial Products Subledger PUBLIC 39
• 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).
3. Call up transaction SE16 and enter table name RSADMINA. Check whether there is an entry with the
following settings. If not, make an entry with these settings here:
• BW_USER: The background user created above.
• BWMANDT: The BW client ID.

4.2.2.4 Setting Up a Financial Products Subledger Client

See Setting Up a Financial Products Subledger Client [page 44].

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
40 PUBLIC Installing SAP S/4HANA for Financial Products Subledger
5 Updating SAP S/4HANA for Financial
Products Subledger

This section provides information about how to prepare for an update and what to do before and after the
update of SAP S/4HANA for financial products subledger.

 Note

Technically a system update involves the installation of one or multiple support packages, irrespective of
whether the support package contains new features or bug fixes. The upgrade to a next major release is not
covered by this section.

Preparing the Update

Updating a support package stack involves updating multiple software components with their individual
support packages.

Note the following information:

2446980 - Release Information about Support Package Contains information about support package stacks and in
Stacks of S/4HANA FIN PROD SUBLDGR 1812 cluded support packages.

2690404 - Release Strategy and Maintenance Informa Contains the required import conditions and other technical
tion for the ABAP Add-On S4FPSL details.

2690406 - Release Strategy and Maintenance Informa If you use Fiori apps in the hub deployment with two differ-
tion for the ABAP Add-On UIFPSL ent system instances, you can apply independent mainte
nance strategies for the two system instances. This SAP
Note contains the required import conditions and technical
details for the Fiori front-end component UIFPSL.

1668882 - Note Assistant: Important notes for SAP_BA Make sure you have the newest version of this SAP Note in
SIS 730,731,740,750,751,752,753,754 your system to prepare further SAP Note implementations
and get the latest corrections needed for transaction SPAU.

Maintenance Planner The Maintenance Planner calculates the appropriate sup

port package level based on the add-on components se
Support Package Manager
lected to be part of your system update.
Software Update Manager
Alternatively, you can perform the update using the Support
Package Manager (transaction SPAM) or the Software Up
date Manager (transaction SUM).

In addition to preparing for the technical update, you also need to consider how to handle your Customizing. It
is possible to run a technical update of a support package without adjusting your Customizing settings.

To adapt new features during your update project, you may need to refer to the related Business Content for
the required Customizing changes. In this case you need to consider how to handle your existing Customizing

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Updating SAP S/4HANA for Financial Products Subledger PUBLIC 41
and the new Business Content that is delivered by SAP as part of the Support Package stack. For more
information about the changes to Business Content, see the What's New section or for more technical details,
see SAP Note 2872308 .

Update Sequence

1. Before the update

• SAP Note 2725310 - Release information about S4FPSL100 Support Packages contains information
for updating the back-end system to a certain Support Package level of S4FPSL 100.

 Recommendation

We strongly recommend that you run the pre-update checks listed in SAP Note 2725310.

Make sure you run all pre-update steps if you include multiple support packages in your maintenance
transaction.
• SAP Note 2725350 - Release information about UIFPSL100 Support Packages contains information
about executing steps before updating the front-end system to a certain support package level of UIFPSL
100.

2. Executing the update

Based on the stack XML file and your Maintenance Planner transaction, you can now execute the plan and
perform the update.

Alternatively, you can use transactions SUM or SPAM.

3. After the update

• Implement additional mandatory SAP Notes in your back-end system (see SAP Note 2725310 ) after you
have reached the intended support package level.
• Follow the mandatory activities described in SAP Note 2725310 - Release information about
S4FPSL100 Support Packages. These post-update activities may differ depending on the support
package level that you want to achieve with the system update:
• After updating from SP01 or higher to any higher support package: Execute Transaction /BA1/
F0_INITCFG_FPSL - Initial Configuration in every client that contains FPSL specific Customizing.
The system records all changes made during the execution of transaction /BA1/F0_INITCFG_FPSL
in a Customizing request. Some upgrade steps may implicate changes in workbench objects. These
changes are recorded in a workbench request.
In clients with identical Customizing, you can import these requests instead of executing
transaction /BA1/F0_INITCFG_FPSL. This might be advisible if you do not want to perform manual
activities in the productive system.
• After updating from SP00 to SP02 or any higher support package: Perform Application-Specific
Upgrade (ASU) steps, which are attached to SAP Note 2725310 .

 Note

Make sure you run these activities to complete the update of your system and reach a consistent target
state.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
42 PUBLIC Updating SAP S/4HANA for Financial Products Subledger
• If you have updated your front-end component UIFPSL, you can find information about mandatory and
recommended SAP Notes in SAP Note 2725350 .
• After you have performed the post-update activities and implemented the additional SAP Notes, you may
need to adjust the Customizing for new features. You can use the delivered Business Content as an
example.

 Caution

If you have deployed other add-ons, such as SAP Profitability and Performance Management 3.0 with
content for Estimated Cash Flow preparation (ECP), changes in FPSL Customizing could also have an
impact on these add-ons.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Updating SAP S/4HANA for Financial Products Subledger PUBLIC 43
6 Setting Up a Financial Products
Subledger Client

After you have configured the Tool BW, you need to configure a financial products subledger (FPSL) client.

We recommend that you create a new client for this. In principle, it is also possible to use the Tool BW client.

 Note

It is not possible to switch the BW to another client later on.

The clear separation of clients in FPSL in contrast to BW might cause issues in the future. For example, a local
client copy is no longer possible.

Setting up a new FPSL client: 1. Create a new client and assign a logical system to it us
ing transaction SCC4.
2. Make a client copy from client 000 to the new client
with copy profile SAP_CUST or SAP_ALL.

 Note
No postprocessing is necessary, which means you
do not need to execute transaction /BA1/AT_INIT
in the new client.

3. Create a background user in the FPSL client using

transaction SU01.
Copy SAP_FPS_EXP_FINANCIAL_ACCTNT to a Z role
and enter the authorization values accordingly. Then as
sign the generated profile and other relevant profiles to
the background user.
For more information, see Authorization Profile for
Background Users.
In this case, only the profile for the source system is rel
evant.
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:
You may not need to make settings. 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

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
44 PUBLIC Setting Up a Financial Products Subledger Client
Setting up the logical FPSL client in the physical Tool BW Check if an RFC destination exists with the same name as
client:
the logical system that is assigned to the BW client.

• RFC destination exists: Enhance the profile of the back

ground user and add role SAP_FSP_EXPERT.
• RFC not created yet: Execute steps 3 and 4 (see above).

Check that client 000 was copied to the BW client after

FPSL was installed. If not, some essential Customizing data
will be missing.

6.1 Business Partner Settings

Financial Products Subledger (software component S4FPSL) is an add-on that is installed on an SAP S/
4HANA instance. There are two different business objects available for the business partner in this type of
installation:

• Recommended: SAP Business Partner, maintained in transaction BP

• Analytical Business Partner (aBP), maintained in transactions BPV1 (Create), BPV2 (Change), BPV3
(Display)

 Note

The Analytical Business Partner is not relevant for SAP S/4HANA, financial posting gateway.

 Recommendation

We strongly recommend that you use SAP Business Partner to avoid SAP Business Partner data being
replicated to the analytical business partner. Data is replicated and multiplied by versioning, and the
versioning of SAP Business Partner data in Financial Products Subledger causes a runtime overhead when
reading data. This will have a negative effect on system performance.

Regardless of which business partner you use, you need to ensure that the business partner IDs are mapped.

For this mapping, use the report FSBP_MAINTAIN_IDTYPE_MAPPING. It maps new identification categories
and types in Customizing table BUT0ID (ID numbers) to existing identification number categories in table
BPID001 (ID numbers) .

 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 Customizing settings. This
is described in SAP Note 1556353 .

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Setting Up a Financial Products Subledger Client PUBLIC 45
Once you have created Customizing settings for the 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 for FSBP_MAINTAIN_IDTYPE_MAPPING (transaction SA38).

More Information

See SAP Note 1556353 : BP_AID: Checklist for migration of "Additional Partner Numbers"

See SAP Note 2798746 : Usage of the Analytical Business Partner in S4FPSL

6.2 Create an Entry in the System Landscape Table

In Customizing for Financial Products Subledger, choose Basic Settings Global Settings Define System
Landscape for Financial Products Subledger .

Make an entry in this Customizing activity for every client in which you want to run FPSL.

In the System Landscape screen, you create a new entry and make the following settings, which apply to the
overall system:

System ID Enter the system ID.

Switch By default, the append generation is set to the Standard

Append Generation mode. For more information, see the F1
help for the field.

Depending on this setting, you may need to make additional

settings for the enhancement tool. For more information,
see the F1 help for the field and press the Information button
in Customizing for Financial Products Subledger under

Data Model Technical Settings Analyze and Generate

Database Appends . You find the settings in the menu un

der Utilities System Settings .

Namespace This is the namespace for transportable objects of the en

hancement tool. Set the namespace to Z or Y, or your own
transportable customer namespace.

In the Active Clients subscreen, make the following settings, which apply in each client that runs FPSL:

Client Enter the financial products subledger client number.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
46 PUBLIC Setting Up a Financial Products Subledger Client
Main Client Indicates the client that is usually used for the transport of
client-independent objects, such as appends of the en
hancement tool and InfoObjects for characteristics and key
figures.

The main client is relevant if the metadata conflicts 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, select this cli
ent as the main client.

Otherwise, select the client that is usually used for Cus

tomizing transports.

Source System ID (mandatory) Enter a source system ID.

This is used to separate the data from different FPSL clients

in the Tool BW. A source system ID consists of two alphanu
meric characters.

 Recommendation
We recommend that you use different source system
IDs for all clients across the whole FPSL system land
scape (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) in FPSL loads data. The staging BI
system can be a separate system or the tool BW client of the
FPSL system. In the latter case, leave this field empty. As a
result, the system does not have to use Remote Function
Calls (RFC) to read data from BI in the Data Loading Process,
which increases performance.

FPSL Client Enter the logical system 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 cor
rect target client.

If the DLP is not used, this field has no effect and can there
fore be left empty.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Setting Up a Financial Products Subledger Client PUBLIC 47
DLP Target Client (Data Loading Process Target Client) If you supply data to the FPSL using the Data Loading Proc
ess, the system creates change pointers in BI and stores
them in the FPSL system. You can use this checkbox to de
termine 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 pro
vided 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 be left
empty.

6.3 Execute Initial Configuration for Subledger Accounting

You execute the initial configuration for subledger accounting in Customizing for Financial Products
Subledger under Basic Settings Global Settings Run Initial Configuration .

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
48 PUBLIC Setting Up a Financial Products Subledger Client
7 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 an example configuration for the system that can be used by the team
members in your implementation project to familiarize themselves with the system architecture and functions.
The examples, templates, and solutions provided with Business Content enable you to create prototypes easily
and speed up the implementation process. Business Content contains sample Customizing for the end-to-end
processing of data for Subledger Accounting for Financial Instruments and Subledger Accounting for Insurance
Contracts.

Business Content is delivered using Business Configuration Sets (BC sets), piece lists, and content for SAP
NetWeaver Business Warehouse (BW). Once you have installed 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.

 Note

Once installed, Business Content is no different to any other Customizing you have done manually. When
the system is updated to a new Feature Package (FP) the Business Content remains valid. Nevertheless,
SAP provides a new Business Content version for every Feature Package that reflects changes to SAP's
internal test Customizing due to new functions, new test scope, fixed errors, or adjustments following
customer feedback.

7.1 Configuring Subledger Accounting

After you have set up an FPSL client, you can install Business Content for Subledger Accounting in this client.

To do this, follow the instructions described in SAP Note 2711006 .

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Configuring SAP S/4HANA for Financial Products Subledger PUBLIC 49
7.2 Configuring Estimated Cash Flow Preparation for Use
with Subledger Accounting

 Note

This chapter is not relevant for SAP S/4HANA, financial posting gateway.

In addition to Business Content for Subledger Accounting, you can install Sample Content for Estimated Cash
Flow Preparation.

Prerequisites

You have installed Business Content for Subledger Accounting (see Configuring Subledger Accounting [page
49]).

Procedure

1. Install the Business Content for the integration of Estimated Cashflow Preparation that is delivered with
SAP S/4HANA for financial products subledger:
Follow the instructions described in SAP Note 2729154 .
2. Install the Sample Content for Estimated Cash Flow Preparation that is delivered with SAP Profitability
and Performance Management:
Follow 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 in the Administration Guide for SAP Profitability and
Performance Management, at SAP Profitability and Performance Management (including SAP Note
2650963 ).

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
50 PUBLIC Configuring SAP S/4HANA for Financial Products Subledger
8 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 https://help.sap.com/s4hana).

Specific Information for Financial Products Subledger

See SAP Note 2874355 - How to Monitor and Operate S4FPSL .

Monitoring
For more information, see Monitoring [page 52].

Trace and Log Files

There are application log objects that are specific to Financial Products Subledger. The objects start with the
prefix /BA1/.

Workload Monitors
Parallel processing and packaging settings affect the processing time and the usage of hardware resources.

You can use monitoring tools such as the report RBANK_PP_MONITOR to verify 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
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 53].

Troubleshooting
For more information, see Troubleshooting [page 55].

Calculation and Valuation Process Manager (CVPM)

You can use the Calculation and Valuation Process Manager to configure and execute analytical processes
beyond Financial Products Subledger.

Support Desk Management

The FS-FPS application component (including subcomponents) is relevant for Financial Products Subledger
and should be used to report problems.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Operating SAP S/4HANA for Financial Products Subledger PUBLIC 51
Reports for Development and Test Systems
For more information, see Reports for Development and Test Systems [page 56].

8.1 Monitoring

This section describes monitoring tasks for SAP S/4HANA for 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, there are no monitoring functions for these interface calls in Financial Products Subledger.

For more information, see RFC Interfaces.

Data Loading

You can also load data to Financial Products Subledger using embedded BW functionality.

The data loading 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 to handle objects with errors.

For more information about data loading topics, see Data Loading Process (FS-FPS-IF-DL).

Data Growth and Data Archiving Monitors

For more information about the archiving processes in Financial Products Subledger, see Archiving Using
Archive Administration.

Calculation and Valuation Process

For more information, see CVPM Process Monitor.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
52 PUBLIC Operating SAP S/4HANA for Financial Products Subledger
Services (SOAP)

Some interfaces to Financial Products Subledger are implemented as web services. The infrastructure is
responsible for the handling of services. The infrastructure is the active component and is responsible for the
logging of information, transaction management, and the required monitoring capabilities. The SAP
infrastructure component for handling SOAP 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 so general descriptions are available. While
implementing the service usage, you must ensure that the monitors are connected to an alerting mechanism
so that an operator or person responsible is informed immediately if an incident occurs (by SMS or e-mail, for
example).

You can use the Postprocessing Office or the Error and Conflict Handler to analyze services used by Financial
Products Subledger. 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, see Error Handling in Financial Services or Handling Errors and Conflicts.

You can access these functions from the SAP Easy Access screen under Cross-Application Components.

8.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 regularly by the administrator.

 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 if the system has stalled
due to an overload of work processes and needs to be restarted.

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
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 https://help.sap.com/s4fpsl .

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Operating SAP S/4HANA for Financial Products Subledger PUBLIC 53
Scheduled Periodic Tasks
This section describes all tasks that can be automated and that must be run periodically to keep the
application running smoothly. 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 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 https://help.sap.com/
s4fpsl, enter Archiving with ILM-Ena
bled Archiving Objects in the search bar,
press Enter , and open the search re
sult 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 need to be run periodically to keep the application running
smoothly over time. Unlike the scheduled tasks listed above, which you can automate using a task scheduler
program, you need to execute manual tasks yourself. 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 data, display more information for each job (run sta
tus, 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 for data loading

Transaction /BA1/F3_DS_PACK Deletes data packages for primary data sources

Database Monitoring

After the initial partitioning of database tables during the installation process (in accordance with consulting
note 2722355 ), the partitioning of tables must be adjusted over time. A set of tables is partitioned based on
the posting date and partitions may have been created for just one or two fiscal years in the future, so new
partitions need to be created on a regular basis. Often tables need to be partitioned when there is no OTHERS
partition, so you must make sure that partitions you require always exist (for example, with regard to posting
dates). If not, the system will terminate processes that try to write in non-existent partitions.

The normal health checks for a database have to be applied. For more information, see the Operations Guide
for SAP S/4HANA.

The data volume growth in the partitions also needs to be checked regularly. The initial partitioning is
performed based on assumptions about data volume growth, so these assumptions may need to be adjusted.
For example, if data volume growth is faster than expected and a finer partitioning is required.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
54 PUBLIC Operating SAP S/4HANA for Financial Products Subledger
8.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.

Specific Problem Analysis

Some problems may arise from specific processes within Financial Products Subledger

Generated Objects
Some functions require objects that are generated when you copy clients, while postprocessing using a client
copy, or when you save or activate Customizing objects. The system generates the objects automatically
without checking data for consistency. To check whether the client was copied successfully, you need to
compare the data in the source client and target client. The following sections provide information about how
to analyze and solve these problems.

If object generation fails, you can manually start the following reports to create the required objects or for an
overview of all generated objects:

• Check report for Customizing and configuration of source data

This check routine identifies inconsistencies in Customizing and the activation of generated objects. In
Customizing for Financial Products Subledger, choose Data Model 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)

For more information, see CVPM Process Monitor, Step Controller, and Capability to Restart Parallel Processes.

Configuration
• You can check whether your settings in Customizing for Subledger Accounting are consistent in
Customizing for Financial Products Subledger under Subledger Accounting Technical Settings
Utilities Check Configuration for Subledger Accounting .
• You can check the current status of your enhancement structures and the status of the generated code for
field mapping in Customizing for Financial Products Subledger under Data Model Master Data and
Flow Data Analyze and Generate Database Appends .
• You can check the current status of your enhancement structures and the status of the generated code for
derivation, and regenerate it if required, in Customizing for Financial Products Subledger under
Subledger Accounting Technical Settings Analyze and Generate Database Appends

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Operating SAP S/4HANA for Financial Products Subledger PUBLIC 55
Problems During Postprocessing

In Financial Products Subledger, a cockpit is available to check problems that occur in postprocessing after
client copies and transports. Use transaction /BA1/AT_INIT to open the cockpit.

For information about client copies and transports, see Client Copy and Transport.

Data Volume

Financial Products Subledger has a full versioning strategy for most of its objects, which increases data
volume. The data volume can be reduced by archiving data as soon as possible.

For more information, go to https://help.sap.com/s4fpsl, enter Data Archiving and Deletion in Financial
Products Subledger in the search bar, press Enter , and open the search result with that title.

Communication with Services (SOAP)

For the analysis of services used by Financial Products Subledger, you can use the Postprocessing Office or
the Error and Conflict Handler (see Monitoring [page 52]).

The system stores messages that could not be processed completely in the Error and Conflict Handler, which is
integrated in the Postprocessing Office. This integration allows you to configure a workflow that forwards errors
to an administrator to handle the problem.

In the event of a configuration error, you can change the application configuration 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 there.

Module Editor Tool

The after-import and post-processing methods of the Module Editor try 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, these cannot be activated 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 need to 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.

8.4 Reports for Development and Test Systems

The section provides information about useful test reports for Financial Products Subledger.

 Note

Note that these reports are designed to be used in test systems only, and cannot be executed in a live
system.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
56 PUBLIC Operating SAP S/4HANA for Financial Products Subledger
Technical Name of Transaction for Re
port Name Additional Information

/BA1/BR_RDL_MAN_CHNG Manual Entry of Results Data You can use this report to upload test
data to the results data storage. The
loading process comprises three steps
for each FPSL result category:

1. Data is created in the display list in

one of the following ways:
• Manual entry
• Reading an CSV file
• Reading existing data from the
results data storage
2. Data is edited in the display list.
3. Data is saved.

/BA1/HW_EXCEL_EXEC Upload results data You can use this report to upload test
data to the results data storage. The
system loads the data for each result
type by reading a CSV file.

/BA1/R6_CHECK_PDS Check worklists You can use this report to check pri
mary data sources. These data sources
are used by the analytical processes to
create worklists for processing. Under
standing how data is provisioned by
these data sources can help you to un
derstand the data processing in the an
alytical processes. In particular, you can
check the reading behavior of the pri
mary data sources that you have cre
ated.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Operating SAP S/4HANA for Financial Products Subledger PUBLIC 57
9 UI Technology Information for SAP S/
4HANA for Financial Products Subledger

 Note

This section deals with UI technology topics relevant for Financial Products Subledger, especially the use
of SAP Fiori apps, and is intended for system administrators and technical consultants.

Workplace for Financial Accountants and Actuaries, not relevant for SAP S/
4HANA, financial posting gateway

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 (go to https://help.sap.com/s4hana).

 Note

Not all the information contained in the UI Technology Guide for SAP S/4HANA is applicable for the apps in
Financial Products Subledger, for example the information about SAP Fiori search and extensibility.

App Implementation

For the implementation of the apps 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

Make sure that you run report /UI5/APP_INDEX_CALCULATE to calculate the SAPUI5 application index.
Schedule the job as a background job. For more information, read the report documentation.

Extensibility

You can extend the Changes in Insurance Liabilities app by adding fields, including custom fields. For more
information, see the SAP Fiori apps reference library.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
58 PUBLIC UI Technology Information for SAP S/4HANA for Financial Products Subledger
Integration with SAP Analytics Cloud (SAC)

The data model in Financial Products Subledger is now integrated with the SAP S/4HANA virtual data model
(VDM). The VDM uses Core Data Services views (CDS views) to provide simplified, business-oriented access to
transaction data in Financial Products Subledger.

You can use the CDS views to integrate with analytical applications such as SAP Analytics Cloud. For more
information, see Importing from the Content Network.

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
UI Technology Information for SAP S/4HANA for Financial Products Subledger PUBLIC 59
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

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

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

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

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

Videos Hosted on External Platforms

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

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

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

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

Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
60 PUBLIC Important Disclaimers and Legal Information
Administration Guide for SAP S/4HANA for Financial Products Subledger 1812 Support
Package Stack 6
Important Disclaimers and Legal Information PUBLIC 61
www.sap.com/contactsap

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

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

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN

SAP-IAG Admin Guide
50% (2)
SAP-IAG Admin Guide
178 pages
Best Practices For SAP BTP 1.0
No ratings yet
Best Practices For SAP BTP 1.0
110 pages
This Documentation As PDF - SAP HANA Cloud PDF
100% (1)
This Documentation As PDF - SAP HANA Cloud PDF
1,472 pages
Best Practices For SAP BTP
50% (2)
Best Practices For SAP BTP
106 pages
Best Practices For SAP BTP: Public 2023-03-22
No ratings yet
Best Practices For SAP BTP: Public 2023-03-22
110 pages
Checklist Design Review
No ratings yet
Checklist Design Review
3 pages
Administration Guide For SAP S/4HANA For Financial Products Subledger 1812
100% (1)
Administration Guide For SAP S/4HANA For Financial Products Subledger 1812
56 pages
SAP AC 12 SP22 Administrator Guide
No ratings yet
SAP AC 12 SP22 Administrator Guide
50 pages
SAP AC 12.0 SP08 Administrator Guide
No ratings yet
SAP AC 12.0 SP08 Administrator Guide
50 pages
GRC12 Administration
No ratings yet
GRC12 Administration
46 pages
SAP Cloud For Customer Security Guide
100% (1)
SAP Cloud For Customer Security Guide
88 pages
Administration Guide For SAP S/4HANA Cloud For Enterprise Contract Assembly
No ratings yet
Administration Guide For SAP S/4HANA Cloud For Enterprise Contract Assembly
40 pages
SAP CAR Security
No ratings yet
SAP CAR Security
82 pages
SAP Cloud For Customer Security Guide
No ratings yet
SAP Cloud For Customer Security Guide
42 pages
Administration Guide For SAP Enterprise Contract Assembly
No ratings yet
Administration Guide For SAP Enterprise Contract Assembly
48 pages
Administrator Guide SAP Access Control 12.0 SP02
No ratings yet
Administrator Guide SAP Access Control 12.0 SP02
50 pages
FSD Ce2108
No ratings yet
FSD Ce2108
274 pages
SAP Application Interface Framework 40 EN
No ratings yet
SAP Application Interface Framework 40 EN
180 pages
PRO424 ApplicationMonitoring 2aug16
No ratings yet
PRO424 ApplicationMonitoring 2aug16
268 pages
https___theerplearning.com_free-materials_-10
No ratings yet
https___theerplearning.com_free-materials_-10
122 pages
SAP IAG Admin Guide
No ratings yet
SAP IAG Admin Guide
182 pages
PDF Sec Guide Ehsm 6.0 en
No ratings yet
PDF Sec Guide Ehsm 6.0 en
70 pages
SAP S/4HANA Cloud 2302: Feature Scope Description
No ratings yet
SAP S/4HANA Cloud 2302: Feature Scope Description
306 pages
Operations Guide Customer Management
No ratings yet
Operations Guide Customer Management
28 pages
s4 Hana 2011
No ratings yet
s4 Hana 2011
250 pages
SAP Business Application Studio
No ratings yet
SAP Business Application Studio
90 pages
FSD_CE2502
No ratings yet
FSD_CE2502
320 pages
DM Security Guide Cloud
No ratings yet
DM Security Guide Cloud
56 pages
FSD Ce2308
No ratings yet
FSD Ce2308
314 pages
Operations Guide Customer Management
No ratings yet
Operations Guide Customer Management
30 pages
A Guide To The ACI Worldwide BASE24-eps On z/OS: Front Cover
No ratings yet
A Guide To The ACI Worldwide BASE24-eps On z/OS: Front Cover
198 pages
TLE 6.2 SAP R3 and R4 Setup and User Guide
No ratings yet
TLE 6.2 SAP R3 and R4 Setup and User Guide
145 pages
SAP Cloud Identity Service
No ratings yet
SAP Cloud Identity Service
252 pages
GRC 12
100% (1)
GRC 12
52 pages
SAP Cloud Platform
100% (5)
SAP Cloud Platform
2,328 pages
GRC12 Secrity Guide
100% (1)
GRC12 Secrity Guide
52 pages
Planning LM
No ratings yet
Planning LM
76 pages
SAP Application Interface Framework 40 EN
No ratings yet
SAP Application Interface Framework 40 EN
190 pages
Best Practices For SAP BTP
No ratings yet
Best Practices For SAP BTP
112 pages
Operations Guide For SAP Access Control 10.1, SAP Process Control 10.1, and SAP Risk Management 10.1
No ratings yet
Operations Guide For SAP Access Control 10.1, SAP Process Control 10.1, and SAP Risk Management 10.1
40 pages
SAP S4 Hana - Integration
No ratings yet
SAP S4 Hana - Integration
50 pages
DCS - Digital compliance Service
No ratings yet
DCS - Digital compliance Service
124 pages
6-5 JDBC Adapter Install and Users Guide
No ratings yet
6-5 JDBC Adapter Install and Users Guide
260 pages
Inst Op2023
No ratings yet
Inst Op2023
94 pages
SAP Cloud Platform Identity Authentication Service
No ratings yet
SAP Cloud Platform Identity Authentication Service
456 pages
Soa Best Practices
No ratings yet
Soa Best Practices
160 pages
DataPower ServicePlanning Implementation BestPractices
No ratings yet
DataPower ServicePlanning Implementation BestPractices
160 pages
71 - System Administrator Guide
No ratings yet
71 - System Administrator Guide
311 pages
SAP Supply Chain Management 70 Security GuideE
100% (1)
SAP Supply Chain Management 70 Security GuideE
45 pages
SG 247943
No ratings yet
SG 247943
160 pages
Salesforce Security Impl Guide
No ratings yet
Salesforce Security Impl Guide
320 pages
WebMethods SAP Adapter User's Guide - Software AG Documentation
No ratings yet
WebMethods SAP Adapter User's Guide - Software AG Documentation
314 pages
GRC Whitepaper
No ratings yet
GRC Whitepaper
32 pages
Salesforce Security Impl Guide 250220 194102
No ratings yet
Salesforce Security Impl Guide 250220 194102
332 pages
SAP BW4HANA Security Guide en
No ratings yet
SAP BW4HANA Security Guide en
52 pages
Salesforce Security Impl Guide
No ratings yet
Salesforce Security Impl Guide
303 pages
ChatGPT for Business: Strategies for Success
From Everand
ChatGPT for Business: Strategies for Success
Matthew C. Smith
No ratings yet
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
From Everand
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
Matthew C. Smith
No ratings yet
Unlocking Statistics for the Social Sciences
From Everand
Unlocking Statistics for the Social Sciences
Norma Sinclair
No ratings yet
Blog Smarter, Not Harder: SEO, Blogging, and AI Strategies to Skyrocket Your Traffic
From Everand
Blog Smarter, Not Harder: SEO, Blogging, and AI Strategies to Skyrocket Your Traffic
Jay Nans
No ratings yet
Software Patterns Made Easy
From Everand
Software Patterns Made Easy
Justice Nanhou
No ratings yet
Subnetting Basics: Michael D. Mann
No ratings yet
Subnetting Basics: Michael D. Mann
28 pages
1.6366!ECTS - 10-11 - Period 3 Och 4
No ratings yet
1.6366!ECTS - 10-11 - Period 3 Och 4
17 pages
SM100
No ratings yet
SM100
106 pages
DS 000347 ICM 42688 P v1.7
No ratings yet
DS 000347 ICM 42688 P v1.7
110 pages
Automation Irrigation System Using Arduino For Smart Crop Field Productivity
No ratings yet
Automation Irrigation System Using Arduino For Smart Crop Field Productivity
8 pages
AI Working Basics
No ratings yet
AI Working Basics
40 pages
Chapter 2 Practise Questions
100% (1)
Chapter 2 Practise Questions
9 pages
IEEE CS ACM Computing Curricula Computer
No ratings yet
IEEE CS ACM Computing Curricula Computer
99 pages
Module 1 Introduction To DataScience and Analytics
No ratings yet
Module 1 Introduction To DataScience and Analytics
10 pages
Bartender Maintenance Update Checklist
No ratings yet
Bartender Maintenance Update Checklist
1 page
VISHALA PERSAD-INFO 0101-Assignment #3 (Powerpoint)
No ratings yet
VISHALA PERSAD-INFO 0101-Assignment #3 (Powerpoint)
11 pages
Test Chapter 07
No ratings yet
Test Chapter 07
15 pages
Module 4 AOA
No ratings yet
Module 4 AOA
97 pages
Car Lift Dubai Website Proposal
No ratings yet
Car Lift Dubai Website Proposal
3 pages
Sdn. Notes
No ratings yet
Sdn. Notes
25 pages
Introduction To Hacking
No ratings yet
Introduction To Hacking
7 pages
Time Calculator - Calculate Download Timespeed
No ratings yet
Time Calculator - Calculate Download Timespeed
1 page
Electronics 11 00518
No ratings yet
Electronics 11 00518
26 pages
CSL 204 Operating Systems Lab
No ratings yet
CSL 204 Operating Systems Lab
81 pages
H446-01 QP Jun19_AC
No ratings yet
H446-01 QP Jun19_AC
28 pages
53 SD WAN Through FortiManager
No ratings yet
53 SD WAN Through FortiManager
265 pages
Cpe186 Pset 2
No ratings yet
Cpe186 Pset 2
3 pages
8TH Class COMPUTER Full Book MCQs For Educator Prep by Bismillah Academy 0300-7980055
No ratings yet
8TH Class COMPUTER Full Book MCQs For Educator Prep by Bismillah Academy 0300-7980055
10 pages
GA4 Solutions
No ratings yet
GA4 Solutions
16 pages
Comp7 - Dec. Exam - 1st Set
No ratings yet
Comp7 - Dec. Exam - 1st Set
2 pages
Quick Manual v1.6: GPRS/GNSS Tracker With Bluetooth
No ratings yet
Quick Manual v1.6: GPRS/GNSS Tracker With Bluetooth
16 pages
Remote Control For Yamaha DM 2000 - Cubase - Steinberg Forums
No ratings yet
Remote Control For Yamaha DM 2000 - Cubase - Steinberg Forums
6 pages
User Manual: Single Board Computer
No ratings yet
User Manual: Single Board Computer
71 pages
Manifest NonUFSFiles Win64
No ratings yet
Manifest NonUFSFiles Win64
6 pages

FPSL Adminguide en

Uploaded by

FPSL Adminguide en

Uploaded by

PUBLIC

Document Version: 1.0 – 2022-11-16

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. . . . . . . . . . . . . . . . 12

4 Installing SAP S/4HANA for Financial Products Subledger. . . . . . . . . . . . . . . . . . . . . . . . . . . 36

6 Setting Up a Financial Products Subledger Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

7 Configuring SAP S/4HANA for Financial Products Subledger. . . . . . . . . . . . . . . . . . . . . . . . . 49

8 Operating SAP S/4HANA for Financial Products Subledger. . . . . . . . . . . . . . . . . . . . . . . . . . . 51

9 UI Technology Information for SAP S/4HANA for Financial Products Subledger. . . . . . . . . . . 58

This guide addresses the following target audience:

1.1 Document History

Version Date Description

1.2 Useful Links

Resource Where to Find It

User assistance for SAP S/4HANA for financial products https://help.sap.com/s4fpsl

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

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

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

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

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

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

1.3 Getting Support

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

The overall system landscape can look like this:

Back End and Front End

SAP S/4HANA server • SAP S/4HANA 1809

Comprised Software Component Ver­

Deployment Scenario Instance Release Comment

Hub SAP Front-End Server 7.52 or SAP Fiori Front-End Server

Hub SAP Front-End Server 7.52 or SAP Fiori Front-End Server

SAP Front-End Server 7.54 or

SAP Front-End Server 7.53 or

SAP Front-End Server 7.54 or

SAP Front-End Server 7.55 or

Comprised Software Component Ver­

Hardware and Software Requirements

You can find more information about sizing at https://www.sap.com/about/benchmark/sizing.expert-

2.2 Overview of Required SAP Notes

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

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 FPSL: Access in Register

F_BABR_BAS /BA1/BRSRC Source System FPSL: Basic Authorizations in

ACC_SYSTEM Accounting System  Recommenda­

F_BABR_CLC /BA1/BRCLC Calculator FPSL: Calculator

/BA1/BRSRC Source System

/BA1/LGENT Legal Entity

ACC_SYSTEM Accounting System

F_BABR_UI /BA1/APP Application (in Fiori or FPSL: Frontend (UI, Work

F_BABR_GLC /BA1/LGENT Legal Entity FPSL: General Ledger Con­

F_BABR_ADJ /BA1/LGENT Legal Entity FPSL: Manual Adjustments

ACC_SYSTEM Accounting System

F_BAFC_PCD /BA1/FCPRC Process Step ID for Process FPSL: Process Controller

F_BABR_SCB ACTVT Activity FPSL: Subledger Coding

/BA1/LGENT Legal Entity

F_BABR_FPS /BA1/ACCSC Accounting Scenario FPSL: Forecasting, Planning

/BA1/NBSCN New Business Scenario

F_FPS_TLS /BA1/TOOLS Tools Tool Methods, Utilities

F_BAHW_RES /BA1/F0CH1 Characteristic Value 1 (for Results Data: Authorization

Characteristic Value 7 (for

Results Data Area

F_BAFW_PM /BA1/F0CH1 Characteristic Value 1 (for CVPM Authorization Object

/BA1/F0CH6 Characteristic Value 4 (for

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

Comprised Software Component Ver

Comprised Software Component Ver

ACC_SYSTEM Accounting System  Recommenda

F_BABR_GLC /BA1/LGENT Legal Entity FPSL: General Ledger Con

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

F_BAFF_ET Enhancement Tool for DDIC extensions in source data, re

Data Subject Any information relating to an identified or identifiable natu

Deletion Deletion of personal data so that the data is no longer avail

Personal data Any information relating to an identified or identifiable natu

• Special categories of personal data, such as data reveal

FPS_ASSG_CHG_DRVRS_SRV Contract ID Assignment of contracts to change rea