SAP FTR_COEX_BALLOG_DISPLAY Function Module for Show Application Log for LOG2Trm









FTR_COEX_BALLOG_DISPLAY is a standard ftr coex ballog display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Show Application Log for LOG2Trm 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 ftr coex ballog display FM, simply by entering the name FTR_COEX_BALLOG_DISPLAY into the relevant SAP transaction such as SE37 or SE38.

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



Function FTR_COEX_BALLOG_DISPLAY 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 'FTR_COEX_BALLOG_DISPLAY'"Show Application Log for LOG2Trm
  EXPORTING
   I_EXTNUMBER =  "External Document Number
*  I_ERRORS_ONLY = ABAP_FALSE "Show errors only?
   I_DATE_FROM =  "Application log: date
   I_DATE_TO =  "Application log: date
   I_TIME_FROM =  "Application log: time
   I_TIME_TO =  "Application log: time
   I_PROG =  "Application log: Program name
   I_TCODE =  "Application Log: Transaction code
   I_USER =  "Application log: user name
   IS_PROFILE =  "Application Log: Log Output Format Profile

EXCEPTIONS
   NO_AUTHORITY = 1
.



IMPORTING Parameters details for FTR_COEX_BALLOG_DISPLAY

I_EXTNUMBER - External Document Number

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

I_ERRORS_ONLY - Show errors only?

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: No
Call by Reference: Yes

I_DATE_FROM - Application log: date

Data type: BALHDR-ALDATE
Optional: No
Call by Reference: Yes

I_DATE_TO - Application log: date

Data type: BALHDR-ALDATE
Optional: No
Call by Reference: Yes

I_TIME_FROM - Application log: time

Data type: BALHDR-ALTIME
Optional: No
Call by Reference: Yes

I_TIME_TO - Application log: time

Data type: BALHDR-ALTIME
Optional: No
Call by Reference: Yes

I_PROG - Application log: Program name

Data type: BALHDR-ALPROG
Optional: No
Call by Reference: Yes

I_TCODE - Application Log: Transaction code

Data type: BALHDR-ALTCODE
Optional: No
Call by Reference: Yes

I_USER - Application log: user name

Data type: BALHDR-ALUSER
Optional: No
Call by Reference: Yes

IS_PROFILE - Application Log: Log Output Format Profile

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

EXCEPTIONS details

NO_AUTHORITY - Authority Check failed

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

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

DATA:
lv_i_extnumber  TYPE FTR_EXTERNAL_DOC_NUMBER, "   
lv_no_authority  TYPE FTR_EXTERNAL_DOC_NUMBER, "   
lv_i_errors_only  TYPE ABAP_BOOL, "   ABAP_FALSE
lv_i_date_from  TYPE BALHDR-ALDATE, "   
lv_i_date_to  TYPE BALHDR-ALDATE, "   
lv_i_time_from  TYPE BALHDR-ALTIME, "   
lv_i_time_to  TYPE BALHDR-ALTIME, "   
lv_i_prog  TYPE BALHDR-ALPROG, "   
lv_i_tcode  TYPE BALHDR-ALTCODE, "   
lv_i_user  TYPE BALHDR-ALUSER, "   
lv_is_profile  TYPE BAL_S_PROF. "   

  CALL FUNCTION 'FTR_COEX_BALLOG_DISPLAY'  "Show Application Log for LOG2Trm
    EXPORTING
         I_EXTNUMBER = lv_i_extnumber
         I_ERRORS_ONLY = lv_i_errors_only
         I_DATE_FROM = lv_i_date_from
         I_DATE_TO = lv_i_date_to
         I_TIME_FROM = lv_i_time_from
         I_TIME_TO = lv_i_time_to
         I_PROG = lv_i_prog
         I_TCODE = lv_i_tcode
         I_USER = lv_i_user
         IS_PROFILE = lv_is_profile
    EXCEPTIONS
        NO_AUTHORITY = 1
. " FTR_COEX_BALLOG_DISPLAY




ABAP code using 7.40 inline data declarations to call FM FTR_COEX_BALLOG_DISPLAY

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.

 
 
DATA(ld_i_errors_only) = ABAP_FALSE.
 
"SELECT single ALDATE FROM BALHDR INTO @DATA(ld_i_date_from).
 
"SELECT single ALDATE FROM BALHDR INTO @DATA(ld_i_date_to).
 
"SELECT single ALTIME FROM BALHDR INTO @DATA(ld_i_time_from).
 
"SELECT single ALTIME FROM BALHDR INTO @DATA(ld_i_time_to).
 
"SELECT single ALPROG FROM BALHDR INTO @DATA(ld_i_prog).
 
"SELECT single ALTCODE FROM BALHDR INTO @DATA(ld_i_tcode).
 
"SELECT single ALUSER FROM BALHDR INTO @DATA(ld_i_user).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!