SAP BAPI_FTR_REPO_CHANGE Function Module for Change a Repo

Search SAP Function Modules

BAPI_FTR_REPO_CHANGE is a standard bapi ftr repo change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change a Repo 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 ftr repo change FM, simply by entering the name BAPI_FTR_REPO_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FTR_BAPI_REPO
Program Name: SAPLFTR_BAPI_REPO
Main Program: SAPLFTR_BAPI_REPO
Appliation area:
Release date: 30-Nov-2012
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_FTR_REPO_CHANGE 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_FTR_REPO_CHANGE'"Change a Repo
  EXPORTING
   COMPANYCODE =  "Company Code
   FINANCIALTRANSACTION =  "Financial Transaction
   REPO =  "Change a Repo per BAPI
   REPOX =  "Change Structure of a Repo by BAPI
   GENERALCONTRACTDATA =  "Structure for changing general (product category independent) transaction data
   GENERALCONTRACTDATAX =  "Change Strucutre of general contract data by BAPI
*  TESTRUN = ' ' "Switch to Simulation Session for Write BAPIs

 IMPORTING
   RETURNCOMPANYCODE =  "Company Code
   RETURNFINANCIALTRANSACTION =  "Financial Transaction

TABLES
*  RETURN =  "Return Parameter

.

IMPORTING Parameters details for BAPI_FTR_REPO_CHANGE

COMPANYCODE - Company Code

Data type: BAPI2042-COMPANY_CODE
Optional: No
Call by Reference: No ( called with pass by value option)

FINANCIALTRANSACTION - Financial Transaction

Data type: BAPI2042-TRANSACTION
Optional: No
Call by Reference: No ( called with pass by value option)

REPO - Change a Repo per BAPI

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

REPOX - Change Structure of a Repo by BAPI

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

GENERALCONTRACTDATA - Structure for changing general (product category independent) transaction data

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

GENERALCONTRACTDATAX - Change Strucutre of general contract data by BAPI

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

TESTRUN - Switch to Simulation Session for Write BAPIs

Data type: BAPI2042-TESTRUN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_FTR_REPO_CHANGE

RETURNCOMPANYCODE - Company Code

Data type: BAPI2042-COMPANY_CODE
Optional: No
Call by Reference: No ( called with pass by value option)

RETURNFINANCIALTRANSACTION - Financial Transaction

Data type: BAPI2042-TRANSACTION
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_FTR_REPO_CHANGE

RETURN - Return Parameter

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

Copy and paste ABAP code example for BAPI_FTR_REPO_CHANGE 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.

ABAP code using 7.40 inline data declarations to call FM BAPI_FTR_REPO_CHANGE

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