SAP DEV_READ_TADIR_SUBOBJCNT_DATA Function Module for DEV Reporting: Extractor for TADIR Sub Object Raw Data

Search SAP Function Modules

DEV_READ_TADIR_SUBOBJCNT_DATA is a standard dev read tadir subobjcnt data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DEV Reporting: Extractor for TADIR Sub Object Raw Data 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 dev read tadir subobjcnt data FM, simply by entering the name DEV_READ_TADIR_SUBOBJCNT_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: DEV_EXTRACTOR
Program Name: SAPLDEV_EXTRACTOR
Main Program: SAPLDEV_EXTRACTOR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DEV_READ_TADIR_SUBOBJCNT_DATA 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 'DEV_READ_TADIR_SUBOBJCNT_DATA'"DEV Reporting: Extractor for TADIR Sub Object Raw Data
  EXPORTING
*  IS_DPS_HEADER =  "DEV Reporting: Header Structure for extracted Data

 IMPORTING
   ES_DPS_HEADER =  "DEV Reporting: Header Structure for extracted Data

TABLES
*  IS_DEVCLASS =  "DEV Reporting: Development Class Extraction Structure
*  IS_OBJECT =  "DEV Reporting: TADIR specific Data (Key)
*  ES_DATA =  "
*  ES_DPS_EXCEPTION =  "

.

IMPORTING Parameters details for DEV_READ_TADIR_SUBOBJCNT_DATA

IS_DPS_HEADER - DEV Reporting: Header Structure for extracted Data

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

EXPORTING Parameters details for DEV_READ_TADIR_SUBOBJCNT_DATA

ES_DPS_HEADER - DEV Reporting: Header Structure for extracted Data

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

TABLES Parameters details for DEV_READ_TADIR_SUBOBJCNT_DATA

IS_DEVCLASS - DEV Reporting: Development Class Extraction Structure

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

IS_OBJECT - DEV Reporting: TADIR specific Data (Key)

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

ES_DATA -

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

ES_DPS_EXCEPTION -

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

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

ABAP code using 7.40 inline data declarations to call FM DEV_READ_TADIR_SUBOBJCNT_DATA

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