SAP RT_VALUE_EXTRACTOR Function Module for

Search SAP Function Modules

RT_VALUE_EXTRACTOR is a standard rt value extractor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for rt value extractor FM, simply by entering the name RT_VALUE_EXTRACTOR into the relevant SAP transaction such as SE37 or SE38.

Function Group: ROUTING_TEST
Program Name: SAPLROUTING_TEST
Main Program: SAPLROUTING_TEST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RT_VALUE_EXTRACTOR pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'RT_VALUE_EXTRACTOR'"
  EXPORTING
*  EXTRTYPE = 'XP' "
*  EXTRVALUE = '/oif1/Felder/feld3' "Extractor
*  EXTRCOBJNS =  "Context Object Namespace
*  EXTRCOBJNAME =  "Context Object Name
*  NAME' 'S =  "Namespace Table
*  PAYLOAD =  "
*  ATTACHMENT =  "Routing Context Table
*  SENDER =  "

 IMPORTING
   VALUES =  "Extractor Message Value Table

EXCEPTIONS
   CX_RD_VALUE_EXTRACTOR = 1    CX_XMS_EXCEPTION = 2    CX_XMS_SYSTEM_ERROR = 3 

.

IMPORTING Parameters details for RT_VALUE_EXTRACTOR

EXTRTYPE -

Data type: RD_EXTRTYPE
Default: 'XP'
Optional: Yes
Call by Reference: Yes

EXTRVALUE - Extractor

Data type: RD_EXTRVALUE
Default: '/oif1/Felder/feld3'
Optional: Yes
Call by Reference: Yes

EXTRCOBJNS - Context Object Namespace

Data type: RD_COBJNS
Optional: Yes
Call by Reference: Yes

EXTRCOBJNAME - Context Object Name

Data type: RD_COBJNAME
Optional: Yes
Call by Reference: Yes

NAMESPACES - Namespace Table

Data type: RDT_NAMESPACE
Optional: Yes
Call by Reference: Yes

PAYLOAD -

Data type: STRING
Optional: Yes
Call by Reference: Yes

ATTACHMENT - Routing Context Table

Data type: RMT_CONTEXT
Optional: Yes
Call by Reference: Yes

SENDER -

Data type: SXI_ADDRESS
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for RT_VALUE_EXTRACTOR

VALUES - Extractor Message Value Table

Data type: RDT_EXTRVALUE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CX_RD_VALUE_EXTRACTOR - Routing Runtime (Value Extraction)

Data type:
Optional: No
Call by Reference: Yes

CX_XMS_EXCEPTION - Exceptions of XMS Messaging APIs

Data type:
Optional: No
Call by Reference: Yes

CX_XMS_SYSTEM_ERROR - XI: System Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RT_VALUE_EXTRACTOR Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM RT_VALUE_EXTRACTOR

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects