SAP IDOC_TRANSFORM Function Module for
IDOC_TRANSFORM is a standard idoc transform 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 transform FM, simply by entering the name IDOC_TRANSFORM into the relevant SAP transaction such as SE37 or SE38.
Function Group: F066
Program Name: SAPLF066
Main Program: SAPLF066
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IDOC_TRANSFORM 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_TRANSFORM'".
TABLES
IDOC_CNTRL = "
IDOC_DATA = "
EXCEPTIONS
WRONG_FUNCTION_CALLED = 1
TABLES Parameters details for IDOC_TRANSFORM
IDOC_CNTRL -
Data type: EDIDCOptional: No
Call by Reference: Yes
IDOC_DATA -
Data type: EDIDDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_FUNCTION_CALLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IDOC_TRANSFORM 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_cntrl | TYPE STANDARD TABLE OF EDIDC, " | |||
| lv_wrong_function_called | TYPE EDIDC, " | |||
| lt_idoc_data | TYPE STANDARD TABLE OF EDIDD. " |
|   CALL FUNCTION 'IDOC_TRANSFORM' " |
| TABLES | ||
| IDOC_CNTRL | = lt_idoc_cntrl | |
| IDOC_DATA | = lt_idoc_data | |
| EXCEPTIONS | ||
| WRONG_FUNCTION_CALLED = 1 | ||
| . " IDOC_TRANSFORM | ||
ABAP code using 7.40 inline data declarations to call FM IDOC_TRANSFORM
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