SAP LOCU_BUPA_SALES_AREA_GET Function Module for Determine Sales Area
LOCU_BUPA_SALES_AREA_GET is a standard locu bupa sales area 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 Determine Sales Area 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 locu bupa sales area get FM, simply by entering the name LOCU_BUPA_SALES_AREA_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: LBU0
Program Name: SAPLLBU0
Main Program: SAPLLBU0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LOCU_BUPA_SALES_AREA_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 'LOCU_BUPA_SALES_AREA_GET'"Determine Sales Area.
IMPORTING
E_VKORG = "Sales Organization
E_VTWEG = "Distribution Channel
E_SPART = "Division
EXPORTING Parameters details for LOCU_BUPA_SALES_AREA_GET
E_VKORG - Sales Organization
Data type: VKORGOptional: No
Call by Reference: No ( called with pass by value option)
E_VTWEG - Distribution Channel
Data type: VTWEGOptional: No
Call by Reference: No ( called with pass by value option)
E_SPART - Division
Data type: SPARTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LOCU_BUPA_SALES_AREA_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_vkorg | TYPE VKORG, " | |||
| lv_e_vtweg | TYPE VTWEG, " | |||
| lv_e_spart | TYPE SPART. " |
|   CALL FUNCTION 'LOCU_BUPA_SALES_AREA_GET' "Determine Sales Area |
| IMPORTING | ||
| E_VKORG | = lv_e_vkorg | |
| E_VTWEG | = lv_e_vtweg | |
| E_SPART | = lv_e_spart | |
| . " LOCU_BUPA_SALES_AREA_GET | ||
ABAP code using 7.40 inline data declarations to call FM LOCU_BUPA_SALES_AREA_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