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.

Use the Convergent Charging Cockpit

Business Scenario

As a Convergent Charging administrator, you want to monitor the system status. Use Convergent Cockpit for the check of system parameters.

As a Convergent Charging pricing expert, you want to add a Service Level FIFTY into the existing mapping table MT_G_##_SLA_CPU_PRICE_V01.

Use the SAP Convergent Charging Cockpit for mapping table maintenance.

Task 1: Connect to SAP Convergent Charging Cockpit

Steps

  1. Log on to the SAP Convergent Charging Cockpit.

    1. Choose the Windows Start icon on the Start Bar.

      System screenshot showing the Start icon on the Start Bar.
    2. Select CC5.0_Cockpit - Shortcut from the Start menu Apps:

      System screenshot showing the Start menu Apps.
    3. Log on to Convergent Charging Cockpit.

      User NameBR235-##
      PasswordWelcome1

Task 2: Check System Parameters

Steps

  1. Check system parameters JCO_JRFC_TRACE_LEVEL and LS_APP_SEVERITY with the SAP Convergent Charging platform administration app Manage System Parameters to view or change parameters.

    1. Open the Manage SAP CC System Parameter app by choosing its tile. By default, the app displays all the system parameter values defined in the running Core Server system.

    2. Enter JCO_JRFC_TRACE_LEVEL in the parameters field. Filter the displayed results to focus on particular parameter values. The persistent value of JCO_JRFC_TRACE_LEVEL is 0.

    3. Enter LS_APP_SEVERITY in the parameters field. Filter the displayed results to focus on particular parameter values. The persistent value of LS_APP_SEVERITY is INFO.

Task 3: Insert an Additional SLA

Steps

  1. Insert an additional SLA FIFTY with Price EUR 0.50 and start date 01.01.2020 into your Mapping Table MT_G_##_SLA_CPU_PRICE_V01 (## is your group number) with SAP Convergent Charging app Manage Mapping Tables.

    1. Open the app Manage Mapping Tables by choosing its tile.

    2. Enter MT_G_##_SLA_CPU_PRICE_V01 in the search field.

    3. Select your Mapping table.

    4. Choose the Edit button.

    5. Choose Edit All.

    6. Choose Plus, add a row.

    7. Insert row:

      IdentifierSLACurrencyStart DateEnd DateAmount
      0FIFTYEUR01.01.202031.12.20210.50
    8. Choose Apply.

    9. Choose Save.

View Parameters with Admin+

Business Scenario

After completing this exercise, you will be able to view the system parameter values.

As the system administrator, you need to view the system log levels to communicate them to the Support team.

Task 1: Log in to Admin+

Steps

  1. Start the Admin+ tool.

    1. Find the Admin+ tool located at N:\My Documents\CC_Tools_2021\core_tool\bin.

    2. Choose admin+.bat.

  2. Connect to your server.

    1. Enter the following command: host.

    2. If the host name is wdflbmt7132, then press Enter.

    3. If the port number is 9100, then press Enter.

  3. Authenticate yourself.

    1. Enter the following command: user BR235-## <password>.

      Result

      System screenshot of the command window.

Task 2: Get the Instance List to Find Rater

Steps

  1. Get the instance name for the rater in your environment .

    1. To get the instance name for the rater in your environment, enter the following command: list.

      System screenshot of the command window.

Task 3: Get the Parameter Value

Steps

  1. Get the current in-memory value for the LS_TRC_SEVERITY parameter for the rater instance.

    1. Enter the following command: get LS_TRC_SEVERITY MEMORY <RaterInstance>.

      System screenshot of the parameter value.

View the Latest Logs with Admin+

Business Scenario

After completing this exercise, you will be able to view the latest log entries from the Admin+ tool for SAP Convergent Charging.

As the system administrator, you need to view the system logs to troubleshoot an issue.

Task 1: Log in to Admin+

You can skip this task if you are already logged into Admin+.

Steps

  1. Start the Admin+ tool.

    1. Choose admin+.bat. Find the Admin+ Tool deployed in Application(N:)\Document\CC_Tools_2021\core_tool_bin\admin+.bin.

  2. Connect to your server.

    1. Enter the following command: host.

    2. If the host name is wdflbmt7132, then press Enter.

    3. If the port number is 9100, then press Enter.

  3. Authenticate yourself.

    1. Enter the following command: user BR235-## <password>.

      Result

      Code Snippet
      12345678
      Server identified by URL: http://wdflbmt7132:9100/ a+ > host Server host name [wdflbmt7132]: Server port [9010]: 9100 Server identified by URL: http://wdflbmt7132:9100/ a+ > user BR235-## <password removed> OK: The SAP CC user BR235-## is now authenticated by the connected SAP CC system. You can administer this system.

Task 2: Get the Log Entries

Steps

  1. Get the latest 10 log entries for the rater instance.

    1. To get the instance name for the rater in your environment, enter the following command: list.

    2. To get the latest 10 log entries for the rater instance, enter the following command: logs LDF1 10 <RaterInstance>.

      System screenshot of log entries.

Log in to track your progress & complete quizzes