SAP IDOC_INPUT_REQOTE Function Module for









IDOC_INPUT_REQOTE is a standard idoc input reqote 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 reqote FM, simply by entering the name IDOC_INPUT_REQOTE into the relevant SAP transaction such as SE37 or SE38.

Function Group: VEDQ
Program Name: SAPLVEDQ
Main Program: SAPLVEDQ
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function IDOC_INPUT_REQOTE 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_REQOTE'"
  EXPORTING
   INPUT_METHOD =  "Method: Background, foreground etc
   MASS_PROCESSING =  "Flag: Mass input

 IMPORTING
   WORKFLOW_RESULT =  "Method result for workflow
   APPLICATION_VARIABLE =  "Application variable
   IN_UPDATE_TASK =  "Flag: Programs called in update task
   CALL_TRANSACTION_DONE =  "Flag: Call transaction called
   DOCUMENT_NUMBER =  "

TABLES
   IDOC_CONTRL =  "IDoc control records
   IDOC_DATA =  "IDoc data records
   IDOC_STATUS =  "IDoc status records
   RETURN_VARIABLES =  "Result variables with values for workflow
   SERIALIZATION_INFO =  "Serialization info - not used
*  EDI_TEXT =  "
*  EDI_TEXT_LINES =  "
.


IDoc processing FM

This FM is the Processing Function module for IDoc: ORDERS01
ORDERS01 - Purchasing/Sales
ORDERS01 - Purchasing/Sales
ORDERS02 - Purchasing/Sales
ORDERS02 - Purchasing/Sales
ORDERS03 - Purchasing/Sales
ORDERS04 - Purchasing/Sales
ORDERS05 - Purchasing/Sales

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLVEDQ_001 SD EDI Inquiry Inbox: Read Additional Data from IDOC
EXIT_SAPLVEDQ_002 SD EDI Inquiry Inbox: Schedule Additional Data for Screen
EXIT_SAPLVEDQ_003 SD EDI: Inquiry Inbox: Additional Sales Activities Call Transaction VA21
EXIT_SAPLVEDQ_004 SD EDI Inquiry Inbox: Final Sales Activities per Inquiry
EXIT_SAPLVEDQ_005 SD EDI Inquiry Inbox: Final Sales Activities (Mass Processing)
EXIT_SAPLVEDQ_006 SD EDI Inquiry Inbox: Set Quotation Type
EXIT_SAPLVEDQ_007 SD EDI Inquiry Inbox: Create Customer Number/Sales Area
EXIT_SAPLVEDQ_008 SD EDI: Inquiry Inbox: Manipulation of Error Table in Processing
EXIT_SAPLVEDQ_009 SD EDI Inquiry Inbox: Additional Check for IDoc Segments
EXIT_SAPLVEDQ_010 SD EDI Inquiry Inbox: Manipulation of Status Table
EXIT_SAPLVEDQ_011 SD EDI Inquiry Inbox: Final Processing of Internal Error Tables
EXIT_SAPLVEDQ_012 SD EDI Inquiry Inbox: Change Internal Table Configurable Materials

IMPORTING Parameters details for IDOC_INPUT_REQOTE

INPUT_METHOD - Method: Background, foreground etc

Data type: BDWFAP_PAR-INPUTMETHD
Optional: No
Call by Reference: No ( called with pass by value option)

MASS_PROCESSING - Flag: Mass input

Data type: BDWFAP_PAR-MASS_PROC
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for IDOC_INPUT_REQOTE

WORKFLOW_RESULT - Method result for workflow

Data type: BDWFAP_PAR-RESULT
Optional: No
Call by Reference: No ( called with pass by value option)

APPLICATION_VARIABLE - Application variable

Data type: BDWFAP_PAR-APPL_VAR
Optional: No
Call by Reference: No ( called with pass by value option)

IN_UPDATE_TASK - Flag: Programs called in update task

Data type: BDWFAP_PAR-UPDATETASK
Optional: No
Call by Reference: No ( called with pass by value option)

CALL_TRANSACTION_DONE - Flag: Call transaction called

Data type: BDWFAP_PAR-CALLTRANS
Optional: No
Call by Reference: No ( called with pass by value option)

DOCUMENT_NUMBER -

Data type: VBAK-VBELN
Optional: No
Call by Reference: Yes

TABLES Parameters details for IDOC_INPUT_REQOTE

IDOC_CONTRL - IDoc control records

Data type: EDIDC
Optional: No
Call by Reference: No ( called with pass by value option)

IDOC_DATA - IDoc data records

Data type: EDIDD
Optional: No
Call by Reference: No ( called with pass by value option)

IDOC_STATUS - IDoc status records

Data type: BDIDOCSTAT
Optional: No
Call by Reference: No ( called with pass by value option)

RETURN_VARIABLES - Result variables with values for workflow

Data type: BDWFRETVAR
Optional: No
Call by Reference: No ( called with pass by value option)

SERIALIZATION_INFO - Serialization info - not used

Data type: BDI_SER
Optional: No
Call by Reference: No ( called with pass by value option)

EDI_TEXT -

Data type: EDIORDTXT1
Optional: Yes
Call by Reference: No ( called with pass by value option)

EDI_TEXT_LINES -

Data type: EDIORDTXT2
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for IDOC_INPUT_REQOTE 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, "   
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, "   
lv_document_number  TYPE VBAK-VBELN, "   
lt_serialization_info  TYPE STANDARD TABLE OF BDI_SER, "   
lt_edi_text  TYPE STANDARD TABLE OF EDIORDTXT1, "   
lt_edi_text_lines  TYPE STANDARD TABLE OF EDIORDTXT2. "   

  CALL FUNCTION 'IDOC_INPUT_REQOTE'  "
    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
         DOCUMENT_NUMBER = lv_document_number
    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
         EDI_TEXT = lt_edi_text
         EDI_TEXT_LINES = lt_edi_text_lines
. " IDOC_INPUT_REQOTE




ABAP code using 7.40 inline data declarations to call FM IDOC_INPUT_REQOTE

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).
 
"SELECT single VBELN FROM VBAK INTO @DATA(ld_document_number).
 
 
 
 

See full list of SAP IDocs

See full list of SAP Function Modules



Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!