Introduction

Each InfoObject can hold a global transfer routine which always gets executed after the transformation or the communication structure. No matter if the updaterule. Using global “transfer routine exists” makes sense if an InfoObjet gets transformed with an ABAP routine always on the same way.

Transfer routine exists

If this indicator is set a transfer routine is defined for the InfoObject.The routine is then integrated in all transfer rules that are containing the InfoObject.

When data is transferred the logic contained in the individual transfer rules at the beginning. The routine is then carried out on the value of the corresponding field for every InfoObject that has a transfer routine. The code you define in the InfoObject you only have to maintain once, but is valid for all transfer rules

Calculating the field in transfer routine only works based on one field in the datasource as only one value can be handled in the routine.

The transfer routine has to be maintained on the InfoObject maintainance in the general tab.

Global transfer routines are great to check syntax or convert strings to upper case. “Transfer routine exists” like other routines is also based on a declaration part, parameter section and the code itself.

Parameters:

RECORD_NO
SOURCE_SYSTEM
RESULT
RETURNCODE
IOBJ_NAME

After calling up the editor of the routine maintenance you get to the framework above.

RECORD_NO

Holds the datarecord number of the record which will be handled in the transferrule.

SOURCE_SYSTEM

Contains the logical name of the source system

RESULT

Contains the current value of the InfoObject which has been assinged in the transfer routine

RETURNCODE

Any value <> 0 will be conisdered an error and causes the cancellation of the datapackages.

IOBJ_NAME

Hold the technical name of the InfoObject

12 Comments

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

karthick Ravichandran October 22, 2013 at 6:59 am

Hi Martin,

Very Useful Document about Transfer routine , Thanks for posting.

Regards

karthick

like (0)
1. Martin Grob Post authorOctober 23, 2013 at 11:10 am
  
  Thanks I think it’s a point often forgotten it’s there and what it actually does 🙂
  
  like (0)
Srinu S November 5, 2013 at 6:54 am

Useful document shared. Thanks Martin for sharing 🙂

like (0)
1. Martin Grob Post authorDecember 6, 2013 at 8:26 am
  
  you’re welcome
  
  like (0)
Ganesh Bothe December 6, 2013 at 8:29 am

Hi martin,

Useful information….thats for sharing 🙂 .

like (0)
Krishna Chaitanya December 6, 2013 at 11:49 am

Another good one from you. Thanks for sharing with all of us.

like (0)
1. Martin Grob Post authorDecember 13, 2013 at 6:32 am
  
  thanks
  
  like (0)
Raghavendra Bellam December 13, 2013 at 6:56 am

Good doc to learn new things. Thanks for sharing martin.

like (0)
Meghana Kuppa June 11, 2014 at 9:53 am

Exactly what I was looking for. Thank you!

like (0)
Naveen Choudhary June 12, 2014 at 7:41 am

Good info..!

like (0)
Isha Gupta June 12, 2017 at 5:42 pm

Hi Martin Grob , nice info but can you pls explain if we need to do any specific setting in transforamtion or just no transforamtion to cal transfer routine

like (0)
Benedict Venmani Felix June 12, 2017 at 7:37 pm

Hi, This blog is from 4yrs ago. You have a better chance of getting a response if you post your query in the BW space as a question. But do search and see if this topic is already discussed.

To answer your question. No specific setting is needed on the transformation side. One a transformation is defined at the infoobject level, it executes by default after all the global routines have run

like (0)