SAP Function Modules
IDOC_INPUT_PATIENT_CREATE SAP Function module
IDOC_INPUT_PATIENT_CREATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name IDOC_INPUT_PATIENT_CREATE into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
1084
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM IDOC_INPUT_PATIENT_CREATE - IDOC INPUT PATIENT CREATE
CALL FUNCTION 'IDOC_INPUT_PATIENT_CREATE' "
EXPORTING
input_method = " bdwfap_par-inputmethd
mass_processing = " bdwfap_par-mass_proc
IMPORTING
workflow_result = " bdwf_param-result
application_variable = " bdwf_param-appl_var
in_update_task = " bdwfap_par-updatetask
call_transaction_done = " bdwfap_par-calltrans
TABLES
idoc_contrl = " edidc
idoc_data = " edidd
idoc_status = " bdidocstat
return_variables = " bdwfretvar
serialization_info = " bdi_ser
EXCEPTIONS
WRONG_FUNCTION_CALLED = 1 "
. " IDOC_INPUT_PATIENT_CREATE
ABAP code example for Function Module IDOC_INPUT_PATIENT_CREATE
The ABAP code below is a full code listing to execute function module IDOC_INPUT_PATIENT_CREATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_workflow_result | TYPE BDWF_PARAM-RESULT , |
| ld_application_variable | TYPE BDWF_PARAM-APPL_VAR , |
| ld_in_update_task | TYPE BDWFAP_PAR-UPDATETASK , |
| ld_call_transaction_done | TYPE BDWFAP_PAR-CALLTRANS , |
| it_idoc_contrl | TYPE STANDARD TABLE OF EDIDC,"TABLES PARAM |
| wa_idoc_contrl | LIKE LINE OF it_idoc_contrl , |
| it_idoc_data | TYPE STANDARD TABLE OF EDIDD,"TABLES PARAM |
| wa_idoc_data | LIKE LINE OF it_idoc_data , |
| it_idoc_status | TYPE STANDARD TABLE OF BDIDOCSTAT,"TABLES PARAM |
| wa_idoc_status | LIKE LINE OF it_idoc_status , |
| it_return_variables | TYPE STANDARD TABLE OF BDWFRETVAR,"TABLES PARAM |
| wa_return_variables | LIKE LINE OF it_return_variables , |
| it_serialization_info | TYPE STANDARD TABLE OF BDI_SER,"TABLES PARAM |
| wa_serialization_info | LIKE LINE OF it_serialization_info . |
DATA(ld_input_method) = some text here
DATA(ld_mass_processing) = some text here
"populate fields of struture and append to itab
append wa_idoc_contrl to it_idoc_contrl.
"populate fields of struture and append to itab
append wa_idoc_data to it_idoc_data.
"populate fields of struture and append to itab
append wa_idoc_status to it_idoc_status.
"populate fields of struture and append to itab
append wa_return_variables to it_return_variables.
"populate fields of struture and append to itab
append wa_serialization_info to it_serialization_info. . CALL FUNCTION 'IDOC_INPUT_PATIENT_CREATE' EXPORTING input_method = ld_input_method mass_processing = ld_mass_processing IMPORTING workflow_result = ld_workflow_result application_variable = ld_application_variable in_update_task = ld_in_update_task call_transaction_done = ld_call_transaction_done TABLES idoc_contrl = it_idoc_contrl idoc_data = it_idoc_data idoc_status = it_idoc_status return_variables = it_return_variables serialization_info = it_serialization_info EXCEPTIONS WRONG_FUNCTION_CALLED = 1 . " IDOC_INPUT_PATIENT_CREATE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_workflow_result | TYPE BDWF_PARAM-RESULT , |
| ld_input_method | TYPE BDWFAP_PAR-INPUTMETHD , |
| it_idoc_contrl | TYPE STANDARD TABLE OF EDIDC , |
| wa_idoc_contrl | LIKE LINE OF it_idoc_contrl, |
| ld_application_variable | TYPE BDWF_PARAM-APPL_VAR , |
| ld_mass_processing | TYPE BDWFAP_PAR-MASS_PROC , |
| it_idoc_data | TYPE STANDARD TABLE OF EDIDD , |
| wa_idoc_data | LIKE LINE OF it_idoc_data, |
| ld_in_update_task | TYPE BDWFAP_PAR-UPDATETASK , |
| it_idoc_status | TYPE STANDARD TABLE OF BDIDOCSTAT , |
| wa_idoc_status | LIKE LINE OF it_idoc_status, |
| ld_call_transaction_done | TYPE BDWFAP_PAR-CALLTRANS , |
| it_return_variables | TYPE STANDARD TABLE OF BDWFRETVAR , |
| wa_return_variables | LIKE LINE OF it_return_variables, |
| it_serialization_info | TYPE STANDARD TABLE OF BDI_SER , |
| wa_serialization_info | LIKE LINE OF it_serialization_info. |
ld_input_method = some text here
"populate fields of struture and append to itab
append wa_idoc_contrl to it_idoc_contrl.
ld_mass_processing = some text here
"populate fields of struture and append to itab
append wa_idoc_data to it_idoc_data.
"populate fields of struture and append to itab
append wa_idoc_status to it_idoc_status.
"populate fields of struture and append to itab
append wa_return_variables to it_return_variables.
"populate fields of struture and append to itab
append wa_serialization_info to it_serialization_info.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name IDOC_INPUT_PATIENT_CREATE or its description.