SAP CNV_10020_GET_ITR_FIELD Function Module for Get the name of a non-transparent field

Search SAP Function Modules

CNV_10020_GET_ITR_FIELD is a standard cnv 10020 get itr field SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get the name of a non-transparent field 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 cnv 10020 get itr field FM, simply by entering the name CNV_10020_GET_ITR_FIELD into the relevant SAP transaction such as SE37 or SE38.

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

Function CNV_10020_GET_ITR_FIELD 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 'CNV_10020_GET_ITR_FIELD'"Get the name of a non-transparent field
  EXPORTING
*  P_MANDT = SY-MANDT "Client
   P_PACKID =  "Package number
   P_FIELDNAME =  "Field name with component or proxy

 IMPORTING
   P_ITR_FIELD =  "Field name of non-transparent field
   P_COMP_EXIST =  "Indicator for the given field is non-transparent or not
   P_FIELDNAME_EXT =  "Field name (extended)

TABLES
*  ET_ITR_COMP =  "Component(s) of non-transparent field

EXCEPTIONS
   PROXY_UNDEFINED = 1 

.

IMPORTING Parameters details for CNV_10020_GET_ITR_FIELD

P_MANDT - Client

Data type: CNV_10020_REFOBJ-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: Yes

P_PACKID - Package number

Data type: CNV_10020_REFOBJ-PACKID
Optional: No
Call by Reference: Yes

P_FIELDNAME - Field name with component or proxy

Data type:
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CNV_10020_GET_ITR_FIELD

P_ITR_FIELD - Field name of non-transparent field

Data type:
Optional: No
Call by Reference: Yes

P_COMP_EXIST - Indicator for the given field is non-transparent or not

Data type: CNV_10020_REFOBJ-XFELD
Optional: No
Call by Reference: Yes

P_FIELDNAME_EXT - Field name (extended)

Data type:
Optional: No
Call by Reference: Yes

TABLES Parameters details for CNV_10020_GET_ITR_FIELD

ET_ITR_COMP - Component(s) of non-transparent field

Data type: CNV_10020_COMPONENTS
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

PROXY_UNDEFINED - proxy is not defined

Data type:
Optional: No
Call by Reference: Yes

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

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