SAP FLCU_BUPA_MEMORY_GET Function Module for OBSOLETE

Search SAP Function Modules

FLCU_BUPA_MEMORY_GET is a standard flcu bupa memory 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 OBSOLETE 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 memory get FM, simply by entering the name FLCU_BUPA_MEMORY_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function FLCU_BUPA_MEMORY_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_MEMORY_GET'"OBSOLETE
  EXPORTING
*  I_PARTNER =  "Partner Number
*  I_KUNNR =  "Account Number of Vendor
*  I_XWA = ' ' "Checkbox: Search Work Area

 IMPORTING
   E_BDS001 =  "Business Partner: Initial Customer Screen Structure

TABLES
*  T_BDS001 =  "Business Partner: Initial Customer Screen Structure

EXCEPTIONS
   NO_DATA_FOUND = 1    WRONG_PARAMETERS = 2 

.

IMPORTING Parameters details for FLCU_BUPA_MEMORY_GET

I_PARTNER - Partner Number

Data type: BUT000-PARTNER
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_KUNNR - Account Number of Vendor

Data type: KNA1-KUNNR
Optional: Yes
Call by Reference: Yes

I_XWA - Checkbox: Search Work Area

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FLCU_BUPA_MEMORY_GET

E_BDS001 - Business Partner: Initial Customer Screen Structure

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

TABLES Parameters details for FLCU_BUPA_MEMORY_GET

T_BDS001 - Business Partner: Initial Customer Screen Structure

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

EXCEPTIONS details

NO_DATA_FOUND - No Partner Data Found

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

WRONG_PARAMETERS - Incorrect parameters

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

Copy and paste ABAP code example for FLCU_BUPA_MEMORY_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.

ABAP code using 7.40 inline data declarations to call FM FLCU_BUPA_MEMORY_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.

Search for further information about these or an SAP related objects