SAP APAR_EBPP_ISR_CREATE_USER Function Module for User über ISR anlegen
APAR_EBPP_ISR_CREATE_USER is a standard apar ebpp isr create user SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User über ISR anlegen 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 apar ebpp isr create user FM, simply by entering the name APAR_EBPP_ISR_CREATE_USER into the relevant SAP transaction such as SE37 or SE38.
Function Group: APAR_EBPP
Program Name: SAPLAPAR_EBPP
Main Program: SAPLAPAR_EBPP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function APAR_EBPP_ISR_CREATE_USER 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 'APAR_EBPP_ISR_CREATE_USER'"User über ISR anlegen.
EXPORTING
I_UNAME = "Benutzername
* I_FORCE_INIT = "Initialisierung erzwingen
* I_DUMMY1 = "
* I_DUMMY2 = "
* I_DUMMY3 = "
* I_DUMMY4 = "
* I_DUMMY5 = "
* I_DUMMY6 = "
* I_WITHOUT_ISR = "Flag (X oder Blank)
* I_REF_USER = "Benutzername
* I_PARTNER = "Biller Direct: Partnerdaten
IT_PARTNER = "Biller Direct: Partnerdaten inkl. Buchungskreis
I_ADDRESS = "Übergabestruktur für eine Adresse (speziell für EBPP)
I_SMTP_ADDRESS = "Übergabestruktur für eine SMTP-Adresse (speziell für EBPP)
* I_BUKRS = "Buchungskreis
* I_PW_LENGTH = "Passwort Länge
* I_ALPHABET = "Alphabet
* I_ALPHABET_LENGTH = "Alphabet Länge
IMPORTING
E_RETURN = "Returnparameter
E_NOTIF_NO = "Meldungsnummer
TABLES
* T_MESSAGES = "Biller Direct: Meldungen
IMPORTING Parameters details for APAR_EBPP_ISR_CREATE_USER
I_UNAME - Benutzername
Data type: UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_FORCE_INIT - Initialisierung erzwingen
Data type: AS4FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DUMMY1 -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DUMMY2 -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DUMMY3 -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DUMMY4 -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DUMMY5 -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DUMMY6 -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_WITHOUT_ISR - Flag (X oder Blank)
Data type: AS4FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REF_USER - Benutzername
Data type: UNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PARTNER - Biller Direct: Partnerdaten
Data type: EBPP_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
IT_PARTNER - Biller Direct: Partnerdaten inkl. Buchungskreis
Data type: EBPP_PARTNER_BUKRS_TOptional: No
Call by Reference: No ( called with pass by value option)
I_ADDRESS - Übergabestruktur für eine Adresse (speziell für EBPP)
Data type: APAR_EBPP_ADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
I_SMTP_ADDRESS - Übergabestruktur für eine SMTP-Adresse (speziell für EBPP)
Data type: APAR_EBPP_ADSMTPOptional: No
Call by Reference: No ( called with pass by value option)
I_BUKRS - Buchungskreis
Data type: BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PW_LENGTH - Passwort Länge
Data type: INT1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ALPHABET - Alphabet
Data type: CHAR256Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ALPHABET_LENGTH - Alphabet Länge
Data type: INT1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for APAR_EBPP_ISR_CREATE_USER
E_RETURN - Returnparameter
Data type: BAPIRET1Optional: No
Call by Reference: No ( called with pass by value option)
E_NOTIF_NO - Meldungsnummer
Data type: QMNUMOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for APAR_EBPP_ISR_CREATE_USER
T_MESSAGES - Biller Direct: Meldungen
Data type: EBPP_MESSAGESOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for APAR_EBPP_ISR_CREATE_USER 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_i_uname | TYPE UNAME, " | |||
| lv_e_return | TYPE BAPIRET1, " | |||
| lt_t_messages | TYPE STANDARD TABLE OF EBPP_MESSAGES, " | |||
| lv_i_force_init | TYPE AS4FLAG, " | |||
| lv_i_dummy1 | TYPE STRING, " | |||
| lv_i_dummy2 | TYPE STRING, " | |||
| lv_i_dummy3 | TYPE STRING, " | |||
| lv_i_dummy4 | TYPE STRING, " | |||
| lv_i_dummy5 | TYPE STRING, " | |||
| lv_i_dummy6 | TYPE STRING, " | |||
| lv_i_without_isr | TYPE AS4FLAG, " | |||
| lv_i_ref_user | TYPE UNAME, " | |||
| lv_i_partner | TYPE EBPP_PARTNER, " | |||
| lv_e_notif_no | TYPE QMNUM, " | |||
| lv_it_partner | TYPE EBPP_PARTNER_BUKRS_T, " | |||
| lv_i_address | TYPE APAR_EBPP_ADDRESS, " | |||
| lv_i_smtp_address | TYPE APAR_EBPP_ADSMTP, " | |||
| lv_i_bukrs | TYPE BUKRS, " | |||
| lv_i_pw_length | TYPE INT1, " | |||
| lv_i_alphabet | TYPE CHAR256, " | |||
| lv_i_alphabet_length | TYPE INT1. " |
|   CALL FUNCTION 'APAR_EBPP_ISR_CREATE_USER' "User über ISR anlegen |
| EXPORTING | ||
| I_UNAME | = lv_i_uname | |
| I_FORCE_INIT | = lv_i_force_init | |
| I_DUMMY1 | = lv_i_dummy1 | |
| I_DUMMY2 | = lv_i_dummy2 | |
| I_DUMMY3 | = lv_i_dummy3 | |
| I_DUMMY4 | = lv_i_dummy4 | |
| I_DUMMY5 | = lv_i_dummy5 | |
| I_DUMMY6 | = lv_i_dummy6 | |
| I_WITHOUT_ISR | = lv_i_without_isr | |
| I_REF_USER | = lv_i_ref_user | |
| I_PARTNER | = lv_i_partner | |
| IT_PARTNER | = lv_it_partner | |
| I_ADDRESS | = lv_i_address | |
| I_SMTP_ADDRESS | = lv_i_smtp_address | |
| I_BUKRS | = lv_i_bukrs | |
| I_PW_LENGTH | = lv_i_pw_length | |
| I_ALPHABET | = lv_i_alphabet | |
| I_ALPHABET_LENGTH | = lv_i_alphabet_length | |
| IMPORTING | ||
| E_RETURN | = lv_e_return | |
| E_NOTIF_NO | = lv_e_notif_no | |
| TABLES | ||
| T_MESSAGES | = lt_t_messages | |
| . " APAR_EBPP_ISR_CREATE_USER | ||
ABAP code using 7.40 inline data declarations to call FM APAR_EBPP_ISR_CREATE_USER
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