SAP TR_SHOW_PROJECT_CONFLICTS Function Module for









TR_SHOW_PROJECT_CONFLICTS is a standard tr show project conflicts 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 tr show project conflicts FM, simply by entering the name TR_SHOW_PROJECT_CONFLICTS into the relevant SAP transaction such as SE37 or SE38.

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



Function TR_SHOW_PROJECT_CONFLICTS 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 'TR_SHOW_PROJECT_CONFLICTS'"
EXPORTING
IV_REQUEST = "

EXCEPTIONS
REQUEST_NOT_USABLE = 1 READ_ERROR = 2 ACCESS_ERROR = 3
.



IMPORTING Parameters details for TR_SHOW_PROJECT_CONFLICTS

IV_REQUEST -

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

EXCEPTIONS details

REQUEST_NOT_USABLE -

Data type:
Optional: No
Call by Reference: Yes

READ_ERROR -

Data type:
Optional: No
Call by Reference: Yes

ACCESS_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TR_SHOW_PROJECT_CONFLICTS 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_iv_request  TYPE TRKORR, "   
lv_request_not_usable  TYPE TRKORR, "   
lv_read_error  TYPE TRKORR, "   
lv_access_error  TYPE TRKORR. "   

  CALL FUNCTION 'TR_SHOW_PROJECT_CONFLICTS'  "
    EXPORTING
         IV_REQUEST = lv_iv_request
    EXCEPTIONS
        REQUEST_NOT_USABLE = 1
        READ_ERROR = 2
        ACCESS_ERROR = 3
. " TR_SHOW_PROJECT_CONFLICTS




ABAP code using 7.40 inline data declarations to call FM TR_SHOW_PROJECT_CONFLICTS

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



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!