Applying the Error Analysis Process

Objectives

After completing this lesson, you will be able to:
  • Apply the error analysis process.
  • Access Catalog Transport Information.

The Error Analysis Process

Visualization of the build of the Error analysis process: The instances, like the Dispatcher, the Updater, or the Guider create log files using an instance trace. Extended log files are created for the logs of the updater and the Bulkloader, which ends by a working directory in the transfer directory. The instance log of the Rater ends as a working directory in the transfer directory, too.

The application log (transaction code: SLG1) in SAP Convergent Invoicing provides information regarding the communication between SAP Convergent Charging and SAP Convergent Invoicing. The relevant information is available via the object FKKBIX with the sub-objects CREATE and RATING.

SAP Convergent Charging provides error information in the log-files and the transfer directory.

Log-Files in SAP Convergent Charging

Log-Files in SAP Convergent Charging

TypeNameBelongs to
Application specific (business processes)LS_APP_SEVERITY
System informationLS_SYS_SEVERITY
Technical trace information

LS_TRC_SEVERITY

LS_TRC_DOMAIN

Technical JCo information

JCO_JRFC_TRACE_LEVEL

JCO_TRACE_LEVEL

JCO_CPIC_TRACE_LEVEL

In the log-files of SAP Convergent Charging, there are three different types of information:

  1. Application-specific
  2. System information
  3. Technical trace information

Additionally, the extended log-files contain technical information regarding the JCo connectivity.

The level of detail could be configured per instance (Guider, Dispatcher, and so on) via system parameters with the Admin+ tool. The command is: # > set <PARAMETER> <LOGLEVEL> <SCOPE> <INSTANCES>.

An SAP Convergent Charging Working Directory was defined during the installation of SAP Convergent Charging. Below this root directory, the following substructure will be created:

SAP Convergent Charging Working Directories

PathDescription
SAPCC_CIT/POSTPAID/Instance#1Contains Postpaid-BITs (billable and billed)
SAPCC_CIT/POSTPAID/COM_EXCEPTION/Instance#1/

Contains Postpaid-BITs with transmission errors (network errors)

SAPCC_CIT/POSTPAID/INVALID/Instance#1/

Contains Postpaid-BITs with transmission errors (reported by CI)

SAPCC_CIT/PREPAID/Instance#1Contains Prepaid-BITs (billable and billed)
SAPCC_CIT/PREPAID/COM_EXCEPTION/Instance#1/

Contains Prepaid-BITs with transmission errors (network errors)

SAPCC_CIT/PREPAID/INVALID/Instance#1/

Contains Prepaid-BITs with transmission errors (reported by CI)

SAPCC_CI/ACQUIRED/Instance#1Contains CITs in status „Unrated"
SAPCC_CI/ACQUIRED/COM_EXCEPTION/Instance#1/

Contains CITs in status „Unrated" with transmission errors (network errors)

SAPCC_CI/ACQUIRED/INVALID/Instance#1/

Contains CITs in status „Unrated" with transmission errors (reported by CI)

SAPCC_CI/CHARGED/Instance#1/Contains CITs in status „Rated"
SAPCC_CI/CHARGED/COM_EXCEPTION/Instance#1

Contains CITs in status „Rated" with transmission errors (network errors)

SAPCC_CI/CHARGED/INVALID/Instance#1

Contains CITs in status „Rated" with transmission errors (reported by CI)

Catalog Transport Information

The figure illustrates the procedure when using the Catalog Transport feature in SAP Convergent Charging. it shows, that an xml file displays with its components.

The Catalog Transport feature in SAP Convergent Charging provides the capability to transport data from a specified pricing catalog in a source system to one or multiple target systems within SAP Convergent Charging. This is made possible by using dedicated change lists, which can then be sent to the configured transport destinations via transport requests.

The process is handled by the source SAP Convergent Charging system, where either an administrator or pricing specialist can initiate the transport request through the Core Tool user interface. A system scheduler executes the requests initiated by the SAP Convergent Charging users.

Alternatively, an integrated SAP CTS system, working in conjunction with a dedicated SAP Convergent Charging CTS+ plugin, handles the transport requests.

More details about the catalog transport process can be found in the SAP Convergent Charging application help.

SAP Convergent Charging Tuning Guide

Visualization of the entry page of the SAP Convergent Charging Tuning Guide.

Obtain the latest version of the Tuning Guide from the help portal. Open an internet browser and visit the SAP Convergent Charging area in the help portal via http://help.sap.com/cc.

Select the version 2021 FPS 2 (Latest) in the drop-down box next to the headline SAP Convergent Charging. This is the latest version, which provides a dedicated Tuning Guide.

Go to the Implement section as pictured earlier, and open the Tuning Guide. Familiarize yourself with the guide. Additional to tuning recommendations for SAP Convergent Charging, the guide contains a sizing guideline as well.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn