SAP BTC_OPTION_GET Function Module for









BTC_OPTION_GET is a standard btc option get 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 btc option get FM, simply by entering the name BTC_OPTION_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function BTC_OPTION_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 'BTC_OPTION_GET'"
  EXPORTING
   NAME =  "
*  IMPVALUE1 =  "
*  IMPVALUE2 =  "

 IMPORTING
   COUNT =  "

TABLES
*  OPTIONS =  "

EXCEPTIONS
   INVALID_NAME = 1
.



IMPORTING Parameters details for BTC_OPTION_GET

NAME -

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

IMPVALUE1 -

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

IMPVALUE2 -

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

EXPORTING Parameters details for BTC_OPTION_GET

COUNT -

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

TABLES Parameters details for BTC_OPTION_GET

OPTIONS -

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

EXCEPTIONS details

INVALID_NAME -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BTC_OPTION_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_name  TYPE C, "   
lv_count  TYPE I, "   
lt_options  TYPE STANDARD TABLE OF BTCOPTIONS, "   
lv_invalid_name  TYPE BTCOPTIONS, "   
lv_impvalue1  TYPE C, "   
lv_impvalue2  TYPE C. "   

  CALL FUNCTION 'BTC_OPTION_GET'  "
    EXPORTING
         NAME = lv_name
         IMPVALUE1 = lv_impvalue1
         IMPVALUE2 = lv_impvalue2
    IMPORTING
         COUNT = lv_count
    TABLES
         OPTIONS = lt_options
    EXCEPTIONS
        INVALID_NAME = 1
. " BTC_OPTION_GET




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



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!