SAP BusinessObjects analysis messages

This page presents the different messages that are produced by the SAP BusinessObjects Analyzer during application source code analysis. Messages are documented with their identifier (referenced in the analysis log files), a description, and a possible remediation. The following information will help you to validate your analysis.

Identifier	BO.01
Message	Starting Business Objects analysis '<JOBNAME>'…
Severity	Information
Explanation	The analyzer starts to process the Business Objects universes and documents.
User Action	Nothing special to do.

Identifier	BO.02
Message	The Business Objects analysis '<JOBNAME>' completed.
Severity	Information
Explanation	The Business Objects universes and documents have been processed and the analysis completed.
User Action	Nothing special to do.

Identifier	BO.03
Message	The Business Objects analysis '<JOBNAME>' did not complete successfully.
Severity	Error
Explanation	The analyzer was not able to complete the analysis successfully. At least one Business Objects universe or document has not been analyzed correctly. This can be the consequence of an extraction issue or due to a non supported character.
User Action	Search in the log the Business Objects universes or documents for which an issue has been encountered and contact CAST Support.

Identifier	BO.04
Message	The Business Objects analysis has been canceled by the user.
Severity	Error
Explanation	The analysis has been explicitely cancelled by the user. No object has not been saved.
User Action	If you need to analyze the Analyis Unit, then restart the Business Objects analysis.

Identifier	BO.05
Message	Analyzing Business Objects universes...
Severity	Information
Explanation	The Business Objects analyzer is currently analyzing Business Objects universes.
User Action	Nothing special to do.

Identifier	BO.06
Message	Analyzing Business Objects documents...
Severity	Information
Explanation	The Business Objects analyzer is currently analyzing Business Objects documents.
User Action	Nothing special to do.

Identifier	BO.07
Message	Number of Business Objects objects that have been found by the analyzer:
Severity	Information
Explanation	Once all Business Objects universes and documents have been analyzed, the number of objects that have created is displayed.
User Action	Nothing special to do.

Identifier	BO.08
Message	Number of <OBJECT_TYPE>: <COUNT>
Severity	Information
Explanation	Once all Business Objects files have been processed, the number of objects for type <OBJECT_TYPE> that have created is displayed. Object types are: classes, objects, dimensions, conditions, and tables.
User Action	Verify if that number corresponds to the Business Objects <OBJECT_TYPE> elements that have been delivered. This verification can be done by comparing numbers available in the Business Objects Repository. In case of difference, then check the delivery, the analysis settings, and potential warning or error messages.

Identifier	BO.09
Message	Total number of objects that have found: <COUNT>.
Severity	Information
Explanation	Once all Business Objects files have been processed, the total number of objects that have been created is displayed.
User Action	Verify if that number corresponds to the Business Objects elements that have been delivered. This verification can be done by comparing numbers available in the Business Objects Repository. In case of difference, then check the delivery, the analysis settings, and potential warning or error messages.

Identifier	BO.10
Message	No file has been selected. The analysis process ends.
Severity	Error
Explanation	The source code scope is empty and the analyzer does not find any Business Objects universe or document to analyze.
User Action	Review the Analysis Unit configuration and the source file settings. Then, restart the analysis process.

Identifier	BO.11
Message	The Business Objects universes analysis failed.
Severity	Error
Explanation	The Business Objects analyzer was not able to parse the Business Objects universes present in the source code scope. No object has been created. This can be the consequence of an extraction issue or due to a non supported character.
User Action	Search in the log the Business Objects universes for which an issue has been encountered and contact CAST Support.

Identifier	BO.12
Message	The Business Objects documents analysis failed.
Severity	Error
Explanation	The Business Objects analyzer was not able to parse the Business Objects universes present in the source code scope. No object has been created. This can be the consequence of an extraction issue or due to a non supported character.
User Action	Search in the log the Business Objects documents for which an issue has been encountered and contact CAST Support.

Identifier	BO.13
Message	Analyzing Business Objects universe '<UNIVERSE>' with schema(s) '<SCHEMAS>'…
Severity	Information
Explanation	The Business Objects analyzer is parsing the Business Objects universe <UNIVERSE> that is associated to the database schema <SCHEMA>.
User Action	Nothing special to do.

Identifier	BO.14
Message	The Business Objects <TYPE1> '<UNIVERSE1>' contains a reference to the universe '<UNIVERSE2>' [<TYPE2>] which is not part of the source code analysis scope.
Severity	Warning
Explanation	The analyzer found in the Business Objects universe <UNIVERSE1> a reference to another universe, called <UNIVERSE2>, and is not able to resolve that reference. This occurs when the referenced universe has not been extracted. Missing universes and unresolved links can impact transaction call graphs.
User Action	Check the extraction parameters, extract the required Business Objects universes and documents again, and restart the analysis.

Identifier	BO.15
Message	The Business Objects universe '<UNIVERSE>' is not part of the analysis scope but is referenced in Business Objects documents.
Severity	Warning
Explanation	The analyzer found in a Business Objects document a reference to a universe, called <UNIVERSE>, and is not able to resolve that reference. This occurs when the referenced universe has not been extracted. Missing universes and unresolved links can impact transaction call graphs.
User Action	Check the extraction parameters, extract the required Business Objects universes and documents again, and restart the analysis.

Identifier	BO.16
Message	Unable to retrieve the Business Objects universe '<UNIVERSE1>' in case sensitive mode, universe candidate is '<OBJNAME2>'.
Severity	Warning
Explanation	The analyzer found a reference to a Business Objects universe but is not able to find out the targetted universe in a case sensitive matching. However, it found out a universe for which the name matches in insensitive case mode. This candidate is taken in account and therefore linked to the calling universe.
User Action	Verify if the universe candidate is the right one. If not, then remove the link in a post-analysis job. It is a good opportunity to check the relation between both calling and called universes in the Business Objects Repository.

Identifier	BO.17
Message	An external reference to Business Objects universe '<UNIVERSE>' [<TYPE>] has been found in analysis job '<JOB>'.
Severity	Information
Explanation	When analyzing a Business Objects universe or document, the analyzer found a reference to another universe. A link is created between both objects.
User Action	Nothing special to do.

Identifier	BO.18
Message	The Business Object analyzer is not installed. Please install the latest version of the extension 'com.castsoftware.businessobject'.
Severity	Fatal error
Explanation	The Business Objects analyzer is now delivered as an extension and this one has not been activated before starting the analysis. As a consequence, the Business Objects universes and documents cannot be processed.
User Action	Download and install the Business Objects analyzer. The download is be done by using the Extension Downloader tool. Once the extensions have been downloaded, run Server Manager to install them in the database schemas. Please see the product documentation for more details in these operations.