SAP OCS_API_GET_PMESSAGES Function Module for









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

Function Group: OCS_API
Program Name: SAPLOCS_API
Main Program: SAPLOCS_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function OCS_API_GET_PMESSAGES 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_API_GET_PMESSAGES'"
IMPORTING
EV_RC = "
EV_MESSAGE = "
ET_BAPIRET = "
.



EXPORTING Parameters details for OCS_API_GET_PMESSAGES

EV_RC -

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

EV_MESSAGE -

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

ET_BAPIRET -

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

Copy and paste ABAP code example for OCS_API_GET_PMESSAGES 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_ev_rc  TYPE INT4, "   
lv_ev_message  TYPE PATCHTXT3, "   
lv_et_bapiret  TYPE OCS_API_T_MESSAGE. "   

  CALL FUNCTION 'OCS_API_GET_PMESSAGES'  "
    IMPORTING
         EV_RC = lv_ev_rc
         EV_MESSAGE = lv_ev_message
         ET_BAPIRET = lv_et_bapiret
. " OCS_API_GET_PMESSAGES




ABAP code using 7.40 inline data declarations to call FM OCS_API_GET_PMESSAGES

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!