SAP FLBP_ADRS_STRUCTURE_FILL Function Module for Fill ADRS Structure









FLBP_ADRS_STRUCTURE_FILL is a standard flbp adrs structure fill SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fill ADRS Structure 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 flbp adrs structure fill FM, simply by entering the name FLBP_ADRS_STRUCTURE_FILL into the relevant SAP transaction such as SE37 or SE38.

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



Function FLBP_ADRS_STRUCTURE_FILL 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 'FLBP_ADRS_STRUCTURE_FILL'"Fill ADRS Structure
EXPORTING
I_PARTNR = "Business Partner Number
* I_ADR_REF = ' ' "Address ID
* I_DATE = SY-DATUM "Key Date
* I_BUKRS = ' ' "Company Code
* I_RLTYP = ' ' "Business Partner Role
* I_RLCAT = ' ' "BP role category
* I_COUNT_LINES = 5 "

IMPORTING
E_ADRS = "Address formating function module transfer structure
E_BUT000 = "BP: General Data I
E_PARTNER_ADREF = "BP Structure: Business Partner - Address
E_BUS020_EXT = "BP: Addresses with Addr. Data (Read)

EXCEPTIONS
PARTNER = 1 ADDRESS = 2
.



IMPORTING Parameters details for FLBP_ADRS_STRUCTURE_FILL

I_PARTNR - Business Partner Number

Data type: VDGPO-PARTNR
Optional: No
Call by Reference: Yes

I_ADR_REF - Address ID

Data type: VDGPO-ADR_REF
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_DATE - Key Date

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

I_BUKRS - Company Code

Data type: T001-BUKRS
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_RLTYP - Business Partner Role

Data type: VDGPO-ROLETYP
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_RLCAT - BP role category

Data type: TB003-ROLECATEGORY
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_COUNT_LINES -

Data type: ADRS-ANZZL
Default: 5
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FLBP_ADRS_STRUCTURE_FILL

E_ADRS - Address formating function module transfer structure

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

E_BUT000 - BP: General Data I

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

E_PARTNER_ADREF - BP Structure: Business Partner - Address

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

E_BUS020_EXT - BP: Addresses with Addr. Data (Read)

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

EXCEPTIONS details

PARTNER - Partner does not exist

Data type:
Optional: No
Call by Reference: Yes

ADDRESS - Adresse nicht vorhanden oder zugeordnet

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FLBP_ADRS_STRUCTURE_FILL 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_adrs  TYPE ADRS, "   
lv_partner  TYPE ADRS, "   
lv_i_partnr  TYPE VDGPO-PARTNR, "   
lv_address  TYPE VDGPO, "   
lv_e_but000  TYPE BUT000, "   
lv_i_adr_ref  TYPE VDGPO-ADR_REF, "   SPACE
lv_i_date  TYPE SY-DATUM, "   SY-DATUM
lv_e_partner_adref  TYPE BPDADREF, "   
lv_i_bukrs  TYPE T001-BUKRS, "   SPACE
lv_e_bus020_ext  TYPE BUS020_EXT, "   
lv_i_rltyp  TYPE VDGPO-ROLETYP, "   SPACE
lv_i_rlcat  TYPE TB003-ROLECATEGORY, "   SPACE
lv_i_count_lines  TYPE ADRS-ANZZL. "   5

  CALL FUNCTION 'FLBP_ADRS_STRUCTURE_FILL'  "Fill ADRS Structure
    EXPORTING
         I_PARTNR = lv_i_partnr
         I_ADR_REF = lv_i_adr_ref
         I_DATE = lv_i_date
         I_BUKRS = lv_i_bukrs
         I_RLTYP = lv_i_rltyp
         I_RLCAT = lv_i_rlcat
         I_COUNT_LINES = lv_i_count_lines
    IMPORTING
         E_ADRS = lv_e_adrs
         E_BUT000 = lv_e_but000
         E_PARTNER_ADREF = lv_e_partner_adref
         E_BUS020_EXT = lv_e_bus020_ext
    EXCEPTIONS
        PARTNER = 1
        ADDRESS = 2
. " FLBP_ADRS_STRUCTURE_FILL




ABAP code using 7.40 inline data declarations to call FM FLBP_ADRS_STRUCTURE_FILL

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 PARTNR FROM VDGPO INTO @DATA(ld_i_partnr).
 
 
 
"SELECT single ADR_REF FROM VDGPO INTO @DATA(ld_i_adr_ref).
DATA(ld_i_adr_ref) = ' '.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_date).
DATA(ld_i_date) = SY-DATUM.
 
 
"SELECT single BUKRS FROM T001 INTO @DATA(ld_i_bukrs).
DATA(ld_i_bukrs) = ' '.
 
 
"SELECT single ROLETYP FROM VDGPO INTO @DATA(ld_i_rltyp).
DATA(ld_i_rltyp) = ' '.
 
"SELECT single ROLECATEGORY FROM TB003 INTO @DATA(ld_i_rlcat).
DATA(ld_i_rlcat) = ' '.
 
"SELECT single ANZZL FROM ADRS INTO @DATA(ld_i_count_lines).
DATA(ld_i_count_lines) = 5.
 


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!