SAP COMMUNICATION_IDOC_CREATE Function Module for

Search SAP Function Modules

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

Function Group: BD11
Program Name: SAPLBD11
Main Program: SAPLBD11
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COMMUNICATION_IDOC_CREATE 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 'COMMUNICATION_IDOC_CREATE'"
  EXPORTING
*  ERROR_FLAG = ' ' "
*  DATA_BASE_FLAG = ' ' "
*  FORWARDED_FLAG = ' ' "
*  OBJ_TYPE =  "
*  CHNUM =  "

TABLES
   IDOC_CONTROL =  "
   IDOC_DATA =  "

EXCEPTIONS
   ERROR_IN_IDOC_DATA_SEGMENTS = 1    ERROR_IN_IDOC_CONTROL_RECORD = 2    ERROR_WRITING_STATUS_RECORDS = 3    ERROR_WRITING_IDOC = 4    RECEIVER_NOT_AUTHORIZED = 5 

.

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_SAPLBD11_001 User Exit for IDoc Version Change

IMPORTING Parameters details for COMMUNICATION_IDOC_CREATE

ERROR_FLAG -

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

DATA_BASE_FLAG -

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

FORWARDED_FLAG -

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

OBJ_TYPE -

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

CHNUM -

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

TABLES Parameters details for COMMUNICATION_IDOC_CREATE

IDOC_CONTROL -

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

IDOC_DATA -

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

EXCEPTIONS details

ERROR_IN_IDOC_DATA_SEGMENTS -

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

ERROR_IN_IDOC_CONTROL_RECORD -

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

ERROR_WRITING_STATUS_RECORDS -

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

ERROR_WRITING_IDOC -

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

RECEIVER_NOT_AUTHORIZED -

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

Copy and paste ABAP code example for COMMUNICATION_IDOC_CREATE 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.

ABAP code using 7.40 inline data declarations to call FM COMMUNICATION_IDOC_CREATE

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.

Search for further information about these or an SAP related objects