SAP SSC_SR_CREATE_MANUALLY Function Module for Launch Service Request UI in create mode
SSC_SR_CREATE_MANUALLY is a standard ssc sr create manually SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Launch Service Request UI in create mode 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 ssc sr create manually FM, simply by entering the name SSC_SR_CREATE_MANUALLY into the relevant SAP transaction such as SE37 or SE38.
Function Group: SSC_SRF
Program Name: SAPLSSC_SRF
Main Program: SAPLSSC_SRF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SSC_SR_CREATE_MANUALLY 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 'SSC_SR_CREATE_MANUALLY'"Launch Service Request UI in create mode.
EXPORTING
IS_APPLICATION_CONTEXT = "Application Context for parameters transfer to CRM SR.
* IT_STATUS = "Shared Service Center: Status inserting table
* IV_BUSINESS_ROLE = "Business Role
* IX_NO_SAPGUI = ' ' "Boolean Variable (X=True, -=False, Space=Unknown)
* IX_NO_SAPGUI_SCREENSHOT = ' ' "Boolean Variable (X=True, -=False, Space=Unknown)
* IS_SCREENSHOT = "Screenshot Image Data Structure
* IX_CHIP_SR = ABAP_FALSE "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
* IT_ACTIVITY = "Shared Service Center: Activity inserting table
* IT_SRV_REQ_H = "Shared Service Center: Service Request Header inserting tab
* IT_SERVICE_OS = "Shared Service Center: Subject inserting table
* IX_OVERWRITE_TARGET = ABAP_TRUE "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
IMPORTING
EV_URL = "URL for the SAP Portal
EV_UI_OBJECT_VALUE = "UI Object Value
EV_UI_OBJECT_ACTION = "UI Object Action
EV_UI_OBJECT_TYPE = "UI Object Type
ET_MESSAGES = "Table with BAPI Return Information
IMPORTING Parameters details for SSC_SR_CREATE_MANUALLY
IS_APPLICATION_CONTEXT - Application Context for parameters transfer to CRM SR.
Data type: SSC_S_APPLICATION_CONTEXTOptional: No
Call by Reference: No ( called with pass by value option)
IT_STATUS - Shared Service Center: Status inserting table
Data type: SSC_T_SRVREQ_STATUS_INSOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_BUSINESS_ROLE - Business Role
Data type: CRMT_UI_PROFILEOptional: Yes
Call by Reference: No ( called with pass by value option)
IX_NO_SAPGUI - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IX_NO_SAPGUI_SCREENSHOT - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IS_SCREENSHOT - Screenshot Image Data Structure
Data type: SSC_S_SCREENSHOTOptional: Yes
Call by Reference: No ( called with pass by value option)
IX_CHIP_SR - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IT_ACTIVITY - Shared Service Center: Activity inserting table
Data type: SSC_T_SRVREQ_ACTIVITY_INSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SRV_REQ_H - Shared Service Center: Service Request Header inserting tab
Data type: SSC_T_SERVICE_REQUEST_H_INSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SERVICE_OS - Shared Service Center: Subject inserting table
Data type: SSC_T_SRVREQ_SERVICE_OS_INSOptional: Yes
Call by Reference: No ( called with pass by value option)
IX_OVERWRITE_TARGET - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: ABAP_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SSC_SR_CREATE_MANUALLY
EV_URL - URL for the SAP Portal
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
EV_UI_OBJECT_VALUE - UI Object Value
Data type: SSC_UI_OBJECT_VALUEOptional: No
Call by Reference: No ( called with pass by value option)
EV_UI_OBJECT_ACTION - UI Object Action
Data type: SSC_UI_OBJECT_ACTIONOptional: No
Call by Reference: No ( called with pass by value option)
EV_UI_OBJECT_TYPE - UI Object Type
Data type: SSC_UI_OBJECT_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGES - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SSC_SR_CREATE_MANUALLY 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_ev_url | TYPE STRING, " | |||
| lv_is_application_context | TYPE SSC_S_APPLICATION_CONTEXT, " | |||
| lv_it_status | TYPE SSC_T_SRVREQ_STATUS_INS, " | |||
| lv_iv_business_role | TYPE CRMT_UI_PROFILE, " | |||
| lv_ix_no_sapgui | TYPE BOOLEAN, " ' ' | |||
| lv_ev_ui_object_value | TYPE SSC_UI_OBJECT_VALUE, " | |||
| lv_ev_ui_object_action | TYPE SSC_UI_OBJECT_ACTION, " | |||
| lv_ix_no_sapgui_screenshot | TYPE BOOLEAN, " ' ' | |||
| lv_is_screenshot | TYPE SSC_S_SCREENSHOT, " | |||
| lv_ev_ui_object_type | TYPE SSC_UI_OBJECT_TYPE, " | |||
| lv_ix_chip_sr | TYPE BOOLE_D, " ABAP_FALSE | |||
| lv_et_messages | TYPE BAPIRETTAB, " | |||
| lv_it_activity | TYPE SSC_T_SRVREQ_ACTIVITY_INS, " | |||
| lv_it_srv_req_h | TYPE SSC_T_SERVICE_REQUEST_H_INS, " | |||
| lv_it_service_os | TYPE SSC_T_SRVREQ_SERVICE_OS_INS, " | |||
| lv_ix_overwrite_target | TYPE BOOLE_D. " ABAP_TRUE |
|   CALL FUNCTION 'SSC_SR_CREATE_MANUALLY' "Launch Service Request UI in create mode |
| EXPORTING | ||
| IS_APPLICATION_CONTEXT | = lv_is_application_context | |
| IT_STATUS | = lv_it_status | |
| IV_BUSINESS_ROLE | = lv_iv_business_role | |
| IX_NO_SAPGUI | = lv_ix_no_sapgui | |
| IX_NO_SAPGUI_SCREENSHOT | = lv_ix_no_sapgui_screenshot | |
| IS_SCREENSHOT | = lv_is_screenshot | |
| IX_CHIP_SR | = lv_ix_chip_sr | |
| IT_ACTIVITY | = lv_it_activity | |
| IT_SRV_REQ_H | = lv_it_srv_req_h | |
| IT_SERVICE_OS | = lv_it_service_os | |
| IX_OVERWRITE_TARGET | = lv_ix_overwrite_target | |
| IMPORTING | ||
| EV_URL | = lv_ev_url | |
| EV_UI_OBJECT_VALUE | = lv_ev_ui_object_value | |
| EV_UI_OBJECT_ACTION | = lv_ev_ui_object_action | |
| EV_UI_OBJECT_TYPE | = lv_ev_ui_object_type | |
| ET_MESSAGES | = lv_et_messages | |
| . " SSC_SR_CREATE_MANUALLY | ||
ABAP code using 7.40 inline data declarations to call FM SSC_SR_CREATE_MANUALLY
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_ix_no_sapgui) | = ' '. | |||
| DATA(ld_ix_no_sapgui_screenshot) | = ' '. | |||
| DATA(ld_ix_chip_sr) | = ABAP_FALSE. | |||
| DATA(ld_ix_overwrite_target) | = ABAP_TRUE. | |||
Search for further information about these or an SAP related objects