SAP MMPUR_TEXT_SET_OKCODE Function Module for NOTRANSL: Überträgt den OK-CODE vom rufenden Programm an den Text-Subscree
MMPUR_TEXT_SET_OKCODE is a standard mmpur text set okcode SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Überträgt den OK-CODE vom rufenden Programm an den Text-Subscree processing and below is the pattern details for this FM, 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 mmpur text set okcode FM, simply by entering the name MMPUR_TEXT_SET_OKCODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MMTE
Program Name: SAPLMMTE
Main Program: SAPLMMTE
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MMPUR_TEXT_SET_OKCODE 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 'MMPUR_TEXT_SET_OKCODE'"NOTRANSL: Überträgt den OK-CODE vom rufenden Programm an den Text-Subscree.
EXPORTING
* IM_TEXTOBJECT = "Texts: Application Object
* IM_OKCODE = "ABAP System Field: PAI-Triggering Function Code
IMPORTING Parameters details for MMPUR_TEXT_SET_OKCODE
IM_TEXTOBJECT - Texts: Application Object
Data type: TTXOB-TDOBJECTOptional: Yes
Call by Reference: Yes
IM_OKCODE - ABAP System Field: PAI-Triggering Function Code
Data type: SY-UCOMMOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for MMPUR_TEXT_SET_OKCODE 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_im_textobject | TYPE TTXOB-TDOBJECT, " | |||
| lv_im_okcode | TYPE SY-UCOMM. " |
|   CALL FUNCTION 'MMPUR_TEXT_SET_OKCODE' "NOTRANSL: Überträgt den OK-CODE vom rufenden Programm an den Text-Subscree |
| EXPORTING | ||
| IM_TEXTOBJECT | = lv_im_textobject | |
| IM_OKCODE | = lv_im_okcode | |
| . " MMPUR_TEXT_SET_OKCODE | ||
ABAP code using 7.40 inline data declarations to call FM MMPUR_TEXT_SET_OKCODE
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 TDOBJECT FROM TTXOB INTO @DATA(ld_im_textobject). | ||||
| "SELECT single UCOMM FROM SY INTO @DATA(ld_im_okcode). | ||||
Search for further information about these or an SAP related objects