SAP IDOC_INPUT_PLL40 Function Module for
IDOC_INPUT_PLL40 is a standard idoc input pll40 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 idoc input pll40 FM, simply by entering the name IDOC_INPUT_PLL40 into the relevant SAP transaction such as SE37 or SE38.
Function Group: RP94
Program Name: SAPLRP94
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IDOC_INPUT_PLL40 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 'IDOC_INPUT_PLL40'".
EXPORTING
INPUT_METHOD = "Should data be processed in foreground or background
MASS_PROCESSING = "Show whether mass entry - several IDocs
IMPORTING
WORKFLOW_RESULT = "?
APPLICATION_VARIABLE = "Not yet used
IN_UPDATE_TASK = "Show that update process started - by COMMIT
CALL_TRANSACTION_DONE = "Show whether input via CALL TRANSACTION
TABLES
IDOC_CONTRL = "Individual IDoc control records
IDOC_DATA = "Internal table with IDoc data
IDOC_STATUS = "Status table for data update
RETURN_VARIABLES = "Assignment table - IDoc <-> Application doc.
SERIALIZATION_INFO = "Serialization information - if required
IDoc processing FM
This FM is the Processing Function module for IDoc: HRPLL40HRPLL40 - Logistics confirmations for Human Resource Management
HRPLL40 - Logistics confirmations for Human Resource Management
IMPORTING Parameters details for IDOC_INPUT_PLL40
INPUT_METHOD - Should data be processed in foreground or background
Data type: BDWFAP_PAR-INPUTMETHDOptional: No
Call by Reference: No ( called with pass by value option)
MASS_PROCESSING - Show whether mass entry - several IDocs
Data type: BDWFAP_PAR-MASS_PROCOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for IDOC_INPUT_PLL40
WORKFLOW_RESULT - ?
Data type: BDWF_PARAM-RESULTOptional: No
Call by Reference: No ( called with pass by value option)
APPLICATION_VARIABLE - Not yet used
Data type: BDWF_PARAM-APPL_VAROptional: No
Call by Reference: No ( called with pass by value option)
IN_UPDATE_TASK - Show that update process started - by COMMIT
Data type: BDWFAP_PAR-UPDATETASKOptional: No
Call by Reference: No ( called with pass by value option)
CALL_TRANSACTION_DONE - Show whether input via CALL TRANSACTION
Data type: BDWFAP_PAR-CALLTRANSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for IDOC_INPUT_PLL40
IDOC_CONTRL - Individual IDoc control records
Data type: EDIDCOptional: No
Call by Reference: No ( called with pass by value option)
IDOC_DATA - Internal table with IDoc data
Data type: EDIDDOptional: No
Call by Reference: No ( called with pass by value option)
IDOC_STATUS - Status table for data update
Data type: BDIDOCSTATOptional: No
Call by Reference: No ( called with pass by value option)
RETURN_VARIABLES - Assignment table - IDoc <-> Application doc.
Data type: BDWFRETVAROptional: No
Call by Reference: No ( called with pass by value option)
SERIALIZATION_INFO - Serialization information - if required
Data type: BDI_SEROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IDOC_INPUT_PLL40 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: | ||||
| lt_idoc_contrl | TYPE STANDARD TABLE OF EDIDC, " | |||
| lv_input_method | TYPE BDWFAP_PAR-INPUTMETHD, " | |||
| lv_workflow_result | TYPE BDWF_PARAM-RESULT, " | |||
| lt_idoc_data | TYPE STANDARD TABLE OF EDIDD, " | |||
| lv_mass_processing | TYPE BDWFAP_PAR-MASS_PROC, " | |||
| lv_application_variable | TYPE BDWF_PARAM-APPL_VAR, " | |||
| lt_idoc_status | TYPE STANDARD TABLE OF BDIDOCSTAT, " | |||
| lv_in_update_task | TYPE BDWFAP_PAR-UPDATETASK, " | |||
| lt_return_variables | TYPE STANDARD TABLE OF BDWFRETVAR, " | |||
| lv_call_transaction_done | TYPE BDWFAP_PAR-CALLTRANS, " | |||
| lt_serialization_info | TYPE STANDARD TABLE OF BDI_SER. " |
|   CALL FUNCTION 'IDOC_INPUT_PLL40' " |
| EXPORTING | ||
| INPUT_METHOD | = lv_input_method | |
| MASS_PROCESSING | = lv_mass_processing | |
| IMPORTING | ||
| WORKFLOW_RESULT | = lv_workflow_result | |
| APPLICATION_VARIABLE | = lv_application_variable | |
| IN_UPDATE_TASK | = lv_in_update_task | |
| CALL_TRANSACTION_DONE | = lv_call_transaction_done | |
| TABLES | ||
| IDOC_CONTRL | = lt_idoc_contrl | |
| IDOC_DATA | = lt_idoc_data | |
| IDOC_STATUS | = lt_idoc_status | |
| RETURN_VARIABLES | = lt_return_variables | |
| SERIALIZATION_INFO | = lt_serialization_info | |
| . " IDOC_INPUT_PLL40 | ||
ABAP code using 7.40 inline data declarations to call FM IDOC_INPUT_PLL40
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 INPUTMETHD FROM BDWFAP_PAR INTO @DATA(ld_input_method). | ||||
| "SELECT single RESULT FROM BDWF_PARAM INTO @DATA(ld_workflow_result). | ||||
| "SELECT single MASS_PROC FROM BDWFAP_PAR INTO @DATA(ld_mass_processing). | ||||
| "SELECT single APPL_VAR FROM BDWF_PARAM INTO @DATA(ld_application_variable). | ||||
| "SELECT single UPDATETASK FROM BDWFAP_PAR INTO @DATA(ld_in_update_task). | ||||
| "SELECT single CALLTRANS FROM BDWFAP_PAR INTO @DATA(ld_call_transaction_done). | ||||
See full list of SAP IDocs
See full list of SAP Function Modules
Search for further information about these or an SAP related objects