Planning Areas

Planning Areas:

Planning areas are the central data structures for Demand Planning and Supply Network Planning.

To go to planning areas, or to create planning areas go to the following:

Both the planning object structure and the planning area can be setup from the same transaction.

Path= Supply Network Planning – Environment – Current Settings – Administration of Demand Planning and Supply Network Planning

POS and Planning Area

They hold key figures. To find out more about key figures see this post.

http://www.scmfocus.com/sapplanning/2009/07/06/key-figures/

Here is an example of a planning object structure, it has a number of characteristics. They must be added to create the POS. When we create one we both add characteristics

Creating the Planning Area

The next step is to create a Planning Area pointing to the Planning Object Structure.


Further it will ask for other details regarding this planning area. Below is the first tab:


The next tab includes the Key Figures (“Key Figures” is just an overly fancy term which means the forecasted line item. Things that you plan that can hold numerical values are Key Figures.)

Now it is very easy to add Key Figures willy nilly however of course its important to remember which need to be setup.


Aggregate Planning Tab

Next its required to select the Aggregate Planning tab which has the various hierarchies to select from. All of these selections need to be setup prior to arriving at this screen. These selections set the level of planning aggregation that you want to do in this particular planning area. After this is filled in its time to save the Planning Area — which creates it.

Planning Area Key Figure Aggregation
The key figure aggregates essentially decide how different key figures will be aggregated (the aggregation type – in this case it is “Pro Rata” which is “S.” Here is what we get when we select the drop down.

Pro Rata
The next feild is how the key figure is disaggregated. The value currently selected which is P, which stands for proportional allocation.

Pro Rata 2
However, this is relatively simple decision making compared to which key figures are to actually be selected. This deserves a great deal of attention.

Once we back out of the S&DP Administration and then go back in we can see that the Planning Area has been created, but it is not yet activated.

Planning Area Activation

Now we need to perform the activation. This is not done in the main area of the object, but requires you go out to the listing level (why, we don’t know). So you save in the item view, but activate in the list view. Below we have a screenshot of the list view. We right mouse click and then select Create Time Series Object.

Create Time Series Object
Its important to fill in the dates. If not, it will activate the time series object for too long of a period of time, and this will tie up the system. This is particularly true since we are setting this up as a test. So we will choose a short time period.

Create Time Series Object 2
Next we will include the Planning Version.

Create Time Series Object 3
Now we are ready to create the time series object. Its important to remember, this creates the time series object, but does not necessarily populate it with data.

SNP Activated
This shows it has been activated.

Characteristics in SCM

Its important to recognize that DP and SNP use different characteristics, and thus different planning areas and planning object structures are created for DP and SNP.


How SAP Could Improve SAP SCM


There are enormous opportunities to improve SCM.

Top Things to Improve

SAP has an immense product offering, of this which this site only focuses on SCM. However, many of the things we notice with SCM apply to the rest of the suite. While doing research and tidying up some of the articles / posts on this site, we increasingly began to notice the following:

  • Missing capabilities in integration modules in such basic areas of error checking
  • Lack of software consistency not only across SCM modules, but within SCM modules
  • Continual user interface limitations, and in the care of SCM, weak functionality in Planning Books
  • Missing documentation, and or documentation which needs to be rewritten in order for the steps to be repeatable

The more we analyzed these issues, the more we have concluded that SAP has been focusing on the wrong things as a company for some time. SAP has continually grown its footprint, but is not investing in the underpinnings of the software sufficiently to support this new funcationality. We recommend that for the next 5 years, SAP simply stop its footprint growth and go back and improve the usability, documentation, consistency and implementability of its software. Other areas that require work are its data traceability from the user interface layer back to the data layer.

How Would Product Marketing Respond?

The product marketing department in SAP would most assuredly be against this approach, as their view is to continually bring out new functionality. Product marketing is going to propose the standard argument about the need to stay competitive in the market. However, the little secret (actually not much of a secret) is that SAP already has more functionality than 99% of companies will even implement. This is a very large set of functions, and is an accomplishment to be proud of. However, the underpinnings of the software needs serious enhancement. Will SAP become a less exciting place for developers to work under this scenario? Maybe so, however, there is also satisfaction in stabilizing and improving present functionality so that is more usable and precise. This is especially true when its in the best interests of your customers.


SPP and Plant Maintenance Installed Base

As we discuss in the post..

http://www.scmfocus.com/sapplanning/2008/10/02/spp-leading-indicator-forecast-profile-tab

…there is a tab in the Forecast Profile that allows you to select an Installed Base. An important question would be where that installed base comes from. There is a way to show the installed base. This is not coming from the material master, but rather from the Equipment BOM or E-BOM. This is part of the Plant Maintenance or Customer Service ECC submodule. Therefore, under standing the integration between PM and CS as well as SPP is critical.

This is the path to view..

ECC- Logistics – Plant Maintenance – Management of Technical Objects – Equipment – Installed Base – Display

ishot-140
You can choose by a variety of criteria. One is serial number.

ishot-144
However, you can also select by Installed Base number.

ishot-141
In addition to selecting by equipment and material, you can select by the External ID. The number we found was under quantity. We are curious if this is the installed base for this E-BOM.

ishot-1421
If we select the Material BOM level, we can see the location and material which corresponds to this Installed Base number.


EWM Warehouse Integration Settings

EWM Integration

EWM is a very different application from the rest of SCM. It is also, along with SNC one of the most integrated. I quote from the book Selecting Software from WMS and ERP providers:

The WMS is interfacing to material handling equipment, AS/RS, carousels, shipment manifesting systems, cubiscan and other computerized systems….the WMS is one of the most highly interfaced computer software systems in the software marketplace. - Philip Obal

SAP EWM may be integrated to SAP ERP through the CIF, however, it is not integrated to the many other systems that talk to the WMS.

Initial Setup

Each EWM warehouse must be setup as a warehouse in ERP in the standard WM definition table. These settings related the plant and storage location to the warehouse must also be made.

EWM Hardware and Technical Setup

Transactional Orientation

EWM has a high amount of transactional integration with ECC due to the necessity to pass real time information such as delivery processing (through BAPIs, which means they do not need to be configured with the CIF). For this reason, it is really quite different from the planning applications in APO, which deal with aggregated data (and thus lower in volume). This means that the integration between SAP ERP and EWM needs to be analyzed on a project to determine the load for the CIF vs. the load for the BAPIs. It is recommended that EWM sit on its own server and it can integrate to SAP R/3 4.6C through ECC 5.0 with service pack SP06.


SPP Bill of Distribution – BOD

BOD as Central Concept

The Bill of Distribution (BOD) is a central concept of SPP. Every part in SPP is assigned to one BOD. A BOD is a combination of locations, and SPP can have multiple BOD which have different combinations of products assigned to them. This many to many relationship between BODs and products means that there is quite a bit of flexibility in SPP when it comes to customizing the viable network flows for different combinations of products. This makes a lot of sense for service parts.

BODs can be created with time limits or effectivity dates, so different ones can come into or our of effect. Once a BOD is no longer effective, the specific product flow that it allows will no longer occur.

The only time the BOD does not apply is if inventory rebalancing is performed — which is where inventory is repositioned. See the link below to find out more about this.

Difference Between Finished Good and Service Parts

However, you do not hear about the BOD with respect to finished goods planning. The bill of distribution is necessary because service parts are moved so frequently, a BOD is necessary to prevent the system from making too many decisions, the BOD basically limits what the shipping relationships can be in normal deployment (we will see later that the BOD does not apply to Inventory Balancing). Furthermore, the BOD only applies to the internal supply chain, it does not define shipping relationships from suppliers or to customers. The BOD terminology uses the terms “children” for subordinate locations and “parents” for superordinate locations (the term is relative. a parent location can have its own parent location, making a child location as well.)

How the BOD Applies to Products

One BOD is relevant for one product at one time. A BOD is simply a hierarchy of locations that are relevant for planning. The advantages of the BOD include:

  1. Prevents the system from over-ordering
  2. Reduces the planning processing time

In this way, all multi-echelon inventory movement, which is so common and necessary to service parts networks it taken out of deployment and concentrated in inventory balancing, which can be run as its own separate process.
_________________________________________

Operations Research Corner

Multi-echelon planning is an operations research term, that in effect means the ability to actively analyze many different locations in terms of supply and demand, and to relocate inventory flexibly. You can find much more detailed explanations of multi-echelon inventory optimization on the web. However, we also cover it under the title SPP Inventory Balancing on this post.

http://www.scmfocus.com/sapplanning/2009/04/23/inventory-balancing-in-spp/

_________________________________________

Integration to CRM

CRM is the reservoir for demand, however, and CRM has more data than SAP ERP. CRM stores

  1. Customer facing
  2. Ship from
  3. Original stock holding location

SAP ERP only stores

  1. Customer facing
  2. Ship from

Steps in BOD Creation and The Transactions

There are a number of steps that are necessary in order to setup the BOD. The BOD is the determination of all the legitimate relationships between locations. As such during the implementation this must be sorted out.

  1. Create the BOD /N/SAPAPO/BOD001
  2. Assign product to BOD /N/SAPAPO/PROD2BOD_M
  3. Display Products that are assigned to BOD /N/SAPAPO/PROD_DISP
  4. Display BOD that is assigned to a product /N/SAPAPO/PROP2BODDISP
  5. Adopt Product Assignment to new BOD /N/SAPAPO/BBOMASS BODs are product specific. You can have multiple BOD networks or “virtual networks” all superimposed on one physical network. However, some locations specialize in some products and not others. By assigning products to a BOD you specify which products and which validity period for which BOD apply.

BOD Setup

We want to go to transaction which will allow us to maintain the BOD. /N/SAPAPO/BOD001

ishot-169

ishot-170

ishot-171
Once in we need to add our currently existing locations into a hierarchy. We can do this by either using the top portion of the GUI, or by simply selecting a parent and right mouse clicking, we will receive this context sensitive menu.


Assigning the BOD to the Active Model

Once it is complete, we want to make sure we assign the BOD to the active model and to any other models we intend to use with it.


Setting up Transportation Lanes

Once we select save, we get an error message that we have not setup Transportation Lanes. Lets go forward and do that with transaction /N/SAPAPO/SCC_TL1. For details on this see the post on this blog on Transportation Lanes at the link below.

http://www.scmfocus.com/sapplanning/2008/09/14/snp-transportation-lane-and-transportation-resource-setup/

Assigning Products to the BOD

Products can only be assigned to one BOD at a time. However, BODs can have different validity periods and as old BODs become invalid, new valid BODs can take over.


We will want to assign products to the BOD /N/SAPAPO/PROD2BOD_M


Now you can see we have successfully assigned our two products to this BOD.


Assigning Planning Rights

Next we want to make sure that our user has all planning rights for SPP. This includes the rights for DRP Planner, supply chain analyst, inventory planner, forecast planner and buyer. However, first we have to have a user setup. This is highly confusing as there are multiple users that have different functions in SCM. The correct one is setup with transaction /N/SAPAPO/SAPSLUU5. For more information on setting up a user, goto the post which explains this in more detail.

http://www.scmfocus.com/sapplanning/2008/09/28/setting-up-a-scm-user-for-planning

If you are back from that post, now we can continue and enable our user for the Product Master views.

The Template Profile

We will select Location Product Master and then the Template Profile.

Now we goto transaction /N/SAPAPO/MNTPROF1


We select Location Product Master and then Template Profile. We create a new profile and call it SPP. As you can see, we don’t want to hide any of the views. We will save this template.


Next we will want to assign our user to this template in our user.


Setting Up Users With Mass Maintenance

Having done all this previous work, we are now setup so that our user will have the necessary access to the template. At this point we want to use the mass maintenance to define our products in all locations as stocked and assign the SPP planner for all locations. We will use the transaction MASSD. This is a mass maintenance function in APO and applies to all modules not just SPP. Its a powerful transaction, but dangerous as well. WIth this transaction the saying measure twice, cut once applies.

We want to enter product for the object type and we are going to want to go to the selection boxes below and enter our selections.


This is the tricky part. We want to search for a Component that is Location Dependent Data and then the attribute which we can search for with the drop down.


When we complete this process, it will look like this.

Now we will save it as a variant for future use.


Next we will go into it by selecting the Select button towards the bottom of the screen. We will get the following pop up and select “Change with Display.”


To see more about mass maintenance, see this post.

http://www.scmfocus.com/sapplanning/2008/09/13/product-location-profiles-and-mass-maintenance/

Location Dependent Data

Next we select the Location Dependent Data and select our planner (SNA) and then ST for the replenishment indicator. We then want to save. We change to “Set Fixed Value,” then we want to enter SPP in all of the entries. We also want to be careful to hit the double down arrow box.


However, don’t forget to select the box with the two down arrows, before you save. This assigns the planner or user to every product location combination.

This next screen shows a successful save.


Successful Assignment

Now we can see the SNA planner in each field in the product master.