cancel
Showing results for 
Search instead for 
Did you mean: 

SPO via BADI

former_member293102
Participant
0 Kudos

Hello Experts,

I was going though below post :

http://scn.sap.com/message/13654521

I really need help in getting the technical name (suffix, last 2 characters) of SPO part provider right. I followed the above post but unable to resolve the issue. I want it ending with LC, LA & LN but I get it as 01,02,03.

Can someone help with sample piece of code to get this done ? I also followed http://scn.sap.com/docs/DOC-26583 and directly pasted the ABAP code available in "Class YCL_IM_RSLPO_BADI_PARTITIONING v1.txt.zip" in link http://scn.sap.com/docs/DOC-26583.

Do I need to modify the code available in http://scn.sap.com/docs/DOC-26583 link ?

 

Regards,

Mihir

Accepted Solutions (1)

Accepted Solutions (1)

esjewett
Active Contributor
0 Kudos

This is a bit beyond me. Probably best to ping and see if he can take a look at this. It looks to me like the generate_partition_counters method generates numeric counters, so you probably have to change this method if you want something else.

former_member293102
Participant
0 Kudos

Hi Ethan,

Thanks for your reply. Is it possible that we prefix an alphabet denoting the region.

Like for example :

SPO name : EOPER

Part 1 : CEOPER01

Part 2 : NEOPER02

Part 3 : AEOPER03

Part 4 : CEOPER04

Part 5 : NEOPER05

Part 6 : AEOPER06

Part 7 : CEOPER07

Part 8 : NEOPER08

Part 9 : AEOPER09

Which area I will have to touch ? The BADI looks complex to me. Your reply would be much appreciated.

Regards,

Mihir

sander_vanwilligen
Active Contributor
0 Kudos

Thanks Ethan, I will be in touch with Mihir on a short notice.

Best regards,

Sander

sander_vanwilligen
Active Contributor
0 Kudos

Hi Mihir,

Please have a look at my reply on Jürgen Haupt's blog on September 13, 2013. In my opinion you should not go into this direction and I have serious doubts if it's even technically possible.

Best regards,

Sander

Answers (2)

Answers (2)

sander_vanwilligen
Active Contributor
0 Kudos

Hi Mihir,

Can you please confirm if my reply of Nov 28, 2013 12:16 AM is clear?

If not, please let me know how I can help you further.

Thanks,

Sander

sander_vanwilligen
Active Contributor
0 Kudos

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 between 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 .

Example:

First partitioning pattern is using XDOMAIN (data domain) with values 'A', 'B' and 'C'.

Second partitioning pattern is 0CALYEAR (current year and 2 preceding years) 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 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 alternative implementation. There are certainly ways to achieve your requirements.

Best regards,

Sander