cancel
Showing results for 
Search instead for 
Did you mean: 

How to disable storing CIT in CI?

0 Kudos

Hello,

integrated solution BRIM.

All usage registration (CIT sent to CC) might be stored in CI. I read in documentation that it is an installation setup.

I have two queastions:

- is there a possibility to disable this globally later (I mean after installation)?

- is there a possibility to disable this for selected CIT types (for example only for Z011, but not Z012)?

best regards

Rafal

Accepted Solutions (0)

Answers (2)

Answers (2)

francois_thimon
Active Participant

Hi Rafal,

We generally discourage disabling this feature once it has been set up.
You'll be much better off if you plan ahead and install only what you actually need.

There's still a way to skip the consumption item process for some classes, using the "consumptionItemMappingIsSet" clause, in the XML CIF configuration, as follows:

  <chargeableItemTransactionProcessor>
    <chargedChargeableItem>
     <switch>
      <case>
       <consumptionItemMappingIsSet />
       <sequence>
        <consumptionItemValidator />
        <customerManagementAreaRouting>
          <bulkWriter adminParameterPrefixName="CHARGED_CI_WRITER" rootPath="/var/sap/41/ci/CHARGED/Instance#@INSTANCE_ID@/@JCO_DESTINATION_NAME@" channelCount="2" timeBasedFileRolloverPolicy="MINUTELY"
            maxSizeBasedFileRolloverPolicy="1M" deflate="true" deflateOutputFormat="GZIP" autoCommit="false" storeFileInformation="true" fileVersion="2" lineNumbering="false"
            fileSequenceId="CHARGEABLE_ITEM" cleanArchivedFile="false" />
        </customerManagementAreaRouting>
        </sequence>
       </case>
      </switch>
    </chargedChargeableItem>
  </chargeableItemTransactionProcessor>


Using that feature, only the CC chargeable item classes that are actually mapped to a CI consumption class will be processed.

Best regards.

François
SAP Convergent Charging Support

0 Kudos

Thanks a lot for your answer.

CITs are sometimes used only for counter changes. Without BIT generated in CI. For "such kind" of CIT it is not needed to be stored in CI. I fought there is a flag to switcc this on/off.

In this situation totally another solution is needed. I am start thinking about a job on CI to remove unnecessary CITs periodically.

Thanks anyway.