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

Function ALE_PATIENT_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_PATIENT_CREATE'".
EXPORTING
CLIENT = "Client
* INSTITUTION = '*' "Institution
* PATIENTID = ' ' "Patient Number
PATIENTDATA = "
* TESTRUN = ' ' "Test Mode (No Changes in Database)
* TRANSACTMODE = 'N' "
* SERIAL_ID = '0' "
TABLES
* IADDRESSES = "
* IADDPHONES = "
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for ALE_PATIENT_CREATE
CLIENT - Client
Data type: BAPINALL-CLIENTOptional: No
Call by Reference: No ( called with pass by value option)
INSTITUTION - Institution
Data type: BAPI1084SRCH-INSTITUTIONDefault: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)
PATIENTID - Patient Number
Data type: BAPI1084OUT-PATIENTIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PATIENTDATA -
Data type: BAPI1084INOptional: No
Call by Reference: No ( called with pass by value option)
TESTRUN - Test Mode (No Changes in Database)
Data type: BAPINALL-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TRANSACTMODE -
Data type: BAPINALL-TRANSACT_MODEDefault: 'N'
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)
TABLES Parameters details for ALE_PATIENT_CREATE
IADDRESSES -
Data type: BAPINADDROptional: Yes
Call by Reference: No ( called with pass by value option)
IADDPHONES -
Data type: BAPINADDR2Optional: 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_PATIENT_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_client | TYPE BAPINALL-CLIENT, " | |||
| lt_iaddresses | TYPE STANDARD TABLE OF BAPINADDR, " | |||
| lv_error_creating_idocs | TYPE BAPINADDR, " | |||
| lt_iaddphones | TYPE STANDARD TABLE OF BAPINADDR2, " | |||
| lv_institution | TYPE BAPI1084SRCH-INSTITUTION, " '*' | |||
| lv_patientid | TYPE BAPI1084OUT-PATIENTID, " SPACE | |||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lv_patientdata | TYPE BAPI1084IN, " | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_testrun | TYPE BAPINALL-TESTRUN, " SPACE | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_transactmode | TYPE BAPINALL-TRANSACT_MODE, " 'N' | |||
| lv_serial_id | TYPE SERIAL-CHNUM. " '0' |
|   CALL FUNCTION 'ALE_PATIENT_CREATE' " |
| EXPORTING | ||
| CLIENT | = lv_client | |
| INSTITUTION | = lv_institution | |
| PATIENTID | = lv_patientid | |
| PATIENTDATA | = lv_patientdata | |
| TESTRUN | = lv_testrun | |
| TRANSACTMODE | = lv_transactmode | |
| SERIAL_ID | = lv_serial_id | |
| TABLES | ||
| IADDRESSES | = lt_iaddresses | |
| IADDPHONES | = lt_iaddphones | |
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| EXCEPTIONS | ||
| ERROR_CREATING_IDOCS = 1 | ||
| . " ALE_PATIENT_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM ALE_PATIENT_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 CLIENT FROM BAPINALL INTO @DATA(ld_client). | ||||
| "SELECT single INSTITUTION FROM BAPI1084SRCH INTO @DATA(ld_institution). | ||||
| DATA(ld_institution) | = '*'. | |||
| "SELECT single PATIENTID FROM BAPI1084OUT INTO @DATA(ld_patientid). | ||||
| DATA(ld_patientid) | = ' '. | |||
| "SELECT single TESTRUN FROM BAPINALL INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
| "SELECT single TRANSACT_MODE FROM BAPINALL INTO @DATA(ld_transactmode). | ||||
| DATA(ld_transactmode) | = 'N'. | |||
| "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