Vous êtes sur la page 1sur 17

Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

15 Financials - Treasury and Risk Management


15.1 S4TWL - Drilldown Reporting in Treasury and Risk Management

Application Components: FIN-FSCM-TRM

Related Notes:

Note Type Note Number Note Description


Business Impact 2270522 S4TWL - Drilldown Reporting in Treasury
and Risk Management

Symptom

You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA transition worklist item is applicable in this case.

Solution

Description

Currently there is no pre-upgrade check available to check if this simplification item is a


valid restriction for your system conversion.

The drilldown reporting has been disabled for Treasury and Risk Management. You can't
use your reports defined with the drilldown reporting.

For reporting purposes, you can use the following logical databases available for the
Treasury and Risk Management:

FTI_TR_CASH_FLOWS Treasury Payment Information


FTI_TR_CASH_FLOWS_2 Treasury Payment Info + addtnl position attrs
FTI_TR_POSITIONS_2 Treasury : Positions Eval + addtnl position attrs
FTI_TR_THX_HEDGE Treasury P-Hedge Accounting Reporting
FTI_TR_DEALS Treasury Transaction Reporting
FTI_TR_EXP_POS Treasury: Exposure Positions
FTI_TR_HEDGE Treasury E-Hedge Accounting Reporting
FTI_TR_PERIODS Treasury: Period-Based Evaluations
FTI_TR_PERIODS_1 Treasury: Period Analysis Projection
FTI_TR_PERIODS_2 Treasury: Period-Based Eval + addtnl postn attrs

Page | 290
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

FTI_TR_PL_CF Treasury: Revenue and Cash Flow Reporting


FTI_TR_PL_CF_2 Treasury: Revenue and Cash Flow Reporting
FTI_TR_POSITIONS Treasury Positions
FTI_TR_POSITIONS_1 Treasury Positions Projection

Based on these logical databases you can use the SAP Query functionality available in
the area menu of the Treasury and Risk Management under Transaction Manager ->
Infosystem -> Tools -> SAP Query and define your own queries using Maintain Queries
(transaction SQ01), Maintain InfoSets (transaction SQ02) and Maintain User Groups
(transaction SQ03).

In addtion you can use the available reports in the area menu of the Treasury and Risk
Management under Transaction Manager -> Infosystem -> Reports.

Other Terms

S4TC, S/4 Transition

15.2 S4TWL - Master Agreements

Application Components: FIN-FSCM-TRM

Related Notes:

Note Type Note Number Note Description


Business Impact 2270523 S4TWL - Master Agreements

Symptom

You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.

Solution

Description

Master agreements are not available in SAP S4/HANA.

Read the following information in case the pre-upgrade check in your system issues a
message for the check ID SI11_MASTER_AGREEMENTS "Master Agreements": This
check issues a warning if it finds entries in the database which indicate that master
Page | 291
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

agreements were created in some client of the system. The warning message is for your
information, no futher mandatory action is required.

Read the following information in case the custom code analysis has detected customer
coding related to this transition worklist item: SAP objects which are used by the detected
customer code shall not be used any more. Adapt the customer code accordingly.

Other Terms

S4TC, S/4 Transition

15.3 S4TWL - Offers

Application Components: FIN-FSCM-TRM

Related Notes:

Note Type Note Number Note Description


Business Impact 2270526 S4TWL - Offers

Symptom

You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.

Solution

Description

Offers in transaction management are not available in S4/HANA.

Read the following information in case the pre-upgrade check in your system issues a
message for the check ID SI12_OFFERS "Offers": This check issues a warning if it finds
entries in the database which indicate that offers were created in some client of the
system. The warning message is for your information, no futher mandatory action is
required.

Read the following information in case the custom code analysis has detected customer
coding related to this transition worklist item: SAP objects which are used by the detected
customer code shall not be used any more. Adapt the customer code accordingly.

Other Terms

Page | 292
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

S4TC, S/4 Transition

15.4 S4TWL - Simulation in Transaction Management

Application Components: FIN-FSCM-TRM

Related Notes:

Note Type Note Number Note Description


Business Impact 2270527 S4TWL - Simulation in Transaction
Management

Symptom

You are planning a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.

Solution

Description

Simulations in transaction management are not available in S/4HANA.

Read the following information in case the pre-upgrade check in your system issues a
message for the check ID SI13_SIMULATION "Simulation in Transaction Manager":
This check issues a warning if it finds entries in the database which indicate that
simulations were created in some clients of the system. The warning message is for your
information, no futher mandatory action is required.

Read the following information in case the custom code analysis has detected customer
coding related to this transition worklist item: SAP objects which are used by the detected
customer code shall not be used any more. Adapt the customer code accordingly.

Other Terms

S4TC, S/4 Transition

15.5 S4TWL - Quantity Ledger Always Active for Money Market


Transactions

Application Components: FIN-FSCM-TRM

Related Notes:

Page | 293
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

Note Type Note Number Note Description


Business Impact 2270529 S4TWL - Quantity Ledger Always Active
for Money Market Transactions

Symptom

You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.

Solution

Description

The quantity ledger is now always used for OTC transactions.

Business Process Related Information

The quantity ledger is a technical prerequisite for the function valuation class transfer.

Required and Recommended Action(s)

Before you make the conversion to SAP S/4HANA, you should set the quantity ledger
active for OTC transactions in your ERP system.

In the Customizing of the Treasury and Risk Management under Transaction Manager -
> General Settings -> Tools -> Conversion -> Conversion Customizing -> Set Migration
Type and Assign to Customizing Request choose the migration type Conversion from >=
Enterprise 2.0 and <= ERP 6.0. Assign your transport request and enter the names of
your logical systems of your production system, test system, and customizing system.

Under Transaction Manager -> General Settings -> Tools -> Conversion Program
(transaction TPM_MIGRATION) you now execute first the step H02 OTC: Adjust
Valuation Class in Bus. Transactions (Optional) and then the step H03 OTC: Generate
Quantity Positions (Optional).

Upgrade Pre-Check

The pre-check for the SAP S/4 HANA transition of the quantity ledger functionality
raises an error with check-id SI14_TRQ (message ‘Conversion required: Client …,
Company Code … . See SAP note 2270529.’) if it finds company codes in at least one
client, with the exception of clients 000 and 066, which require generation of quantity
positions. Generation of quantity positions is required if an entry exists in table
TRGT_MIG_CC_PT providing a defined conversion status which is incomplete. If there

Page | 294
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

is no entry in table TRGT_MIG_CC_PT or the check finds otherwise an undefined


conversion status, it further checks table TRQT_BUSTRANS where for each business
transaction a corresponding entry has to exist. If there are no entries in
TRQT_BUSTRANS for at least one business transaction, the pre-check raises the same
error.

For SAP Enhancement Packages < 3 for SAP ERP 6.0 (EA-FINSERV 600), the pre-
check raises a skippable message with check id SI14_ACCR (message ‘Conversion
required. See SAP note 2270529.’). This message does not show an insistency and can be
skipped during the SUM upgrade. Note that you have to do the conversion after finishing
the upgrade.

Other Terms

S4TC, S/4 Transition

15.6 S4TWL - Several Kinds of Financial Objects Disabled

Application Components: FIN-FSCM-TRM

Related Notes:

Note Type Note Number Note Description


Business Impact 2270530 S4TWL - Several Kinds of Financial
Objects Disabled

Symptom

You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA transition worklist item is applicable in this case.

Solution

Description

SEM Banking is not part of SAP S/4HANA edition. So the creation of the following
outdated kinds of financial objects of SEM Banking has been disabled in function
Process Financial Objects (transaction JBDO) of the Risk Analyzers of the Treasury and
Risk Management:

• Security Order
o Namespace of Financial Object: T2*
o Master Data Maintenance Transaction: JBWPORD

Page | 295
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

o [IMPORTANT] The namespace T2* is shared between the security order


of SEM Banking (maintained via transaction JBWPORD; Radiobutton
"Security Order" in financial object master data transaction JBDO), and
the security transaction of SAP Treasury and Risk Management (financial
transaction created via FTR_CREATE or TS01; Radiobutton
Derivatives/Money Market/Forex/Listed Transaction/Security Transaction
in financial object master data transaction JBDO). The T2*-financial
objects of SAP Treasury and Risk Management are continued to be
supported.

• Positions
o Namespace of Financial Object: B1*
o Master Data Maintenance Transactions: JBB0, JBB1. JBB2
o [IMORTANT] This is to be distinguished from the financial objects for
different kinds of positions in SAP Treasury and Risk Management, like
the securities account class position (namespace of financial object: T9*),
class position in futures account (namespace of financial objects: TA*) or
the lot-based position in futures account (namespace of financial objects:
TF*) which are continued to be supported.

• Variable Transactions (applies for the SAP Banking application component only)
o Namespace of Financial Object: BV*
o Master Data Maintenance Transactions: JBVT*

• Positions of Fictitious/Simulated Transactions


o Namespace of Financial Object: R3*
o Master Data Maintenance Transaction: RTBST

• Facilities in SAP Banking


o Namespace of Financial Object: F2*
o Master Data Maintenance Transactions: KLFZ01, KLFZ02. KLFZ03
o [IMORTANT] This is to be distinguished from the facility instrument in
SAP Treasury and Risk Management (product category 560) which is
continued to be supported in SAP S/4HANA edition. The namespace of
the financial object for facilities of product category 560 is T5*.

• Non-Interest Profit and Loss Items


o Namespace of Financial Object: PL*
o Master Data Maintenance Transaction: JBA_US_MD_NIPL

The other financial objects of group 1 (= SAP Banking) and of group 2 (= Treasury and
Risk Management objects) are still available.

Customer code which makes use of coding objects which are specific to the disabled
financial object types is no longer relevant.

Page | 296
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

Business Process Related Information

The SEM Banking is not part of SAP S/4HANA edition. So these objects are obsolete.

How to Determine Relevancy

Check in the Customizing of your system whether you activated the financial object
integration for these financial objects or not.

Other Terms

S4TC, S/4 Transition

15.7 S4TWL - Allocation of FX Transactions to Financial Documents and


Cash Management

Application Components: FIN-FSCM-TRM

Related Notes:

Note Type Note Number Note Description


Business Impact 2524941 S4TWL - Allocation of FX Transactions to
Financial Documents and Cash Management

Symptom

You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.

Solution

The allocation of FX transactions of SAP Treasury and Risk Management to financial


documents of the classical Financial Accounting or to memo records of the classical Cash
Management as a preparational step for special revaluation programs has been disabled
(see also simplification item S4TWL - General Ledger, business impact note 2270339,
and simplification item S4WTL - Cash Management General, business impact note
2270400).

There is no successing function offered.

In case of transferring FX hedging effects of SAP Treasury and Risk Management to


the new General Ledger using hedge accounting rules contact SAP for further
information of the new functionality.

Page | 297
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

Other Terms

S4TC, S/4 Transition

15.8 S4TWL - Correspondence Functionality

Application Components: FIN-FSCM-TRM-TM

Related Notes:

Note Type Note Number Note Description


Business Impact 2270450 S4TWL - Correspondence Functionality

Symptom

You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.

Solution

Business Value

Starting with SAP enhancement package 4 for SAP ERP 6.0 the Treasury and Risk
Management provides a new correspondence framework for incoming and outgoing
correspondence. Within SAP enhancement package 5 for SAP ERP 6.0 this
correspondence framework was enhanced.

This new correspondence framework offers a higher automation in the correspondence


processing and a higher flexibility. Details can be found in the EKT Material of
Enhancement Package 4 and 5.

Description

In SAP ERP starting with SAP enhancement package 4 for SAP ERP 6.0 you can activate
the correspondence framework via business function FIN_TRM_CORR_FW. With SAP
enhancement package 5 for SAP ERP 6.0 business function FIN_TRM_CORR_FW_2 is
available.

From SAP S/4HANA OP 1511 on the new correspondence framework is the only possible
way to manage incoming and outgoing correspondence. The support of SAPScript ceases
with the new correspondence framework.

Required and Recommended Action(s)

Page | 298
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

Customers have to implement the Correspondence Framework before they go to SAP


S/4HANA OP 1511 or subsequent releases.

If you are not using old correspondence functionality and you do not plan to use the
Correspondence Framework you can upgrade to S/4HANA without any difficulties.

If you are using old correspondence functionality and upgrade to SAP S/4HANA from a
release in which the Correspondence Framework is technically available, you need to
activate the Correspondence Framework and create necessary customizing before
upgrading to SAP S/4HANA. It is possible to migrate customizing from old
correspondence functionality, but this will create many technical customizing entries.
SAP strongly recommends that you do not migrate and instead manually create necessary
customizing (which is an own project and needs time).

If you are using old correspondence functionality and upgrade to SAP S/4HANA from an
older release in which the Correspondence Framework is technically not available, you
first need to upgrade to a release in which the Correspondence Framework is available
and activate the Correspondence Framework including necessary customizing creation
(which is an own project and needs time), before upgrading to SAP S/4HANA.

Pre-Upgrade-Check

The pre-upgrade check for SAP S/4HANA transition issues an error with check ID
SI1_TCOR if business function FIN_TRM_CORR_FW (more
precise: switch FTRMO_SFWS_SC_C02S04_CORR) is not active and at least one
client exists in system in which correspondence was created with old correspondence
functionality within the last year (database table VTBKORES contains an according
entry).
Information: SAP reserved clients 000 and 066 are exempt from the check.

You can stop the error message by activating business function FIN_TRM_CORR_FW.

Other Terms

S4TC S/4 Transition

15.9 S4TWL - Interest Rate and Yield Curve Functionality

Application Components: FIN-FSCM-TRM

Related Notes:

Note Type Note Number Note Description


Business Impact 2270461 S4TWL - Interest Rate and Yield Curve
Functionality

Page | 299
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

Symptom

You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.

Solution

Business Value

With the new yield curve framework customers can benefit from

• More flexibility in the calculation of net present values of financial transactions


• The ability to comply with accounting standards like IFRS13
• The possibility to reduce the number of yield curves for which market data needs
to be stored

Description

The classical yield curve functionality has been replaced by the more flexible yield curve
framework, which enables you to do the following:

• Define reference interest rates with independent payment and compounding


frequencies of less than one year
• Define basis spreads (tenor or currency spreads) and basis spread curves in market
data management
• Add basis spread curves and credit spread curves to yield curves and account for
them in net present value calculations

Refer to note 1873119 for more information on the yield curve framework functionality
and technical availability.

In SAP ERP, the yield curve framework can be activated via business function
FIN_TRM_YCF and a customizing activity. In S/4HANA, on-premise-edition, it is
always active, irrespective of the customizing setting.

Required and Recommended Action(s)

The definition of reference interest rates and yield curves in customizing differs between
the classical yield curve functionality and the yield curve framework. Therefore, the
customizing needs to be adapted when switching to the new yield curve framework.
Report FTBB_YC_MIGRATE is available to partly automate the necessary migration
steps.

Page | 300
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

If you upgrade to S/4HANA from a release in which the yield curve framework is
technically available, SAP recommends that you activate the yield curve framework
before upgrading to S/4HANA.

If you upgrade to S4/HANA directly from an older release, in which the yield curve
framework is not yet available, you have to perform the migration to the yield curve
framework in S4/HANA before you can continue using yield-curve related functionality,
such as the calculation of NPVs with transaction TPM60.

Refer to note 1873119 and its related notes for more information on the yield curve
framework.

The pre-upgrade-check for S4/H transition issues a warning with check ID SI5_YCF if at
least one client exists in the system in which the yield curve framework is not active, or if
the system is on a release level in which the yield curve framework is not yet technically
available. (Clients 000 and 066 are exempt from the check.)

How to Determine Relevancy

Use transaction SFW_BROWSER to check the activation status of object


FIN_TRM_YCF .

If the business function is not activated, the classical interest rate and yield curve
functionality is active.

If the business function is activated, use transaction SPRO to check the status of the
following customizng activity:

Financial Supply Chain Management -> Treasury and Risk Management -> Basic
Functions -> Market Data Management -> Settings for Ref. Interest Rates and Yield
Curves -> Activate Yield Curve Framework

If the Yield Curve Framework is activated in the customizing, the classical interest rate
and yield curve functionality is not technically in use anymore. Otherwise it is still active.

15.10 S4TWL - Accrual/Deferral of Expenses and Revenues

Application Components: FIN-FSCM-TRM

Related Notes:

Note Type Note Number Note Description

Page | 301
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

Business Impact 2270462 S4TWL - Accrual/Deferral of Expenses and


Revenues

Symptom

You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA transition worklist item is applicable in this case.

Solution

Description

As of SAP Enhancement Package 3 for ERP 6.0 (EA-FINSERV 603), Business Function
TRM: Hedge Accounting, New Financial Products, New Key Figures a central function
for Accrual/Deferral of Expenses and Revenues (transaction TPM44, reversal transaction
TPM45) for all financial transactions is available.

The accrual/deferral functions for OTC transactions (transactions TBB4 and TBB5) have
been replaced by this new functionality.

In SAP S/4HANA only this central function is available.

Required and Recommended Action(s)

If you are upgrading from SAP Enhancement Packages >= 3 for SAP ERP 6.0 (EA-
FINSERV 603 ff.), and you are still using the old functionality, you have to switch to the
new functionality before you make the conversion to SAP S/4 HANA edition.

If you are upgrading from SAP Enhancement Package < 3 for SAP ERP 6.0 (EA-
FINSERV 600) to S/4HANA and you are still using the old functionality for the
accrual/deferral of expenses and revenues for OTC transactions, you may continue the
conversion to S/4HANA, because the needed migration tool is not available on this
release. However, you have to switch to the new functionality after finishing the upgrade
to SAP S/4HANA edition.

Conversion to the new Functionality

In the Customizing of the Treasury and Risk Management under Transaction Manager -
> General Settings -> Tools -> Conversion -> Conversion Customizing -> Set Migration
Type and Assign to Customizing Request choose the migration type Conversion from >=
Enterprise 2.0 and <= ERP 6.0. Assign your transport request and enter the names of
your logical systems of your production system, test system, and customizing system.

Page | 302
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

In your Customizing system in the Customizing of the Treasury and Risk Management
under Transaction Manager -> General Settings -> Tools -> Conversion Program
(transaction TPM_MIGRATION) you now execute the report G01 OTC: Convert
Customizing for Accrual/Deferral.

When the new Customizing is available in the productive system you now execute the
step H01 OTC: Convert Accruals/Deferrals available in the Customizing of the Treasury
and Risk Management under Transaction Manager -> General Settings -> Tools ->
Conversion Program (transaction TPM_MIGRATION).

Upgrade Pre-Check

The pre-check for the SAP S/4 HANA transition of the Accrual/Deferral functionality
raises an error with check-id SI3_ACCR (message ‘Conversion required: Client …,
Company Code … . See SAP note 2270462.’) if it finds company codes in at least one
client, with the exception of clients 000 and 066, which require conversion. Conversion is
required if an entry exists in table TRGT_MIG_CC_PT providing a defined conversion
status which is incomplete. Undefined conversion status are checked in table
TRDT_TRDBUSTRANS where at least one business transaction for the company code
and one of the versions “Enterprise 2.0 to ERP 2005”, “Enterprise 1.10” or “CFM 1.0 SP
4 to CFM 2.0” has to exist.

For SAP Enhancement Packages < 3 for SAP ERP 6.0 (EA-FINSERV 600), the pre-
check raises a skippable message with check id SI3_ACCR (message ‘Conversion
required. See SAP note 2270462.’). This message does not show an insistency and can be
skipped during the SUM upgrade. Note that you have to do the conversion after finishing
the upgrade.

Other Terms

S4TC, S/4 Transition

15.11 S4TWL - Credit Risk Analyzer Link to Cash Management

Application Components: FIN-FSCM-TRM

Related Notes:

Note Type Note Number Note Description


Business Impact 2270470 S4TWL - Credit Risk Analyzer Link to Cash
Management Disabled in S/4HANA

Symptom

Page | 303
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

You are planning a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.

Solution

Description

The link from classical Cash Management to the Treasury and Risk Management
analyzers (transactions RMCM and KLMAP) has been disabled in S/4 HANA.

Instead with SAP S/4HANA 1709 Bank Account Management is integrated with the
Market Risk Analyzer and the Credit Risk Analyzer of the Treasury and Risk
Management by a new type of financial object for bank account balances.

Required and Recommended Actions

Read the following information in case the pre-upgrade-check in your system issues a
message for the check ID SI5_CM_TO_CRA "Classic cash management link to
analyzers":

The link from classic cash management to the analyzers (transactions RMCM and
KLMAP) is no longer supported in SAP S/4HANA. This check issues a warning if it
finds entries in the corresponding customizing table KLCMMAPPING in any client of
the system. The warning message is for your information, no futher mandatory action is
required. You can stop the warning message from appearing by removing all customizing
entries from table KLCMMAPPING (transaction KLMAP) in all clients of the system.

Read the following information in case the custom code analysis has detected customer
coding related to this transition worklist item:

SAP objects which are used by the detected customer code are deprecated and shall not
be used any more. The customer code will not work any more.

If you want to use the integration of Bank Account Management with Treasury and Risk
Management in SAP S/4HANA 1709, you have to setup the automatic integration of
financial objects for bank accounts.

Other Terms

S4TC, S/4 Transition

15.12 S4TWL - Exposure Management 1.0

Application Components: FIN-FSCM-TRM

Page | 304
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

Related Notes:

Note Type Note Number Note Description


Business Impact 2340804 S4TWL - Exposure Management 1.0 within
Treasury and Risk Management

Symptom

You are planning a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.

Solution

The Exposure Management 1.0 is no longer the target architecture and has been disabled
technically. Exposure Management 2.0 is the more flexible and comprehensive successor
application. There is no standard migration tool from Exposure Management 1.0 to
Exposure Management 2.0 though. You have to set up Exposure Management 2.0 and
transfer the data into the new application just in the same way as if you had used another
software system before and wanted to migrate to the SAP solution.

The basic functionality of the Exposure Management 2.0 is available with the business
functions TRM, Hedge and Exposure Management, New Financial Product
(FIN_TRM_LR_FI_AN_2) deliverd with SAP ERP 6.0 enhancement package 4.

There are several other business functions, for example, TRM, Enhancements in Exposure
Management 2.0 (FIN_TRM_LR_FI_AN_4) delivered with SAP ERP 6.0 enhancement
package 7 . These business functions are always on in SAP S/4HANA.

Customers have to implement the Exposure Management 2.0 before they go to SAP
S/4HANA.

• If you are not using Exposure Management 1.0 and you do not plan to use
Exposure Management 2.0 you can upgrade to SAP S/4HANA without any
difficulties.
• If you are using Exposure Management 1.0 and upgrade to SAP S/4HANA from a
release in which Exposure Management 2.0 is technically available, SAP
recommends that you set up Exposure Management 2.0 and create necessary
customizing before upgrading to SAP S/4HANA. However it is possible to
upgrade to SAP S/4HANA without setting up Exposure Management 2.0, but in
that case you cannot use Exposure Management 2.0 in SAP S/4HANA until
customizing for the Exposure Management 2.0 is available (which is an own
project and needs time).
• If you are using Exposure Management 1.0 and upgrade to SAP S/4HANA from
an older release in which Exposure Management 2.0 is technically not available,

Page | 305
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack

SAP recommends that you first upgrade to a release in which Exposure


Management 2.0 is available and set up the Exposure Management 2.0 including
necessary customizing creation, before upgrading to SAP S/4HANA. However it
is possible to upgrade to SAP S/4HANA without setting up Exposure
Management 2.0, but in that case you cannot use Exposure Management 2.0 in
SAP S/4HANA until customizing for the Exposure Management 2.0 is available
(which is an own project and needs time).

Read the following information in case the Pre-Upgrade-Check in your system issues a
message for the check ID SI6_EXP_MGT_10 "Exposure Management 1.0": This check
issues a warning if it finds entries in the database which means that exposures have been
entered in at least one client in the system. The warning message is for your information,
no futher mandatory action is required.

Read the following information in case the custom code analysis has detected customer
coding related to this transition worklist item: SAP objects which are used by the detected
customer code are deprecated and shall not be used any more. The customer code will not
work any more.

Other Terms

S4TC, S/4 Transition

15.13 S4TWL - Drawable Bonds

Application Components: FIN-FSCM-TRM

Related Notes:

Note Type Note Number Note Description


Business Impact 2270521 S4TWL - Drawable Bonds

Symptom

You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA transition worklist item is applicable in this case.

Solution

Description

Drawable bonds based on product category 041 are not available within SAP S/4HANA,
on-premise edition 1511, and subsequent releases.

Page | 306