SAP FLCU_BUPA_BDS001_GET Function Module for NOTRANSL: Geschäftspartner: BCS001 GET









FLCU_BUPA_BDS001_GET is a standard flcu bupa bds001 get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Geschäftspartner: BCS001 GET 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 flcu bupa bds001 get FM, simply by entering the name FLCU_BUPA_BDS001_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function FLCU_BUPA_BDS001_GET 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 'FLCU_BUPA_BDS001_GET'"NOTRANSL: Geschäftspartner: BCS001 GET
IMPORTING
E_BDS001 = "Business Partner: Initial Screen for Vendor Screen Structure
E_DATA = "
.



EXPORTING Parameters details for FLCU_BUPA_BDS001_GET

E_BDS001 - Business Partner: Initial Screen for Vendor Screen Structure

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

E_DATA -

Data type: BUSSDI3-DATA
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FLCU_BUPA_BDS001_GET 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_e_bds001  TYPE BDS001, "   
lv_e_data  TYPE BUSSDI3-DATA. "   

  CALL FUNCTION 'FLCU_BUPA_BDS001_GET'  "NOTRANSL: Geschäftspartner: BCS001 GET
    IMPORTING
         E_BDS001 = lv_e_bds001
         E_DATA = lv_e_data
. " FLCU_BUPA_BDS001_GET




ABAP code using 7.40 inline data declarations to call FM FLCU_BUPA_BDS001_GET

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 DATA FROM BUSSDI3 INTO @DATA(ld_e_data).
 


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!