on 03-11-2015 6:13 AM
Hi Experts,
we have two master planning object structures for two planning areas, each for annual and monthly demand planning.
Both MPOS's have few similar characteristics and few different characteristics. Also navigation attributes may vary for each characteristics in both MPOS's. i.e the same characteristic may have navigation attribute in first MPOS and may not have navigation attribute in second MPOS.
Is it advisable to merge both master planning object structures into one MPOS and use it for both planning areas?
Both Planning areas may have few similar and few different key figures.
IF merged int one MPOS what is the impact on demand planning process?
RK,
Is it advisable to merge both master planning object structures into one MPOS and use it for both planning areas?
Don't know why you are asking us. Why are you even considering this issue? If you have a sound business reason to merge them, then the answer is yes. If you don't, then the answer is no.
You are talking about generating a lot of work for yourself, and a lot of testing to validate the changed solution for your end users. What do you think will be the benefit?
"If it ain't broke, don't fix it."
Best Regards,
DB49
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear RK
i think you require to consider few below things.
with merge PLOB, you will have multiple storage bucket options i.e.annual and monthly.
This means all the data will get stored with lowest granularity.
as you mentioned, you have different characteristics for respective PLOB. You really require to be careful with selecting future CVC structure to assure all the business requirements are getting fullfilled.
You also have to think @ data migrations once you merge both the PLOBs.
So if you ask me, unless you have to strong business case I will not merge PLOBs.
Don´t touch the running system 🙂
Amol
Hi RK,
There must be a pretty good reason why they were not created as one from the beginning, but I will assume you believe there is a strong business case to motivate this project.
There are numerous advantages to pooling (master data maintenance, data loading, data extractions, storage space in LiveCache and DB, less background jobs overall, data sync, data backup ....) With a good design, it should be transparent to the users and the demand planning process.
Why would you only merge MPOS and not planning area?
- You can create monthly / Annual time bucket profiles to be used in different planning books in the same planning area
- You can specify which key figures / characteristics / nav attributes you want to display in each planning book of the same planning area
"There is always room for improvement, no matter how long you've been in business"
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
4 | |
3 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.