SAP CONTEXT_DEMAND_BY_NAME Function Module for









CONTEXT_DEMAND_BY_NAME is a standard context demand by name 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 context demand by name FM, simply by entering the name CONTEXT_DEMAND_BY_NAME into the relevant SAP transaction such as SE37 or SE38.

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



Function CONTEXT_DEMAND_BY_NAME 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 'CONTEXT_DEMAND_BY_NAME'"
EXPORTING
FIELD_NAME = "

IMPORTING
FIELD_VALUE = "

CHANGING
CONTEXT = "

TABLES
* MESSAGES = "

EXCEPTIONS
FIELD_NAME_INVALID = 1 FIELD_VALUE_NULL = 2 FIELD_VALUE_ERROR = 3
.



IMPORTING Parameters details for CONTEXT_DEMAND_BY_NAME

FIELD_NAME -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CONTEXT_DEMAND_BY_NAME

FIELD_VALUE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for CONTEXT_DEMAND_BY_NAME

CONTEXT -

Data type:
Optional: No
Call by Reference: Yes

TABLES Parameters details for CONTEXT_DEMAND_BY_NAME

MESSAGES -

Data type: SYMSG
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

FIELD_NAME_INVALID -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

FIELD_VALUE_NULL -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

FIELD_VALUE_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CONTEXT_DEMAND_BY_NAME 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.

DATA:
lv_context  TYPE STRING, "   
lt_messages  TYPE STANDARD TABLE OF SYMSG, "   
lv_field_name  TYPE SYMSG, "   
lv_field_value  TYPE SYMSG, "   
lv_field_name_invalid  TYPE SYMSG, "   
lv_field_value_null  TYPE SYMSG, "   
lv_field_value_error  TYPE SYMSG. "   

  CALL FUNCTION 'CONTEXT_DEMAND_BY_NAME'  "
    EXPORTING
         FIELD_NAME = lv_field_name
    IMPORTING
         FIELD_VALUE = lv_field_value
    CHANGING
         CONTEXT = lv_context
    TABLES
         MESSAGES = lt_messages
    EXCEPTIONS
        FIELD_NAME_INVALID = 1
        FIELD_VALUE_NULL = 2
        FIELD_VALUE_ERROR = 3
. " CONTEXT_DEMAND_BY_NAME




ABAP code using 7.40 inline data declarations to call FM CONTEXT_DEMAND_BY_NAME

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!