How to Flag Unused Documents with 360Eyes

How to Flag Unused Documents with 360Eyes

Overview

360Eyes can automatically identify unused documents on your BusinessObjects platform by analyzing usage data from the SAP BusinessObjects Audit database. Unused documents are flagged with the tag #TOARCHIVE in their description field, making them easy to target for archiving or deletion with 360Plus.

Prerequisites

  • SAP BusinessObjects Auditing must be enabled and configured (see SAP BusinessObjects Auditing vs. 360Suite – Understanding the Difference).

  • The 360Eyes Audit database connection must be configured in the 360Suite Admin Console.

Procedure

1. Configure the flagging parameters

Update the following parameters in 360Eyes.param:

Parameter

Description

Example value

ia.content

Report types to analyze

Webi, CrystalReports

content.flag

Enable flagging

ON

content.flag.month

Number of months without usage to consider a document unused

13 (most common)

2. Run the 360Eyes_IA job

Run the job with the -no_impact_analysis flag so that only the usage analysis and flagging step is executed.

To add the flag:

  1. In the CMC, go to Folders → 360Eyes Jobs.

  2. Right-click 360Eyes and select Default Settings.

  3. Select Program Parameters.

  4. Append -no_impact_analysis to the Arguments field.

Result

All documents matching the criteria (report type and inactivity period) will have #TOARCHIVE added to their description field. These flagged documents can then be archived or cleaned up using 360Plus.

Next Steps

    • Related Articles

    • How to Archive Flagged Documents with 360Plus

      Overview After unused documents have been flagged by 360Eyes (identified by the #TOARCHIVE tag in their description), use 360Plus to safely back them up and move them to an archive location. Prerequisites Unused documents must already be flagged with ...

    • 360Eyes evolution: from "standalone" to 360Suite web application

      Context On the meta-level, 360Eyes is part of 360Suite, a suite a modules working with BusinessObjects environments to help BI administrators with their day-to-day activities. On a practical level, the 360Eyes module itself has known changes over ...

    • SAP BusinessObjects Auditing vs. 360Suite – Understanding the Difference

      Purpose This article clarifies a common misconception: SAP BusinessObjects Auditing (commonly referred to as "Auditor") is not a 360Suite module. It is a native SAP BusinessObjects feature. This distinction matters when checking whether Auditing is ...

    • Handling UNISTR() Function Issue when Migrating 360Eyes Repository from Oracle to PostgreSQL

      Introduction This article explains a known behavior when migrating a 360Eyes repository from Oracle to PostgreSQL: Web Intelligence can generate SQL that includes UNISTR(), which is Oracle-specific, UNISTR() are generally used via filter on ...

    • "Invalid tag: FORMAT_DICT" error

      Symptoms After upgrading a BusinessObjects (BOBJ) environment, you may encounter the error with 360Suite feature like 360Cast or 360Bind: Unexpected exception: Failed to parse document. Invalid tag: FORMAT_DICT These features typically work with ...