cancel
Showing results for 
Search instead for 
Did you mean: 

Number range object COPA_TRPR

0 Kudos

Dear All,

Number range object COPA_TRPR was consumed almost 97% in our system.

I have gone through the related links to this object, and it was explained as below:

You can check this object in SNRO. If the flag 'No interval rolling' isn't set for object COPA_TRPR, the number assignment begins again with the first number in the interval if the last number in the interval has been issued.

https://wiki.scn.sap.com/wiki/display/ERPFI/Information+on+number+range+object+COPA_TRPR.

Could you please suggest me do we need to take any action or is it ok to leave the object to start the number range again.

Thanks in Advance

A.Prasad

Accepted Solutions (0)

Answers (1)

Answers (1)

sebastian_wasl
Explorer
0 Kudos

Well, the question is 5 years old, but now I do have an answer:

First: wenn the rollover occurs, this object picks the next available number from the beginning. It doesn't try to re-use a former number, so you will have no dumps with INSERT_DUPREC occurring.

Example (second column is timestamp):

Second: there is a reorganisation abap RKETREPROTDEL that deletes any entries in table TKETRPROT older than 120 days. It seems as if SAP itself doesn't really need the old logging entries.

The numbers only get burned so fast because COPA_TRPR is set to a buffering of 1.000, which means that with every restart of the system you're burning up to 999 unused numbers... but as I've written, it works even if the interval is restarted.