SAP PT_FIELD_TAB_GET Function Module for

Search SAP Function Modules

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

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

Function PT_FIELD_TAB_GET 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 'PT_FIELD_TAB_GET'"
  EXPORTING
   IM_SCREEN_AREA =  "
*  IM_MAX_FIELD_LENGTH =  "

 IMPORTING
   EX_FIELD_TAB =  "

EXCEPTIONS
   NO_SCREEN_AREA_FOUND = 1    NO_FIELD_CATALOG_DEFINED = 2    MISSING_FIELD_CATALOG = 3    EXCEPTION_DDIF_FIELDINFO_GET = 4    INTERFACE_NOT_EXISTING = 5    INTERFACE_IS_REALLY_CLASS = 6    ERROR_CREATE_OBJECT = 7    ERROR_GET_FIELD_TAB = 8 

.

IMPORTING Parameters details for PT_FIELD_TAB_GET

IM_SCREEN_AREA -

Data type: PT_SCREEN_AREA
Optional: No
Call by Reference: Yes

IM_MAX_FIELD_LENGTH -

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

EXPORTING Parameters details for PT_FIELD_TAB_GET

EX_FIELD_TAB -

Data type: TAB_PT_FIELD_SEL
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_SCREEN_AREA_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NO_FIELD_CATALOG_DEFINED -

Data type:
Optional: No
Call by Reference: Yes

MISSING_FIELD_CATALOG -

Data type:
Optional: No
Call by Reference: Yes

EXCEPTION_DDIF_FIELDINFO_GET -

Data type:
Optional: No
Call by Reference: Yes

INTERFACE_NOT_EXISTING -

Data type:
Optional: No
Call by Reference: Yes

INTERFACE_IS_REALLY_CLASS -

Data type:
Optional: No
Call by Reference: Yes

ERROR_CREATE_OBJECT -

Data type:
Optional: No
Call by Reference: Yes

ERROR_GET_FIELD_TAB -

Data type:
Optional: No
Call by Reference: Yes

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

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