SAP SD_SALES_ACTIVITY_SAVE Function Module for Initiate update of sales activity









SD_SALES_ACTIVITY_SAVE is a standard sd sales activity save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initiate update of sales activity 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 sd sales activity save FM, simply by entering the name SD_SALES_ACTIVITY_SAVE into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_SALES_ACTIVITY_SAVE 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 'SD_SALES_ACTIVITY_SAVE'"Initiate update of sales activity
  EXPORTING
*  FI_UPDATE_TASK = 'C' "Update mode
   FI_AKTYP =  "

TABLES
*  FI_XVBADR =  "
*  FI_YVBADR =  "
*  FI_XVBFA =  "
*  FI_XVBKA =  "
*  FI_XVBPA =  "
*  FI_XVBUK =  "
*  FI_XVBUV =  "
*  FI_YVBKA =  "
*  FI_YVBPA =  "
*  FI_YVBUK =  "
.



IMPORTING Parameters details for SD_SALES_ACTIVITY_SAVE

FI_UPDATE_TASK - Update mode

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

FI_AKTYP -

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

TABLES Parameters details for SD_SALES_ACTIVITY_SAVE

FI_XVBADR -

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

FI_YVBADR -

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

FI_XVBFA -

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

FI_XVBKA -

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

FI_XVBPA -

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

FI_XVBUK -

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

FI_XVBUV -

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

FI_YVBKA -

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

FI_YVBPA -

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

FI_YVBUK -

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

Copy and paste ABAP code example for SD_SALES_ACTIVITY_SAVE 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_fi_xvbadr  TYPE STANDARD TABLE OF SADRVB, "   
lv_fi_update_task  TYPE SADRVB, "   'C'
lt_fi_yvbadr  TYPE STANDARD TABLE OF SADRVB, "   
lv_fi_aktyp  TYPE T180-AKTYP, "   
lt_fi_xvbfa  TYPE STANDARD TABLE OF VBFAVB, "   
lt_fi_xvbka  TYPE STANDARD TABLE OF VBKAVB, "   
lt_fi_xvbpa  TYPE STANDARD TABLE OF VBPAVB, "   
lt_fi_xvbuk  TYPE STANDARD TABLE OF VBUKVB, "   
lt_fi_xvbuv  TYPE STANDARD TABLE OF VBUV, "   
lt_fi_yvbka  TYPE STANDARD TABLE OF VBKAVB, "   
lt_fi_yvbpa  TYPE STANDARD TABLE OF VBPAVB, "   
lt_fi_yvbuk  TYPE STANDARD TABLE OF VBUKVB. "   

  CALL FUNCTION 'SD_SALES_ACTIVITY_SAVE'  "Initiate update of sales activity
    EXPORTING
         FI_UPDATE_TASK = lv_fi_update_task
         FI_AKTYP = lv_fi_aktyp
    TABLES
         FI_XVBADR = lt_fi_xvbadr
         FI_YVBADR = lt_fi_yvbadr
         FI_XVBFA = lt_fi_xvbfa
         FI_XVBKA = lt_fi_xvbka
         FI_XVBPA = lt_fi_xvbpa
         FI_XVBUK = lt_fi_xvbuk
         FI_XVBUV = lt_fi_xvbuv
         FI_YVBKA = lt_fi_yvbka
         FI_YVBPA = lt_fi_yvbpa
         FI_YVBUK = lt_fi_yvbuk
. " SD_SALES_ACTIVITY_SAVE




ABAP code using 7.40 inline data declarations to call FM SD_SALES_ACTIVITY_SAVE

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.

 
DATA(ld_fi_update_task) = 'C'.
 
 
"SELECT single AKTYP FROM T180 INTO @DATA(ld_fi_aktyp).
 
 
 
 
 
 
 
 
 


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!