PUBLIC

Document version: 4.0 – 2022-08-02

Installation Guide – SAP S/4HANA for Financial Products

Subledger 2107 Business Content
Document History

Caution
Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version at the following location: SAP Note 3066343

The following table provides an overview of the most important document changes.

Table 1

Version Date Description

1.0 2021-07-28 First Version

2.0 2022-01-14 Second Version

3.0 2022-07-11 Third Version, References to Admin Guide corrected

4.0 2022-08-02 Correction Regarding Available Languages, Reviewed Version

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

2 All rights reserved.

Contents
Installation Guide – SAP S4/HANA for Financial Products Subledger 2107 Business Content ............................................ 4

1. Use and Positioning of Business Content ......................................................................................................................... 4

1.1. Positioning and Scope of Business Content ......................................................................................... 4

1.2. Business Content in Implementation Projects ..................................................................................... 4
1.3. Maintenance of Business Content....................................................................................................... 4
2. Installation of Business Content ...................................................................................................................................... 5

2.1. Objectives .......................................................................................................................................... 6

2.2. System Requirements ......................................................................................................................... 6
2.3. Problem Handling ............................................................................................................................... 6
2.4. Activation of Business Content ........................................................................................................... 6
2.5. Update of Business Content................................................................................................................ 9
3. Technical Aspects of Activating Business Content ........................................................................................................... 9

3.1. System Landscape .............................................................................................................................. 9

3.2. Languages ........................................................................................................................................ 10
3.3. Authorization ................................................................................................................................... 11
3.4. Objects in the Business Content Delivery .......................................................................................... 11
Important Disclaimers and Legal Information .................................................................................................................... 17

Coding Samples ..................................................................................................................................................................... 17

Gender-Neutral Language....................................................................................................................................................... 17

Internet Hyperlinks................................................................................................................................................................. 17

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

All rights reserved. 3

Installation Guide – SAP S4/HANA for Financial Products Subledger
2107 Business Content
This document explains the concept, the technical steps, and the installation procedure of the Business Content
for SAP S4/HANA for Financial Products Subledger 2107.

1. Use and Positioning of Business Content

1.1. Positioning and Scope of Business Content
Business Content is a set of Customizing settings that provides a preconfiguration for the business scenario
Financial Products Subledger.
In general, SAP provides end-to-end scenarios. Once Business Content has been successfully activated, the
system contains ‘ready to run’ Customizing for the respective business scenario.

1.2. Business Content in Implementation Projects

Business Content contains generic Customizing for the Financial Products Subledger business scenario. Some
parts of this Customizing are quite generic, while other parts are based on assumptions (for example,
availability of data or the semantics of data).
Therefore, in a customer project, Business Content must be adapted to the relevant needs of the customer.
This means that Business Content is the basis (or starting point) for a customer project on which additional
Customizing settings are made. Because of these changes, a customer’s Customizing and Business Content
will differ. Although the customer’s Customizing is based on Business Content (in other words, “Business
Content” is the Customizing that is shipped by SAP), as soon as it is changed, it is no longer Business Content
but customer-specific Customizing).
This leads to the following restrictions:
SAP will create and ship corrections for any errors in Customizing that has been shipped with Business
Content. However, since these corrections are based on Business Content (and not on the customer’s
Customizing that is itself based on Business Content), you cannot implement the corrections in your
development client, but only in an (unchanged) reference client. See section 1.3 for details.
We recommend that you use project Customizing that closely reflects the delivered Business Content, and
that you update your own implementation in each Support Package. This will simplify the implementation of
any Business Content changes delivered in subsequent Support Packages that you want to implement in your
own Customizing.

1.3. Maintenance of Business Content

Changes to Business Content are necessary if errors are found. These changes are provided in SAP Notes. The
SAP Notes (typically) contain descriptions of the changes, which must be applied manually. These descriptions
are not only relevant for applying the changes to the reference client for Business Content, but they also
provide a clear explanation of why the change is necessary and which steps must be executed. The
description enables you to judge whether a change is necessary in your own implementation if this is
different from Business Content. If you update your system to a new Support Package, we recommend that
you apply the latest Business Content changes in the reference client (see also 3.1 System Landscape).

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

4 All rights reserved.

 You must not apply Business Content changes directly to a client where the Business Content has
already been modified.

Support Package
with Business Project Customizing
Apply Business Content changes
Content Changes Client

Support Package
with Business Apply Business Content changes Reference Client
Content Changes

If you update to a new feature package or if you install multiple Support Packages all at once, we recommend
building a new Business Content reference client. For the update of a single Support Package without new
features, it is sufficient to implement the delta in the existing Business Content reference client (SAP Note
3131068 - SAP S/4HANA for Financial Products Subledger 2107: Revision of BC). In this case, a new Business
Content reference client has no added value.
In Feature Packages new functions require new Business Content and changes to existing Business Content.
Due to the amount of these changes, it is not possible to describe them in detail. In this case we recommend
creating a new Business Content reference client. This enables you to trace back the changes by comparing
the different Business Content reference clients.
It is not possible to install the latest Business Content in a client that already contains Business Content for a
different Feature Package.
If you have further questions about your specific case, create a customer incident on component FS-FPS-BC to
get more information.

2. Installation of Business Content

The step sequence for the installation is defined in an XML file. This file contains all the information needed to
activate Financial Products Subledger Business Content. The client in which you want to install Business
Content must not contain any Customizing or Business Content from a previous delivery for FPSL.
Using the ASU tool reduces the complexity of installation and ensures transparency about the status. The
following features are used:
- List of predefined steps (to ensure the correct execution sequence)

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

All rights reserved. 5

 - Logging of execution time (transparency on which user started which step and when)
- Status definition for each step (the status for each step can be set manually)
- Direct link to existing programs, transactions or Customizing activities
- Direct link to SAP Notes
- Direct link to documents

2.1. Objectives
The aim of the activation process is to activate Business Content in a Financial Products Subledger client.
During this process, several steps must be performed which are described in the following sections.

2.2. System Requirements

Business Content must be activated in an empty Financial Products Subledger client. The system and the
client must be set up as described in the Administration Guide for SAP S/4HANA for financial products
subledger. Chapter 7, Setting Up a Financial Products Subledger Client, of the Administration Guide provides
details about how to set up the client. The ASU task list for Business Content activation in SAP Note 3066343
contains the required installation activities.

2.3. Problem Handling

If problems occur during activation, check the logs for tips on how to solve the problem. Do not proceed with
the activation unless the problems have been solved.
If you cannot solve the problems, you can create a customer incident on component FS-FPS-BC. Note: You
should also refer to SAP Note 67739.

SAP recommends that the installation and activation of Financial Products Subledger Business Content is
performed by a team whose members have the following roles:
 SAP Basis administrator (for questions regarding system setup, authorizations, …)
 Senior SAP Financial Products Subledger consultant (for the activation process and problem handling)
 SAP BI consultant (for SAP BI-related topics)

2.4. Activation of Business Content

BC sets must be activated in a Financial Products Subledger client.
1. Download the relevant attached ZIP file from SAP Note 3066343 and extract it.
It is important to store all the attached documents in the same folder. Otherwise, the ASU task list
will not be complete.
2. Execute transaction: /n/asu/start in your Financial Products Subledger client.
3. Upload the XML file ASU_BC_INST_S4FPSL200_SPxx_Vxx.xml by choosing “Import New ASU Content
Definition”. This task list contains the steps to set up a new Business Content reference client for Financial
Products Subledger.
4. The ASU Import function also uploads the PDF files, which are part of the ZIP file. However, this is only
possible if the ASU XML file and the PDF files are in the same folder and are not moved to another file
path.
5. Expand the column on the left and choose “Create New Task List”.

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

6 All rights reserved.

 Figure 1: ASU Toolbox Start Screen

6. Choose Jump to Task List <XXXX> – the new task list is displayed.
7. Start with the first step under “Manual Preparation Steps”.
This section covers all the steps required to enable Business Content activation in a Financial Products
Subledger client that contains neither Customizing nor Business Content and has been set up as described
in the administration guide.
The section is divided into 2 blocks:
1. Activities before starting BC installation
This block especially contains the check after the setup of the client according to the administration
guide and a consistency check.
It also contains steps for the implementation of new SAP Notes, if needed.
2. Technical Preparation Steps
This block contains all additional activities that are required for the Business Content activation.
(a) Step to upload BC sets
In this step, a local BC Set is loaded with the work list for the ASU program generation.
If BC Sets have been adjusted after the Feature Package assembly, this step is used to load
the latest version of the affected BC Sets to avoid problems during activation of Business
Content.
(b) Step to generate the ASU programs
A program is generated for each ASU toolbox step that executes the activation of a BC Set or
piece list. If the program generation is missing or if it was executed with the wrong work list,
many of the follow-up steps cannot be executed. Then, the following error message is
displayed: Execution not possible - program /1BA/RFZ_BCACT_… does not exist.

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

All rights reserved. 7

 Figure 2: Manual preparation steps in ASU task list for Business Content

8. Once you have successfully finished the manual preparation steps, start with the manual follow-up steps
and execute these steps.
In general, there are 5 kinds of steps:
a) Activation of a BC Set. See section 3.4.1 for more information.
b) Activation of a piece list. See section 3.4.2 for more information.
c) Replication of master data for Profit Center, Cost Center and Organizational Units.
d) Manual steps. Refer to the description or the assigned note for a description of which steps must
be executed.
e) Consistency checks after installation of Business Content.
Read the description for every step. Some descriptions contain specific information about the step.

Figure 3: Manual Follow-Up Steps in ASU Task List for Business Content

9. After a step has been successfully executed, set the status of the step to “Processing checked and is OK”
Each mandatory step of the content activation is based on successful execution of the predecessor
steps. If you ignore error messages in the log after executing a step, the next step cannot run
properly.
10. The installation is successfully completed when the last step has been executed correctly.

To ensure successful activation of Business Content, make sure that you execute all the steps
belonging to your required scenarios.

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

8 All rights reserved.

2.5. Update of Business Content
After the initial installation of Business Content, you can correct errors or enhance the Business Content for
new functions. The corrections are delivered with SAP Notes that describe the necessary changes as manual
activities. Find a reference to these SAP Notes in SAP Note 3131068 - SAP S/4HANA for Financial Products
Subledger 2107: Corrections to BC.
If you update to a new Support Package, we recommend that you install the latest Business Content changes
in the reference client (see also 1.3 Maintenance of Business Content) using SAP Note 3131068 - SAP
S/4HANA for Financial Products Subledger 2107: Corrections to BC.
If the Business Content reference client is marked for automatic recording of changes, create a transport
request for each correction (each SAP Note). If you didn’t change the affected Customizing in your project
implementation, you can use these transport requests to transfer the changes to your project Customizing
client.
We recommend that you use project Customizing that closely reflects the delivered Business Content, and
that you update your own implementation after the implementation of Support Packages. This will simplify
the implementation of any Business Content changes delivered in subsequent Support Packages that you
want to implement in your own Customizing.

3. Technical Aspects of Activating Business Content

3.1. System Landscape
Business Content must be activated in a client that contains neither Customizing nor Business Content of a
previous feature package.
We recommend setting up the Financial Products Subledger system with a separate Business Content
reference client. This reference client serves as the basis for supplying the development client(s) with
Business Content Customizing.
The Customizing of this reference client should be kept untouched, so that it is possible to test whether the
project Customizing causes unexpected behavior in comparison with the Business Content.
There are two options for providing other clients with Business Content:
1. Client Copy (see SAP Note 2710975 )
2. During the activation of Financial Products Subledger Business Content collect the created
Customizing in transport requests. We also strongly recommend that you create an individual
transport request for each activation step. Due to the many dependencies, these transport requests
must be imported in the same order as the steps are activated.

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

All rights reserved. 9

 Tool BW
Client Tool BW Tool BW
Client Client
Reference
Client

Test Client Transport Production

Development Transport
Client
Client

Dev-System Q-System P-System

Figure 4: System Landscape

After importing the Customizing from the reference client into the development client, all changes to the
Customizing must be made exclusively in the development client. The reference client must not be changed
from this point on to ensure that future SAP Notes and SAP Feature Packages can later be installed.

3.2. Languages
Financial Products Subledger is delivered in several languages (but not in all languages possible at SAP). The
Business Content is also available in these languages. If you plan to install it in a language other than German,
you need to keep the following in mind:
 All relevant languages need to be installed for Financial Products Subledger before you start the
activation of Financial Products Subledger Business Content.
 Make sure that all relevant languages are installed in the system and that these languages appear when
activating the BC Sets. You can check this using transaction SCPR20 -> Utilities -> System Settings.

Figure 5: BC Set System Settings - Languages

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

10 All rights reserved.

 Make sure that the user settings do not override the system settings when activating the BC Sets. Check
this using transaction SCPR20 -> Utilities -> User Settings. Flag “Use User Languages” must be switched
off.

3.3. Authorization
To activate BC Sets, you need to log on to the target system. The user needs to have the relevant
authorizations for activating BC Sets and for making changes in the respective Customizing activities. We
recommend the “SAP_ALL” profile.

Using the SAP_ALL profile involves a security risk because a large number of authorizations are granted
with this profile. The profile should be removed from the user as soon as the activation task is completed. The
profile should also only be assigned to selected users.
A user without the SAP_ALL profile needs at least the following:
 All relevant authorizations for making Customizing settings
 All relevant authorizations to copy the piece lists with the derivation strategies to the current client using
transaction SCC1
 Role SAP_BCS_ADMIN for updating BC Sets
 Roles SAP_FPS_CUSTOMIZER and SAP_FPS_EXP_FINANCIAL_ACCTNT for activating the BC Sets in block
Basic Data and Source Data / Results Data

3.4. Objects in the Business Content Delivery

This chapter describes technical details of the objects to be installed as part of Business Content and the
procedures for installing the objects. This chapter gives only a technical description. The sequence and the
steps to be executed are described in the ASU file (see section 2.4).
The following objects are used for the Business Content delivery and are described below:
 BC Sets
 Piece Lists
 BI Content
The following subchapters describe the activation steps required for the different objects.
3.4.1. BC Sets
BC Sets (Business Configuration Sets) are used to move settings for Customizing activities between systems.
By activating the BC Sets, the Customizing settings are transferred to the respective Customizing tables and
additional generation steps can be executed.
Typically, Customizing settings are dependent on other Customizing settings. Therefore, the BC Sets must be
activated in the order specified in the ASU file.

Ensure that you adhere to the sequence defined in the ASU file. SAP does not recommend or support the
activation of Business Content in an arbitrary order. We can only provide support if Business Content has
been activated according to the steps defined in the ASU file.
The activation program for BC Sets is started by executing the respective step in ASU. The ASU tool passes all
the required information on to the program and no manual selection of the BC Set is required. In the
program, you can select whether the activation is performed in expert mode or whether the logs of a
previous activation are shown.

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

All rights reserved. 11

 Figure 6: Activation program for a specific BC Set

During BC Set activation, the relevant table entries for Customizing are generated.

Note the following restrictions when activating BC Sets:

The activation of a BC Set cannot be undone.
Entries with identical keys will be overwritten
Overwritten data cannot be restored.
BC Sets cannot remove entries from Customizing.
As long as you have not continued with the subsequent steps of the ASU list, you may activate
BC Sets again.
During activation of a BC Set, the system creates a log. This contains information about the BC Set, that has
been activated, which objects were involved, and which methods were invoked. A status is available for each
step. Any errors that occur during activation are displayed in the log.

Figure 7: Log of successful BC Set activation

Most warnings that are logged are caused by BC Sets that do not contain data at all levels. These warnings can
be ignored. Not all Customizing tables are filled with content, but the activation tool recognizes this and
issues a warning.

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

12 All rights reserved.

We strongly recommend that you check the log for each BC Set after activation. The figure below shows an
example of a log for a successfully activated BC Set with warnings:

Figure 8: Warning during BC Set activation

Figure 9 shows an example of a log for an activated BC Set with errors. You can find further information about
the error in the long text of the message by clicking the question mark at the end of the line.
In addition to the relevant error messages there are subsequent errors in the log, written by the tools used by
S/4FPSL, for example, the Financials Basis. Examples for this kind of errors are:
FINB_TR012 After-import handling completed for object /BA1/VC_HM()
PU133 Errors occurred during post-handling FINB_TR_AFTER_IMP_METHOD for /BA1/VC_HM C
PU136 The errors affect the following components:
PU137 FIN-FB (Financials Basis)
SCPR259 Activation of customizing object /BA1/VC_HM with errors
Ignore these errors.

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

All rights reserved. 13

 Figure 9: Errors during BC Set activation

The ASU activation program starts the BC Set activation in the background to avoid timeout problems during
activation of large hierarchical BC Sets, and waits until the batch job has finished. Note that if the background
job is aborted or you check the BC Set activation log while the job is running, the system displays only success
messages on the Activation Log tab on the right-hand side of the screen. However, the job log is marked with
the icon “Activation Cancelled” on the left of the screen (see Figure 10). When you display the Activation
Information tab, there is no data under “Activation Options”; (Figure 12). In this case, check the job status
using transaction SM37 and select Active or Canceled Jobs. If the job has been aborted, check the job log.

Figure 10: Log of aborted BC Set activation

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

14 All rights reserved.

 Figure 11: Activation log legend

Figure 12: Incomplete activation

Almost every BC Set activated using the ASU steps is a hierarchical BC Set that contains multiple sub-BC Sets.
However, when errors occur during the BC Set activation, it is not easy to find the root cause because the
same error message occurs several times in the log file of a hierarchical BC Set. In Financial Products
Subledger, we use after-import methods to check or generate objects with regards to the Customizing that
was imported. The BC Set tool is not able to assign the error messages to the BC Set that triggered the error.
The relevant BC Set can only be identified based on the error message text. See also SAP Note 1361903 .
3.4.2. Piece Lists
For certain Customizing activities, Business Content cannot be shipped in BC Sets. Derivation rules are one
example.
You start the activation program for piece lists by executing the relevant step in ASU.
On the start screen of the report, you can choose which activity is executed.

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

All rights reserved. 15

 Figure 13: Piece list activation using ASU report

Figure 14: Confirmation dialog box (activation of piece list)

The logs for the piece list and the BC Set are displayed according to the activities you have chosen. After the
activation of the content, check both logs to see if the activation was successful.
3.4.3. BI objects in Business Content – Common Information
BW objects are used by Financial Products Subledger for several purposes, for example InfoObjects which will
be registered as characteristics. Therefore, Financial Products Subledger Business Content also contains BW
objects that are shipped as BI Business Content for component S4FPSL.
These objects are assigned to InfoArea Business Content for Financial Products Subledger (/BA1C/FPSL_MAIN)
or sub- InfoAreas and activated using transaction RSOR.
The ASU toolbox displays a document for the relevant ASU step, which describes the activities for activating BI
content.

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

16 All rights reserved.

Important Disclaimers and Legal Information

Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and
are not intended to be used in a productive system environment. The Code is only intended to better explain and
visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness
of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code,
unless damages were caused by SAP intentionally or by SAP's gross negligence.

Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed
directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring
to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does
not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the
documentation remains comprehensible.

Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint
about where to find related information. SAP does not warrant the availability and correctness of this related
information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful
misconduct. All links are categorized for transparency (see: https://help.sap.com/viewer/disclaimer).

Documentation for SAP S/4HANA © Copyright 2018 SAP SE or an SAP affiliate company.

All rights reserved. 17

www.sap.com

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

No part of this publication may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP SE or an SAP affiliate company. The
information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary
software components of other software vendors. National product specifications may
vary.

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

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

Please see https://www.sap.com/corporate/en/legal/copyright.html for additional

trademark information and notices.