Best Practices for monitoring/maintenance of number ranges

[Astrid_Gambill]

Hi All

We've been live with ECC 6.0 Ehp3 for Utility Billing for a year now, and have been encountering issues with Number Ranges.

Through trial and error we've been able to work through the issues, and have started manually monitoring the number ranges, initially for just the FKK_BELEG object (financial documents), but now for all objects with status > 0.

I can see that there is a % warning level defined in table TNRO, but how is this warning issued? especially for mass processing in batch? We had 5 ranges for the AM clearing docs that were full, and without detailed inspection of the application logs, we didn't know there was a problem until users reported anomalies.

Given it doesn't look like we got enough bandwidth defined within the ranges at go-live, is it better to do an analysis across the board and plan out ranges for all objects to cover for 5+ years, or is it more common to manually monitor and add ranges on an as-needed basis?

Are there any other options we aren't aware of?

Thanks in advance for any suggestions/advice.

Astrid

[william_eastman · Accepted solution]

Astrid:

A bit late - but maybe still of value.  Of course NRIV contains the objects, ranges and their statuses.  Program RSNUMHOT can be used to check the status and identify ranges which have reached critical stage.  You can also trigger alerts when ranges reach some stage.  Here is a blog posting about that

regards,

bill.

[Astrid_Gambill]

Hi Bill

Thanks for letting me know about the RSNUMHOT program.  It works for everything but the 2 EMMA objects.  We were initially set up with some rather small number ranges for the EMMA_RUNID object, and they've run out rather quickly, so if we hadn't been monitoring manually there'd be issues.

Regards

Astrid