SAP CRM_SSC_SRVREQ_CREATE Function Module for Create Service Requests
CRM_SSC_SRVREQ_CREATE is a standard crm ssc srvreq create 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 Requests 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 crm ssc srvreq create FM, simply by entering the name CRM_SSC_SRVREQ_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_SRVREQ_API
Program Name: SAPLCRM_SRVREQ_API
Main Program: SAPLCRM_SRVREQ_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CRM_SSC_SRVREQ_CREATE 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 'CRM_SSC_SRVREQ_CREATE'"Create Service Requests.
EXPORTING
* IS_CM_BIN_FILE_KEY = "Key Structure for attachment of bin. file to Content Mgmt
TABLES
CT_HEADER = "BO BusProcessND: Administration Data Trans. Header Create()
* IT_PRODUCT_I = "BO BusProcessND: Product data
* IT_QUALIF = "Qualification Requirement Set
* IT_SCHEDULELINE = "BO BusProcessND: Schedule line
* IT_SERVICE_I = "Service Item - Inserting structure
* IT_SERVICE_OS = "BO BusProcessND: Transaction Subject Create ()
* IT_SRV_REQ_H = "Service Request Header - Inserting structure
* IT_STATUS = "BO BusProcessND: Business Transaction Status:Process Methods
* IT_SUBJECT = "Subject
* IT_SURVEY = "Survey table
* IT_TEXT = "BO BusProcessND: Process Texts of a Business Transaction
* CT_ITEM = "BO BusProcessND: Administrative Data - Transaction Item
IT_INPUT_FIELDS = "BO BusProcessND: Fields Entered
* IT_EXTENSION = "Ref. structure for BAPI parameter ExtensionIn/ExtensionOut
* ET_RETURN = "Return Parameter
* IT_CM_BIN_FILE_CONTENT = "SDOK: Table with Binary Document Content for Web Server
* IT_ACTIVITY = "BO BusProcessND: Header Data for CRM Activity in Create Mode
* IT_APPOINTMENT = "BO BusProcessND: Process Dates of a Transaction
* IT_CUSTOMER_H = "BO BusProcessND: Customer data - header
* IT_CUSTOMER_I = "BO BusProcessND: Customer data - item
* IT_DOC_FLOW = "Object reference - inserting structure
* IT_ORGANISATION = "Organisation data - inserting structure
* IT_PARTNER = "BO BusProcessND: Process Partner for a Transaction Create()
IMPORTING Parameters details for CRM_SSC_SRVREQ_CREATE
IS_CM_BIN_FILE_KEY - Key Structure for attachment of bin. file to Content Mgmt
Data type: CRMS_PREFILL_CM_BIN_FILE_KEYOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CRM_SSC_SRVREQ_CREATE
CT_HEADER - BO BusProcessND: Administration Data Trans. Header Create()
Data type: BAPIBUS20001_HEADER_INSOptional: No
Call by Reference: Yes
IT_PRODUCT_I - BO BusProcessND: Product data
Data type: BAPIBUS20001_PRODUCTOptional: Yes
Call by Reference: Yes
IT_QUALIF - Qualification Requirement Set
Data type: CRMS_SSC_QUALIF_INSOptional: Yes
Call by Reference: Yes
IT_SCHEDULELINE - BO BusProcessND: Schedule line
Data type: BAPIBUS20001_SCHEDLINOptional: Yes
Call by Reference: Yes
IT_SERVICE_I - Service Item - Inserting structure
Data type: CRMS_SSC_SERVICE_I_INSOptional: Yes
Call by Reference: Yes
IT_SERVICE_OS - BO BusProcessND: Transaction Subject Create ()
Data type: CRMS_SSC_SERVICE_OS_INSOptional: Yes
Call by Reference: Yes
IT_SRV_REQ_H - Service Request Header - Inserting structure
Data type: CRMS_SSC_SERVICE_REQUEST_H_INSOptional: Yes
Call by Reference: Yes
IT_STATUS - BO BusProcessND: Business Transaction Status:Process Methods
Data type: BAPIBUS20001_STATUS_INSOptional: Yes
Call by Reference: Yes
IT_SUBJECT - Subject
Data type: CRMS_SSC_SUBJECT_INSOptional: Yes
Call by Reference: Yes
IT_SURVEY - Survey table
Data type: CRMS_SSC_SURVEY_INSOptional: Yes
Call by Reference: Yes
IT_TEXT - BO BusProcessND: Process Texts of a Business Transaction
Data type: BAPIBUS20001_TEXT_INSOptional: Yes
Call by Reference: Yes
CT_ITEM - BO BusProcessND: Administrative Data - Transaction Item
Data type: BAPIBUS20001_ITEMOptional: Yes
Call by Reference: Yes
IT_INPUT_FIELDS - BO BusProcessND: Fields Entered
Data type: BAPIBUS20001_INPUT_FIELDSOptional: No
Call by Reference: Yes
IT_EXTENSION - Ref. structure for BAPI parameter ExtensionIn/ExtensionOut
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
ET_RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
IT_CM_BIN_FILE_CONTENT - SDOK: Table with Binary Document Content for Web Server
Data type: SDOKCNTBINSOptional: Yes
Call by Reference: Yes
IT_ACTIVITY - BO BusProcessND: Header Data for CRM Activity in Create Mode
Data type: BAPIBUS20001_ACTIVITY_INSOptional: Yes
Call by Reference: Yes
IT_APPOINTMENT - BO BusProcessND: Process Dates of a Transaction
Data type: BAPIBUS20001_APPOINTMENT_INSOptional: Yes
Call by Reference: Yes
IT_CUSTOMER_H - BO BusProcessND: Customer data - header
Data type: BAPIBUS20001_CUSTOMER_HOptional: Yes
Call by Reference: Yes
IT_CUSTOMER_I - BO BusProcessND: Customer data - item
Data type: BAPIBUS20001_CUSTOMER_IOptional: Yes
Call by Reference: Yes
IT_DOC_FLOW - Object reference - inserting structure
Data type: CRMS_SSC_DOC_FLOW_INSOptional: Yes
Call by Reference: Yes
IT_ORGANISATION - Organisation data - inserting structure
Data type: CRMS_SSC_ORGMAN_INSOptional: Yes
Call by Reference: Yes
IT_PARTNER - BO BusProcessND: Process Partner for a Transaction Create()
Data type: CRMS_SSC_PARTNER_INSOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for CRM_SSC_SRVREQ_CREATE 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_ct_header | TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS, " | |||
| lv_is_cm_bin_file_key | TYPE CRMS_PREFILL_CM_BIN_FILE_KEY, " | |||
| lt_it_product_i | TYPE STANDARD TABLE OF BAPIBUS20001_PRODUCT, " | |||
| lt_it_qualif | TYPE STANDARD TABLE OF CRMS_SSC_QUALIF_INS, " | |||
| lt_it_scheduleline | TYPE STANDARD TABLE OF BAPIBUS20001_SCHEDLIN, " | |||
| lt_it_service_i | TYPE STANDARD TABLE OF CRMS_SSC_SERVICE_I_INS, " | |||
| lt_it_service_os | TYPE STANDARD TABLE OF CRMS_SSC_SERVICE_OS_INS, " | |||
| lt_it_srv_req_h | TYPE STANDARD TABLE OF CRMS_SSC_SERVICE_REQUEST_H_INS, " | |||
| lt_it_status | TYPE STANDARD TABLE OF BAPIBUS20001_STATUS_INS, " | |||
| lt_it_subject | TYPE STANDARD TABLE OF CRMS_SSC_SUBJECT_INS, " | |||
| lt_it_survey | TYPE STANDARD TABLE OF CRMS_SSC_SURVEY_INS, " | |||
| lt_it_text | TYPE STANDARD TABLE OF BAPIBUS20001_TEXT_INS, " | |||
| lt_ct_item | TYPE STANDARD TABLE OF BAPIBUS20001_ITEM, " | |||
| lt_it_input_fields | TYPE STANDARD TABLE OF BAPIBUS20001_INPUT_FIELDS, " | |||
| lt_it_extension | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_it_cm_bin_file_content | TYPE STANDARD TABLE OF SDOKCNTBINS, " | |||
| lt_it_activity | TYPE STANDARD TABLE OF BAPIBUS20001_ACTIVITY_INS, " | |||
| lt_it_appointment | TYPE STANDARD TABLE OF BAPIBUS20001_APPOINTMENT_INS, " | |||
| lt_it_customer_h | TYPE STANDARD TABLE OF BAPIBUS20001_CUSTOMER_H, " | |||
| lt_it_customer_i | TYPE STANDARD TABLE OF BAPIBUS20001_CUSTOMER_I, " | |||
| lt_it_doc_flow | TYPE STANDARD TABLE OF CRMS_SSC_DOC_FLOW_INS, " | |||
| lt_it_organisation | TYPE STANDARD TABLE OF CRMS_SSC_ORGMAN_INS, " | |||
| lt_it_partner | TYPE STANDARD TABLE OF CRMS_SSC_PARTNER_INS. " |
|   CALL FUNCTION 'CRM_SSC_SRVREQ_CREATE' "Create Service Requests |
| EXPORTING | ||
| IS_CM_BIN_FILE_KEY | = lv_is_cm_bin_file_key | |
| TABLES | ||
| CT_HEADER | = lt_ct_header | |
| IT_PRODUCT_I | = lt_it_product_i | |
| IT_QUALIF | = lt_it_qualif | |
| IT_SCHEDULELINE | = lt_it_scheduleline | |
| IT_SERVICE_I | = lt_it_service_i | |
| IT_SERVICE_OS | = lt_it_service_os | |
| IT_SRV_REQ_H | = lt_it_srv_req_h | |
| IT_STATUS | = lt_it_status | |
| IT_SUBJECT | = lt_it_subject | |
| IT_SURVEY | = lt_it_survey | |
| IT_TEXT | = lt_it_text | |
| CT_ITEM | = lt_ct_item | |
| IT_INPUT_FIELDS | = lt_it_input_fields | |
| IT_EXTENSION | = lt_it_extension | |
| ET_RETURN | = lt_et_return | |
| IT_CM_BIN_FILE_CONTENT | = lt_it_cm_bin_file_content | |
| IT_ACTIVITY | = lt_it_activity | |
| IT_APPOINTMENT | = lt_it_appointment | |
| IT_CUSTOMER_H | = lt_it_customer_h | |
| IT_CUSTOMER_I | = lt_it_customer_i | |
| IT_DOC_FLOW | = lt_it_doc_flow | |
| IT_ORGANISATION | = lt_it_organisation | |
| IT_PARTNER | = lt_it_partner | |
| . " CRM_SSC_SRVREQ_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM CRM_SSC_SRVREQ_CREATE
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.Search for further information about these or an SAP related objects