Maintaining number ranges for contracts in BRIM

[Csaba3]

Hello all,

we face the following situation: we have an S4HANA BRIM Rollout where we need to define number ranges for the SOM subscription order (object CRM_PRVORD), SOM subscription contract (object CRM_PRVCTR) and provider contract in CI (object FKK_VT).

As of our experiences we also need an additional object to maintain: CRM_TELCO (provider contract in SOM?) – is it like this?

we have some unclear issues regarding number range object CRM_TELCO. Let me list our questions:

is this number range object used for other areas than SOM?

why can't you find anything about this object in SAP Help?

why do we need additionally object CRM_TELCO when there is already object CRM_PRVCTR for "contracts"?

why does CRM_PRVCTR only have 10 characters and CRM_TELCO 20?

why does FKK_VT have 20 characters for provider contracts in CI and not 10 like CRM_PRVCTR?

does anyone know what happens when CRM_PRVORD and/or CRM_PRVCTR reaches the limit of 9,999,999,999 - is an error message thrown? How should I deal with this?

is there any other objects regarding contract number ranges that we need to take into account?

Thank you for clarification in advance!

[deepak_dash]

Hi,

The number ranges belong to subscription order, subscription contract and subscription contract item objects in SOM and the subscription contract item (with contract ID) is externally mapped to create FICA provider contract with same ID.

CRM_PRVORD: Subscription order (Header)
CRM_PRVCTR: Subscription contract document (Header)
CRM_TELCO: Subscription contract item (Contract ID of main item in a subscription contract document)
FKK_VT: FICA provider contract and must have the externally generated number range assignment in integration with SOM

So, the number ranges of CRM_TELCO and FKK_VT are in sync as they belong to individual contracts and can be more. While the CRM_PRVORD and CRM_PRVCTR belong to header objects which ideally are less. This is similar to any other header object number range like Service order, Purchase order, etc. Thank you.

Regards
Deepak

[Csaba3]

Thanks Deepak!