List of things to be in APO DP/SNP with new plant

[Former Member]

Hi All-

We are running on APO DP/SNP from last 3 years.

In this year we wil lbe adding a new plant to our supply chain process, so we need to update DP/SNP to take into consideration this new plant.

What are the list of things need to be configured or master data maintenance needs to be done so that we can start planning for this new plant?

Thanks for your help.

Yousuf

[rajkj]

Hi Yousuf,

Apart from CIF integration models update in ECC to transfer additional master and transactional data to APO, you may consider the following in your checklist,

• Location master record - Set/verify the time zone, define appropriate calendars (production, shipping, and receiving)
• Location product master record update especially SNP relevant data (SNP1, SNP2, Demand, Lot Size tabs)
• Resources and corresponding capacity variants
• Product, location, and resource hierarchies to support aggregating planning and disaggregate the planning data using SDM. 
• Quotas, priorities, and Transportation lines
• CVC for demand planning (if relevant)
• Changes to your selection profiles to include the new plant location in your network
• Interchangeability (IC) master data (if applicable)
• SPRO configuration for instance distribution definition (to publish transactional data to ECC)
• Extension of custom behavior (user exits, enhancements, etc.) to the new location (if there is any hard code)

Thanks,
Rajesh

[aparna_ranganathan]

In addition to the points mentioned in Pawan's thread , you also have to update your location hierarchy if you run aggregate SNP planning.

Thanks

Aparna

[former_member209769]

Hi Yousuf,

It's not possible to give an answer to your question, as it totally depends on your design.

You should see in which all jobs the new plant, relevant materials, resources, production versions, or any other relevant master data need to be included. Also, need to think correspondingly for the transaction data.

First of all, the data needs to come from R/3 to APO through CIF, so many CIF jobs might need to be updated with all the master data/transaction data relevant to the new plant. You might also need to maintain publication settings in APO, if you send the planning results over to R/3.

On the APO side, depending on what all planning functionalities you use, you would need to identify and maintain data as needed. e.g. there are specific data to be maintained for Deployment, TLB, or other things like forecast horizon, etc. May be you already have a MASSD running in APO, then you could update that job for the data related to the new plant also. Any relevant APO planning jobs would need to be updated with the relevant plant.

If you have any exits, you need to consider if any maintenance is needed related to the same also.

These are some of the pointers that I can give as an outsider. You would need to look at all the aspects along the above lines.

Thanks - Pawan