Migration of BI 3.5 Modeling to BI 7.x

Use Of Scenario : This document will gives us the step by step guide to migrate the 3.5 modeling to new BI 7.x. We have to migrate the all the modeling to BI 7.x because the business content provide the 3.x modeling with transfer rule, update rule, info source and old (3.5) data source.




Description:

Prerequisites for the migration.



Copy the info provider to Z info provider.



Copy the all the transformations Routines code to other documents as safer side. Because after migrate, all the ABAP code are shifted to OOPs code.



Please make sure that data source should migrate at the last.



Please find the Step by Step guide with screen shot.



1. First you have to copy the info provider and make another copy with Z name ( like original name 0FIGL_O02 and make it ZFIGL_O02) Please give the Z name and also put it in the Z info area.

2. Then first we have to migrate the Update rule with Z info source. Please make a separate copy off transformation routine will require later on. Like Interest Calculation Numerator Days 1 (Agreed) KF



PROGRAM for UPDATE_ROUTINE.

*$*$ begin of global - insert your declaration only below this line *-*

* TABLES: ...

* DATA: ...

*$*$ end of global - insert your declaration only before this line *-*FORM compute_data_field

TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring

USING COMM_STRUCTURE LIKE /BIC/CS80FIAR_O03

RECORD_NO LIKE SY-TABIX

RECORD_ALL LIKE SY-TABIX

SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS

CHANGING RESULT LIKE /BI0/V0FIAR_C03T-NETTAKEN

RETURNCODE LIKE SY-SUBRC

ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update

*

*$*$ begin of routine - insert your code only below this line *-*

* fill the internal table "MONITOR", to make monitor entries* result value of the routine

IF COMM_STRUCTURE-FI_DOCSTAT EQ 'C'.

RESULT = COMM_STRUCTURE-CLEAR_DATE - COMM_STRUCTURE-NETDUEDATE.

ELSE.

RESULT = 0.

endif.

* if the returncode is not equal zero, the result will not be updated

RETURNCODE = 0.

* if abort is not equal zero, the update process will be canceled

ABORT = 0.*$*$ end of routine - insert your code only before this line *-*

*

ENDFORM.



Then Right click update rules , additional functions --->Create transformations

Then use Copy info Source 3.x New Info source option to make new copy of the info source

Then give the Z name for that info source which will help you to make new copy of the info source.



3. Then Map and Activated ( Most of the fields are mapped automatically ) .Then Right click transfer rules, additional functions --> Create transformations Please assigned newly created info source with Use available infosource Option. Then map and activate.



4. Then Right click datasource, click migrate ,click with export. Please select only With export.



5.Now Migration part is completed and look at Routine code tat was provided.



Some Tips:

Do not use:

DATA:BEGIN OF itab OCCURS n,

fields...,

END OF itab.



REPLACED by

TYPES:BEGIN OF line_type,

fields...,

END OF line_type.

DATA itab TYPE TABLE OF line_type INITIAL SIZE n.



Internal tables with header lines are not allowed. Header line in an internal table is a default line that the system uses when looping through the internal table



Short forms of internal table line operations are not allowed. For example, you cannot use the syntax INSERT TABLE itab. However, you can use INSERT wa INTO TABLE itab



Transformations do not permit READ itab statement in which the system reads values from header lines.

For example, the code READ TABLE itab. is now outdated, but you could use the code READ TABLE itab WITH KEY . . . INTO wa.



Calling external subroutines using the syntax PERFORM FORM(PROG) is not allowed.

In this example, FORM is a subroutine in the program PROG.