Multi-Level Categorization
- CrossALM
- Yannic Zinke
This article shows how to configure the synchronization of the Multi-Level Categorization (MLC) entries. The configuration shows both directions, Jira → SolMan and SolMan → Jira.
For the setup of the synchronization of the MLC entries, a field on Jira side of type Select List (cascading) is needed. Please be aware that this field type only supports two hierarchy levels even though more than two hierarchy levels are used on SolMan side. That means, only the first two hierarchy levels can be synchronized between SolMan and Jira.
Set Up on Jira side
Prerequisites
(Custom) field of type Select List (cascading).
Inbound Configuration:
JSON Key | Function | Field | Custom Field ID |
|---|---|---|---|
IVCATEGORY | Import | Custom Field | customfield_<ID of custom cascading field> (e.g. customfield_10702) |
Outbound Configuration:
JSON Key | Function | Field | Custom Field ID |
|---|---|---|---|
IVCATEGORY | Export | Custom Field | customfield_<ID of custom cascading field> (e.g. customfield_10702) |
Set Up on SAP side
Prerequisites
Active MLC schema that is assigned to the transaction type that is to be synchronized.
Viewcluster Customizing
Transaction Field Mapping & Conversion
Attribute | Object Name | Field Name | Logical Key |
|---|---|---|---|
IVCATEGORY | SUBJECT | CAT_ID | C/D (Catalog Category that is assigned to the transaction type) |
To find out which value has to be entered in the field Custom Field ID, please take a look at the MLC schema.
Transaction Value Mapping
Attribute | Internal Value | External Value |
|---|---|---|
IVCATEGORY | Category ID of SolMan category | Text of the first two category levels separated by “/” |