Hierarchy
⤷ BW-WHM-DST (Application Component) Data Staging
⤷ RSTRAN_R (Package) Transformation Runtime
Basic Data
Data Element | RSROUT_TRFN |
Short Description | Link to Documentation for Routines Editor |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
You use routines to define complex transformation rules for a key figure or characteristic.
Routines are local ABAP classes that consist of a predefined definition area and an implementation area. The TYPES for the input and output parameters and the signature of the method are stored in the definition area. The actual routine is created in the implementation area. ABAP object statements are available in the method. this method is embedded in the transformation program at generation.
The transformation includes the following types of routine:
- Start Routine
- Routine for Key Figures or Characteristics
- End Routine
- Expert Routine: This type of routine is only intended for use in special cases. You can use the expert routine if there are not sufficient functions to perform a transformation. The expert routine should be used as an interim solution until the necessary functions are available in the standard routine. You can use this to program the transformation yourself without using the available rule types. You must implement the message transfer to the monitor yourself.
- Inversion Routine
Procedure
To create a routine, enter the following:
- You can define the global data declarations 'CLASS DATA' between *$*$ begin of global ... and *$*$ end of global ... . These data declarations are available in all routines. Data declarations with 'DATA' can only be accessed in the current package.
This means that you can use intermediate results in other routines, for example, or reuse results when you call a routine again at a later time.Note:
With serial loads, data declared as 'CLASS DATA' is retained as long as the process instance reserved exclusively for this request also remains. With parallel loads, processes that have been instantiated are also reused for performance reasons. The 'CLASS-DATA' data for a process instance is retained.
For this reason, use 'CLASS DATA' or 'DATA' for the global data, depending on the scenario.
- Enter your program code for the routine between
*$*$ begin of routine ...
and*$*$ end of routine ...
. Check the syntax of your routine.Do not use a SAP COMMIT (ABAP statement: COMMIT WORK) in your coding. When this statement is executed, the cursor that is used from the source for reading is lost. Use a DB COMMIT (call function module DB_COMMIT) instea,d or avoid using such COMMITs altogether.
- Check the syntax of your routine.
- Save the routine.
You end the maintenance session for the routine by leaving the editor.
Use
Dependencies
Data is updated in serial or parallel mode in accordance with the batch manager settings.
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 700 |