SAP L_CHECK_LTAP_SUB_RELEVANCE Function Module for









L_CHECK_LTAP_SUB_RELEVANCE is a standard l check ltap sub relevance 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 l check ltap sub relevance FM, simply by entering the name L_CHECK_LTAP_SUB_RELEVANCE into the relevant SAP transaction such as SE37 or SE38.

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



Function L_CHECK_LTAP_SUB_RELEVANCE 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 'L_CHECK_LTAP_SUB_RELEVANCE'"
EXPORTING
I_LTAK = "Transfer order header
I_LTAP = "Transfer order item
I_ZSYST = "Target system of WM message

IMPORTING
O_RELEVANCE = "Indicator: item relevant
O_QUSUB = "

EXCEPTIONS
NO_LINK_FOR_ITEM = 1
.



IMPORTING Parameters details for L_CHECK_LTAP_SUB_RELEVANCE

I_LTAK - Transfer order header

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

I_LTAP - Transfer order item

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

I_ZSYST - Target system of WM message

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

EXPORTING Parameters details for L_CHECK_LTAP_SUB_RELEVANCE

O_RELEVANCE - Indicator: item relevant

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

O_QUSUB -

Data type: T327A-QUSUB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_LINK_FOR_ITEM - TO item for link to subsystem does not exist

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

Copy and paste ABAP code example for L_CHECK_LTAP_SUB_RELEVANCE 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_ltak  TYPE LTAK, "   
lv_o_relevance  TYPE LTAK, "   
lv_no_link_for_item  TYPE LTAK, "   
lv_i_ltap  TYPE LTAP, "   
lv_o_qusub  TYPE T327A-QUSUB, "   
lv_i_zsyst  TYPE T327A-ZSYST. "   

  CALL FUNCTION 'L_CHECK_LTAP_SUB_RELEVANCE'  "
    EXPORTING
         I_LTAK = lv_i_ltak
         I_LTAP = lv_i_ltap
         I_ZSYST = lv_i_zsyst
    IMPORTING
         O_RELEVANCE = lv_o_relevance
         O_QUSUB = lv_o_qusub
    EXCEPTIONS
        NO_LINK_FOR_ITEM = 1
. " L_CHECK_LTAP_SUB_RELEVANCE




ABAP code using 7.40 inline data declarations to call FM L_CHECK_LTAP_SUB_RELEVANCE

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.

 
 
 
 
"SELECT single QUSUB FROM T327A INTO @DATA(ld_o_qusub).
 
"SELECT single ZSYST FROM T327A INTO @DATA(ld_i_zsyst).
 


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!