SAP META_STATUS_READ Function Module for Status information









META_STATUS_READ is a standard meta status read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Status information 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 meta status read FM, simply by entering the name META_STATUS_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function META_STATUS_READ 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 'META_STATUS_READ'"Status information
EXPORTING
* LOGICAL_SYSTEM = "

TABLES
REQ_REF = "
UPD_LINE = "
UPD_REF = "
RETURN = "
* CONTROL_RECORD = "Meta BAPI control record
.



IMPORTING Parameters details for META_STATUS_READ

LOGICAL_SYSTEM -

Data type: BBP_BACKEND_DEST-LOG_SYS
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for META_STATUS_READ

REQ_REF -

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

UPD_LINE -

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

UPD_REF -

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

RETURN -

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

CONTROL_RECORD - Meta BAPI control record

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

Copy and paste ABAP code example for META_STATUS_READ 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:
lt_req_ref  TYPE STANDARD TABLE OF REQREF, "   
lv_logical_system  TYPE BBP_BACKEND_DEST-LOG_SYS, "   
lt_upd_line  TYPE STANDARD TABLE OF REQLINE, "   
lt_upd_ref  TYPE STANDARD TABLE OF REQREF, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_control_record  TYPE STANDARD TABLE OF BBP_CONTROL_RECORD. "   

  CALL FUNCTION 'META_STATUS_READ'  "Status information
    EXPORTING
         LOGICAL_SYSTEM = lv_logical_system
    TABLES
         REQ_REF = lt_req_ref
         UPD_LINE = lt_upd_line
         UPD_REF = lt_upd_ref
         RETURN = lt_return
         CONTROL_RECORD = lt_control_record
. " META_STATUS_READ




ABAP code using 7.40 inline data declarations to call FM META_STATUS_READ

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 LOG_SYS FROM BBP_BACKEND_DEST INTO @DATA(ld_logical_system).
 
 
 
 
 


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!