SAP FINB_TR_NAMETAB_GET Function Module for

Search SAP Function Modules

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

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

Function FINB_TR_NAMETAB_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 'FINB_TR_NAMETAB_GET'"
  EXPORTING
   I_TABNAME =  "Table Name
*  IO_MSG =  "Message Collector - Tools and Enhancements
*  I_NO_BUFFERING = ' ' "

 IMPORTING
   ET_DFIES =  "DD: Field List
   ET_KEY_DFIES =  "
   ES_HEADER =  "Nametab Header, Database Structure DDNTT
   E_NONCHAR_KEY =  "
   ET_TR_FIELDINFO =  "Table of Field Information for Generation
   EO_CX =  "FINB TR: Factory for Transport Objects

EXCEPTIONS
   ERROR_PASSED_TO_MSG = 1    NAMETAB_ERROR = 2 

.

IMPORTING Parameters details for FINB_TR_NAMETAB_GET

I_TABNAME - Table Name

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

IO_MSG - Message Collector - Tools and Enhancements

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

I_NO_BUFFERING -

Data type: BOOLE_D
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FINB_TR_NAMETAB_GET

ET_DFIES - DD: Field List

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

ET_KEY_DFIES -

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

ES_HEADER - Nametab Header, Database Structure DDNTT

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

E_NONCHAR_KEY -

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

ET_TR_FIELDINFO - Table of Field Information for Generation

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

EO_CX - FINB TR: Factory for Transport Objects

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

EXCEPTIONS details

ERROR_PASSED_TO_MSG -

Data type:
Optional: No
Call by Reference: Yes

NAMETAB_ERROR -

Data type:
Optional: No
Call by Reference: Yes

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