SAP OCS_TEXT2MESSAGE Function Module for









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

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



Function OCS_TEXT2MESSAGE 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 'OCS_TEXT2MESSAGE'"
EXPORTING
IV_ERROR_TEXT = "
* IV_MSG_ID = 'TN_LUP' "
* IV_MSG_NO = '000' "
* IV_MSG_TYPE = 'I' "

IMPORTING
ES_MSG = "
.



IMPORTING Parameters details for OCS_TEXT2MESSAGE

IV_ERROR_TEXT -

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

IV_MSG_ID -

Data type: SYMSGID
Default: 'TN_LUP'
Optional: Yes
Call by Reference: Yes

IV_MSG_NO -

Data type: SYMSGNO
Default: '000'
Optional: Yes
Call by Reference: Yes

IV_MSG_TYPE -

Data type: SYMSGTY
Default: 'I'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for OCS_TEXT2MESSAGE

ES_MSG -

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

Copy and paste ABAP code example for OCS_TEXT2MESSAGE 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_es_msg  TYPE OCS_S_MSG, "   
lv_iv_error_text  TYPE STRING, "   
lv_iv_msg_id  TYPE SYMSGID, "   'TN_LUP'
lv_iv_msg_no  TYPE SYMSGNO, "   '000'
lv_iv_msg_type  TYPE SYMSGTY. "   'I'

  CALL FUNCTION 'OCS_TEXT2MESSAGE'  "
    EXPORTING
         IV_ERROR_TEXT = lv_iv_error_text
         IV_MSG_ID = lv_iv_msg_id
         IV_MSG_NO = lv_iv_msg_no
         IV_MSG_TYPE = lv_iv_msg_type
    IMPORTING
         ES_MSG = lv_es_msg
. " OCS_TEXT2MESSAGE




ABAP code using 7.40 inline data declarations to call FM OCS_TEXT2MESSAGE

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.

 
 
DATA(ld_iv_msg_id) = 'TN_LUP'.
 
DATA(ld_iv_msg_no) = '000'.
 
DATA(ld_iv_msg_type) = 'I'.
 


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!