Issue Management

Identifying and Generating Issues

Supply Chain Orchestrator provides many ways to identify and formally generate issues.

• Through KPIs. If a KPI is configured to generate issues, an automated system task (SC.Core.Tasks.UpdateKPIssue) evaluates that KPI and generates issues for every record that meets the KPI conditions. For example, a late-delivery KPI for sales orders can generate an issue for every late-delivery order.

• Through BPL/DTL processes in Supply Chain Orchestrator. Any data integration or business process can be used to generate issues for specific conditions.

• By a Smart Data Service (SDS). For example, a SDS can be implemented to subscribe to external events, and determine the impacts on current supply chain. Such impacts can be captured in the form of issues and persisted in InterSystems IRIS.

  The SDS would use the data APIOpens in a new tab to create issues.

• Sent in from external systems. Supply chain risks can be determined outside Supply Chain Orchestrator. For example, a manufacturing application may determine a part shortage for certain product at a plant, and the information can be sent to Supply Chain Orchestrator as an issue through API for issue resolution and reporting purpose.

  The external system would use the data APIOpens in a new tab to create issues.

• Your own custom logic, which would scan the relevant tables periodically and then use the data APIOpens in a new tab to create issues.

In each case, Supply Chain Orchestrator generates issues in an internal table, which is then available for automated processing and for your API calls, depending on the use case.

Running Issue Analysis

After an issue has been generated, your code can run an issue analysis. This can happen in several different ways:

• For an issue generated by a KPI, an automated system task (SC.Core.Tasks.AnalyzeAllNewIssues) starts issue analysis. The analysis is defined in an InterSystems IRIS business process by using a graphical UI that is designed for business logic.

• For other issues, your code must invoke the analytics API to start issue analysis.

Issue Management API Details

For reference, the data APIOpens in a new tab includes options for creating and getting issues:

Creating an issue

POST {{IRIS-SERVER}}/api/scbi/v1/issues

With the issue value in JSON format added to the body of the request.

Getting issues

GET {{IRIS-SERVER}}/api/scbi/v1/issues

Additional query parameters based on any issue attributes can be added in the form of HTTP parameters, such as `status=open`.

Also, the analytics API includes options for running issue analysis and managing issues:

Updating issues for a KPI

POST {{IRIS-SERVER}}/api/scbi/v1/kpiissues

Forces an issue update for the given KPI. This applies to KPIs that are issue-enabled. In this case, specify KPI information in the JSON body data, for example:

{
    "kpi": "SalesOrderLateShipVsCommitted"
}

Forcing a new analysis for an issue

POST {{IRIS-SERVER}}/api/scbi/v1/runissueanalysis/[ISSUE-ID]

This option applies if a business process is associated with an issue. In this case, specify the process to use by including the following JSON body data:

{
    "processName": "YourProcessName"
}

For an example, see Testing the Business Process.

See Also

• Supply Chain Solution Overview

• API Reference

• Supply Chain Task Reference