SAP ADD_DBA_PLANNING Function Module for









ADD_DBA_PLANNING is a standard add dba planning 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 add dba planning FM, simply by entering the name ADD_DBA_PLANNING into the relevant SAP transaction such as SE37 or SE38.

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



Function ADD_DBA_PLANNING 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 'ADD_DBA_PLANNING'"
EXPORTING
PLANNING_DESC = "DBA Action Table
PLANNING_STRUCT = "Internal Table for DBA Scheduling
START_IMMED = "Single-Character Flag
* TASK_STR = "
* TASK_NAME = "

IMPORTING
PLANNING_RC = "Return Value, Return Value After ABAP Statements

TABLES
RESOURCE_TABLE = "DBA Resource Table
.



IMPORTING Parameters details for ADD_DBA_PLANNING

PLANNING_DESC - DBA Action Table

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

PLANNING_STRUCT - Internal Table for DBA Scheduling

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

START_IMMED - Single-Character Flag

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

TASK_STR -

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

TASK_NAME -

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

EXPORTING Parameters details for ADD_DBA_PLANNING

PLANNING_RC - Return Value, Return Value After ABAP Statements

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

TABLES Parameters details for ADD_DBA_PLANNING

RESOURCE_TABLE - DBA Resource Table

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

Copy and paste ABAP code example for ADD_DBA_PLANNING 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_planning_rc  TYPE SY-SUBRC, "   
lv_planning_desc  TYPE SDBAC, "   
lt_resource_table  TYPE STANDARD TABLE OF SDBAR, "   
lv_planning_struct  TYPE SDBAP, "   
lv_start_immed  TYPE CHAR1, "   
lv_task_str  TYPE MSQIMPORT-COLULIST, "   
lv_task_name  TYPE MSQIMPORT-COLULIST. "   

  CALL FUNCTION 'ADD_DBA_PLANNING'  "
    EXPORTING
         PLANNING_DESC = lv_planning_desc
         PLANNING_STRUCT = lv_planning_struct
         START_IMMED = lv_start_immed
         TASK_STR = lv_task_str
         TASK_NAME = lv_task_name
    IMPORTING
         PLANNING_RC = lv_planning_rc
    TABLES
         RESOURCE_TABLE = lt_resource_table
. " ADD_DBA_PLANNING




ABAP code using 7.40 inline data declarations to call FM ADD_DBA_PLANNING

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 SUBRC FROM SY INTO @DATA(ld_planning_rc).
 
 
 
 
 
"SELECT single COLULIST FROM MSQIMPORT INTO @DATA(ld_task_str).
 
"SELECT single COLULIST FROM MSQIMPORT INTO @DATA(ld_task_name).
 


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!