banking services from sap 9.0 (fsappl500) · banking services from sap 9.0 - release strategy ......

Component Upgrade Guide

banking services from SAP

®

9.0

(FSAPPL500)

Target Audience

System administrators

Technology consultants

Document version: 2 (November 18, 2016)

CUSTOMER

Component Upgrade Guide banking services from SAP 9.0 (FSAPPL500)

2

History of Changes The following table provides an overview of the most important changes that were made in the latest versions of this guide:

Version Date Description

1 December 4, 2015 Initial version

2 November 18, 2016 Updated chapter: Troubleshooting

Make sure that you have the latest version of this document before you start the implementation. You can find the latest version on SAP Help Portal at http://help.sap.com/bankingservices → Installation and Upgrade.

http://help.sap.com/bankingservices


3

Contents HISTORY OF CHANGES ....................................................................................................2

1. INTRODUCTION ....................................................................................................... 4

1.1. ABOUT THIS DOCUMENT ........................................................................................4 1.2. USING THE ASU CONTENT .....................................................................................5 1.3. IMPORTANT SAP NOTES AND DOCUMENTS ............................................................6

2. UPGRADE TO BANKING SERVICES FROM SAP 9.0 – STEP-BY-STEP .................... 8

2.1. INFORMATION INDEPENDENT OF START RELEASE .................................................8 2.1.1. UPGRADE FOR BANK ANALYZER ........................................................................... 8 2.2. XPRAS EXECUTED DURING UPGRADE ...................................................................9 2.3. UPGRADE FROM ACCOUNTING FOR FINANCIAL INSTRUMENTS (BASED ON SAP

HANA®) AS PART OF BANKING SERVICES FROM SAP 8.0 (FSAPPL450) ...........................10 2.4. UPGRADE FROM BANKING SERVICES FROM SAP 8.0 (FSAPPL400) ........................10 2.5. UPGRADE FROM BANKING SERVICES FROM SAP 7.0 (FSAPPL300) ........................10 2.6. UPGRADE FROM BANKING SERVICES FROM SAP 6.0 (FSAPPL200) ........................11 2.7. UPGRADE FROM SAP BANKING SERVICES 5.0 (FSAPPL100) .................................12 2.8. UPGRADE FROM SAP BANK ANALYZER 5.0 ............................................................13 2.9. UPGRADE FROM SAP BANK ANALYZER 4.2 ............................................................13 2.10. UPGRADE FROM SAP DEPOSITS MANAGEMENT 4.0..............................................13

3. TROUBLESHOOTING ............................................................................................. 19


4

1. Introduction

1.1. About this Document

Purpose

This document focuses on the software component FSAPPL and describes the following upgrade scenarios to bank ing services from SAP 9.0 (FSAPPL500):

Upgrade from Accounting for Financial Instruments (based on SAP HANA®) as part

of bank ing services from SAP 8.0 (software component FSAPPL 450)

Upgrade from bank ing services from SAP 8.0 (software component FSAPPL 400)



Upgrade from SAP Bank ing Services 5.0 (software component FSAPPL 100)

Upgrade from SAP Deposits Management 4.0 (BANK-TRBK 40)

Upgrade from SAP Bank Analyzer 5.0 (BANK-ALYZE 50)

Upgrade from SAP Bank Analyzer 4.2 (BANK-ALYZE 42)

This document provides information about the prerequisites, necessary adjustments, and

solutions to problems in upgrade scenarios.

General information relevant for all upgrade scenarios is provided in this introduction section.

The Component Upgrade Guide no longer contains the description and the list of manual

upgrade tasks for most upgrade scenarios. This information is now stored in the ASU content. General information about the ASU content is provided in the next section.

The sections specific to the upgrade scenarios in the step-by-step section below contain

information about the following:

o Which ASU content file to use (if applicable)

o Additional scenario-specific information about the upgrade you might need

This document does not describe the settings needed to go live with the new functions delivered with bank ing services from SAP 9.0. For this information, see the relevant release information. You can obtain a list of release

information in your application system by choosing Help → Release Information.

Integration

For more information about the upgrade from SAP Capital Yield Tax Management 5.0, SAP Capital Yield Tax Management 6.0, or SAP Capital Yield Tax Management 7.0 to SAP Capital Yield Tax Management for Bank ing 8.0, see the Master Guide for Banking on SAP

Help Portal at http://help.sap.com/bankingservices → Installation and Upgrade.

For more information, see SAP Note 1694729 and the CYT Upgrade Guide under

http://help.sap.com/cytm80 → Upgrade Guide.


http://service.sap.com/sap/support/notes/1694729

http://help.sap.com/cytm80


5

Constraints

This document does not describe the technical upgrade.

For more information about making a technical add-on upgrade of the underlying software components, see SAP NetWeaver Guides on SAP Service Marketplace at http://service.sap.com/instguides → SAP NetWeaver → SAP NetWeaver 7.5

and SAP Note 2178306.

1.2. Using the ASU Content You use the ASU toolbox to manage manual pre- and post-upgrade tasks and to execute automated tasks that are not implemented as XPRAs. ASU is the abbreviation for application specific upgrade.

For most upgrade scenarios to bank ing services from SAP 9.0, the manual pre- and post- upgrade tasks that are required during the upgrade are documented and managed using only the ASU toolbox. For more information about the ASU toolbox, see SAP Note 1000009.

Please also install SAP Note 2118652 for the ASU toolbox.

If the upgrade scenario is supported and ASU steps are necessary, we provide ASU content files, which you must download and import into your system before you start the upgrade.

The ASU content files are available in SAP Notes 1786042, 1765305 and 1556353. If a specific software component does not require any ASU steps, no ASU content is delivered and this is stated in the available SAP Notes for the ASU content just mentioned.

Make sure the user who is executing the ASU steps is authorized to import the XML files and execute the ASU transactions. The relevant role for such activities delivered by SAP is SAP_CA_ASU_ADMINISTRATOR. In addition, further authorizations may be necessary

depending on the individual ASU step.

The usage of the ASU toolbox follows the standalone use case described in SAP Note 1000009. You need to download the specific ASU content from SAP Notes 1786042,

1765305 and 1556353 depending on your source release of bank ing services from SAP. Then import the respective xml files using transaction /ASU/START.

After you start the ASU toolbox, navigate to the task list that corresponds to the ASU content.

Check whether individual tasks are relevant for your upgrade by reading the task description and accompanying SAP Notes. Execute any relevant manual or automatic upgrade step in the sequence displayed in the task list.

We recommend that you use the latest version of the ASU content.

Take note of whether individual ASU steps are client dependent. If this is

case, then execute the necessary tasks in all your clients (except client 000).

http://service.sap.com/instguides

https://service.sap.com/sap/support/notes/2178306











6

1.3. Important SAP Notes and Documents Make sure that you have the latest version of each SAP Note, which you can find on SAP Service Marketplace at http://service.sap.com/notes.

SAP Note Number

Component Description

2178306 BC-UPG-ADDON

Banking Services From SAP 9.0 - Release strategy

for the ABAP Software Component Versions

2155664 BC-UPG-RDM Central Note - Software Update Manager 1.0 SP15

1000009 SV-SMG-ASU

XX-PROJ-IMS-UPGR

ASU Toolbox 2008

2118652 SV-SMG-ASU ASU toolbox program cannot be executed (/ASU/GENERAL96)

1786042 FS-AM

FS-BA

FS-CMS

FS-MCM

ASU content for target release FSAPPL 500

1765305 FS-BP ASU content for migration of credit standing data for SAP Business Partner

1556353 FS-BP ASU content for migration of additional partner

numbers for SAP Business Partner

1692363 FS-AM

FS-BP

FS-BA

FS-CMS

FS-MCM

bank ing services from SAP 9.0: Deprecation of Services

1956035 FS-AM Application-specific information about Support Packages for bank ing services from SAP 9.0

(FSAPPL500)

2212888 FS-BA-SD-PO

FS-BA-BC-IF

FRDP: View access to the SDL master data framework (financial transactions, financial instruments, ...)

2098653 FS-BP BP_VER: Introduction new database design for BP

versioning in Bank Analyzer

The following documents contain additional information about upgrading SAP solutions:

Document Location

Upgrade Master Guide - SAP NetWeaver

7.5 SAP Service Marketplace at http://service.sap.com/instguides

http://service.sap.com/notes












http://service.sap.com/instguides


7

→ SAP NetWeaver → SAP NetWeaver 7.5

Master Guide SAP for Bank ing SAP Help Portal at http://help.sap.com/bankingservices

→ Installation and Upgrade



8

2. Upgrade to banking services from SAP 9.0 – Step-by-Step

The upgrade requires Software Update Manager 1.0 SP15 or higher. For more information, see SAP Note 2155664.

In addition to all technical upgrade steps, the upgrade also consists of phases in which application-specific steps may be processed. These phases are the preparation phase, the phase where XPRAs are executed, and the postprocessing phase. Application-specific

upgrade steps that need to be executed during the preparation phase or the postprocessing phase are collected in the ASU content. The following sections will provide you with information about which ASU content to use, which XPRAs are executed during the upgrade,

and any other additional upgrade-relevant information for each upgrade scenario.

2.1. Information Independent of Start Release

When you upgrade to bank ing services from SAP 9.0 (FSAPPL 500), we recommend that you upgrade to the latest available support package for

bank ing services from SAP 9.0. If you do not choose the latest available support package for bank ing services from SAP 9.0, we recommend that you upgrade to at least a support package of bank ing services from SAP 9.0 that

was released at the same date, or later, than the support package of your start release. Note that you may need to re-install any SAP Note that you had installed in

your start release in bank ing services from SAP 9.0 if the support package of bank ing services from SAP 9.0 to which you upgraded does not include this specific correction. Usually, corrections delivered in SAP Notes are delivered across all releases (included in higher releases) with the synchronized set of

support packages released at the same date across all releases.

2.1.1. Upgrade for Bank Analyzer

Note that some of the mentioned SAP Notes were written for releases prior to bank ing services from SAP 9.0. They serve as a starting point for your upgrade activities.

We recommend that you read the release notes for Bank Analyzer within bank ing services from SAP 9.0 on SAP Help Portal at

http://help.sap.com/bankingservices.

Bank Analyzer installations can differ substantially depending on the components installed.

They can also differ depending on whether you use accounting for financial instruments and,




9

if so, whether you use a merge or subledger scenario. The ASU content contains a number of tasks that are only relevant if you have the appropriate system configuration. For more

information, see the short and long texts of the ASU tasks. While most ASU tasks for Bank Analyzer are defined as obligatory, a task is only obligatory if its description defines it as relevant for your installation. Refer to the short and long text of the task to determine if it is

relevant for your specific installation.

Note that after an upgrade the templates for reports must also be

updated.

If you are using the subledger scenario and upgrade from the start release bank ing services from SAP 7.0 or lower, a new initialization is necessary after the technical upgrade described

in this document. For more information, see SAP Note 1593272.

2.2. XPRAs Executed During Upgrade The following table contains all the application-specific XPRAs that will be started during the

upgrade to bank ing services from SAP 9.0 (FSAPPL500). Each XPRA contains checks to determine whether it really needs to convert or migrate any data based on the current data in the system. For a detailed description of the purpose and the prerequisites of the XPRA, see

the documentation provided for the XPRA. The documentation can be accessed with the XPRA name in transaction SE38 (choose Goto -> Documentation -> Display).

The table also specifies the release with which the XPRA was first delivered. If you upgrade

from a start release greater or equal to the release in which the XPRA was delivered, you can expect that the XPRA is executed faster and without any data transfer as the data in your system is already in the desired final state.

There may be additional XPRAs delivered with the underlying release of SAP NetWeaver that are not listed here.

XPRA Released Short Description

/BA1/RAL_B0_AL_XPRA01 FSAPPL200 XPRA for the accounting

scenario. Fill the Scenario field in table /BA1/TAL_B0_CATT.

/BA1/RAL_B0_XPRA_ACCSYSTEM FSAPPL200 This XPRA report copies

entries from the old value tables in the accounting

system into new value tables for all clients in which Bank Analyzer has been activated.

/BA1/RB0_PERIOD_XPRA FSAPPL200 The XPRA fills the new table /BA1/B0_PERIOD with the

open periods from the tables ACCCSSTPPER and ACCLEGENT0C.

/BA1/RB0_XPRA_ACC_SYS_ATTR FSAPPL200 Creates entries in the

Customizing table /BA1/TB0_AS_ATTR.

/BA1/RIA_XPRA_AS2RDA FSAPPL300 Creates new Customizing entries in the tables

/BA1/TIA_RDA and /BA1/TIA_AET_EXC.



10

/FSFAC/UTIL_CONVERT_XPRA FSAPPL300 Migration of utilization data for participant accounts of master contracts with Facilities feature

to new database tables.

BABP_XPRA_CUSTOMIZING FSAPPL200 Data conversion of Customizing in analytical business partner.

RBCA_SEPA_TRANSFER_STATUS_XPRA FSAPPL500 Data conversion for locks on

SEPA mandates.

RBCA_XPRA_COND_CUSTOMIZING FSAPPL100 Conversion of Customizing entries for condition type Customizing in table

TBCA_CONDTYPE.

2.3. Upgrade from Accounting for Financial Instruments (based on SAP HANA®) as part of banking services from SAP 8.0 (FSAPPL450)

Download and install ASU content file UPG_FSAPPL500_FROM_FSAPPL450.xml. See SAP Note 1786042 containing the ASU content for bank ing services from SAP 9.0 (FSAPPL500).

2.4. Upgrade from banking services from SAP 8.0 (FSAPPL400)




Important Additional Notes Specific to this Upgrade Scenario

SAP Note Number


1556023 FS-AM

FS-BP

FS-BA

FS-CMS







11

FS-MCM

1510223 FS-AM

FS-MCM

FSAPPL400: Changes to existing interfaces



In the accounting scenario, an upgrade can generate follow-up activities. You may need to

change the Customizing settings for the Results Data Layer (RDL). For more information, see SAP Note 1281465.


SAP Note Number


1281465 FS-BA-PM-EIC Uniqueness of Results Data Area for required internal costs

1556023 FS-AM

FS-BP

FS-BA

FS-CMS

FS-MCM

bank ing services from SAP 8.0: Deprecation of

Services

1339110 FS-AM

FS-BP

FS-BA

FS-CMS

FS-MCM


1510223 FS-AM

FS-MCM


1320350 FS-AM

FS-MCM


Constraints

If your start release system uses the Facilities application from Master Contract Management, check whether both of the following two circumstances are relevant to you before you upgrade to bank ing services

from SAP 9.0:










12

Your master contracts and participant accounts are hosted on different systems.

The system that you want to upgrade hosts participant accounts. In these cases, you must upgrade your system hosting the master contracts

to bank ing services from SAP 9.0 before you upgrade your system hosting the participant accounts.

2.7. Upgrade from SAP Banking Services 5.0 (FSAPPL100)

Download and install ASU content file UPG_FSAPPL500_FROM_FSAPPL100.xml. See SAP

Note 1786042 containing the ASU content for bank ing services from SAP 9.0 (FSAPPL500).


SAP Note

Number


1556023 FS-AM

FS-BP

FS-BA

FS-CMS

FS-MCM


1339110 FS-AM

FS-BP

FS-BA

FS-CMS

FS-MCM


1072286 FS-AM

FS-CMS

FS-MCM

bank ing services from SAP 6.0: Deprecation of

Services

1510223 FS-AM

FS-MCM


1320350 FS-AM

FS-MCM


1094411 FS-AM

FS-MCM


Constraints









13

If your start release system uses the Facilities application from Master Contract Management, check whether both of the following two

circumstances are relevant to you before you upgrade to bank ing services from SAP 9.0:

Your master contracts and participant accounts are hosted on different systems.

The system that you want to upgrade hosts participant accounts.

In these cases, you must upgrade the system that hosts the master contracts to bank ing services from SAP 9.0 before you upgrade the system that hosts the participant accounts.

2.8. Upgrade from SAP Bank Analyzer 5.0 Download and install ASU content file UPG_FSAPPL500_FROM_BANKALYZE50_AN.xml.

See SAP Note 1786042 containing the ASU content for bank ing services from SAP 9.0.

Upgrade information with regard to the underlying SAP NetWeaver release can be found in SAP Note 2178306.

2.9. Upgrade from SAP Bank Analyzer 4.2 Download and install ASU content file UPG_FSAPPL500_FROM_BANKALYZE42 _AN.xml.

See SAP Note 1786042 containing the ASU content for bank ing services from SAP 9.0.

Upgrade information with regard to the underlying SAP NetWeaver release can be found in SAP Note 2178306.

2.10. Upgrade from SAP Deposits Management 4.0 A minimum patch level is required for SAP Deposits Management 4.0 to execute the upgrade

to bank ing services from SAP 9.0. You need Support Package 2. Note that manual steps are necessary during the upgrade process (see below). For more information see also SAP Notes 988766, 980478, and 1019271.

If you want to upgrade from Deposits Management 4.0 to SAP Banking Services 5.0, manual steps are necessary (for more information about this

upgrade, see the Master Guide for SAP Bank ing Services 5.0). The upgrade to bank ing services from SAP 9.0 requires the same upgrade steps.

For more information about the upgrade from SAP Account Management 4.0 to bank ing services from SAP 9.0, see the additional information for the upgrade from SAP Deposits Management 4.0 given in SAP Note 962336.










14


SAP Note Number


962336 FS-AM Addendum Upgrade Guide SAP Banking Services

988766 FS-AM-EP-ST Extension of the APYE field to allow values larger

than 99,999

980478 FS-AM Missing table entries in TB_FSP_TBL_LST

1019271 FS-AM Upgrade SAP Banking Services 5.0: Corrections

1510223 FS-AM

FS-MCM


1320350 FS-AM

FS-MCM


1094411 FS-AM

FS-MCM


988669 FS-AM

FS-MCM

FSAPPL100: Changes to BAPI and BTE interfaces

Preparation of the Upgrade

If the following tasks are required, you must complete them to execute the upgrade efficiently:

Change pointers If you are using the functions of SAP NetWeaver Business Intelligence (BI) (now known as SAP NetWeaver Business Warehouse (BW)), complete the

following steps:

Extract data to your SAP NetWeaver BW system before the upgrade.

In Customizing for Account Management (FS-AM), reduce the latency time for the change pointer under Tools → Change Service → Define Participants in Change Notification Service.

Delete any obsolete change pointers by running the report CNS_CP_DELETE. You can start the report from the SAP Easy Access screen under Account

Management →Tools → Change Pointer Service → Delete Change Pointer.

New secondary index for database table

BCA_INFOITEM

The BCA_INFOITEM table has a new secondary index for SAP Bank ing Services 5.0. The table and its entries are

converted during the upgrade.

Due to the number of table entries in the table BCA_INFOITEM, this conversion may affect the runtime

of the upgrade.

Alternatively, you can execute the conversion before the upgrade. If you want to do this, contact SAP so that we

can supply the relevant conversion report using an SAP Note.










15

Upgrade Process

Execute your upgrade as described in SAP Note 1554729.

Follow-Up Activities

After you have upgraded from SAP Deposits Management 4.0 to bank ing services from SAP 9.0, you must implement the following notes:

Potential directory traversals in

applications

If you have not installed SAP_BASIS 711 Support Package 7 (SAPKB71107) in the upgraded system, it is

mandatory to implement security note 1497003. This security note is the basis for developments made in transactional banking for FSAPPL400 to avoid potential

directory traversals in some programs.

If you do not implement this note or the respective support package, the execution of some programs in the area of

Card Management may lead to runtime errors.

To upgrade from SAP Deposits Management 4.0 to bank ing services from SAP 9.0, you must run the following conversion reports:

Condition types for interest

As of SAP Bank ing Services 5.0, you can calculate interest for aggregated balances or period balances.

In prior releases, you can only calculate interest for aggregated balances, regardless of the Customizing settings for the underlying condition types.

If you want to continue calculating interest for aggregated balances after the upgrade, adjust the condition types. In Customizing for Account Management (FS-AM), choose

Product Management → Financial Conditions → Define Condition Type to define condition types. To have the system behave the same way that it did

before the upgrade, set the Balance Basis to the value Aggregated Balance for each interest condition type that has the Period Balance value.

Enhancement of

existing account contracts by BAC ID

The BAC ID is the unique external ID for an account used

in service-oriented architecture (SOA) services provided in the releases SAP Bank ing Services 5.0 to bank ing services from SAP 9.0.

To add the new BAC ID to existing account contracts, run report RBCA_FSP_UPG_BAC_ID_PP.

Only start this activity if you want to use services for

account contracts for communication processes or if you

want to use accounts as participants of master contracts.

For more information, see SAP Note 1088812 and release note FSP_10_AM_BAC_ID1.

Enhancement of

account proxy by BAC ID

The BAC ID is the unique external ID of an account used

in service-oriented architecture (SOA) services provided in the releases SAP Bank ing Services 5.0 to bank ing services from SAP 9.0.





16

The BAC ID of accounts that are part of a master contract for the applications Facility, Combined Settlement, and Effective Cash Pooling must be stored in the account

proxy. This is to enable communication processes between master contract and participating accounts using SOA services.

Report RBCA_AC_PROXY_ENHANCE_EXT_IDS adds the BAC ID of the accounts to the account proxy entries.

Run report RBCA_FS_UPG_BAC_ID_PP before you

run this report.

Transfer maximum size for ordering file for

cards

This report enables you to transfer the value of the Maximum Size for Ordering File field

(BP_BCA_DTE_CARD_MAX_FILE_SIZE) to a business partner whose role is that of processor (BCA050) from the business partner into the new Customizing table

TBCA_MAXFILESIZE.

After you have upgraded from SAP Account Management 4.0 to bank ing services from SAP 9.0, you must modify Customizing as follows:

Customizing of the

change notification service (CNS)

If you use SAP NetWeaver Business Warehouse (BW),

check the contents of the Customizing table TCNS_SET_EXPOBJ (settings for the export object type, maintenance view V_TCNS_SET_EXPOB) in all clients.

This table must contain all entries for each export object type of the FS-AM application that are also contained in the object TBCA_CNS_EOBJ_PT Assignment of

Extractor/DataSource to Export object Type and Product Category (maintenance view V_TBCA_CNS_EOBJ).

If entries are missing from the TCNS_SET_EXPOBJ table,

the system may display runtime error message MESSAGE_TYPE_X_TEXT with the text XXX. XXX stands for the export object types missing from the

TCNS_SET_EXPOBJ table.

Enhancement spot for BTEs in the settlement

Use

As of SAP Bank ing Services 5.0, the enhancement spot BCA_SETTL_CALC provides new Business Transaction

Events (BTEs) for settlement. This renders the previous BTEs obsolete. Existing customers are provided with a transition phase. We recommend that new customers do

not use the obsolete BTEs.

Effects on Existing Data

For compatibility reasons, we provide an enhancement

implementation with the corresponding BAdI implementations that call the existing BTEs. You must activate these before use.

Effects on Customizing

To use the BTEs as before, you must activate the


17

enhancement implementation or the individual BAdI implementations:

BTE (old)

BAdI (new)

PR0BCA4400, bonus calculation

AFTER_APPLY_AMOUNT_LIMITS

PR0BCA4500, rounding AFTER_CURRENCY_CONVERSION

PR0BCA4150, credit

commission

AFTER_ROUNDING_R

ESULTS

PR0BCA4450, interest penalty posting

AFTER_ROUNDING_RESULTS

PR0BCA4530, determination periods

CONDITION_DETERMINATION

PR0BCA4510, compress

settlement details

COMPRESS DETAILS

*)

PR0BCA4520, determine calculation bases

GET_TIME_PERIOD *)

PR0BCA4540, determine conditions

PROVIDE_CONDITIONS *)

These BAdIs are not available until Support Package

1, and are available separately. Until Support Package 1 is available, use the methods in the BAdI

INTEREST_CALCULATION.

For more information, see release note RELNFSP_10_AM_EP_SL_BTE.

Synchronization of

attribute hierarchies

Transfer new attributes from the template client 000 to the

attribute hierarchies as follows:

Contract specialization Account, Card, Card Pool

1. In Customizing for Account Management (FS-AM),

choose Product Management → Product Definition → Product Categories → Attributes for Account Products (Card Products/Card Pool Products).

2. Choose Change Hierarchy and then, from the menu, choose Attribute Hierarchy → Client Copy.

Contract specialization Master Contract

1. In Customizing for Master Contract Management (FS-MCM), choose Product Management → Product Definition → Product Categories → Attributes for

Master Contract Products.

2. Choose Change Hierarchy and then, from the menu, choose Attribute Hierarchy → Client Copy.

SAPEVENT:DOCU_LINK/DS:DE.PR0BCA4400









18

Deletion of obsolete product attributes from existing products

The following product attributes are no longer available as of release SAP Bank ing Services 5.0:

Contract

Specialization

Attribute

Description

Attribute

Number

Card Maximum number of participant

accounts

SAP4KBI500000193

Master Contract Combined settlement tracks

SAP4KBI500000141

Master Contract Combined settlement type

SAP4KBI500000140

To remove the above attributes from existing products,

use transaction FIPR_ATTR_DEL and run the report Delete Use of an Attribute.

Addition of new functions to existing

contracts

Make sure that you can use the new and extended functions in existing contracts as follows:

1. Create a new product.

You can make additions by creating a new version of the old product, or you can create a new product that

has all of the required functions.

2. Change the product or the product version.

You can change a product or product version for a

contract, or for multiple contracts in a mass run.

Existing product versions display the new attributes in the

Product Configurator. Note that these attributes are deactivated.

For more information about the activation or deactivation

of attributes using the traffic light and padlock, see the documentation for the product definition (for example, Create Account Product).

No product change functions are available for the master contracts. If you want to upgrade existing master

contracts to use new functions according to the release notes for bank ing services from SAP 9.0, create an SAP OSS ticket for component FS-MCM-MC.


19

3. Troubleshooting Problems and solutions in the upgrade to banking services from SAP 9.0

There have been no known problems in the upgrade to the underlying software component FSAPPL 500 other than those mentioned for the below support package level.

If the target support package level of FSAPPL500 is SP 04 (SAPK-50004INFSAPPL) or higher, but the underlying software component SAP_ABA of SAP Netweaver is lower than support package 06 (SAPK-75006INSAPABA), the import/installation of support package 04

of FSAPPL500 may yield errors (syntax errors) in the mass generation phase for technical class name “CL_CN_FICO_REL_PROC_INDCOND”. These errors can be ignored during the import/installation of the support package and can be resolved as described in section “Error

resolution for upgrade to target support package level 04 of FSAPPL500”.

3.1. Error resolution for upgrade to target support package level 04 of FSAPPL500

In case the import of support package 04 for FSAPPL500 yields syntax errors in class “CL_CN_FICO_REL_PROC_INDCOND” (Type “IF_EX_FICO_REL_PROC_INDCOND” is

unknown), you can apply SAP Note 2285592 (Title: Joint Release Logic) after the import/installation of the support package. After note implementation you can activate class “CL_CN_FICO_REL_PROC_INDCOND”.

Recommendation: If support package 06 (SAPK-75006INSAPABA) of software component SAP_ABA of SAP Netweaver is available, it is recommended to set your target support package level to at least support package 06. Then no errors are expected upon upgrade.

Note: You can restrict the occurrence of such errors to the development system in your system landscape. If you apply the support package/upgrade to a test or productive system, you should include a transport containing the objects of the note implementation for SAP note

2285592 into the transport buffer for the import/upgrade (applied after import/upgrade).

https://service.sap.com/sap/bc/bsp/spn/spat/index.htm?sp1=SAPK-50004INFSAPPL

https://service.sap.com/sap/bc/bsp/spn/spat/index.htm?sp1=SAPK-75006INSAPABA

https://service.sap.com/sap/bc/bsp/spn/spat/index.htm?sp1=SAPK-75006INSAPABA


20

Typographic Conventions

Type Style Description

Example Text Words or characters quoted from the screen. These include field

names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

EXAMPLE TEXT Technical names of system objects. These include report names,

program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database

tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example

text>

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different

types of information at a glance. For more information, see Help on Help General

Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.


21

© 2016 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.

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 http://www.sap.com/corporate-

en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark