SAP OCS_GET_MSG_FOR_COMP_STEP Function Module for









OCS_GET_MSG_FOR_COMP_STEP is a standard ocs get msg for comp step 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 get msg for comp step FM, simply by entering the name OCS_GET_MSG_FOR_COMP_STEP 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_GET_MSG_FOR_COMP_STEP 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_GET_MSG_FOR_COMP_STEP'"
EXPORTING
IV_IMPORT_STEP = "
IT_PAT_Q = "
IV_PACKAGE = "

IMPORTING
ET_MSGS = "

EXCEPTIONS
FAILURE = 1
.



IMPORTING Parameters details for OCS_GET_MSG_FOR_COMP_STEP

IV_IMPORT_STEP -

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

IT_PAT_Q -

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

IV_PACKAGE -

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

EXPORTING Parameters details for OCS_GET_MSG_FOR_COMP_STEP

ET_MSGS -

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

EXCEPTIONS details

FAILURE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OCS_GET_MSG_FOR_COMP_STEP 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_et_msgs  TYPE TTOCS_APIMSGS, "   
lv_failure  TYPE TTOCS_APIMSGS, "   
lv_iv_import_step  TYPE CHAR1, "   
lv_it_pat_q  TYPE TT_PAT_Q, "   
lv_iv_package  TYPE PATCH. "   

  CALL FUNCTION 'OCS_GET_MSG_FOR_COMP_STEP'  "
    EXPORTING
         IV_IMPORT_STEP = lv_iv_import_step
         IT_PAT_Q = lv_it_pat_q
         IV_PACKAGE = lv_iv_package
    IMPORTING
         ET_MSGS = lv_et_msgs
    EXCEPTIONS
        FAILURE = 1
. " OCS_GET_MSG_FOR_COMP_STEP




ABAP code using 7.40 inline data declarations to call FM OCS_GET_MSG_FOR_COMP_STEP

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!