SAP IDOC_OUTPUT_DESADT Function Module for EDI outbound: shipping notification (DESADV)
IDOC_OUTPUT_DESADT is a standard idoc output desadt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for EDI outbound: shipping notification (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 idoc output desadt FM, simply by entering the name IDOC_OUTPUT_DESADT into the relevant SAP transaction such as SE37 or SE38.
Function Group: VED2
Program Name: SAPLVED2
Main Program: SAPLVED2
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IDOC_OUTPUT_DESADT 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_OUTPUT_DESADT'"EDI outbound: shipping notification (DESADV).
EXPORTING
CONTROL_RECORD_IN = "Document number of order in SD
OBJECT = "EDI partner information for output
IMPORTING
CONTROL_RECORD_OUT = "Control record for EDI
OBJECT_TYPE = "Object type for workflow link
TABLES
INT_EDIDD = "
EXCEPTIONS
CODE_NOT_IN_CODELIST = 1 WRONG_INTERMEDIATE_DOCUMENT = 10 EDI_DOCUMENT_NOT_CLOSED = 2 IDENTIFIER_INVALID = 3 NO_ORDERING_PARTY = 4 PARAMETER_ERROR = 5 PARTNER_DATA_ERROR = 6 PROGRAM_ERROR = 7 RECEIVER_INVALID = 8 SENDER_INVALID = 9
IMPORTING Parameters details for IDOC_OUTPUT_DESADT
CONTROL_RECORD_IN - Document number of order in SD
Data type: EDIDCOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT - EDI partner information for output
Data type: NASTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for IDOC_OUTPUT_DESADT
CONTROL_RECORD_OUT - Control record for EDI
Data type: EDIDCOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_TYPE - Object type for workflow link
Data type: TOJTB-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for IDOC_OUTPUT_DESADT
INT_EDIDD -
Data type: EDIDDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CODE_NOT_IN_CODELIST - Error during translation into external code
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_INTERMEDIATE_DOCUMENT - Incorrect intermediate document category at input
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EDI_DOCUMENT_NOT_CLOSED - Error when closing intermediate document
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IDENTIFIER_INVALID - IDoc number not correct (Basis error)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ORDERING_PARTY - Ordering party not in document (Table VBPA)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAMETER_ERROR - Wrong parameter during transfer of a segment
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_DATA_ERROR - Partner has no external number or address
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROGRAM_ERROR - Program error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RECEIVER_INVALID - Recipient does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SENDER_INVALID - Sender does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IDOC_OUTPUT_DESADT 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_int_edidd | TYPE STANDARD TABLE OF EDIDD, " | |||
| lv_control_record_in | TYPE EDIDC, " | |||
| lv_control_record_out | TYPE EDIDC, " | |||
| lv_code_not_in_codelist | TYPE EDIDC, " | |||
| lv_wrong_intermediate_document | TYPE EDIDC, " | |||
| lv_object | TYPE NAST, " | |||
| lv_object_type | TYPE TOJTB-NAME, " | |||
| lv_edi_document_not_closed | TYPE TOJTB, " | |||
| lv_identifier_invalid | TYPE TOJTB, " | |||
| lv_no_ordering_party | TYPE TOJTB, " | |||
| lv_parameter_error | TYPE TOJTB, " | |||
| lv_partner_data_error | TYPE TOJTB, " | |||
| lv_program_error | TYPE TOJTB, " | |||
| lv_receiver_invalid | TYPE TOJTB, " | |||
| lv_sender_invalid | TYPE TOJTB. " |
|   CALL FUNCTION 'IDOC_OUTPUT_DESADT' "EDI outbound: shipping notification (DESADV) |
| EXPORTING | ||
| CONTROL_RECORD_IN | = lv_control_record_in | |
| OBJECT | = lv_object | |
| IMPORTING | ||
| CONTROL_RECORD_OUT | = lv_control_record_out | |
| OBJECT_TYPE | = lv_object_type | |
| TABLES | ||
| INT_EDIDD | = lt_int_edidd | |
| EXCEPTIONS | ||
| CODE_NOT_IN_CODELIST = 1 | ||
| WRONG_INTERMEDIATE_DOCUMENT = 10 | ||
| EDI_DOCUMENT_NOT_CLOSED = 2 | ||
| IDENTIFIER_INVALID = 3 | ||
| NO_ORDERING_PARTY = 4 | ||
| PARAMETER_ERROR = 5 | ||
| PARTNER_DATA_ERROR = 6 | ||
| PROGRAM_ERROR = 7 | ||
| RECEIVER_INVALID = 8 | ||
| SENDER_INVALID = 9 | ||
| . " IDOC_OUTPUT_DESADT | ||
ABAP code using 7.40 inline data declarations to call FM IDOC_OUTPUT_DESADT
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 NAME FROM TOJTB INTO @DATA(ld_object_type). | ||||
Search for further information about these or an SAP related objects