SAP ALE_BANK_CREATE Function Module for BAPI -> IDoc: ALE_BANK_CREATE









ALE_BANK_CREATE is a standard ale bank create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: ALE_BANK_CREATE 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 ale bank create FM, simply by entering the name ALE_BANK_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function ALE_BANK_CREATE 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_BANK_CREATE'"BAPI -> IDoc: ALE_BANK_CREATE
  EXPORTING
   BANKCTRY =  "
*  BANKKEY =  "Bank Key
   BANKADDRESS =  "
*  BANKMETHOD =  "
*  BANKFORMATTING =  "
*  BANKADDRESS1 =  "
*  SERIAL_ID = '0' "

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

EXCEPTIONS
   ERROR_CREATING_IDOCS = 1
.



IMPORTING Parameters details for ALE_BANK_CREATE

BANKCTRY -

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

BANKKEY - Bank Key

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

BANKADDRESS -

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

BANKMETHOD -

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

BANKFORMATTING -

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

BANKADDRESS1 -

Data type: BAPIADDR1
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_BANK_CREATE

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_BANK_CREATE 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_bankctry  TYPE BAPI1011_KEY-BANK_CTRY, "   
lt_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lv_error_creating_idocs  TYPE BDI_LOGSYS, "   
lv_bankkey  TYPE BAPI1011_KEY-BANK_KEY, "   
lt_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_bankaddress  TYPE BAPI1011_ADDRESS, "   
lt_application_objects  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_bankmethod  TYPE BAPI1011_DETAIL-METHOD, "   
lv_bankformatting  TYPE BAPI1011_DETAIL-FORMATTING, "   
lv_bankaddress1  TYPE BAPIADDR1, "   
lv_serial_id  TYPE SERIAL-CHNUM. "   '0'

  CALL FUNCTION 'ALE_BANK_CREATE'  "BAPI -> IDoc: ALE_BANK_CREATE
    EXPORTING
         BANKCTRY = lv_bankctry
         BANKKEY = lv_bankkey
         BANKADDRESS = lv_bankaddress
         BANKMETHOD = lv_bankmethod
         BANKFORMATTING = lv_bankformatting
         BANKADDRESS1 = lv_bankaddress1
         SERIAL_ID = lv_serial_id
    TABLES
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_BANK_CREATE




ABAP code using 7.40 inline data declarations to call FM ALE_BANK_CREATE

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.

"SELECT single BANK_CTRY FROM BAPI1011_KEY INTO @DATA(ld_bankctry).
 
 
 
"SELECT single BANK_KEY FROM BAPI1011_KEY INTO @DATA(ld_bankkey).
 
 
 
 
"SELECT single METHOD FROM BAPI1011_DETAIL INTO @DATA(ld_bankmethod).
 
"SELECT single FORMATTING FROM BAPI1011_DETAIL INTO @DATA(ld_bankformatting).
 
 
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id).
DATA(ld_serial_id) = '0'.
 


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!