SAP Function SSC_SR_MASS_PERSIST_CREATE - Mass Creation of Service Request with Persistence

Parameter Reference Type Length Default Optional Text
IT_APPLICATION_CONTEXT SSC_T_APPLICATION_CONTEXT h 176 Shared Service Cetner: Application Context
IT_APPLICATION_PERSISTENCE SSC_T_APPLICATION_PERSISTENCE h 168 Table of App. Context which needs to be saved into Pers.

Parameter Reference Type Length Text
ET_MESSAGES BAPIRETTAB h 548 Table with BAPI Return Information

Functionality
Application developers can use the function moduleSSC_SR_MASS_PERSIST_CREATE to mass create CRM Service Requests in queueand asynchronous way by means of CRM Middleware instead of usingexisting synchronous foundation API SSC_SR_CREATE.
The main difference between function module SSC_SR_MASS_CREATE andSSC_SR_MASS_PERSIST_CREATE is that SSC_SR_MASS_PERSIST_CREATE firstsaves some application information into local persistence table SSCSRand SSCSRLINK for local reporting usage. If your application supportsLocal Reporting for Service Reqeusts, application developers can usethis function module to mass create CRM Service Requests.
The logic inside this function module considers the application contextand application persistence, which share the same Handle and belong tothe same Service Request scope.

Description
Export parameter ET_MESSAGES returns messages raised during theoperation.

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_APPLICATION_PERSISTENCE is mandatory. It includesthe common attributes and application-relevant parameters that have tobe saved in local persistence tables SSCSR and SSCSRLINK.