SAP IDOCFIELD2BAPIFIELD Function Module for

Search SAP Function Modules

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

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

Function IDOCFIELD2BAPIFIELD 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 'IDOCFIELD2BAPIFIELD'"
  EXPORTING
*  E2_STRUCNAME =  "
*  E2_FIELDNAME =  "
*  E1_STRUCNAME =  "
*  E1_FIELDNAME =  "

 IMPORTING
   BAPI_STRUCNAME =  "
   BAPI_FIELDNAME =  "
   ROLLNAME =  "

EXCEPTIONS
   ONLY_E1_OR_E2_STRUCTURE = 1    E1_STRUCTURE_IS_MISSING = 2    E1_FIELDNAME_IS_MISSING = 3    E2_STRUCTURE_IS_MISSING = 4    E2_FIELDNAME_IS_MISSING = 5    UNKNOWN_E1_STRUCNAME = 6    UNKNOWN_E2_STRUCNAME = 7    UNKNOWN_FIELDNAME = 8 

.

IMPORTING Parameters details for IDOCFIELD2BAPIFIELD

E2_STRUCNAME -

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

E2_FIELDNAME -

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

E1_STRUCNAME -

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

E1_FIELDNAME -

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

EXPORTING Parameters details for IDOCFIELD2BAPIFIELD

BAPI_STRUCNAME -

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

BAPI_FIELDNAME -

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

ROLLNAME -

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

EXCEPTIONS details

ONLY_E1_OR_E2_STRUCTURE -

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

E1_STRUCTURE_IS_MISSING -

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

E1_FIELDNAME_IS_MISSING -

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

E2_STRUCTURE_IS_MISSING -

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

E2_FIELDNAME_IS_MISSING -

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

UNKNOWN_E1_STRUCNAME -

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

UNKNOWN_E2_STRUCNAME -

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

UNKNOWN_FIELDNAME -

Data type:
Optional: No
Call by Reference: Yes

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

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