SAP FIBKRU_SAVE_APPROVALS_INTO_DB Function Module for Save Step Approval Information of Memo Order into DB Table









FIBKRU_SAVE_APPROVALS_INTO_DB is a standard fibkru save approvals into db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save Step Approval Information of Memo Order into DB Table 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 fibkru save approvals into db FM, simply by entering the name FIBKRU_SAVE_APPROVALS_INTO_DB into the relevant SAP transaction such as SE37 or SE38.

Function Group: FIBKRU_MEMO_ORDER
Program Name: SAPLFIBKRU_MEMO_ORDER
Main Program: SAPLFIBKRU_MEMO_ORDER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function FIBKRU_SAVE_APPROVALS_INTO_DB 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 'FIBKRU_SAVE_APPROVALS_INTO_DB'"Save Step Approval Information of Memo Order into DB Table
EXPORTING
I_APPROVALS = "
* I_ACTION = 'I' "'I' - insert, 'M' - modify

EXCEPTIONS
UPDATE_ERROR = 1 WRONG_OPERATION = 2
.



IMPORTING Parameters details for FIBKRU_SAVE_APPROVALS_INTO_DB

I_APPROVALS -

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

I_ACTION - 'I' - insert, 'M' - modify

Data type: CHAR1
Default: 'I'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

UPDATE_ERROR -

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

WRONG_OPERATION -

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

Copy and paste ABAP code example for FIBKRU_SAVE_APPROVALS_INTO_DB 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_i_approvals  TYPE FIBKRUD_MO_APPRS, "   
lv_update_error  TYPE FIBKRUD_MO_APPRS, "   
lv_i_action  TYPE CHAR1, "   'I'
lv_wrong_operation  TYPE CHAR1. "   

  CALL FUNCTION 'FIBKRU_SAVE_APPROVALS_INTO_DB'  "Save Step Approval Information of Memo Order into DB Table
    EXPORTING
         I_APPROVALS = lv_i_approvals
         I_ACTION = lv_i_action
    EXCEPTIONS
        UPDATE_ERROR = 1
        WRONG_OPERATION = 2
. " FIBKRU_SAVE_APPROVALS_INTO_DB




ABAP code using 7.40 inline data declarations to call FM FIBKRU_SAVE_APPROVALS_INTO_DB

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.

 
 
DATA(ld_i_action) = 'I'.
 
 


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!