SAP Function SSC_SR_CHANGE_BD - Change service request(s)

Parameter Reference Type Length Default Optional Text
IT_ACTIVITY SSC_T_SRVREQ_ACTIVITY_INS h 1736 X Shared Service Center: Activity inserting table
IT_APPLICATION_CONTEXT SSC_T_APPLICATION_CONTEXT h 176 Shared Service Cetner: Application Context
IT_APPOINTMENT SSC_T_SRVREQ_APPOINTMENT_INS h 171 X Shared Service Center: Appointment inserting table
IT_CUSTOMER_H SSC_T_SRVREQ_CUSTOMER_H_INS h 43 X Shared Service Center: Customer header inserting table
IT_CUSTOMER_I SSC_T_SRVREQ_CUSTOMER_I_INS h 43 X Shared Service Center: Customer item inserting table
IT_EXTENSION BAPIPAREXTAB h 990 X Table with BAPIPAREX as Row Type
IT_INPUT_FIELDS SSC_T_INPUTFIELD h 146 X Shared Service Center: Fields Entered
IT_ITEM SSC_T_SRVREQ_ITEM_INS h 442 X Shared Service Center: Administration Item inserting table
IT_ORGANISATION SSC_T_ORGMAN_INS h 151 X Shared Service Center: Organisation data inserting table
IT_PRODUCT_I SSC_T_SRVREQ_PRODUCT_I_INS h 232 X Shared Service Center: Product data inserting table
IT_QUALIF SSC_T_QUALIF_INS h 125 X Shared Service Center: Qualification inserting table
IT_SCHEDULELINE SSC_T_SRVREQ_SCHEDLIN_INS h 251 X Shared Service Center: Schedule line inserting table
IT_SERVICE_I SSC_T_SERVICE_I_INS h 486 X Shared Service Center: Service Item inserting table
IT_SERVICE_OS SSC_T_SRVREQ_SERVICE_OS_INS h 173 X Shared Service Center: Subject inserting table
IT_SRV_REQ_H SSC_T_SERVICE_REQUEST_H_INS h 113 X Shared Service Center: Service Request Header inserting tab
IT_STATUS SSC_T_SRVREQ_STATUS_INS h 61 X Shared Service Center: Status inserting table
IT_SUBJECT SSC_T_SUBJECT_INS h 552 X Shared Service Center: Subject inserting table
IT_SURVEY SSC_T_SURVEY_INS h 183 X Shared Service Center: Survey inserting table
IV_SCENARIO SSC_SCENARIO C 10 Shared Services Center: Application

Parameter Reference Type Length Text
ET_HEADER SSC_T_SRVREQ_HEADER_UPD h 113 Shared Service Center: Administration Header changing table
ET_RETURN BAPIRETTAB h 548 Table with BAPI Return Information

Functionality
An application developer can use the function module SSC_SR_CHANGE tochange one or more Service Requests without UI. In the applicationcontext in the importing parameters, consumers have to provide theService Request GUID.
There are import parameters for service request related sub-objects,such as activity, organization, or appointment. REF_GUID is the GUID ofchanged service requests. Subobjects Partner, ObjectReference and Notes are not displayed because they are readfrom the application context.

Description
Import parameter IT_APPLICATION_CONTEXT is mandatory. It includes thecommon attributes and the following application-relevant parameters:

  • GUID: technical identification of service request. If HANDLE is
    • provided, a GUID is generated for created service requests.
    • HANDLE (mandatory): a random 10-digit number used to link a service
      • request to its sub-objects. Ensure that the handle is unique in currentcall.
      • SCENARIO (mandatory): your application, defined in Customizing

      • ELEMENT (mandatory): your activity, defined in Customizing

      • BUSINESS_PARTNERS

        • PARTNER_NO: business partner number
        PARTNER_NO_TYPE: type of business partner number. 'BP' is partner numberand '' is partner GUID.
        PARTNER_FUNCTION_CATEGORY: partner function category. It will decide theUI field to which the partner number is assigned. Available values are0001 (Customer), 0007 (Reporter), 0008 (Employee responsible) and 0016(Service team).
        • COMPANY_CODE: company code

        • TITLE: description of service request

        • NOTE

          • NOTE_TYPE: note type. This can also be set in static parameter transfercustomizing. Available note types are defined in CRM text determinationprocedure.
          TDFORMAT: '*' is new line and paragraph, and '=' is concatenation
          TDLINE: note line, up to 132 characters
          • LINKED_OBJECTS

            • OBJKEY: linked object key, concatenation of BOR key values
            OBJTYPE: linked object type, BOR type
            LOGSYS: logical system of linked object
            RELTYPE: the binary relationship with Service Request. It could be BLLOfor linked objects in business context tab by default if the developerleaves it initial. Alternatively, it could be SRAC for ERP anchor toindicate that creation of Service Requests is triggered out of ERP.
            • ADDITIONAL_INFO: if you define source fields in your scenario, you need
              • to pass their values through this parameter. You can also pass someapplication-specific attribute values through it if you want to makeyour own parameter transfer in Business Add-In SSC_PARA_TRANSFER

              Description
              Import parameter IT_INPUT_FIELDS includes fields and their values youwill store in the service request. You need to use it only if subobjectparameters are filled.