SAP BBP_BUPA_GET_TITLEKEY_F4 Function Module for









BBP_BUPA_GET_TITLEKEY_F4 is a standard bbp bupa get titlekey f4 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bbp bupa get titlekey f4 FM, simply by entering the name BBP_BUPA_GET_TITLEKEY_F4 into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_BUPA_GET_TITLEKEY_F4 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 'BBP_BUPA_GET_TITLEKEY_F4'"
EXPORTING
* LANGUAGE = SY-LANGU "
* PERSON = "
* ORGANIZATION = "

TABLES
* ET_TITLE_KEYS = "

EXCEPTIONS
TITLE_NOT_FOUND = 1 TITLE_TEXT_NOT_FOUND = 2 PARAMETER_ERROR = 3
.



IMPORTING Parameters details for BBP_BUPA_GET_TITLEKEY_F4

LANGUAGE -

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

PERSON -

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

ORGANIZATION -

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

TABLES Parameters details for BBP_BUPA_GET_TITLEKEY_F4

ET_TITLE_KEYS -

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

EXCEPTIONS details

TITLE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

TITLE_TEXT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

PARAMETER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_BUPA_GET_TITLEKEY_F4 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_language  TYPE SPRAS, "   SY-LANGU
lt_et_title_keys  TYPE STANDARD TABLE OF ADVALTITLE, "   
lv_title_not_found  TYPE ADVALTITLE, "   
lv_person  TYPE AD_XPERS, "   
lv_title_text_not_found  TYPE AD_XPERS, "   
lv_organization  TYPE AD_XORGA, "   
lv_parameter_error  TYPE AD_XORGA. "   

  CALL FUNCTION 'BBP_BUPA_GET_TITLEKEY_F4'  "
    EXPORTING
         LANGUAGE = lv_language
         PERSON = lv_person
         ORGANIZATION = lv_organization
    TABLES
         ET_TITLE_KEYS = lt_et_title_keys
    EXCEPTIONS
        TITLE_NOT_FOUND = 1
        TITLE_TEXT_NOT_FOUND = 2
        PARAMETER_ERROR = 3
. " BBP_BUPA_GET_TITLEKEY_F4




ABAP code using 7.40 inline data declarations to call FM BBP_BUPA_GET_TITLEKEY_F4

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.

DATA(ld_language) = SY-LANGU.
 
 
 
 
 
 
 


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!