SAP HR_SSC_CREATE_SERVICE_OBJECT Function Module for Create Service Object









HR_SSC_CREATE_SERVICE_OBJECT is a standard hr ssc create service object SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Service Object 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 hr ssc create service object FM, simply by entering the name HR_SSC_CREATE_SERVICE_OBJECT into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_SSC_CREATE_SERVICE_OBJECT 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 'HR_SSC_CREATE_SERVICE_OBJECT'"Create Service Object
  EXPORTING
*  SERVICE_APPL_TYPE = 'WDJAVA' "
*  INITIATOR_ROLE =  "Default Initiator Role of Self-Service
*  SERVICE_APPL_PATH =  "
   SERVICE_APPL_NAME =  "
   START_TIME_STAMP =  "UTC Start Time Stamp
*  END_TIME_STAMP =  "UTC End Time Stamp
*  OBJECT_PLVAR =  "Plan Variant
*  OBJECT_OTYPE =  "Object Type
*  OBJECT_ID =  "Object ID
*  TRACKING_ID =  "Tracking ID

 IMPORTING
   IS_TRACKING_ACTIVE =  "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
.



IMPORTING Parameters details for HR_SSC_CREATE_SERVICE_OBJECT

SERVICE_APPL_TYPE -

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

INITIATOR_ROLE - Default Initiator Role of Self-Service

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

SERVICE_APPL_PATH -

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

SERVICE_APPL_NAME -

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

START_TIME_STAMP - UTC Start Time Stamp

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

END_TIME_STAMP - UTC End Time Stamp

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

OBJECT_PLVAR - Plan Variant

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

OBJECT_OTYPE - Object Type

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

OBJECT_ID - Object ID

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

TRACKING_ID - Tracking ID

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

EXPORTING Parameters details for HR_SSC_CREATE_SERVICE_OBJECT

IS_TRACKING_ACTIVE - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')

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

Copy and paste ABAP code example for HR_SSC_CREATE_SERVICE_OBJECT 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_service_appl_type  TYPE SSC_SERVICE_APPL_TYPE, "   'WDJAVA'
lv_is_tracking_active  TYPE BOOLE_D, "   
lv_initiator_role  TYPE SSC_INITIATOR_ROLE, "   
lv_service_appl_path  TYPE SSC_SERVICE_APPL_PATH, "   
lv_service_appl_name  TYPE SSC_SERVICE_APPL_NAME, "   
lv_start_time_stamp  TYPE SSC_UTC_TIMESTAMP_START, "   
lv_end_time_stamp  TYPE SSC_UTC_TIMESTAMP_END, "   
lv_object_plvar  TYPE PLVAR, "   
lv_object_otype  TYPE OTYPE, "   
lv_object_id  TYPE HROBJID, "   
lv_tracking_id  TYPE SSC_TRACKING_ID. "   

  CALL FUNCTION 'HR_SSC_CREATE_SERVICE_OBJECT'  "Create Service Object
    EXPORTING
         SERVICE_APPL_TYPE = lv_service_appl_type
         INITIATOR_ROLE = lv_initiator_role
         SERVICE_APPL_PATH = lv_service_appl_path
         SERVICE_APPL_NAME = lv_service_appl_name
         START_TIME_STAMP = lv_start_time_stamp
         END_TIME_STAMP = lv_end_time_stamp
         OBJECT_PLVAR = lv_object_plvar
         OBJECT_OTYPE = lv_object_otype
         OBJECT_ID = lv_object_id
         TRACKING_ID = lv_tracking_id
    IMPORTING
         IS_TRACKING_ACTIVE = lv_is_tracking_active
. " HR_SSC_CREATE_SERVICE_OBJECT




ABAP code using 7.40 inline data declarations to call FM HR_SSC_CREATE_SERVICE_OBJECT

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_service_appl_type) = 'WDJAVA'.
 
 
 
 
 
 
 
 
 
 
 


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!