cancel
Showing results for 
Search instead for 
Did you mean: 

2 planning areas for DP

Former Member
0 Kudos

Hi gurus,

Currently we have 1 PA for DP and seperate PA for SNP for USA. But in future release for another countrywe are thinkin to create a new PA for DP.... Will this impact the number of PA for SNP?In case we decide on having a seperate PA for DP for another country, do we have to create a seperate PA in SNP for another country or is there an option to give PA1 and PA2(from DP) as input to single SNP PA as the data flows from DP to SNP. How are the PA connected between DP and SNP. Can you explain in detail please

Any quick responses are greatly appreciated.

Sai

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Sai,

DP to SNP release is happens from time series to order series data, hence having multiple planning area for DP doesn't stop you releasing to single SNP planning area. Infact the release happens at version level and not at planning area in SNP. You actually copy the data from DP planning area to SNP version through /SAPAPO/MC90. You can create separate variants for each country planning area and release it to your SNP versions in /SAPAPO/MC90.

Thanks,

Rajesh

Answers (1)

Answers (1)

former_member209769
Active Contributor
0 Kudos

Hello Sai,

SNP works mostly with Product-location combination.

Since the names of your locations in different countries/regions would be different, there's no issue in using the same SNP planning area for these different countries/regions.

You would have jobs which would release forecast from both the planning areas to the respective location-products in SNP. Then in SNP you would use a relevant selection criteria for location-products, and carry out SNP planning as per your need.

This is a standard set-up in many of the projects.

Also consider whether you really need to have a separate planning area for DP. For ease of maintenance, it might make sense that you use the same DP planning area, unless the number of CVCs is really growing to a very high value and causing you performance issue in DP.

Thanks - Pawan

Former Member
0 Kudos

Thank you Pawan and Rajesh for your very helpful answers.

Hi Pawan,

In case of DP, we have not yet decided whether to use one PA or separate the PA for new country data. All the characteristics and KF are the same for both countries but regarding CVC's, currently we have 100, 000 and for the new country we are expecting to have 100,000. I have a question here, how will the performance in DP be affected whether we use one PA or 2 PA's as all the data will be stored in the same live cache. What I mean to ask here is , In case we have 1 PA in DP with 200,000 CVC's or we have 2 PA in DP with 100,000 CVC for each PA, how will the performance ge affected?

Thanks in advance!

Sai

former_member209769
Active Contributor
0 Kudos

Hi Sai,

From livecache storage perspective, it should mostly not be different. But when you display data or process data, then you could see the effects. Imagine when some user needs to load the data for all the Sales Organizations or countries. If you have common PA, double the data would need to be loaded. If user needs to use pivot sorting or see detailed data, then with more CVCs, the amount of data to be stored in internal temporary tables increases, and would affect performance. The macros that you would have put need to run for all the CVCs that you select (either in foreground or in background). These are the main places where you could see the performance impact. And of course, things like backups/extraction of data, initialization of planning area, consistency checks, etc would get impacted.

Thanks - Pawan

Former Member
0 Kudos

Adding further to Pawan's reply

Using different PA for different regions / country will help you in devising a better job plan. For example, if you have 2 different PA for US & IN, you don't have to worry about the performance while the batch jobs are running on one region and users active on the other. During monthly initialization of your PA, the users will not get affected due to the time zones. Different PA also helps you to seggregate the data that can be accessed by planners (which can also be done through planning book restrictions otherwise).

Thanks- Rajesh