Migration of BI Modeling to 3.x to BI 7.x

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 1

Migration of BI Modeling to 3.x to

BI 7.x

Applies to:

SAP BW 7.x. For more information, visit the Business Intelligence homepage.

Summary

The objective of this Article is to explain 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.

Author: Viral Shah

Company: Essar Information Technology Ltd.

Created on: 16 January 2010

Author Bio

The author has been involved in SAP BW Implementation and Support Services and having near about 3 years of experience and part of many SAP implementation project.

Migration of BI Modeling to 3.x to BI 7.x


2010 SAP AG 2

Table of Contents

Information and Instruction ................................................................................................................................. 3

Step By Step Solution ......................................................................................................................................... 3

Some Tips ........................................................................................................................................................... 9

Disclaimer and Liability Notice .......................................................................................................................... 10



2010 SAP AG 3

Information and Instruction

This document will give you 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.

Following are the 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.

Step By Step Solution

This document will give you the step by step guide to migrate the 3.5 modeling to new BI 7.x. We have to 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)



2010 SAP AG 4

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



2010 SAP AG 5

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.



2010 SAP AG 6

3. Then Map and Activated ( Most of the fields are mapped automatically )

4. Then you will get like following screen.



2010 SAP AG 7

5. Then Right click transfer rules, additional functions --> Create transformations

Please assigned newly created info source with Use available infosource Option.

6. Then map and activated.



2010 SAP AG 8

7. Then Right click datasource, click migrate ,click with export.

Please select only With export.

8. Now Your Migration is completed now just look at the Routine code.



2010 SAP AG 9

Some Tips

Dont work. 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_typeINITIAL 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.



2010 SAP AG 10

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

Migration of BI Modeling to 3.x to BI 7.x

Documents

Transcript of Migration of BI Modeling to 3.x to BI 7.x