SAP FTI_RD_THX_ET_LOG Function Module for Effective Test Log Display

Search SAP Function Modules

FTI_RD_THX_ET_LOG is a standard fti rd thx et log SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Effective Test Log Display 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 fti rd thx et log FM, simply by entering the name FTI_RD_THX_ET_LOG into the relevant SAP transaction such as SE37 or SE38.

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

Function FTI_RD_THX_ET_LOG 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 'FTI_RD_THX_ET_LOG'"Effective Test Log Display
  EXPORTING
   I_BUKRS =  "Company Code
   I_VALUATION_AREA =  "Valuation Area
   I_HREL_NUMBER =  "Hedging Relationship Number (external/internal)
   I_FISCAL_YEAR =  "Fiscal Year
*  I_DATE =  "Key Date

EXCEPTIONS
   NO_HEDGE_RELATION = 1    INCOMPLETE_INPUT = 2    NO_VAL_AREA = 3    NO_BUKRS = 4    NO_EFFECTIVE_LOG_UUID = 5 

.

IMPORTING Parameters details for FTI_RD_THX_ET_LOG

I_BUKRS - Company Code

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

I_VALUATION_AREA - Valuation Area

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

I_HREL_NUMBER - Hedging Relationship Number (external/internal)

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

I_FISCAL_YEAR - Fiscal Year

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

I_DATE - Key Date

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

EXCEPTIONS details

NO_HEDGE_RELATION - Hedging Relationship Does Not Exist

Data type:
Optional: No
Call by Reference: Yes

INCOMPLETE_INPUT - Incomplete Entry

Data type:
Optional: No
Call by Reference: Yes

NO_VAL_AREA - Valuation Area is Missing

Data type:
Optional: No
Call by Reference: Yes

NO_BUKRS - Company code is missing

Data type:
Optional: No
Call by Reference: Yes

NO_EFFECTIVE_LOG_UUID - Effective Log UUID is missing

Data type:
Optional: No
Call by Reference: Yes

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

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