Show TOC

Calculation Report - Automatic Run vs. Manual SchedulingLocate this document in the navigation structure

Changes to the content of the SAPUI5 ABAP repository require the index to be updated using the calculation report /UI5/APP_INDEX_CALCULATE. Depending on how the content of the repository is changed, the report is executed automatically or you have to run it manually.

Changes to Content in the Repository

This scenario usually happens in development systems. The content is changed, for example, by uploads from development tools like SAP Web IDE or Eclipse, the available SAPUI5 repository upload and download reports, the implementation of an SAP Note, or manual changes using transaction SE80 (the latter is not supported and therefore not recommended at all).

The execution of the report to update the index is in most cases triggered automatically. Exceptions: implementation of SAP Notes, changes to texts in the text repository with ABAP translation tools, and manual changes using transaction SE80 (not supported and therefore not recommended). In these cases, you have to trigger an update for the applications in question manually or schedule a full calculation of the index with a reasonable time interval. Here’s an overview:

Type of Change to the SAPUI5 ABAP Repository

Manual Execution of the Calculation Report Required?

Deployment with SAP Web IDE

No, the report is executed automatically.

Upload with report /UI5/UI5_REPOSITORY_LOAD

Synchronization from Eclipse using the team repository provider (version 1.30.x or higher)

Installation of a new version of the SAPUI5 distribution layer

(SAP Note 2209229 is applied in the system for user interface add-on for SAP NetWeaver 2.0 SP01.)

Synchronization from Eclipse using the team repository provider (version 1.28.x or below)

Yes, run the report manually to update the index for the app or distribution layer in question.

Implementation of an SAP Note containing changes for an SAPUI5 app

Installation of a new version of the SAPUI5 distribution layer

(SAP Note 2209229 is not applied in the system for user interface add-on for SAP NetWeaver 2.0 SP00.)

Manual changes using transaction SE80 (not supported and therefore not recommended)

Import of Content to the Repository

This scenario usually happens in test and production systems. The system automatically updates the index after transports which have been imported under certain conditions, for example, which version of the user interface add-on for SAP NetWeaver is installed and whether the Business Add-In (BAdI) CTS_IMPORT_FEEDBACK is called after an import. For more information, see SAP Note 2253480.

If you are unsure whether the BAdI is called, you can verify this in the import log of a transport. The BAdI is called if the import log contains a Feedback after import or export entry (there might be one after import and one after export entry) and the after import entry contains the following logs:

  • Start: Executing method FEEDBACK_AFTER_IMPORT for business add-on CTS_IMPORT_FEEDBACK

  • Scheduled index update after finished import of transports

Here’s how you can decide whether you need to schedule the report after transports:

If the version of the user interface add-on for SAP NetWeaver is lower than 2.0 SP02, the report is not executed automatically and you have to schedule it manually. If the version is 2.0 SP02 or higher and the import is triggered by ABAP, the report is executed automatically. If the import is triggered by OS command line (not by ABAP) and the NetWeaver version is lower than 7.42, the report is not executed automatically. If the NetWeaver version is 7.42 or higher and the transport profile parameter FEEDBACK_IMPORT is set, the report is executed automatically. If the transport profile parameter is not set, the report is not executed automatically.

If you have to schedule the report, there are three options for this:

  • With a periodic time interval

    This is the easiest way. However, it has the small disadvantage that some time might elapse between the import of a transport and the start of the update depending on the interval you choose.

  • Starting after event SAP_IMPORT_STO

    This triggers the report automatically after all transports of the import queue have been imported. However it doesn’t trigger the report in cases where you perform a special import of a single transport.

  • Schedule the report in both ways

    This is the most secure and fast way to ensure the index is up-to-date. The report ensures that no problems occur in cases where multiple executions are triggered in parallel.