SAP BORES_IDOC_INPUT_DESADV1 Function Module for NOTRANSL: Schnittstelle Lieferung: Eingang DESADV
BORES_IDOC_INPUT_DESADV1 is a standard bores idoc input desadv1 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Schnittstelle Lieferung: Eingang DESADV 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 bores idoc input desadv1 FM, simply by entering the name BORES_IDOC_INPUT_DESADV1 into the relevant SAP transaction such as SE37 or SE38.
Function Group: BORES
Program Name: SAPLBORES
Main Program: SAPLBORES
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BORES_IDOC_INPUT_DESADV1 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 'BORES_IDOC_INPUT_DESADV1'"NOTRANSL: Schnittstelle Lieferung: Eingang DESADV.
EXPORTING
INPUT_METHOD = "Method: Background/Foreground processing, etc.
MASS_PROCESSING = "Flag: Mass input (otherwise single input)
IMPORTING
WORKFLOW_RESULT = "
APPLICATION_VARIABLE = "Application Variable
IN_UPDATE_TASK = "Flag: Process IDocs using update
CALL_TRANSACTION_DONE = "
TABLES
IDOC_CONTRL = "IDoc control records
IDOC_DATA = "
IDOC_STATUS = "IDoc Status Records
RETURN_VARIABLES = "
SERIALIZATION_INFO = "
EXCEPTIONS
WRONG_FUNCTION_CALLED = 1
IMPORTING Parameters details for BORES_IDOC_INPUT_DESADV1
INPUT_METHOD - Method: Background/Foreground processing, etc.
Data type: BDWFAP_PAR-INPUTMETHDOptional: No
Call by Reference: No ( called with pass by value option)
MASS_PROCESSING - Flag: Mass input (otherwise single input)
Data type: BDWFAP_PAR-MASS_PROCOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BORES_IDOC_INPUT_DESADV1
WORKFLOW_RESULT -
Data type: BDWFAP_PAR-RESULTOptional: No
Call by Reference: No ( called with pass by value option)
APPLICATION_VARIABLE - Application Variable
Data type: BDWFAP_PAR-APPL_VAROptional: No
Call by Reference: No ( called with pass by value option)
IN_UPDATE_TASK - Flag: Process IDocs using update
Data type: BDWFAP_PAR-UPDATETASKOptional: No
Call by Reference: No ( called with pass by value option)
CALL_TRANSACTION_DONE -
Data type: BDWFAP_PAR-CALLTRANSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BORES_IDOC_INPUT_DESADV1
IDOC_CONTRL - IDoc control records
Data type: EDIDCOptional: No
Call by Reference: No ( called with pass by value option)
IDOC_DATA -
Data type: EDIDDOptional: No
Call by Reference: No ( called with pass by value option)
IDOC_STATUS - IDoc Status Records
Data type: BDIDOCSTATOptional: No
Call by Reference: No ( called with pass by value option)
RETURN_VARIABLES -
Data type: BDWFRETVAROptional: No
Call by Reference: No ( called with pass by value option)
SERIALIZATION_INFO -
Data type: BDI_SEROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_FUNCTION_CALLED - System cannot process IDocs
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BORES_IDOC_INPUT_DESADV1 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 BDWFAP_PAR-RESULT, " | |||
| lv_wrong_function_called | TYPE BDWFAP_PAR, " | |||
| lt_idoc_data | TYPE STANDARD TABLE OF EDIDD, " | |||
| lv_mass_processing | TYPE BDWFAP_PAR-MASS_PROC, " | |||
| lv_application_variable | TYPE BDWFAP_PAR-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 'BORES_IDOC_INPUT_DESADV1' "NOTRANSL: Schnittstelle Lieferung: Eingang DESADV |
| 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 | |
| EXCEPTIONS | ||
| WRONG_FUNCTION_CALLED = 1 | ||
| . " BORES_IDOC_INPUT_DESADV1 | ||
ABAP code using 7.40 inline data declarations to call FM BORES_IDOC_INPUT_DESADV1
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 BDWFAP_PAR INTO @DATA(ld_workflow_result). | ||||
| "SELECT single MASS_PROC FROM BDWFAP_PAR INTO @DATA(ld_mass_processing). | ||||
| "SELECT single APPL_VAR FROM BDWFAP_PAR 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). | ||||
Search for further information about these or an SAP related objects