Skip to Content

Much of the business content we are activating is built upon the 3.x data flow methodology.  It may be desirable (performance, flexibility, consistency) to upgrade to 7.0 technologies as we implement these solutions for productive usage. 

 

Note the key difference from a logic perspective is that 3.x goes

DataSource -> transfer rules -> InfoSource -> update rules -> InfoProvider.

In 7.0 we could have just DataSource -> transformation -> InfoProvider. 

Because SAP doesn’t know how to automatically combine the separate transfer rules and update rules into a single transformation, an automated “migration” actually results in two separate transformations running through an InfoSource (virtual level). 

 

In some cases, it might therefore be worthwhile to manually implement the transformation using the 3.x rules only as a guideline.  This needs to be evaluated based upon the complexity of the rules in the 3.x transfer and update rules. 

 

I wanted to provide a recommended way to “migrate” from 3.x to 7.0 technologies.

Here is a standard 3.x example.

 
1 

 

 

 

 

 

 

 

 

Don’t do this first — if you migrate the DataSource to 7.0 immediately, the transfer rules will be deleted and won’t be available as a reference!

2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Warning SAP provides:

3

 

 

 

 

 

 

 

 

 

 

1. To migrate the update rules to a transformation, right-click and choose the following option.

4

 

 

 

 

 

 

 

 

2. Click the green check mark to create a “New InfoSource”.

5

 

 

 

 

 

 

 

 

 

 

 

3. Choose an appropriate name.  Replacing just the first number with a Z would work well.

6

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4. The white icon represents our new inactive transformation.

7

 

 

 

 

 

 

 

 

 

5. It contains all of the rules we need, and just needs to be activated.  It is possible that a syntax error would be introduced by the migration, so they are resolved manually.

8 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

6. Now we can migrate the transfer rules as well.

9

 

 

 

 

 

 

 

 

7. Now that the InfoSource has been built, we can use it in migrating the transfer rules to a transformation.

10

 

 

 

 

 

 

 

 

 

 

 

8. Note that even after this step is successfully completed, the DataSource -> InfoSource is not visible.  This is because the DataSource is still in 3.x format.

 
11

 

 

 

 

 

 

 

 

9. Now we can finally migrate the DataSource to 7.0

12

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

10. I would recommend the With Export option, which allows us to recover the 3.x DataSource, transfer rules, and update rules if necessary.

13

 

 

 

 

 

 

 

 

 

 

11. Now the transformation from DataSource -> InfoSource is available.  Again this needs to be activated to be usable.  Also note the 3.x update rules are still available.  I would recommend deleting these rules eventually.

14

 

 

 

 

 

 

 

 

 

12. Existing InfoPackages can continue to be used, but have been automatically converted to load only to PSA.

15

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

13. A DTP needs to be created manually to load data from PSA to InfoProvider.

16

 

 

 

 

 

 

 

 

 

 

 

14. All of the fields will be automatically populated correctly, so the DTP only needs to be activated and run.

17

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Some tips on Routines

 

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

 

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.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply