SAP CONTEXT_ID_FROM_PROGRAM_NAME Function Module for









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

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



Function CONTEXT_ID_FROM_PROGRAM_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_ID_FROM_PROGRAM_NAME'"
EXPORTING
PROG = "

IMPORTING
CONTEXT_ID = "
.



IMPORTING Parameters details for CONTEXT_ID_FROM_PROGRAM_NAME

PROG -

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

EXPORTING Parameters details for CONTEXT_ID_FROM_PROGRAM_NAME

CONTEXT_ID -

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

Copy and paste ABAP code example for CONTEXT_ID_FROM_PROGRAM_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_prog  TYPE SY-REPID, "   
lv_context_id  TYPE RS33F-FRMID. "   

  CALL FUNCTION 'CONTEXT_ID_FROM_PROGRAM_NAME'  "
    EXPORTING
         PROG = lv_prog
    IMPORTING
         CONTEXT_ID = lv_context_id
. " CONTEXT_ID_FROM_PROGRAM_NAME




ABAP code using 7.40 inline data declarations to call FM CONTEXT_ID_FROM_PROGRAM_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.

"SELECT single REPID FROM SY INTO @DATA(ld_prog).
 
"SELECT single FRMID FROM RS33F INTO @DATA(ld_context_id).
 


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!