SAP Function SSC_SR_PERSIST_CREATE_MANUALLY - Launch Service Request UI in create mode

Parameter Reference Type Length Default Optional Text
IS_APPLICATION_CONTEXT SSC_S_APPLICATION_CONTEXT v 176 Application Context for parameters transfer to CRM SR.
IS_APPLICATION_PERSISTENCE SSC_S_APPLICATION_PERSISTENCE v 168 Application Context which needs to be saved into Persistence
IX_CLOSED_SR ABAP_BOOL 0 ABAP_UNDEFINED X
IX_SHOW_EXISTING_SR BOOLE_D C 1 ABAP_TRUE X Boolean Variable (X=True, -=False, Space=Unknown)

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

Functionality
Application developers can use the function moduleSSC_SR_PERSIST_CREATE_MANUALLY to launch the CRM Service Request UI increation mode with prefilled values.
All application-relevant parameters can be passed in application contextlist in importing parameters. The main difference between functionmodule SSC_SR_CREATE_MANUALLY and SSC_SR_PERSIST_CREATE_MANUALLY is thatSSC_SR_PERSIST_CREATE_MANUALLY first saves some application informationinto local persistence tables SSCSR and SSCSRLINK for local reportingusage. If your application supports Local Reporting for ServiceReqeusts, application developers can use this function module to launchthe CRM Service Request UI in creation mode.

Description
Export parameter ET_MESSAGES returns messages raised during theoperation.

Description
Import parameter IS_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 IS_APPLICATION_PERSISTENCE is mandatory. It includesthe common attributes and application-relevant parameters that have tobe saved in local persistence table SSCSR and SSCSRLINK.

              Description
              The parameter IX_CLOSED_SR works together with parameterIX_SHOW_EXISTING_SR. This indicates whether only closed service requestsare displayed in local reporting UI. If this parameter equals toABAP_UNDEFINED, then all relevant service requests are displayed inthe local reporting UI.

              Description
              The parameter IX_SHOW_EXISTING indicates whether the local reporting UIfor existing and relevant service request lists are shown first of all.If this is the case, the user sees the local reporting UI first and canthen have the chance to launch Service Request UI in creation mode.