In newest release of Focused Build SP16, the solution readiness dashboard has been enhanced to incorporate external tool integration-related fields within the requirements, work packages, and work items details pages. This integration helps users to track and report on the entities that were initially created or derived from external tools such as JIRA and then transferred to Focused Build.
Background
Previously, customers had no way to view or report on external tool integration (Mapping field -external Id) within any Focused Build reporting feature. This limitation resulted in an inability to report on all requirements, work packages, or work items that originated in an external tool and were subsequently transferred to Focused Build.
Integration Enhancements
To address these limitations, the field External Id has been made available for reporting in the following areas:
Requirements
Requirements Details
External Tool fields in Requirement Details Page
Work Packages
Work Packages Details
Work Packages KPI Details
Work Packages Distribution
External Tool fields in Work package Details Page
Work Items
Work Items Details
Work Items KPI Details
Work Items Distribution
External Tool fields in Work Item Details Page
Technical details for fetching and displaying the external fields
Specifics for Requirements:
For requirements, the reporting includes the combination of the following fields:
CRM_ORDERADM_H-/SALM/EXT_ID: The external tool ID.
System GUID (/SALM/C_EXI_MAPP-GUID_EXT): The globally unique identifier for the external system.
These fields are necessary to correctly map the external system and the corresponding ID.
Specifics for Work Packages and Work Items:
For work packages (WPs) and work items (WIs), the reporting requirements are more specific:
The combination of CRM_ORDERADM_H-/SALM/EXT_ID and External System Profile (/SALM/C_EXI_PRJ-EXI_PROFILE) must be included for reporting.
This is only applicable when CRM_ORDERADM_H-/SALM/EXI_ACTIVE = ‘X’—indicating that integration with the external tool is active.
Benefits
With these enhancements, customers now have the ability to:
Track and report on the entities derived/created in external tools.
Enhance reporting and visibility, ensuring that external tool integrations are accurately tracked and managed.
Also, it is possible to extract the external tool related fields to an excel from respective detailed pages of solution readiness dashboard.
Introduction In newest release of Focused Build SP16, the solution readiness dashboard has been enhanced to incorporate external tool integration-related fields within the requirements, work packages, and work items details pages. This integration helps users to track and report on the entities that were initially created or derived from external tools such as JIRA and then transferred to Focused Build. Background Previously, customers had no way to view or report on external tool integration (Mapping field -external Id) within any Focused Build reporting feature. This limitation resulted in an inability to report on all requirements, work packages, or work items that originated in an external tool and were subsequently transferred to Focused Build. Integration Enhancements To address these limitations, the field External Id has been made available for reporting in the following areas: Requirements Requirements Details External Tool fields in Requirement Details Page Work Packages Work Packages Details Work Packages KPI Details Work Packages Distribution External Tool fields in Work package Details Page Work Items Work Items Details Work Items KPI Details Work Items Distribution External Tool fields in Work Item Details Page Technical details for fetching and displaying the external fields Specifics for Requirements: For requirements, the reporting includes the combination of the following fields: CRM_ORDERADM_H-/SALM/EXT_ID: The external tool ID. System GUID (/SALM/C_EXI_MAPP-GUID_EXT): The globally unique identifier for the external system. These fields are necessary to correctly map the external system and the corresponding ID. Specifics for Work Packages and Work Items: For work packages (WPs) and work items (WIs), the reporting requirements are more specific: The combination of CRM_ORDERADM_H-/SALM/EXT_ID and External System Profile (/SALM/C_EXI_PRJ-EXI_PROFILE) must be included for reporting. This is only applicable when CRM_ORDERADM_H-/SALM/EXI_ACTIVE = ‘X’—indicating that integration with the external tool is active. Benefits With these enhancements, customers now have the ability to: Track and report on the entities derived/created in external tools. Enhance reporting and visibility, ensuring that external tool integrations are accurately tracked and managed. Also, it is possible to extract the external tool related fields to an excel from respective detailed pages of solution readiness dashboard. Important Links and Resources: Focused Build for Solution Manager Agile Project Delivery with Focused Build for SAP Solution Manager ALM Community page Read More Technology Blog Posts by SAP articles
