Transfer routine exists on an InfoObject

[MGrob]

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