SAP DEV_EX_SCOV_DEVC Function Module for DEV Reporting: Extractor for SCOV Data
DEV_EX_SCOV_DEVC is a standard dev ex scov devc 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 SCOV 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 ex scov devc FM, simply by entering the name DEV_EX_SCOV_DEVC into the relevant SAP transaction such as SE37 or SE38.
Function Group: DEV_EXTRACTORS
Program Name: SAPLDEV_EXTRACTORS
Main Program: SAPLDEV_EXTRACTORS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function DEV_EX_SCOV_DEVC 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_EX_SCOV_DEVC'"DEV Reporting: Extractor for SCOV Data.
EXPORTING
* IS_DPS_HEADER = "DPS Extraktion: Kopfdaten
* IS_RFCDEST_HRORG = "Anzeigestruktur fuer RFCDES-Pflege
* IV_RFCDEST_HRORG = "logische Destination (Wird bei Funktionsaufruf angegeben)
IMPORTING
ES_DPS_HEADER = "DPS Extraktion: Kopfdaten
EV_EXTRACTOR_VERSION = "Version des Funktionsbausteins
EV_RECORDS = "Anzahl der Meldungen
EV_BASIS_RELEASE = "R/3 Release
EV_LAST_VERSION = "Version der Ergebnisse
TABLES
* ES_DPS_DATA = "Returnparameter
* ES_DPS_EXCEPTION = "Returnparameter
IMPORTING Parameters details for DEV_EX_SCOV_DEVC
IS_DPS_HEADER - DPS Extraktion: Kopfdaten
Data type: DRP_HEADER_SOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_RFCDEST_HRORG - Anzeigestruktur fuer RFCDES-Pflege
Data type: DRP_RFCDISPLAYOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_RFCDEST_HRORG - logische Destination (Wird bei Funktionsaufruf angegeben)
Data type: DRP_RFCDISPLAY-RFCDESTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DEV_EX_SCOV_DEVC
ES_DPS_HEADER - DPS Extraktion: Kopfdaten
Data type: DRP_HEADER_SOptional: No
Call by Reference: No ( called with pass by value option)
EV_EXTRACTOR_VERSION - Version des Funktionsbausteins
Data type: DRP_HEADER_S-VERSIONOptional: No
Call by Reference: No ( called with pass by value option)
EV_RECORDS - Anzahl der Meldungen
Data type: DRP_DATA_S-COUNTEROptional: No
Call by Reference: No ( called with pass by value option)
EV_BASIS_RELEASE - R/3 Release
Data type: DRP_HEADER_S-BASIS_RELEASEOptional: No
Call by Reference: No ( called with pass by value option)
EV_LAST_VERSION - Version der Ergebnisse
Data type: DRP_HEADER_S-VERSIONOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DEV_EX_SCOV_DEVC
ES_DPS_DATA - Returnparameter
Data type: DRP_SCOV_DEVC_ALL_SOptional: Yes
Call by Reference: Yes
ES_DPS_EXCEPTION - Returnparameter
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DEV_EX_SCOV_DEVC 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: | ||||
| lt_es_dps_data | TYPE STANDARD TABLE OF DRP_SCOV_DEVC_ALL_S, " | |||
| lv_es_dps_header | TYPE DRP_HEADER_S, " | |||
| lv_is_dps_header | TYPE DRP_HEADER_S, " | |||
| lt_es_dps_exception | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_is_rfcdest_hrorg | TYPE DRP_RFCDISPLAY, " | |||
| lv_ev_extractor_version | TYPE DRP_HEADER_S-VERSION, " | |||
| lv_ev_records | TYPE DRP_DATA_S-COUNTER, " | |||
| lv_iv_rfcdest_hrorg | TYPE DRP_RFCDISPLAY-RFCDEST, " | |||
| lv_ev_basis_release | TYPE DRP_HEADER_S-BASIS_RELEASE, " | |||
| lv_ev_last_version | TYPE DRP_HEADER_S-VERSION. " |
| CALL FUNCTION 'DEV_EX_SCOV_DEVC' "DEV Reporting: Extractor for SCOV Data |
| EXPORTING | ||
| IS_DPS_HEADER | = lv_is_dps_header | |
| IS_RFCDEST_HRORG | = lv_is_rfcdest_hrorg | |
| IV_RFCDEST_HRORG | = lv_iv_rfcdest_hrorg | |
| IMPORTING | ||
| ES_DPS_HEADER | = lv_es_dps_header | |
| EV_EXTRACTOR_VERSION | = lv_ev_extractor_version | |
| EV_RECORDS | = lv_ev_records | |
| EV_BASIS_RELEASE | = lv_ev_basis_release | |
| EV_LAST_VERSION | = lv_ev_last_version | |
| TABLES | ||
| ES_DPS_DATA | = lt_es_dps_data | |
| ES_DPS_EXCEPTION | = lt_es_dps_exception | |
| . " DEV_EX_SCOV_DEVC | ||
ABAP code using 7.40 inline data declarations to call FM DEV_EX_SCOV_DEVC
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 VERSION FROM DRP_HEADER_S INTO @DATA(ld_ev_extractor_version). | ||||
| "SELECT single COUNTER FROM DRP_DATA_S INTO @DATA(ld_ev_records). | ||||
| "SELECT single RFCDEST FROM DRP_RFCDISPLAY INTO @DATA(ld_iv_rfcdest_hrorg). | ||||
| "SELECT single BASIS_RELEASE FROM DRP_HEADER_S INTO @DATA(ld_ev_basis_release). | ||||
| "SELECT single VERSION FROM DRP_HEADER_S INTO @DATA(ld_ev_last_version). | ||||
Search for further information about these or an SAP related objects