SAP BAPI_FUNCLOC_GETLIST Function Module for BAPI PM: Read List of Functional Locations (with Internal Key)









BAPI_FUNCLOC_GETLIST is a standard bapi funcloc getlist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI PM: Read List of Functional Locations (with Internal Key) 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 bapi funcloc getlist FM, simply by entering the name BAPI_FUNCLOC_GETLIST into the relevant SAP transaction such as SE37 or SE38.

Function Group: ITOB_BAPI_FL
Program Name: SAPLITOB_BAPI_FL
Main Program: SAPLITOB_BAPI_FL
Appliation area:
Release date: 03-Feb-2000
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_FUNCLOC_GETLIST 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 'BAPI_FUNCLOC_GETLIST'"BAPI PM: Read List of Functional Locations (with Internal Key)
EXPORTING
* LANGUAGE = SY-LANGU "Language Key
* LANGUAGE_ISO = "Language According to ISO 639
* PARTNERFUNCTION = "Partner Role

IMPORTING
RETURN = "Return Parameter

TABLES
* FUNCLOC_RA = "BAPI Communication Structure: Range for Functional Location
* ADDRESS_SEARCH_TERM_2_RA = "BAPI Communication Structure: Range for Address Search Term 2
* ADDRESS_NAME_RA = "BAPI Communication Structure: Range for Address Name
* ADDRESS_POST_CODE_RA = "BAPI Communication Structure: Range for Address Postal Code
* ADDRESS_CITY_RA = "BAPI Communication Structure: Range for Address City
* ADDRESS_STREET_RA = "BAPI Communication Structure: Range for Address Street
* PARTNER_RA = "BAPI Communication Structure: Range for Partner
* OBJECTTYPE_RA = "BAPI Communication Structure: Range for Object Type
* DESCRIPT_RA = "BAPI Communication Structure: Description Range
* MAINTPLANT_RA = "BApi Communication Structure: Range for Maintenance Plant
* PLANGROUP_RA = "BAPI Communication Structure: Range for Maintenance Planner Group
* PLANPLANT_RA = "BAPI Communication Structure: Range for Maintenance Planning
* SORTFIELD_RA = "BAPI Communication Structure: Range for Sort Field
FUNCLOC_LIST = "BAPI Communication Structure: Results List of Selection
* STATUS_RA = "BAPI Communication Structure: Range for Status
* ADDRESS_SEARCH_TERM_1_RA = "BAPI Communication Structure: Range for Address Search Term 1
.



IMPORTING Parameters details for BAPI_FUNCLOC_GETLIST

LANGUAGE - Language Key

Data type: BAPI_ITOB_PARMS-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGUAGE_ISO - Language According to ISO 639

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

PARTNERFUNCTION - Partner Role

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

EXPORTING Parameters details for BAPI_FUNCLOC_GETLIST

RETURN - Return Parameter

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

TABLES Parameters details for BAPI_FUNCLOC_GETLIST

FUNCLOC_RA - BAPI Communication Structure: Range for Functional Location

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

ADDRESS_SEARCH_TERM_2_RA - BAPI Communication Structure: Range for Address Search Term 2

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

ADDRESS_NAME_RA - BAPI Communication Structure: Range for Address Name

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

ADDRESS_POST_CODE_RA - BAPI Communication Structure: Range for Address Postal Code

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

ADDRESS_CITY_RA - BAPI Communication Structure: Range for Address City

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

ADDRESS_STREET_RA - BAPI Communication Structure: Range for Address Street

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

PARTNER_RA - BAPI Communication Structure: Range for Partner

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

OBJECTTYPE_RA - BAPI Communication Structure: Range for Object Type

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

DESCRIPT_RA - BAPI Communication Structure: Description Range

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

MAINTPLANT_RA - BApi Communication Structure: Range for Maintenance Plant

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

PLANGROUP_RA - BAPI Communication Structure: Range for Maintenance Planner Group

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

PLANPLANT_RA - BAPI Communication Structure: Range for Maintenance Planning

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

SORTFIELD_RA - BAPI Communication Structure: Range for Sort Field

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

FUNCLOC_LIST - BAPI Communication Structure: Results List of Selection

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

STATUS_RA - BAPI Communication Structure: Range for Status

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

ADDRESS_SEARCH_TERM_1_RA - BAPI Communication Structure: Range for Address Search Term 1

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

Copy and paste ABAP code example for BAPI_FUNCLOC_GETLIST 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_return  TYPE BAPIRET2, "   
lv_language  TYPE BAPI_ITOB_PARMS-LANGU, "   SY-LANGU
lt_funcloc_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_FUNCLOC, "   
lt_address_search_term_2_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_ADDR_SORT2, "   
lt_address_name_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_ADDR_NAME, "   
lt_address_post_code_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_ADDR_POST_CODE, "   
lt_address_city_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_ADDR_CITY, "   
lt_address_street_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_ADDR_STREET, "   
lt_partner_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_PARTNER, "   
lt_objecttype_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_OBJECTTYPE, "   
lt_descript_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_DESCRIPT, "   
lv_language_iso  TYPE BAPI_ITOB_PARMS-LANGU_ISO, "   
lt_maintplant_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_MAINTPLANT, "   
lv_partnerfunction  TYPE BAPIIHPA-PAR_FUNCT, "   
lt_plangroup_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_PLANGROUP, "   
lt_planplant_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_PLANPLANT, "   
lt_sortfield_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_SORTFIELD, "   
lt_funcloc_list  TYPE STANDARD TABLE OF BAPI_ITOB_FL_SEL_RESULT, "   
lt_status_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_STATUS, "   
lt_address_search_term_1_ra  TYPE STANDARD TABLE OF BAPI_ITOB_SEL_ADDR_SORT1. "   

  CALL FUNCTION 'BAPI_FUNCLOC_GETLIST'  "BAPI PM: Read List of Functional Locations (with Internal Key)
    EXPORTING
         LANGUAGE = lv_language
         LANGUAGE_ISO = lv_language_iso
         PARTNERFUNCTION = lv_partnerfunction
    IMPORTING
         RETURN = lv_return
    TABLES
         FUNCLOC_RA = lt_funcloc_ra
         ADDRESS_SEARCH_TERM_2_RA = lt_address_search_term_2_ra
         ADDRESS_NAME_RA = lt_address_name_ra
         ADDRESS_POST_CODE_RA = lt_address_post_code_ra
         ADDRESS_CITY_RA = lt_address_city_ra
         ADDRESS_STREET_RA = lt_address_street_ra
         PARTNER_RA = lt_partner_ra
         OBJECTTYPE_RA = lt_objecttype_ra
         DESCRIPT_RA = lt_descript_ra
         MAINTPLANT_RA = lt_maintplant_ra
         PLANGROUP_RA = lt_plangroup_ra
         PLANPLANT_RA = lt_planplant_ra
         SORTFIELD_RA = lt_sortfield_ra
         FUNCLOC_LIST = lt_funcloc_list
         STATUS_RA = lt_status_ra
         ADDRESS_SEARCH_TERM_1_RA = lt_address_search_term_1_ra
. " BAPI_FUNCLOC_GETLIST




ABAP code using 7.40 inline data declarations to call FM BAPI_FUNCLOC_GETLIST

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 LANGU FROM BAPI_ITOB_PARMS INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
 
 
 
 
 
 
 
 
 
"SELECT single LANGU_ISO FROM BAPI_ITOB_PARMS INTO @DATA(ld_language_iso).
 
 
"SELECT single PAR_FUNCT FROM BAPIIHPA INTO @DATA(ld_partnerfunction).
 
 
 
 
 
 
 


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!