SAP BALW_BAPIRETURN_GET1 Function Module for Fills the BAPI Return Parameter as of 4.0









BALW_BAPIRETURN_GET1 is a standard balw bapireturn get1 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fills the BAPI Return Parameter as of 4.0 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 balw bapireturn get1 FM, simply by entering the name BALW_BAPIRETURN_GET1 into the relevant SAP transaction such as SE37 or SE38.

Function Group: BFRT
Program Name: SAPLBFRT
Main Program:
Appliation area: S
Release date: 30-Nov-1998
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BALW_BAPIRETURN_GET1 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 'BALW_BAPIRETURN_GET1'"Fills the BAPI Return Parameter as of 4.0
  EXPORTING
   TYPE =  "Message Type
   CL =  "Message Class (Message ID)
   NUMBER =  "Message Number
*  PAR1 = ' ' "Variable 1
*  PAR2 = ' ' "Variable 2
*  PAR3 = ' ' "Variable 3
*  PAR4 = ' ' "Variable 4
*  LOG_NO = ' ' "Application Log ID
*  LOG_MSG_NO = ' ' "Current Number in Application Log

 IMPORTING
   BAPIRETURN =  "BAPI Return Parameter
.



IMPORTING Parameters details for BALW_BAPIRETURN_GET1

TYPE - Message Type

Data type: BAPIRETURN-TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

CL - Message Class (Message ID)

Data type: SY-MSGID
Optional: No
Call by Reference: No ( called with pass by value option)

NUMBER - Message Number

Data type: SY-MSGNO
Optional: No
Call by Reference: No ( called with pass by value option)

PAR1 - Variable 1

Data type: SY-MSGV1
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PAR2 - Variable 2

Data type: SY-MSGV2
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PAR3 - Variable 3

Data type: SY-MSGV3
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PAR4 - Variable 4

Data type: SY-MSGV4
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOG_NO - Application Log ID

Data type: BAPIRETURN-LOG_NO
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOG_MSG_NO - Current Number in Application Log

Data type: BAPIRETURN-LOG_MSG_NO
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BALW_BAPIRETURN_GET1

BAPIRETURN - BAPI Return Parameter

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

Copy and paste ABAP code example for BALW_BAPIRETURN_GET1 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_type  TYPE BAPIRETURN-TYPE, "   
lv_bapireturn  TYPE BAPIRET1, "   
lv_cl  TYPE SY-MSGID, "   
lv_number  TYPE SY-MSGNO, "   
lv_par1  TYPE SY-MSGV1, "   SPACE
lv_par2  TYPE SY-MSGV2, "   SPACE
lv_par3  TYPE SY-MSGV3, "   SPACE
lv_par4  TYPE SY-MSGV4, "   SPACE
lv_log_no  TYPE BAPIRETURN-LOG_NO, "   SPACE
lv_log_msg_no  TYPE BAPIRETURN-LOG_MSG_NO. "   SPACE

  CALL FUNCTION 'BALW_BAPIRETURN_GET1'  "Fills the BAPI Return Parameter as of 4.0
    EXPORTING
         TYPE = lv_type
         CL = lv_cl
         NUMBER = lv_number
         PAR1 = lv_par1
         PAR2 = lv_par2
         PAR3 = lv_par3
         PAR4 = lv_par4
         LOG_NO = lv_log_no
         LOG_MSG_NO = lv_log_msg_no
    IMPORTING
         BAPIRETURN = lv_bapireturn
. " BALW_BAPIRETURN_GET1




ABAP code using 7.40 inline data declarations to call FM BALW_BAPIRETURN_GET1

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 TYPE FROM BAPIRETURN INTO @DATA(ld_type).
 
 
"SELECT single MSGID FROM SY INTO @DATA(ld_cl).
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_number).
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_par1).
DATA(ld_par1) = ' '.
 
"SELECT single MSGV2 FROM SY INTO @DATA(ld_par2).
DATA(ld_par2) = ' '.
 
"SELECT single MSGV3 FROM SY INTO @DATA(ld_par3).
DATA(ld_par3) = ' '.
 
"SELECT single MSGV4 FROM SY INTO @DATA(ld_par4).
DATA(ld_par4) = ' '.
 
"SELECT single LOG_NO FROM BAPIRETURN INTO @DATA(ld_log_no).
DATA(ld_log_no) = ' '.
 
"SELECT single LOG_MSG_NO FROM BAPIRETURN INTO @DATA(ld_log_msg_no).
DATA(ld_log_msg_no) = ' '.
 


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!