SAP FS_BAPI_BAPIRET2_FILL Function Module for

Search SAP Function Modules

FS_BAPI_BAPIRET2_FILL is a standard fs bapi bapiret2 fill 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 fs bapi bapiret2 fill FM, simply by entering the name FS_BAPI_BAPIRET2_FILL into the relevant SAP transaction such as SE37 or SE38.

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

Function FS_BAPI_BAPIRET2_FILL 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 'FS_BAPI_BAPIRET2_FILL'"
  EXPORTING
   TYPE =  "Message Type
*  PARAMETER = ' ' "Parameter Name
*  ROW = 0 "Row Number
*  FIELD = ' ' "Field Name
   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
   RETURN =  "BAPI Return Parameter

.

IMPORTING Parameters details for FS_BAPI_BAPIRET2_FILL

TYPE - Message Type

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

PARAMETER - Parameter Name

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

ROW - Row Number

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

FIELD - Field Name

Data type: BAPIRET2-FIELD
Default: SPACE
Optional: Yes
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 FS_BAPI_BAPIRET2_FILL

RETURN - BAPI Return Parameter

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

Copy and paste ABAP code example for FS_BAPI_BAPIRET2_FILL 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.

ABAP code using 7.40 inline data declarations to call FM FS_BAPI_BAPIRET2_FILL

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