SAP FIEB_MAPPING_STATUS_X Function Module for









FIEB_MAPPING_STATUS_X is a standard fieb mapping status x 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 fieb mapping status x FM, simply by entering the name FIEB_MAPPING_STATUS_X into the relevant SAP transaction such as SE37 or SE38.

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



Function FIEB_MAPPING_STATUS_X 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 'FIEB_MAPPING_STATUS_X'"
EXPORTING
I_BANK_STATEMENT = "
* IV_XSLT_TRANSF = "
* IV_BADI_FILTER_VAL = "

IMPORTING
ET_BAPIRET = "

EXCEPTIONS
ERROR_IN_BADI = 1 ERROR_IN_TRANSF = 2
.



IMPORTING Parameters details for FIEB_MAPPING_STATUS_X

I_BANK_STATEMENT -

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

IV_XSLT_TRANSF -

Data type: CXSLTDESC
Optional: Yes
Call by Reference: Yes

IV_BADI_FILTER_VAL -

Data type: BADI_FILTER_VAL
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FIEB_MAPPING_STATUS_X

ET_BAPIRET -

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

EXCEPTIONS details

ERROR_IN_BADI -

Data type:
Optional: No
Call by Reference: Yes

ERROR_IN_TRANSF -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FIEB_MAPPING_STATUS_X 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_et_bapiret  TYPE BAPIRET2_T, "   
lv_error_in_badi  TYPE BAPIRET2_T, "   
lv_i_bank_statement  TYPE STRING, "   
lv_iv_xslt_transf  TYPE CXSLTDESC, "   
lv_error_in_transf  TYPE CXSLTDESC, "   
lv_iv_badi_filter_val  TYPE BADI_FILTER_VAL. "   

  CALL FUNCTION 'FIEB_MAPPING_STATUS_X'  "
    EXPORTING
         I_BANK_STATEMENT = lv_i_bank_statement
         IV_XSLT_TRANSF = lv_iv_xslt_transf
         IV_BADI_FILTER_VAL = lv_iv_badi_filter_val
    IMPORTING
         ET_BAPIRET = lv_et_bapiret
    EXCEPTIONS
        ERROR_IN_BADI = 1
        ERROR_IN_TRANSF = 2
. " FIEB_MAPPING_STATUS_X




ABAP code using 7.40 inline data declarations to call FM FIEB_MAPPING_STATUS_X

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



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!