SAP Function SSC_SR_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_SCREENSHOT SSC_S_SCREENSHOT v 16 X Screenshot Image Data Structure
IX_NO_SAPGUI BOOLEAN C 1 ' ' X Boolean Variable (X=True, -=False, Space=Unknown)
IX_NO_SAPGUI_SCREENSHOT BOOLEAN C 1 ' ' Boolean Variable (X=True, -=False, Space=Unknown)

Parameter Reference Type Length Text
ET_MESSAGES BAPIRETTAB h 548 Table with BAPI Return Information
EV_UI_OBJECT_ACTION SSC_UI_OBJECT_ACTION C 2 UI Object Action
EV_UI_OBJECT_TYPE SSC_UI_OBJECT_TYPE C 20 UI Object Type
EV_UI_OBJECT_VALUE SSC_UI_OBJECT_VALUE C 32 UI Object Value
EV_URL STRING g 0 URL for the SAP Portal

Functionality
An application developer can use the function moduleSSC_SR_CREATE_MANUALLY to launch CRM Service Request UI in creation modewith prefilling values. All application relevant parameter can be passedin application context list in importing parameters.

Description
export parameter ET_MESSAGES returns messages raised during theoperation.

Description
A URL for Service Request UI can be returned in exporting parameterEV_URL. Application developer can use this URL to launch Service RequestUI later.

Description
import parameter IS_APPLICATION_CONTEXT is mandatory. It includes thecommon and application relevant attributes:
GUID: technical identification of service request. If HANDLE isprovided, a GUID will be generated for created service request
HANDLE(mandatory): a random 10-digit number used to link service requestto its sub-objects. Only ensure that the handle is unique in currentcall
SCENARIO(mandatory): your application defined in the customizing
ELEMENT(mandatory): your activity defined in the customizing
BUSINESS_PARTNERS
- PARTNER_NO: business partner number
- PARTNER_NO_TYPE: type of business partner number. 'BP' is partnernumber and '' is partner GUID.
- PARTNER_FUNCTION_CATEGORY: partner function category. It willdecide the UI field to which the partner number is assigned. Avaiablevalues are 0001(Customer), 0007(Reporter), 0008(Employee responsible)and 0016(Service team).
COMPANY_CODE: company code
TITLE: description of service request
NOTE
- NOTE_TYPE: note type. It can also be set in static paramtertransfer customizing. Available note types are defined in CRM textdetermination procedure
- TDFORMAT: '*' is new line and paragraph, and '=' is concatenation
- TDLINE: note line, 132 characters at most
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, could beBLLO for linked object in business context tab by default if developerleave it initial or SRAC for ERP anchor to indicate creation of ServiceRequests is triggered out of ERP
ADDITIONAL_INFO: if you define source fields in your scenario, you needto pass their values through this parameter. You can also pass someapplication-special attribute values through it if you want to make yourown parameter transfer in Business Add-In SSC_PARA_TRANSFER

Description
If importing parameter IX_NO_SAPGUI_SCREENSHOT is false, thenapplication developers can decide whether they will also pass screenshotdata directly into this function module to transfer to Service Requestattachment or not. If nothing is supplied for this parameter. Thefunction module inside has the logic to get the screenshot.

Description
importing parameter IX_NO_SAPGUI indicates whether Service Request UI islaunched in the SAPGUI context or not. If Service Request UI is launchedin non SAPGUI context like web dynpro, then the function module SSC_S
R_CREATE_MANUALLY will not directly launch CRM UI, instead a URL forService Request UI will be returned in exporting parameter EV_URL.Application developer can use this URL to launch Service Request UIlater.

Description
importing parameter IX_NO_SAPGUI_SCREENSHOT indicates whether functionmodule SSC_SR_CREATE_MANUALLY has to catch screenshot and pass it toService Request as an attachment.