SAP ALE_PAYMENTREQUEST_CREATE Function Module for
ALE_PAYMENTREQUEST_CREATE is a standard ale paymentrequest create 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 paymentrequest create FM, simply by entering the name ALE_PAYMENTREQUEST_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: B2021
Program Name: SAPLB2021
Main Program: SAPLB2021
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALE_PAYMENTREQUEST_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_PAYMENTREQUEST_CREATE'".
EXPORTING
ORIGIN = "
* REFERENCES = "
* RELEASEPOST = 'X' "
* RELEASEPAY = 'X' "
* TESTRUN = "
* OBJ_TYPE = 'BUS2021' "
* SERIAL_ID = '0' "
ORGANISATIONS = "
ACCOUNTS = "
AMOUNTS = "
VALUEDATES = "
PAYMCONTROL = "
* CORRDOC = "
* CENTRALBANKREP = "
* INSTRUCTIONS = "
TABLES
ADDRESSDATA = "
* BANKDATA = "
* REFERENCETEXT = "
* EXTENSIONIN = "
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for ALE_PAYMENTREQUEST_CREATE
ORIGIN -
Data type: BAPI2021_ORIGINOptional: No
Call by Reference: No ( called with pass by value option)
REFERENCES -
Data type: BAPI2021_REFERENCESOptional: Yes
Call by Reference: No ( called with pass by value option)
RELEASEPOST -
Data type: BAPI2021_HELP-RELEASEPOSTDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
RELEASEPAY -
Data type: BAPI2021_HELP-RELEASEPAYDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TESTRUN -
Data type: BAPI2021_HELP-TESTRUNOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJ_TYPE -
Data type: SERIAL-OBJ_TYPEDefault: 'BUS2021'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SERIAL_ID -
Data type: SERIAL-CHNUMDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ORGANISATIONS -
Data type: BAPI2021_ORGANISATIONSOptional: No
Call by Reference: No ( called with pass by value option)
ACCOUNTS -
Data type: BAPI2021_ACCOUNTSOptional: No
Call by Reference: No ( called with pass by value option)
AMOUNTS -
Data type: BAPI2021_AMOUNTSOptional: No
Call by Reference: No ( called with pass by value option)
VALUEDATES -
Data type: BAPI2021_DATESOptional: No
Call by Reference: No ( called with pass by value option)
PAYMCONTROL -
Data type: BAPI2021_PAYMENTCTRLOptional: No
Call by Reference: No ( called with pass by value option)
CORRDOC -
Data type: BAPI2021_CORRDOCOptional: Yes
Call by Reference: No ( called with pass by value option)
CENTRALBANKREP -
Data type: BAPI2021_CENTRALBANKREPOptional: Yes
Call by Reference: No ( called with pass by value option)
INSTRUCTIONS -
Data type: BAPI2021_INSTRUCTIONSOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ALE_PAYMENTREQUEST_CREATE
ADDRESSDATA -
Data type: BAPI2021_ADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
BANKDATA -
Data type: BAPI2021_BANKOptional: Yes
Call by Reference: No ( called with pass by value option)
REFERENCETEXT -
Data type: BAPI2021_REFTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSIONIN -
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
RECEIVERS -
Data type: BDI_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_DOCUMENTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
APPLICATION_OBJECTS -
Data type: SWOTOBJIDOptional: 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_PAYMENTREQUEST_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_origin | TYPE BAPI2021_ORIGIN, " | |||
| lt_addressdata | TYPE STANDARD TABLE OF BAPI2021_ADDRESS, " | |||
| lv_error_creating_idocs | TYPE BAPI2021_ADDRESS, " | |||
| lv_references | TYPE BAPI2021_REFERENCES, " | |||
| lv_releasepost | TYPE BAPI2021_HELP-RELEASEPOST, " 'X' | |||
| lv_releasepay | TYPE BAPI2021_HELP-RELEASEPAY, " 'X' | |||
| lv_testrun | TYPE BAPI2021_HELP-TESTRUN, " | |||
| lv_obj_type | TYPE SERIAL-OBJ_TYPE, " 'BUS2021' | |||
| lv_serial_id | TYPE SERIAL-CHNUM, " '0' | |||
| lt_bankdata | TYPE STANDARD TABLE OF BAPI2021_BANK, " | |||
| lv_organisations | TYPE BAPI2021_ORGANISATIONS, " | |||
| lv_accounts | TYPE BAPI2021_ACCOUNTS, " | |||
| lt_referencetext | TYPE STANDARD TABLE OF BAPI2021_REFTEXT, " | |||
| lv_amounts | TYPE BAPI2021_AMOUNTS, " | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lv_valuedates | TYPE BAPI2021_DATES, " | |||
| lv_paymcontrol | TYPE BAPI2021_PAYMENTCTRL, " | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_corrdoc | TYPE BAPI2021_CORRDOC, " | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_centralbankrep | TYPE BAPI2021_CENTRALBANKREP, " | |||
| lv_instructions | TYPE BAPI2021_INSTRUCTIONS. " |
|   CALL FUNCTION 'ALE_PAYMENTREQUEST_CREATE' " |
| EXPORTING | ||
| ORIGIN | = lv_origin | |
| REFERENCES | = lv_references | |
| RELEASEPOST | = lv_releasepost | |
| RELEASEPAY | = lv_releasepay | |
| TESTRUN | = lv_testrun | |
| OBJ_TYPE | = lv_obj_type | |
| SERIAL_ID | = lv_serial_id | |
| ORGANISATIONS | = lv_organisations | |
| ACCOUNTS | = lv_accounts | |
| AMOUNTS | = lv_amounts | |
| VALUEDATES | = lv_valuedates | |
| PAYMCONTROL | = lv_paymcontrol | |
| CORRDOC | = lv_corrdoc | |
| CENTRALBANKREP | = lv_centralbankrep | |
| INSTRUCTIONS | = lv_instructions | |
| TABLES | ||
| ADDRESSDATA | = lt_addressdata | |
| BANKDATA | = lt_bankdata | |
| REFERENCETEXT | = lt_referencetext | |
| EXTENSIONIN | = lt_extensionin | |
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| EXCEPTIONS | ||
| ERROR_CREATING_IDOCS = 1 | ||
| . " ALE_PAYMENTREQUEST_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM ALE_PAYMENTREQUEST_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 RELEASEPOST FROM BAPI2021_HELP INTO @DATA(ld_releasepost). | ||||
| DATA(ld_releasepost) | = 'X'. | |||
| "SELECT single RELEASEPAY FROM BAPI2021_HELP INTO @DATA(ld_releasepay). | ||||
| DATA(ld_releasepay) | = 'X'. | |||
| "SELECT single TESTRUN FROM BAPI2021_HELP INTO @DATA(ld_testrun). | ||||
| "SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type). | ||||
| DATA(ld_obj_type) | = 'BUS2021'. | |||
| "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