SAP OCS_DISPLAY_LOG Function Module for









OCS_DISPLAY_LOG is a standard ocs display log 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 ocs display log FM, simply by entering the name OCS_DISPLAY_LOG into the relevant SAP transaction such as SE37 or SE38.

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



Function OCS_DISPLAY_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 'OCS_DISPLAY_LOG'"
  EXPORTING
*  IV_LOG_TYPE = 'MEMORY' "Log type
*  IV_LOG_NAME =  "
*  IV_LOG_DIRTYPE = 'T' "
*  IV_LOG_FILE =  "
*  IV_OCS_TOOL =  "
*  IV_TITLEBAR =  "Screens, Title Text
*  IV_DISPLAY_LEVEL = '1' "Log Level
*  IV_LANGUAGE = SY-LANGU "SAP R/3 System, Current Language

EXCEPTIONS
   WRONG_CALL = 1    EMPTY_LOG = 2    INTERNAL_ERROR = 3
.



IMPORTING Parameters details for OCS_DISPLAY_LOG

IV_LOG_TYPE - Log type

Data type: C
Default: 'MEMORY'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_LOG_NAME -

Data type: PATLOG3-LOG_NAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_LOG_DIRTYPE -

Data type: TSTRF01-DIRTYPE
Default: 'T'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_LOG_FILE -

Data type: TSTRF01-FILE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_OCS_TOOL -

Data type: PAT10-OCS_TOOL
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TITLEBAR - Screens, Title Text

Data type: SY-TITLE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_DISPLAY_LEVEL - Log Level

Data type: PAT_SPROT-PLEVEL
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_LANGUAGE - SAP R/3 System, Current Language

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

WRONG_CALL - Invalid call

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

EMPTY_LOG -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - Internal Error

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

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

DATA:
lv_wrong_call  TYPE STRING, "   
lv_iv_log_type  TYPE C, "   'MEMORY'
lv_empty_log  TYPE C, "   
lv_iv_log_name  TYPE PATLOG3-LOG_NAME, "   
lv_internal_error  TYPE PATLOG3, "   
lv_iv_log_dirtype  TYPE TSTRF01-DIRTYPE, "   'T'
lv_iv_log_file  TYPE TSTRF01-FILE, "   
lv_iv_ocs_tool  TYPE PAT10-OCS_TOOL, "   
lv_iv_titlebar  TYPE SY-TITLE, "   
lv_iv_display_level  TYPE PAT_SPROT-PLEVEL, "   '1'
lv_iv_language  TYPE SY-LANGU. "   SY-LANGU

  CALL FUNCTION 'OCS_DISPLAY_LOG'  "
    EXPORTING
         IV_LOG_TYPE = lv_iv_log_type
         IV_LOG_NAME = lv_iv_log_name
         IV_LOG_DIRTYPE = lv_iv_log_dirtype
         IV_LOG_FILE = lv_iv_log_file
         IV_OCS_TOOL = lv_iv_ocs_tool
         IV_TITLEBAR = lv_iv_titlebar
         IV_DISPLAY_LEVEL = lv_iv_display_level
         IV_LANGUAGE = lv_iv_language
    EXCEPTIONS
        WRONG_CALL = 1
        EMPTY_LOG = 2
        INTERNAL_ERROR = 3
. " OCS_DISPLAY_LOG




ABAP code using 7.40 inline data declarations to call FM OCS_DISPLAY_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.

 
DATA(ld_iv_log_type) = 'MEMORY'.
 
 
"SELECT single LOG_NAME FROM PATLOG3 INTO @DATA(ld_iv_log_name).
 
 
"SELECT single DIRTYPE FROM TSTRF01 INTO @DATA(ld_iv_log_dirtype).
DATA(ld_iv_log_dirtype) = 'T'.
 
"SELECT single FILE FROM TSTRF01 INTO @DATA(ld_iv_log_file).
 
"SELECT single OCS_TOOL FROM PAT10 INTO @DATA(ld_iv_ocs_tool).
 
"SELECT single TITLE FROM SY INTO @DATA(ld_iv_titlebar).
 
"SELECT single PLEVEL FROM PAT_SPROT INTO @DATA(ld_iv_display_level).
DATA(ld_iv_display_level) = '1'.
 
"SELECT single LANGU FROM SY INTO @DATA(ld_iv_language).
DATA(ld_iv_language) = SY-LANGU.
 


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!