| Table of Contents | ||||
|---|---|---|---|---|
|
...
Please import the SAP Transport Requests provided to you after reaching out to solutions@crossalm.com https://crossalm2.atlassian.net/servicedesk/customer/portal/6 these include the oData Services necessary to continue with the configuration.
...
SAP - Focused Build Business Requirement (Standard)
Create Configuration Profile (Standard Mode)
Goto SPRO → SAP Solution Manager Implementation Guide → SAP Solution Manager → Cross Connector → Configuration / Mapping → Create new customizing profile.
Run this report (/XALM/CC4_CUST_CREATE).
It will create a new configuration profile based on one of our templates.
After creation is completed, you might need to adjust the profile to your needs as described below. Please do’t forget to add the complete configuration profile to your transport request using transaction SM34.
Update Configuration Profile (Standard Mode)
After updating to a new version of our Cross Connector, some new features might be available. Since you already created your own configuration profile these new features might not be available to you out of the box. In order to activate these new features (for instances attachment support), please run the report (/XALM/CC4_CUST_UPDATE)
SPRO → SAP Solution Manager Implementation Guide → SAP Solution Manager → Cross Connector → Configuration / Mapping → Update existing customizing profile.
Content Mapping via view cluster Maintenance (Expert Mode)
The shipped transport mentioned above introduces a view cluster that serves as mapping table for all synchronization calls.
...
In section Field Definition you find a collection of all JSON keys that are used by the interface. As specified in the Jira configuration section for this template some of these are purpose bound and can therefore not be mapped freely.
Currently it is not possible to send data with JSON keys deviating from this list:
JSON field | Note |
|---|---|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| only available SAP inbound |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
...
By default the shipped transport includes a some sample mappings.
...
Field Mapping
...
Object Key | Description | Notable Examples |
|---|---|---|
| Standard SAP Header fields | Title |
| Customer Fields | any custom field |
| Standard SAP Activity fields | Priority |
| Status | Status |
| Text types | Description (long) |
| Partner Functions | Creator |
| Service Process | Long Description (up to 120 character) |
| Sales | External Reference |
| Service Request Header Fields | Urgency, Impact |
| Categories | Category 1-4 |
| Attachments | URLs and File attachments |
Mandatory - Status
JSON key IVSTATUS has to be mapped with object STATUS
...
Otherwise, if a predecessor is mapped, no custimizing customizing for the predecessor Id is required.
...
To map both category one JSON key has to be mapped for each category, e.g. IVCATEGORY and IVCUSTOM01. Both field fields have to be mapped with the object SUBJECT and the logical key receives the value of the technical ID of the catalog type for the category scheme, e.g. C or D.
...
The specified SOCM actions can also be called via PPF action.
This option has be the added benefit of freely choosing the execution time of the outbound update but requiring requires more effort to set up.
Open administration of ppf actions via transaction SPPFCADM and navigate to the action of the process type you want to synchronize.
...
Also, the field ‘Direction’ helps to Identify identify whether the synchronization was inbound or outbound.
...