SAP FIBKRU_MEM_ORDER_FOR_APPROVAL Function Module for MO for approval procedure









FIBKRU_MEM_ORDER_FOR_APPROVAL is a standard fibkru mem order for approval SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MO for approval procedure 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 mem order for approval FM, simply by entering the name FIBKRU_MEM_ORDER_FOR_APPROVAL into the relevant SAP transaction such as SE37 or SE38.

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



Function FIBKRU_MEM_ORDER_FOR_APPROVAL 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_MEM_ORDER_FOR_APPROVAL'"MO for approval procedure
EXPORTING
I_BUKRS = "Company Code
I_BELNR = "Primary document number
I_GJAHR = "Fiscal Year

IMPORTING
E_STATUS = "Approval Status (A - Approved, R - Rejected)
E_MEMORDERS = "Memo Orders for Banking RU
.



IMPORTING Parameters details for FIBKRU_MEM_ORDER_FOR_APPROVAL

I_BUKRS - Company Code

Data type: BKPF-BUKRS
Optional: No
Call by Reference: Yes

I_BELNR - Primary document number

Data type: BKPF-BELNR
Optional: No
Call by Reference: Yes

I_GJAHR - Fiscal Year

Data type: BKPF-GJAHR
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FIBKRU_MEM_ORDER_FOR_APPROVAL

E_STATUS - Approval Status (A - Approved, R - Rejected)

Data type: FIBKRUD_CMO_HD-STATUS
Optional: No
Call by Reference: Yes

E_MEMORDERS - Memo Orders for Banking RU

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

Copy and paste ABAP code example for FIBKRU_MEM_ORDER_FOR_APPROVAL 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_bukrs  TYPE BKPF-BUKRS, "   
lv_e_status  TYPE FIBKRUD_CMO_HD-STATUS, "   
lv_i_belnr  TYPE BKPF-BELNR, "   
lv_e_memorders  TYPE FIBKRU_T_CMO_HD, "   
lv_i_gjahr  TYPE BKPF-GJAHR. "   

  CALL FUNCTION 'FIBKRU_MEM_ORDER_FOR_APPROVAL'  "MO for approval procedure
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_BELNR = lv_i_belnr
         I_GJAHR = lv_i_gjahr
    IMPORTING
         E_STATUS = lv_e_status
         E_MEMORDERS = lv_e_memorders
. " FIBKRU_MEM_ORDER_FOR_APPROVAL




ABAP code using 7.40 inline data declarations to call FM FIBKRU_MEM_ORDER_FOR_APPROVAL

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 BUKRS FROM BKPF INTO @DATA(ld_i_bukrs).
 
"SELECT single STATUS FROM FIBKRUD_CMO_HD INTO @DATA(ld_e_status).
 
"SELECT single BELNR FROM BKPF INTO @DATA(ld_i_belnr).
 
 
"SELECT single GJAHR FROM BKPF INTO @DATA(ld_i_gjahr).
 


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!