SAP SDB_GET_DATA_AREA_SIZES Function Module for
SDB_GET_DATA_AREA_SIZES is a standard sdb get data area sizes 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 sdb get data area sizes FM, simply by entering the name SDB_GET_DATA_AREA_SIZES into the relevant SAP transaction such as SE37 or SE38.
Function Group: SSDBDATA
Program Name: SAPLSSDBDATA
Main Program: SAPLSSDBDATA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SDB_GET_DATA_AREA_SIZES 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 'SDB_GET_DATA_AREA_SIZES'".
EXPORTING
SYSID = "
IMPORTING
SIZEDETAILS_TAB = "
EXCEPTIONS
CX_DBA_SDB = 1
IMPORTING Parameters details for SDB_GET_DATA_AREA_SIZES
SYSID -
Data type: DB6NAVSYST-SYSIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for SDB_GET_DATA_AREA_SIZES
SIZEDETAILS_TAB -
Data type: SDB_AREAVOLDESCRIPT_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
CX_DBA_SDB -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SDB_GET_DATA_AREA_SIZES 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_sysid | TYPE DB6NAVSYST-SYSID, " | |||
| lv_cx_dba_sdb | TYPE DB6NAVSYST, " | |||
| lv_sizedetails_tab | TYPE SDB_AREAVOLDESCRIPT_TAB. " |
|   CALL FUNCTION 'SDB_GET_DATA_AREA_SIZES' " |
| EXPORTING | ||
| SYSID | = lv_sysid | |
| IMPORTING | ||
| SIZEDETAILS_TAB | = lv_sizedetails_tab | |
| EXCEPTIONS | ||
| CX_DBA_SDB = 1 | ||
| . " SDB_GET_DATA_AREA_SIZES | ||
ABAP code using 7.40 inline data declarations to call FM SDB_GET_DATA_AREA_SIZES
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 SYSID FROM DB6NAVSYST INTO @DATA(ld_sysid). | ||||
Search for further information about these or an SAP related objects