SAP BTFR_CHANGE_PACKAGE Function Module for









BTFR_CHANGE_PACKAGE is a standard btfr change package 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 btfr change package FM, simply by entering the name BTFR_CHANGE_PACKAGE into the relevant SAP transaction such as SE37 or SE38.

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



Function BTFR_CHANGE_PACKAGE 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 'BTFR_CHANGE_PACKAGE'"
  EXPORTING
   CONCEPT_TAB =  "Concepts
*  NEW_PACKAGE =  "
*  FLAG_STRING =  "Indicator: 'X': Long Text (String), ' ': Short Text
*  FLAG_ENQ_CORR =  "

 IMPORTING
   ALIAS_TAB =  "
   ERROR_TAB =  "
   FLAG_CANCELLED =  "
   PACKAGE_NEW =  "

CHANGING
*  CORR_NUM =  "

EXCEPTIONS
   INVALID_PACKAGE = 1    INVALID_TADIR_ENTRY = 2    UPDATE_ERROR = 3
.



IMPORTING Parameters details for BTFR_CHANGE_PACKAGE

CONCEPT_TAB - Concepts

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

NEW_PACKAGE -

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

FLAG_STRING - Indicator: 'X': Long Text (String), ' ': Short Text

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

FLAG_ENQ_CORR -

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

EXPORTING Parameters details for BTFR_CHANGE_PACKAGE

ALIAS_TAB -

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

ERROR_TAB -

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

FLAG_CANCELLED -

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

PACKAGE_NEW -

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

CHANGING Parameters details for BTFR_CHANGE_PACKAGE

CORR_NUM -

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

EXCEPTIONS details

INVALID_PACKAGE -

Data type:
Optional: No
Call by Reference: Yes

INVALID_TADIR_ENTRY -

Data type:
Optional: No
Call by Reference: Yes

UPDATE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BTFR_CHANGE_PACKAGE 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_corr_num  TYPE TRKORR, "   
lv_alias_tab  TYPE BTFR_CONCEPT_ALIAS_TT, "   
lv_concept_tab  TYPE BTFR_CONC_TT, "   
lv_invalid_package  TYPE BTFR_CONC_TT, "   
lv_error_tab  TYPE BTFR_CONCEPT_ALIAS_TT, "   
lv_new_package  TYPE DEVCLASS, "   
lv_invalid_tadir_entry  TYPE DEVCLASS, "   
lv_flag_string  TYPE BTFR_F_STRING, "   
lv_update_error  TYPE BTFR_F_STRING, "   
lv_flag_cancelled  TYPE BTFR_FLAG, "   
lv_package_new  TYPE DEVCLASS, "   
lv_flag_enq_corr  TYPE BTFR_FLAG. "   

  CALL FUNCTION 'BTFR_CHANGE_PACKAGE'  "
    EXPORTING
         CONCEPT_TAB = lv_concept_tab
         NEW_PACKAGE = lv_new_package
         FLAG_STRING = lv_flag_string
         FLAG_ENQ_CORR = lv_flag_enq_corr
    IMPORTING
         ALIAS_TAB = lv_alias_tab
         ERROR_TAB = lv_error_tab
         FLAG_CANCELLED = lv_flag_cancelled
         PACKAGE_NEW = lv_package_new
    CHANGING
         CORR_NUM = lv_corr_num
    EXCEPTIONS
        INVALID_PACKAGE = 1
        INVALID_TADIR_ENTRY = 2
        UPDATE_ERROR = 3
. " BTFR_CHANGE_PACKAGE




ABAP code using 7.40 inline data declarations to call FM BTFR_CHANGE_PACKAGE

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!