CC4 Focused Build Use Cases Configuration

Use Case 1: Create Requirements in external tool and synchronize them into SolMan

To display the link to the external ticket, it must be ensured that the value of the external ticket ID (IVEXTID) is stored in table/field CRMD_ORDERADM_H-/SALM/EXT_ID.

CC4-specific customizing

In the CC4 view cluster, in the Transaction Field Mapping & Conversion for transaction type S1BR (Focused Build Requirement), a new entry for attribute IVEXTID must be maintained accordingly:

Open

This entry enables the link in the UI5 app “My Requirements”:

Open

However, the link is still missing in the app “Requirements Management”:

In order to display the link in the app, some Focused Build-specific customizing is needed.

Focused Build-specific customizing

Transaction SPRO → SAP Solution Manager → Focused Build → Integration → Integrate External Requirement

Customizing for Outbound Update:

An entry for the respective configuration profile must be added:

This entry is necessary that the link to the external requirement is displayed in the app “Requirements Management”:

Use Case 2: Create Work Packages / Work Items in SolMan and synchronize them to an external tool

CC4-specific customizing

To display the link to the external ticket, it must be ensured that the value of the external ticket ID (IVEXTID) is stored in table/field CRMD_ORDERADM_H-/SALM/EXT_ID.

We must differentiate the following scenarios:

1. Outbound Create/Update Cloud using SX
   We receive the EXT_ID back. The SX method only saves it in the integration record if the customizing says so. Consequently, we need another attribute here to save the EXT_ID additionally somewhere else. The field mapping of IVEXTID must not be changed! The name of the new attribute can be anything, /SALM/EXTID is allowed.

2. Outbound Create/Update DC using SX
   Analogous to Cloud. Only the JSON path is different. In general, it is recommended to define the new attribute (e.g. /SALM/EXTID) as an alias to IVEXTID. This would make the customization of Cloud and DC identical because the path would be inherited from IVEXTID.

3. Outbound Create/Update DC using CR/UP
   IVEXTID is automatically saved in the integration record. The customizing can be bent so that EXTID is also saved in ORDERADM_H-/SALM/EXTID.

Outbound Create/Update Cloud using SX

A new attribute, e.g. /SALM/EXT_ID must be defined under Action Definition & Connection Settings - Create Outbound - Attribute Definition & Payload Mapping:

Checkbox ‘In’ must be ticked and th JSON path is ‘/key’:

Additionally, the new attribute must be maintained under Transaction Field Mapping & Conversion for the respective transaction type:

Attribute = <Attribute_Name>
Object Name = ORDERADM_H
Field Name = /SALM/EXT_ID

Outbound Create/Update DC using SX

A new attribute, e.g. /SALM/EXT_ID must be defined under Action Definition & Connection Settings - Create Outbound - Attribute Definition & Payload Mapping:

In = 'X'

Path Type = A Alias

Value Type = Autodetect

Dep. Attribute = IVEXTID

Additionally, the new attribute must be maintained under Transaction Field Mapping & Conversion for the respective transaction type:

Attribute = <Attribute_Name>
Object Name = ORDERADM_H
Field Name = /SALM/EXT_ID

Outbound Create/Update DC using CR/UP

In the CC4 view cluster, in the Transaction Field Mapping & Conversion for the respective transaction type, a new entry for attribute IVEXTID must be maintained accordingly:

Focused Build-specific customizing

Transaction SPRO → SAP Solution Manager → Focused Build → Integration → Integrate External Tools

External Tool Integration:

Either create a custom ‘External Integration Profile’ or use the standard /SALM/FBDF profile.

In the Process Types Mapping the process types that should be synchronized must be maintained.

Mapping for external Tool Integration:

Maintain an entry for every Focused Build project that should be synchronized to an external tool (Focused Build project must be mapped to an ‘External Integration Profile’).

This entry is mainly needed for the correct jump in URL to the external ticket. Without the entry the ‘external Tool ID’ may be displayed in the Work Package / Work Item but is pointing to a wrong destination.