Supply Chain Task Reference
The Supply Chain Framework provides tasks which you should add to Task Manager schedule so that they run at suitable times for your business needs. This page briefly describes all these tasks.
Task Reference
Starts issue analysis. This task looks at all non-closed issues that have an associated BPL and that do not yet have an issue analysis record. For these issues, the task creates a new issue analysis. In the Visual Trace for the production, you will see SC.Core.BP.Service.SingleIssueSS receiving an issue analysis request message. SC.Core.BP.Service.SingleIssueSS will then send a message to the business process that is named by the issue.
If the business process includes workflow, the Visual Trace will also show the workflow components as applicable.
Rebuilds all of the predefined BI cubes.
Checks all issue analyses which are in the running custom bp state, and updates their state to "workflow, completed, or failedbased on the status of the custom business process.
Closes or cancels issues after a user resolves them through workflow analysis.
Deletes bulk upload data that either failed to upload or is archived for more than DaysToSave days.
Computes predicted inventory over forecastWindow days for all products and locations.
Performs a cube sync on the predefined BI cubes (except for Consolidated/PredictedInventory, which are populated daily, and IssueCube, which has its own task). A cube sync updates a cube with changes from the source data; this is an alternative to a full cube rebuild.
Performs a cube sync on the issue cube. A cube sync updates a cube with changes from the source data; this is an alternative to a full cube rebuild.
Errors out issue analyses which have been running custom business processes for more than TimeoutHours hours.
Generates issues as needed for KPIs. Specifically, this task does the following for each issue-enabled KPI:
-
Identify the records that triggered the KPI condition (such as the late orders).
-
Check to see if the database contains issues that correspond to these records in combination with this KPI. If the issues do not yet exist, the task creates them, using information contained in the KPI definition, including the name of the business process that analyzes this kind of issue by default. The new issues have open status.
-
Check to see if the database contains additional records associated with this KPI (records not currently triggering the condition but that previously did so). If so, the task updates those issues to close them; specifically it sets the status to closed, and resolutionType to noLongerValid.