IDOC_OUTPUT_ORDERS SAP Function module

IDOC_OUTPUT_ORDERS 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_OUTPUT_ORDERS into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: EINM
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM IDOC_OUTPUT_ORDERS - IDOC OUTPUT ORDERS

CALL FUNCTION 'IDOC_OUTPUT_ORDERS' "
  EXPORTING
    object =                    " nast          Complete current NAST record
    control_record_in =         " edidc         Control record filled with recipient info
  IMPORTING
    object_type =               " wfas1-asgtp   Document category for definition of transaction/event
    control_record_out =        " edidc         Extended control record with sender information
  TABLES
    int_edidd =                 " edidd         Internal table for IDoc
  EXCEPTIONS
    ERROR_MESSAGE_RECEIVED = 1  "               Error Occurred on Output Processing
    DATA_NOT_RELEVANT_FOR_SENDING = 2  "
    .  "  IDOC_OUTPUT_ORDERS

ABAP code example for Function Module IDOC_OUTPUT_ORDERS

The ABAP code below is a full code listing to execute function module IDOC_OUTPUT_ORDERS 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).

DATA:
ld_object_type  
 
 TYPE WFAS1-ASGTP
,
ld_control_record_out  
 
 TYPE EDIDC
,
it_int_edidd  
 
 TYPE STANDARD TABLE OF EDIDD,"TABLES PARAM
wa_int_edidd
 
 LIKE LINE OF it_int_edidd
.


DATA(ld_object) = 'Check type of data required'.

DATA(ld_control_record_in) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_int_edidd to it_int_edidd.
.

CALL FUNCTION 'IDOC_OUTPUT_ORDERS'
  EXPORTING
    object =                     ld_object
    control_record_in =          ld_control_record_in
  IMPORTING
    object_type =                ld_object_type
    control_record_out =         ld_control_record_out
  TABLES
    int_edidd =                  it_int_edidd
  EXCEPTIONS
    ERROR_MESSAGE_RECEIVED =     1
    DATA_NOT_RELEVANT_FOR_SENDING =    2
    .  "  IDOC_OUTPUT_ORDERS

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "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_object_type
 
 TYPE WFAS1-ASGTP ,
ld_object
 
 TYPE NAST ,
it_int_edidd
 
 TYPE STANDARD TABLE OF EDIDD ,
wa_int_edidd
 
 LIKE LINE OF it_int_edidd,
ld_control_record_out
 
 TYPE EDIDC ,
ld_control_record_in
 
 TYPE EDIDC .


ld_object = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_int_edidd to it_int_edidd.
ld_control_record_in = 'Check type of data required'.