SAP SDCAS_ACT_MAINTAIN_VIA_DIALOG Function Module for









SDCAS_ACT_MAINTAIN_VIA_DIALOG is a standard sdcas act maintain via dialog 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 sdcas act maintain via dialog FM, simply by entering the name SDCAS_ACT_MAINTAIN_VIA_DIALOG into the relevant SAP transaction such as SE37 or SE38.

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



Function SDCAS_ACT_MAINTAIN_VIA_DIALOG 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 'SDCAS_ACT_MAINTAIN_VIA_DIALOG'"
EXPORTING
FI_HANDLE = "
* FI_DISPLAY_ONLY = "
* FI_UPDATE_TASK = '?' "
* FI_FCODE = "
* FI_TRVOG = '9' "
* FI_EXIT_AFTER_SAVE = ' ' "

IMPORTING
FE_SUBSCREEN = "
FE_SUBSCREEN_PROGRAM = "
FE_HANDLE = "

EXCEPTIONS
NO_AUTHORITY = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLV43D_001 GUI Exit for Sales Activities: FCode +3X1
EXIT_SAPLV43D_004 GUI Exit for Sales Activities: FCode +5X1
EXIT_SAPLV43D_005 GUI Exit for Sales Activities: FCode +6X1

IMPORTING Parameters details for SDCAS_ACT_MAINTAIN_VIA_DIALOG

FI_HANDLE -

Data type: VBKA-VBELN
Optional: No
Call by Reference: Yes

FI_DISPLAY_ONLY -

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

FI_UPDATE_TASK -

Data type:
Default: '?'
Optional: Yes
Call by Reference: Yes

FI_FCODE -

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

FI_TRVOG -

Data type: TRVOG
Default: '9'
Optional: Yes
Call by Reference: Yes

FI_EXIT_AFTER_SAVE -

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

EXPORTING Parameters details for SDCAS_ACT_MAINTAIN_VIA_DIALOG

FE_SUBSCREEN -

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

FE_SUBSCREEN_PROGRAM -

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

FE_HANDLE -

Data type: VBKA-VBELN
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_AUTHORITY -

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

Copy and paste ABAP code example for SDCAS_ACT_MAINTAIN_VIA_DIALOG 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_fi_handle  TYPE VBKA-VBELN, "   
lv_fe_subscreen  TYPE SYDYNNR, "   
lv_no_authority  TYPE SYDYNNR, "   
lv_fi_display_only  TYPE XFELD, "   
lv_fe_subscreen_program  TYPE SYREPID, "   
lv_fe_handle  TYPE VBKA-VBELN, "   
lv_fi_update_task  TYPE VBKA, "   '?'
lv_fi_fcode  TYPE SYUCOMM, "   
lv_fi_trvog  TYPE TRVOG, "   '9'
lv_fi_exit_after_save  TYPE XFELD. "   SPACE

  CALL FUNCTION 'SDCAS_ACT_MAINTAIN_VIA_DIALOG'  "
    EXPORTING
         FI_HANDLE = lv_fi_handle
         FI_DISPLAY_ONLY = lv_fi_display_only
         FI_UPDATE_TASK = lv_fi_update_task
         FI_FCODE = lv_fi_fcode
         FI_TRVOG = lv_fi_trvog
         FI_EXIT_AFTER_SAVE = lv_fi_exit_after_save
    IMPORTING
         FE_SUBSCREEN = lv_fe_subscreen
         FE_SUBSCREEN_PROGRAM = lv_fe_subscreen_program
         FE_HANDLE = lv_fe_handle
    EXCEPTIONS
        NO_AUTHORITY = 1
. " SDCAS_ACT_MAINTAIN_VIA_DIALOG




ABAP code using 7.40 inline data declarations to call FM SDCAS_ACT_MAINTAIN_VIA_DIALOG

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 VBELN FROM VBKA INTO @DATA(ld_fi_handle).
 
 
 
 
 
"SELECT single VBELN FROM VBKA INTO @DATA(ld_fe_handle).
 
DATA(ld_fi_update_task) = '?'.
 
 
DATA(ld_fi_trvog) = '9'.
 
DATA(ld_fi_exit_after_save) = ' '.
 


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!