SAP ALE_BUPA_FS_BANK_CHANGE Function Module for

Search SAP Function Modules

ALE_BUPA_FS_BANK_CHANGE is a standard ale bupa fs bank change 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 ale bupa fs bank change FM, simply by entering the name ALE_BUPA_FS_BANK_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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

Function ALE_BUPA_FS_BANK_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 'ALE_BUPA_FS_BANK_CHANGE'"
  EXPORTING
   BUSINESSPARTNER =  "Business Partner ID for BAPI
   BANKATTRIBUTE =  "Business Partner: Bank Details (Partner = Bank)
*  CHANGEDOCU =  "FSBP: BAPI Structure for General Switches and Data
*  TESTRUN =  "Switch to Simulation Session for Write BAPIs
   BANKATTRIBUTECHANGE =  "FS-BP: BAPI Structure for TR Org. Attributes, Update Bar
*  OBJ_TYPE = 'BUSISB990' "
*  SERIAL_ID = '0' "

TABLES
   RECEIVERS =  "
*  COMMUNICATION_DOCUMENTS =  "
*  APPLICATION_OBJECTS =  "

EXCEPTIONS
   ERROR_CREATING_IDOCS = 1 

.

IMPORTING Parameters details for ALE_BUPA_FS_BANK_CHANGE

BUSINESSPARTNER - Business Partner ID for BAPI

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

BANKATTRIBUTE - Business Partner: Bank Details (Partner = Bank)

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

CHANGEDOCU - FSBP: BAPI Structure for General Switches and Data

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

TESTRUN - Switch to Simulation Session for Write BAPIs

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

BANKATTRIBUTECHANGE - FS-BP: BAPI Structure for TR Org. Attributes, Update Bar

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

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'BUSISB990'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_BUPA_FS_BANK_CHANGE

RECEIVERS -

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

COMMUNICATION_DOCUMENTS -

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

APPLICATION_OBJECTS -

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

EXCEPTIONS details

ERROR_CREATING_IDOCS -

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

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