SAP IDOCTYPE_CREATE Function Module for









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

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



Function IDOCTYPE_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 'IDOCTYPE_CREATE'"
EXPORTING
PI_IDOCTYP = "Basic Type
* PI_DEVCLASS = "Package
PI_ATTRIBUTES = "
* WI_SET_GENFLAG = ' ' "

IMPORTING
PE_ATTRIBUTES = "

CHANGING
* PC_ORDER = "Request

TABLES
PT_SYNTAX = "

EXCEPTIONS
OBJECT_NOT_FOUND = 1 OBJECT_EXISTS = 2 ACTION_NOT_POSSIBLE = 3 SYNTAX_ERROR = 4 SEGMENT_ERROR = 5 TRANSPORT_ERROR = 6 DB_ERROR = 7 NO_AUTHORITY = 8
.



IMPORTING Parameters details for IDOCTYPE_CREATE

PI_IDOCTYP - Basic Type

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

PI_DEVCLASS - Package

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

PI_ATTRIBUTES -

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

WI_SET_GENFLAG -

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

EXPORTING Parameters details for IDOCTYPE_CREATE

PE_ATTRIBUTES -

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

CHANGING Parameters details for IDOCTYPE_CREATE

PC_ORDER - Request

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

TABLES Parameters details for IDOCTYPE_CREATE

PT_SYNTAX -

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

EXCEPTIONS details

OBJECT_NOT_FOUND -

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

OBJECT_EXISTS -

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

ACTION_NOT_POSSIBLE -

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

SYNTAX_ERROR -

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

SEGMENT_ERROR -

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

TRANSPORT_ERROR -

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

DB_ERROR - Database Error

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

NO_AUTHORITY -

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

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

DATA:
lv_pc_order  TYPE EDI_IAPI00-TRKORR, "   
lt_pt_syntax  TYPE STANDARD TABLE OF EDI_IAPI02, "   
lv_pi_idoctyp  TYPE EDI_IAPI00-IDOCTYP, "   
lv_pe_attributes  TYPE EDI_IAPI01, "   
lv_object_not_found  TYPE EDI_IAPI01, "   
lv_pi_devclass  TYPE EDI_IAPI00-DEVCLASS, "   
lv_object_exists  TYPE EDI_IAPI00, "   
lv_pi_attributes  TYPE EDI_IAPI05, "   
lv_action_not_possible  TYPE EDI_IAPI05, "   
lv_syntax_error  TYPE EDI_IAPI05, "   
lv_wi_set_genflag  TYPE TADIR-GENFLAG, "   SPACE
lv_segment_error  TYPE TADIR, "   
lv_transport_error  TYPE TADIR, "   
lv_db_error  TYPE TADIR, "   
lv_no_authority  TYPE TADIR. "   

  CALL FUNCTION 'IDOCTYPE_CREATE'  "
    EXPORTING
         PI_IDOCTYP = lv_pi_idoctyp
         PI_DEVCLASS = lv_pi_devclass
         PI_ATTRIBUTES = lv_pi_attributes
         WI_SET_GENFLAG = lv_wi_set_genflag
    IMPORTING
         PE_ATTRIBUTES = lv_pe_attributes
    CHANGING
         PC_ORDER = lv_pc_order
    TABLES
         PT_SYNTAX = lt_pt_syntax
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
        OBJECT_EXISTS = 2
        ACTION_NOT_POSSIBLE = 3
        SYNTAX_ERROR = 4
        SEGMENT_ERROR = 5
        TRANSPORT_ERROR = 6
        DB_ERROR = 7
        NO_AUTHORITY = 8
. " IDOCTYPE_CREATE




ABAP code using 7.40 inline data declarations to call FM IDOCTYPE_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.

"SELECT single TRKORR FROM EDI_IAPI00 INTO @DATA(ld_pc_order).
 
 
"SELECT single IDOCTYP FROM EDI_IAPI00 INTO @DATA(ld_pi_idoctyp).
 
 
 
"SELECT single DEVCLASS FROM EDI_IAPI00 INTO @DATA(ld_pi_devclass).
 
 
 
 
 
"SELECT single GENFLAG FROM TADIR INTO @DATA(ld_wi_set_genflag).
DATA(ld_wi_set_genflag) = ' '.
 
 
 
 
 


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!