SAP JBIBP_MAP2E_BP021_TO_FISCYEAR Function Module for bp021 -> bapi_str_bupa_fs_fiscyear









JBIBP_MAP2E_BP021_TO_FISCYEAR is a standard jbibp map2e bp021 to fiscyear SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for bp021 -> bapi_str_bupa_fs_fiscyear 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 jbibp map2e bp021 to fiscyear FM, simply by entering the name JBIBP_MAP2E_BP021_TO_FISCYEAR into the relevant SAP transaction such as SE37 or SE38.

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



Function JBIBP_MAP2E_BP021_TO_FISCYEAR 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 'JBIBP_MAP2E_BP021_TO_FISCYEAR'"bp021 -> bapi_str_bupa_fs_fiscyear
EXPORTING
BP021 = "

CHANGING
BAPI_STR_BUPA_FS_FISCYEAR = "FS-BP: BAPI-Struktur für Geschäftsjahresdaten
.



IMPORTING Parameters details for JBIBP_MAP2E_BP021_TO_FISCYEAR

BP021 -

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

CHANGING Parameters details for JBIBP_MAP2E_BP021_TO_FISCYEAR

BAPI_STR_BUPA_FS_FISCYEAR - FS-BP: BAPI-Struktur für Geschäftsjahresdaten

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

Copy and paste ABAP code example for JBIBP_MAP2E_BP021_TO_FISCYEAR 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_bp021  TYPE BP021, "   
lv_bapi_str_bupa_fs_fiscyear  TYPE JBIBP_BAPI_STR_BUPA_FS_FISCYEA. "   

  CALL FUNCTION 'JBIBP_MAP2E_BP021_TO_FISCYEAR'  "bp021 -> bapi_str_bupa_fs_fiscyear
    EXPORTING
         BP021 = lv_bp021
    CHANGING
         BAPI_STR_BUPA_FS_FISCYEAR = lv_bapi_str_bupa_fs_fiscyear
. " JBIBP_MAP2E_BP021_TO_FISCYEAR




ABAP code using 7.40 inline data declarations to call FM JBIBP_MAP2E_BP021_TO_FISCYEAR

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!