Business Partner Code Conversion (Phase II) 

Purpose

In order to provide centralized business partner management across all applications, SAP is introducing the SAP Business Partner. This involves replacing the Treasury Business Partner with the SAP Business Partner. Individual application components are spread across a heterogeneous system infrastructure, and are linked to the Treasury Business Partner at different levels of complexity. It is therefore not possible to convert all applications to the SAP Business Partner at the same time, or for the same Release. The Treasury Business Partner is therefore converted to the SAP Business Partner in two phases.

These guidelines provide information on the procedures involved in phase II of the conversion from the Treasury Business Partner to the SAP Business Partner. They describe both the conversion process for the references from the Treasury Business Partner to the SAP Business Partner, and also the “temporary” tables that are required for the conversion, together with their tasks and attributes.

Prerequisites

Read the detailed Implementation Considerations under Business Partner Conversion. They contain important information on the conditions under which you should carry out the business partner code conversion (phase II).

·        You must have carried out the upgrade to Release Banking 4.63/CFM 2.0 or higher

·        You must have successfully carried out the phase I conversion of the Treasury Business Partner to the SAP Business Partner

·        You must have processed all open releases prior to beginning the code conversion (and thus completed all open workflow items). In the open releases there are references to the business partner number. These references are not converted.

·        If you want to use Real Estate Management, note that under no circumstances must you carry out the business partner code conversion (phase II) for the real estate tables.

Process Flow

Phase II begins with the upgrade to Release Banking 4.63/CFM 2.0. After the upgrade, you replace all keys that refer to the TR Business Partner with references to the SAP Business Partner. You can carry out this code conversion in two blocks:

...

       1.      Convert the DDIC references for all the fields in the tables and structures that referred to data elements and domains belonging to the Treasury Business Partner to the corresponding data elements and domains for the SAP Business Partner.

SAP provides you with the following report programs:

                            a.      Copy control tables (RFTBUH02_0)

                            b.      Generate list of data elements to be converted from domains (RFTBUH02_1)

                            c.      Copy data elements (RFTBUH05)

                            d.      Swap domains in data elements (RFTBUH03)

                            e.      Reassign data elements (RFTBUH06)

                              f.      Reassign foreign keys (RFTBUH04)

                            g.      Determine BP fields to be converted in tables (RFTBUH02_2)

                            h.      Analyze usage of BP fields to be converted in objects (RFTBUH02_3)

                              i.      Conversion report for table BP000 (RFTBUP10_BP000)

                              j.      Generate coding for conversion (RFTBUP09)

       2.      You have to convert the field values in tables that previously referenced the Treasury Business Partner to the corresponding field values for the SAP Business Partner.

SAP provides the following reports to assist you with the conversion:

                            a.       General code conversion (RFTBUP11)

                            b.      Conversion reports for individual tables (RFTBUP10_tabname)

The IMG activities for the conversion are in Customizing under Corporate Finance Management -> Basic Functions -> SAP Business Partner for Financial Services -> Settings for Conversion and Parallel Maintenance of TR BP and SAP BP -> Conversion: Phase II.

What special points do I need to note in connection with the code conversion?

·         You have to carry out the code conversion for each system and each client. You can only carry out the code conversion for one client after another, and not for several clients in parallel.

·         When you run the report programs RFTBUH05, RFTBUH03, RFTBUH06 and RFTBUH04, the system calls for correction orders. You must release the orders before you can activate the converted tables (mass activation report RADMASG0) after you have run the reports.

The mass activation report RADMASG0 is a program that activates a list of objects from the ABAP Dictionary. You can use the program to activate objects after imports have taken place, when all the objects in a transport request are activated. After the objects have been successfully converted in the development system, they also need to be transferred to the consolidation system and the productive system. You must release and transport the orders in the sequence in which they were generated. This task supports the mass activation program by reading the objects from the transport request and activating the inactive versions.

Note that objects from package $TEMP (local objects) are not read/activated by the mass activation program. You have to activate these objects manually.

When do I have to intervene manually in the code conversion?

·         If you are a new customer and have installed Release Banking 4.63/CFM 2.0, you need carry out neither phase I not phase II.

·         If you are upgrading from Release Banking 4.62/CFM 1.0 or lower without customer enhancements, you can use the reports delivered with the system. No additional manual settings are required.

·         If you are upgrading from Release Banking 4.62/CFM1.0 or lower with customer enhancements, you must check the effects of the reports on your enhancements and make any necessary changes. The documentation for the specific reports tells you which changes need to be made.

·         If you are using the Banking or CFM applications, which previously used the Treasury Business Partner, and are now converting to the SAP Business Partner, you also need to run several Risk Analysis conversion reports. This is necessary because the business partner, and/or one of its attributes, is used as a characteristic in risk analysis. Objects specific to risk analysis that are dependent on analysis characteristics and analysis structures for business partner objects, must be adapted accordingly. You will find the necessary steps described in SAP Notes 388237 (business partner conversion (market risk analysis)) and 389644 (business partner code conversion (market risk)).

New installation CFM / CML	No conversion necessary
Release upgrade Identical numbers No customer enhancements	Convert BP000 and VDGPO, amongst other things
Release upgrade No identical numbers No customer enhancements	All referencing tables must be converted
Release upgrade No identical numbers Customer enhancements	All referencing tables must be converted Domain conversion is also carried out beforehand

Result

You have replaced all references to Treasury Business Partners with references to SAP Business Partners. After the conversion (phase II), the Treasury Business Partner is not used by any Financial Services application (Loans Management (CML) and Corporate Finance Management (CFM)). Except for Real Estate Management (RE), all applications use only the SAP Business Partner. The conversion from the Treasury Business Partner to the SAP Business Partner is complete.