SAP TLR_TARO_DB_SEL_COUNT_TARO Function Module for Count then of TAROs according select options









TLR_TARO_DB_SEL_COUNT_TARO is a standard tlr taro db sel count taro SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Count then of TAROs according select options 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 tlr taro db sel count taro FM, simply by entering the name TLR_TARO_DB_SEL_COUNT_TARO into the relevant SAP transaction such as SE37 or SE38.

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



Function TLR_TARO_DB_SEL_COUNT_TARO 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 'TLR_TARO_DB_SEL_COUNT_TARO'"Count then of TAROs according select options
  EXPORTING
*  I_TREP =  "Trade Repository
*  IT_RANGE_PROC_STATUS =  "Range Taro Processing Status
*  IT_RANGE_ACTION_TYPE =  "Range Taro Action Type
*  IT_RANGE_BUKRS =  "Range Company Code
*  IT_RANGE_RFHA =  "Range Transaction
*  IT_RANGE_UTI =  "Range Trade ID
*  IT_RANGE_ENTERED_ON =  "Range Taro Entered On
*  IT_RANGE_PROD_TYPE =  "Range Producttype
*  IT_RANGE_FIN_TR_TYPE =  "Range Financial Transaction Type

 IMPORTING
   E_COUNTER =  "
.



IMPORTING Parameters details for TLR_TARO_DB_SEL_COUNT_TARO

I_TREP - Trade Repository

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

IT_RANGE_PROC_STATUS - Range Taro Processing Status

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

IT_RANGE_ACTION_TYPE - Range Taro Action Type

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

IT_RANGE_BUKRS - Range Company Code

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

IT_RANGE_RFHA - Range Transaction

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

IT_RANGE_UTI - Range Trade ID

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

IT_RANGE_ENTERED_ON - Range Taro Entered On

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

IT_RANGE_PROD_TYPE - Range Producttype

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

IT_RANGE_FIN_TR_TYPE - Range Financial Transaction Type

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

EXPORTING Parameters details for TLR_TARO_DB_SEL_COUNT_TARO

E_COUNTER -

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

Copy and paste ABAP code example for TLR_TARO_DB_SEL_COUNT_TARO 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_trep  TYPE FTR_TARO_TRADE_REPOSITORY, "   
lv_e_counter  TYPE INT4, "   
lv_it_range_proc_status  TYPE TLRY_TARO_RANGE_PROC_STATUS, "   
lv_it_range_action_type  TYPE TLRY_TARO_RANGE_ACTION_TYPE, "   
lv_it_range_bukrs  TYPE TPMY_RANGE_BUKRS, "   
lv_it_range_rfha  TYPE TPMY_RANGE_RFHA, "   
lv_it_range_uti  TYPE TLRY_TARO_RANGE_UTI, "   
lv_it_range_entered_on  TYPE TLRY_TARO_RANGE_ENTERED_ON, "   
lv_it_range_prod_type  TYPE TLRY_TARO_RANGE_PROD_TYPE, "   
lv_it_range_fin_tr_type  TYPE TLRY_TARO_RANGE_FIN_TR_TYPE. "   

  CALL FUNCTION 'TLR_TARO_DB_SEL_COUNT_TARO'  "Count then of TAROs according select options
    EXPORTING
         I_TREP = lv_i_trep
         IT_RANGE_PROC_STATUS = lv_it_range_proc_status
         IT_RANGE_ACTION_TYPE = lv_it_range_action_type
         IT_RANGE_BUKRS = lv_it_range_bukrs
         IT_RANGE_RFHA = lv_it_range_rfha
         IT_RANGE_UTI = lv_it_range_uti
         IT_RANGE_ENTERED_ON = lv_it_range_entered_on
         IT_RANGE_PROD_TYPE = lv_it_range_prod_type
         IT_RANGE_FIN_TR_TYPE = lv_it_range_fin_tr_type
    IMPORTING
         E_COUNTER = lv_e_counter
. " TLR_TARO_DB_SEL_COUNT_TARO




ABAP code using 7.40 inline data declarations to call FM TLR_TARO_DB_SEL_COUNT_TARO

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!