SAP S_CUS_ACTIVITY_SAVE Function Module for









S_CUS_ACTIVITY_SAVE is a standard s cus 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 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 s cus activity save FM, simply by entering the name S_CUS_ACTIVITY_SAVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: S_CUS_ACTIVITY
Program Name: SAPLS_CUS_ACTIVITY
Main Program: SAPLS_CUS_ACTIVITY
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function S_CUS_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 'S_CUS_ACTIVITY_SAVE'"
  EXPORTING
   ACTIVITY =  "
   ACTIVITY_TYPE =  "
   TCODE =  "
   CUSTOMER_EXIT =  "
*  CUSTOMER_EXIT_IMPLEMENTATION = ' ' "Business Add-In Implementation
*  CUSTOMER_EXIT_ENHANCEMENT = ' ' "

 IMPORTING
   MESSAGE =  "

TABLES
*  ACTIVITY_TITLE =  "
*  OBJECTS =  "
*  OBJECTS_TEXTS =  "
.



IMPORTING Parameters details for S_CUS_ACTIVITY_SAVE

ACTIVITY -

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

ACTIVITY_TYPE -

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

TCODE -

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

CUSTOMER_EXIT -

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

CUSTOMER_EXIT_IMPLEMENTATION - Business Add-In Implementation

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

CUSTOMER_EXIT_ENHANCEMENT -

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

EXPORTING Parameters details for S_CUS_ACTIVITY_SAVE

MESSAGE -

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

TABLES Parameters details for S_CUS_ACTIVITY_SAVE

ACTIVITY_TITLE -

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

OBJECTS -

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

OBJECTS_TEXTS -

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

Copy and paste ABAP code example for S_CUS_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:
lv_message  TYPE HIER_MESS, "   
lv_activity  TYPE CUS_ACTH-ACT_ID, "   
lt_activity_title  TYPE STANDARD TABLE OF CUS_ACTT, "   
lt_objects  TYPE STANDARD TABLE OF CUS_ACTOBJ, "   
lv_activity_type  TYPE CUS_ACTH-ACT_TYPE, "   
lv_tcode  TYPE CUS_ACTH-TCODE, "   
lt_objects_texts  TYPE STANDARD TABLE OF CUS_ACTOBT, "   
lv_customer_exit  TYPE CUS_ACTEXT-EXIT_NAME, "   
lv_customer_exit_implementation  TYPE CUS_ACTEXT-IMPL_NAME, "   SPACE
lv_customer_exit_enhancement  TYPE CUS_ACTEXT-ENHANCEMENT. "   SPACE

  CALL FUNCTION 'S_CUS_ACTIVITY_SAVE'  "
    EXPORTING
         ACTIVITY = lv_activity
         ACTIVITY_TYPE = lv_activity_type
         TCODE = lv_tcode
         CUSTOMER_EXIT = lv_customer_exit
         CUSTOMER_EXIT_IMPLEMENTATION = lv_customer_exit_implementation
         CUSTOMER_EXIT_ENHANCEMENT = lv_customer_exit_enhancement
    IMPORTING
         MESSAGE = lv_message
    TABLES
         ACTIVITY_TITLE = lt_activity_title
         OBJECTS = lt_objects
         OBJECTS_TEXTS = lt_objects_texts
. " S_CUS_ACTIVITY_SAVE




ABAP code using 7.40 inline data declarations to call FM S_CUS_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.

 
"SELECT single ACT_ID FROM CUS_ACTH INTO @DATA(ld_activity).
 
 
 
"SELECT single ACT_TYPE FROM CUS_ACTH INTO @DATA(ld_activity_type).
 
"SELECT single TCODE FROM CUS_ACTH INTO @DATA(ld_tcode).
 
 
"SELECT single EXIT_NAME FROM CUS_ACTEXT INTO @DATA(ld_customer_exit).
 
"SELECT single IMPL_NAME FROM CUS_ACTEXT INTO @DATA(ld_customer_exit_implementation).
DATA(ld_customer_exit_implementation) = ' '.
 
"SELECT single ENHANCEMENT FROM CUS_ACTEXT INTO @DATA(ld_customer_exit_enhancement).
DATA(ld_customer_exit_enhancement) = ' '.
 


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!