SAP CC BITs are not transferred to CI

[former_member831228]

Hi SAP CC Experts,

I performed the rating from CI however i haven't received BIT . I don't have Cockpit to analyze the root cause as i am checking this in Dev system.

Question : I am trying to analyze this from CC Admin+ and when i run Command: get_files_to_bulkload i am getting file name along with error status (True/False) but how to filter based on the date and time as this contains entire history of files.

I can also get the Paths to *INVALID dirs using command: get CHARGED_CI_ERR_INVALID_WRITER_ROOT_PATH But i dont know how to check the files and its data in this directory.

Can you please help me how we can check the files in *INVALID dirs along with the error message (reason for invalid).

Also please help me how to check COM_EXCEPTION folder incase of SAP CI downtime and how to move the file in the regular folder to allow the bulkLoader to load the file content into SAP CI.

Thanks

Praveen K.

[francois_thimon · Accepted solution]

Hi Praveen,

The "get_files_to_bulkload" command doesn't have any filtering/sorting options, so it may be easier to rely upon the tools provided by your operating system, since the files are visible in the directories, as you mentioned. Also, "get_files_to_bulkload" is meant to list the operations performed by CC, but is not supposed to reflect changes made directly in the file system (so, if someone deletes or moves a file, that won't be shown by "get_files_to_bulkload").

Regarding how to analyse the error files: for each reported issue, you should find one actual item file (CSV, ZIP or GZ, depending upon your CIF settings), and one associated "control" file (with the CTL extension).
The procedure is detailed in Convergent Charging's Administration guide, in section "Inspecting the Control Files and Resuming the System Operations":
https://help.sap.com/docs/Convergent_Charging/11f35b088b20494ab55e788b213b9102/f6012bdcdee34ef192c2d...

Depending upon the problem, either the control file or the item file contains a legible error message, which should directly help you diagnose the reported error (e.g., cannot find CI server, invalid field values, network timeout, etc.).
The CTL file also contains bytes that you cannot read directly, but which will be used by the bulkloader to determine how much of the item file has already been transferred by CC or not (in order to prevent duplicate items in CI).

So, for each case, you just need to:
- analyse the control file and/or the item file to see if the described error warrants a manual intervention (network issues may be temporary, but invalid item fields or incorrect JCo connection information usually require you to fix data in CC and/or CI)
- perform any required fixes
- put both files (the CSV/GZ/ZIP, and the associated CTL) back into the regular directory; the bulkloader will just reprocess them normally, and delete the CTL files when it's done (unless another error occurs)
- attention, though: the bulkloader processes only "archived" files (those with ".ARC" in their name), not the "error" files (those with ".ERR" in their name); so, for example if you have ".ERR.GZ" files, you must first manually rename them to ".ARC.GZ" (or "ARC.CSV" or ".ARC.ZIP", depending upon their actual format)

Can you please try that and confirm if that solves your issue?

Best regards.

François
SAP Convergent Charging Support

[doris_karapici · Accepted solution]

Perfect explanation Francois. Thanks a lot

[former_member831228]

Hi Francois, Thank you very much for your response, i will try this and let you know incase of help need.

[former_member831228]

Hi Francois, Thank you very much for your response, i will try this and let you know incase of help need.