Manhattan Active SCI Status

Track and monitor the usage of SCI across Manhattan Active® products

1: Troubleshooting Guidelines

Overview

The Manhattan Active SCI Status tracks and monitors the usage of SCI across Manhattan Active® products. It intends to continuously monitor and inform users to take proactive actions for interactive and scheduled reports, performance and configuration-related issues, and long-running reports that signal a potential risk of crashing and avoid downtime.

You can access it by navigating to Team Content > SCI Audit Reports > System Activity > Manhattan Active SCI Status.

Manhattan Active SCI Status contains the date filter which you can use to reflect data accordingly. The following table explains the sections it includes. Some sections comprise links to detailed reports that you can view for more insights and analysis.

Report Prompt

The following table explains the fields on the prompt page of this report:

Prompt Field	Description
Select Date	The default value for this filter is ‘Last 24 Hr’, and you can also select a date from the last 15 days.
Report Type	You can select the report type that fetches values from ‘Report reportservice’, ‘ReportView reportservice’, or ‘Exploration queryservice’.
Type	You can run the report for Standard and Unsaved reports.

Report Sections

The following table describes the sections in the Manhattan Active SCI Status report and their color coding parameters:

Section Name	Description	Color Code for Visualization
Reports in 24Hrs	This visualization includes two metrics for Interactive and Scheduled reports to capture the number of reports users execute in the SCI instance. Detailed Report: You can access the drill-down or detailed report for interactive and scheduled reports by clicking the links on the numbers. This page provides the report name, timestamp, username, package, execution status, execution time in seconds, and issues. You can also filter the drill-down reports by report name and/or username.	Note: The Interactive and Scheduled report metrics do not have any threshold defined.
Failed Reports	This visualization indicates the percentage of reports that failed to generate for the date you select. Detailed Report: This section also contains a link to the drill-down or detailed report that includes the report name, timestamp, username, package, report type, execution time in seconds, issues, error details, and KB link. You can also filter the drill-down reports by report name and/or username.	Green : less than 2% , Yellow : between 2 and 3% , Red : greater than or equal to 3%
Long Running Reports	This section provides the number of reports that ran for more than two minutes for Interactive and 30 minutes for schedule. Depending upon the data availability, this report displays either a Green check or a bar visualization for a report type as shown in the image. Detailed Report: To access the drill-down or detailed report for interactive and scheduled reports, Red double-click individual columns on the bar visualization. The detailed report provides the report name, timestamp, username, package, execution status, execution breakdown time, execution time in seconds, and issues.	Color Codes for Interactive Reports : Green : greater than or equal to 0 but less than or equal to 2, Yellow : greater than or equal to 2 but less than or equal to 5, Red : greater than 5, Maximum: 8. Color Codes for Scheduled Reports: Green : less than or equal to 30, Yellow : greater than or equal to 31 but less than or equal to 60, Red : greater than 60, Maximum: 90
Max Runtime Minutes Per Hour	This section provides the highest execution time in minutes per hour for a day and the time interval when it is at its maximum.	Note: The report metrics do not have any threshold defined.
Ad hoc Reports	This section provides a count of all ad hoc or unsaved reports users execute. Detailed Report: You can access the drill-down or detailed report by clicking the links on the number. This page provides the report name, timestamp, username, package, execution status, report type, and execution time in seconds. You can also filter the drill-down reports by report name and/or username.	Green : less than or equal to 2, Yellow : greater than or equal to 2 but less than or equal to 5, Red : greater than 5
Operational Documents	This section highlights the number of operational documents that users execute. Examples of these documents are packing lists, bills of lading, and others.	Red : greater than 0
Multiple Users Same Report	This section provides the number of reports that multiple users execute in an hour of a day. Detailed Report: You can access the drill-down or detailed report by clicking the links on the number. This page provides the report name, timestamp, username, package, execution status, report type, and execution time in seconds.	Green : greater than or equal to 0 but less than or equal to 5, Yellow : greater than or equal to 5 but less than or equal to 10, Red : greater than 10

Report Types

The following table summarizes the standard IBM Cognos report types used in Operational SCI and their category in the Manhattan Active SCI Report:

IBM Cognos Service Type	Report Type	Metric Category/Usage in Manhattan Active SCI Status Report
Exploration queryservice	Dashboards/Story	Not considered in the MA Active status report
Exploration queryservice	Unsaved Report	Adhoc
Report reportservice	Unsaved Report	Interactive / Adhoc
Report reportservice	Standard Report	Interactive
Report batchreportservice	Standard Report	Scheduled
ReportView batchreportservice	Standard Report	Scheduled
Report promptforward reportservice	Unsaved Report	Not considered in the MA Active status report
Report promptforward reportservice	Standard Report	Not considered in the MA Active status report

Manhattan Active SCI Status

Drill-down report for reports in 24Hrs

Drill-down report for long-running reports

Drill-down report for failed reports

Drill-down report for multiple users same report

Drill-down report for ad hoc reports

1 - Troubleshooting Guidelines

Recommended guidelines for Manhattan Active Status Reports

Overview

This document outlines best practices for managing long-running reports, addressing report failures, and efficiently utilizing ad-hoc reporting in SCI. Adhering to these guidelines will help maintain optimal system performance.

Long-Running Reports

A long-running report takes more time than expected to execute.

General Guidelines to avoid long-running reports (interactive and scheduled)

Understand user requirements: Focus on key metrics/KPIs to avoid unnecessary data, minimizing processing time.
Limit data retrieval:
- Implement filtering options to restrict the volume of data processed and displayed.
- Enable users to select specific time periods and other necessary prompts before running the report.
Use summary reports: Instead of detailed reports, create summary reports that provide high-level insights without processing more data.
Break down complex reports: If a report is complex, consider splitting it into smaller, more manageable reports/sections based on the use case.
Optimize data sources: After applying the other recommendations and if the report is still slow, connect with MA services to verify the indexes.

Scheduled Reports

Schedule during off-peak hours: Whenever possible, schedule long-running reports during off-peak hours when system usage is lower. Also, pay attention to the frequency of scheduling.

Failed Reports

Follow the recommendations below to minimize the failures.

Review error messages: Verify the error message and resolve the issue if the failure is self-explanatory.
Attempt to re-run the report: If the failure was possibly a one-time issue, try executing the report again after a brief wait.
Verify data sources: Ensure all required data sources are accessible from the Cognos admin console.
Check report logic: Review any filters, calculations, and joins for potential issues that may cause failures.
Document the failure: Keep a record of the failure, including error codes and any relevant details of the resolution, for future reference.

Ad-Hoc Reports

Ad-hoc reports are generated on a need basis to meet specific business requirements quickly. They allow users to analyze data flexibly and dynamically.

Leverage existing reports: Before creating a new ad-hoc report, check if an existing report can be adjusted to meet the business needs.
Limit data scope: Focus on specific datasets relevant to the use case to improve performance and reduce execution time.
Understand the purpose: Clearly define what is needed from the ad-hoc report to avoid unnecessary complexity.
Avoid excessive runs: Be mindful of the number of ad-hoc report executions within a short timeframe, as it may affect overall system performance.
Utilize report parameters: Use prompts effectively to customize reports without creating multiple versions of the same report.

Operational Documents

Operational documents are reports that offer insights into the performance, status, and tracking of various supply chain operations. SCI should not be used for creating or running operational document reports, such as Bills of Lading, Packing Slips, Worksheets, or Manifests.

Multiple Users Running the Same Report

Follow the below recommendations:

Schedule reports: Encourage users to schedule reports to avoid simultaneous, on-demand generation.
Use prompts and filters: Implement dynamic prompts and filters to tailor reports to individual user needs.
Consolidate and standardize reports: Minimize redundancy and ensure that users are running the latest versions of reports.
Leverage report bursting: Use bursting to generate personalized reports and distribute them automatically.