cancel
Showing results for 
Search instead for 
Did you mean: 

Provider contract limitation in CC

chandru_sdn80
Participant
0 Kudos
771

Hi,

Do we have a solution to support more than 10 line items under one Provider contract in CC?

As per SAP Note '2478958', it supports only 10 lines. Did you guys come across any business model where you supported more than 10? Could you pls share some guidance on this?

Thanks

Chandru.R

Accepted Solutions (0)

Answers (3)

Answers (3)

frederic_plessis
Associate
Associate

Hi Chandru,

First of all, recommendations put in the SAP Note Note #2478958 are mainly towards telco customers that are very demanding in terms of performance (especially response time).

So of course, figures in the note can be exceeded but we have to be aware to make sure the system still runs smoothly.

For example, we have already allowed for a customer implementation to have up to 100 items per contract.

Best regards,

--Fred

chandru_sdn80
Participant
0 Kudos

Hi frederic.plessis,

Thanks for your response. We were able to test in DEV environment for 500, 700 lines, whereas in a few instances it failed during ODI between SOM to CC in Q environment. When we asked SAP, SAP asked to follow this recommendation. Will it really break CC system when we have more 100, 200 lines under one Provider contract? Did you come across in production environment where you got to see more than 100,200 under 1 provider worked without ODI failure? We are on S/4 2020 and CC 5.0 version. Can you pls answer? So that I can ask SAP and get their second opinion?

THanks

Chandru.R

0 Kudos

Hi,

there is an additional snapshot limitation to be considered when using large contracts or small contracts with long history (many changes). By default each snapshot of a contract is put in BLOB field as zipped XML. Snapshots are done before and after every contract change. I would recommend to test also change processes (if exists; including CCM update) to see how it will work with so many items in one contract.

Personally I would recommend to create many contracts for the same customer with one item(one contract with one item). All BITs generated later can be grouped on the invoice in one line. For example there can be one shared "reference number" in all contracts. Additional reference field can be added to the BIT structure. And this reference can be used later for grouping to one item during billing or invoicing in CI.

best regards

Rafal

chandru_sdn80
Participant
0 Kudos

Hi Rafal, Thanks for your response. Yes we are evaluating flattening the PC vs Billing Plan(Via Custom ABAP) for recurring SKU to keep a large no of items under a single PC.

Thanks

Chandru.R

ravirbt_sap
Explorer
0 Kudos

Hi Chandru,

The note 2478958 provides recommendations on limiting various configurations in CC. There is no technical limitation as such, there can be more than 10 line items under 1 provider contract. This note just recommends to keep it under 10 to avoid performance related issues. If the no of contracts for which more than 10 line items are needed are handful then you can go ahead but if it is significant then it should be avoided.

Regards,

Ravindra

chandru_sdn80
Participant
0 Kudos

Hi Ravindra, I understand. This is just a recommendation, but we have an issue where an order failed during distribution between SOM to CC. We asked SAP, SAP suggested this note and recommended, to change our design. Do you have any alternative way to handle more than 10 lines or Did you ever face such situation in your experience?

THanks

Chandru.R

ravirbt_sap
Explorer

Hi Chandru,

We had some scenarios where more than 10 lines were there in a single provider contract but no such issue was faced then. Instead of SOM we had CRM. Besides the charge plans had limited parameters in them. In your case it is possible that charges plans have many parameters making the contract payload too heavy for S/4 to send to CC.

Regards,

Ravindra

chandru_sdn80
Participant
0 Kudos

Thanks Ravindra.