Hi Mihir,
Let's discuss it on a short notice but here is already my point-of-view.
The suffix generated in my example implementation is on purpose numeric (i.e. a sequential number starting at '01' up to '99'). The concept behind the implementation is defining so-called "partitioning patterns". In an LSA (Layered, Scalable Architecture) context, we can distinguish strategic partitioning (using data domains) and tactical partitioning (usually using time characteristics, e.g. fiscal year or calendar year). The combination of both leads to a number of partitions.
Please refer to my blogs for more information on the concept behind. You can start with the introductory blog Pattern-based Partitioning using the SPO BAdI - Part 1: Introduction.
Example:
First partitioning pattern is using XDOMAIN with values 'A', 'B' and 'C'.
Second partitioning pattern is 0CALYEAR with values '2011', '2012' and '2013'.
The combination of both patterns will generate 9 partitions. In first instance, the numbering will start at '01'.
In the example the tactical partitioning using 0CALYEAR is volatile. Every year you will have to shift one year. This will result in generating a new partitions (3 in total: A 2014, B 2014 and C 2014) and dropping the oldest partitions (also 3 in total: A 2011, B 2011 and C 2011).
The implementation is built around this concept. In my opinion the numeric suffix is in line with standard SAP logic and does not have to be meaningful. The description of each partition will include information on the contents.
You are of course free to go for a different concept and implementation. There are certainly ways to achieve your requirements.
Best regards,
Sander