Concept of Aggregates in APO

Hi Everybody,
Can any one tell me -
What are Aggregates in the context of APO? What are their uses?
Thanks & Regards,
Ujwal Arora

An APO aggregate contains a subset of the characteristics in the master planning object structure.
The creation and use of aggregates is optional. The data is always saved on the lowest level of detail. If aggregates exist, the system saves the planning data on the defined aggregate levels as well as on the lowest level of detail. The data is saved twice, but consistently; that is, the sum of the details equals the aggregate value.
The aggregates in APO are not the same as those in the Business Information Warehouse (BW), but they have the same purpose: to speed up data access and therefore increase performance. SAP recommends that you use aggregates in Demand Planning and Supply Network Planning
For example you are having Product Group -- P
Having Product as P1, P2, P3
Your forecast data for month 092008 for product P1 is 200
P2 300
P3 500
Then forecast data for product group P is for month 092008 is 1000
Aggregation is the summation at group level

Similar Messages

Client concept for SAP SCM APO and SAP TM

Hello,
We are installing SAP SCM APO 5.1 (SNP, gATP, DP) and SAP TM 7.0 (ramp up). Both connect via CIF to ECC 6.0 SP3. As far as my knowledge goes for CIF, both master data and transactional data is exchanged via CIF.
In ECC we have a three client concept:
100 customizing only
200 customizing + master data (golden client)
300 customizing + master data + transaction data
Can we use a similar model for TM and SCM APO as well? Should we then only connect ECC-300 to TM-300 and ECC300 to SCM-300 via CIF?
I have also heard that also some ECC customizing is transferred via CIF to SCM/TM. Is that true and does that change this model?
Regards,
Rob Veenman
SAP Basis.

Rob,
As a general rule of thumb, for each ECC client you will probably want an SCM client. From your landscape description, it is not clear to me in which clients you perform the everyday functions of development/test/production, but I guess you have already worked that out. Without knowing exactly how you manage your environment, I will say that it is probably a good idea to have active CIF connections between each of the three pairs of clients. Once you have set up a single connection between your first pair (ECC/SCM), you will find that setting up the second and third is pretty trivial.
Yes, quite a bit of ATP configuration can be CIFd across. Typically, you do this one time, and then lock the transfer of config out (there is a config setting in SCM to stop further transfer of config). From that point forward, any config that must be parallelled in both systems is usually done manually in both systems. Notable exceptions are Factory Calendars, units of measure, and Fiscal Periods, which can be pulled across from ECC to SCM any time you want via standard program.
Regards,
DB49

How to use Aggregates??

Hello Folks,
I created Aggregates for my Infocube and assigned fixed values for the following infoobjects:-
Sales Organization, Sales office and Sales group
1. When I click on Aggregate Data icon, I don't see any data?. But when I right click on the Infocube and select Manage I can see tons of data in my Info cube.
2. How can I see whether these aggrgates will improve my query performance?
3. Can I see the Aggregates in the Query Analyzer.
I would appreciate if someone can shred some light on the concepts of aggregates.
Thanks in advance
Kumar

Hi Kumar,
Goto RSRT and check aggregate is used or not, click 'execute+debug' and option 'aggs' -> 'display aggregate found', 'select aggregate'.
Check this:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3f66ba90-0201-0010-ac8d-b61d8fd9abe9
Bye
Dinesh

Fixing at aggregate level & unfixing at detailed level.

Hi,
Our requirement is as given below......
Our Demand Planning Process is Top-down process. Head Quarter will enter the demand at Territory, Channel and Product Group Level. These values are fixed and gets disaggregated to further planning level based on historical sales. The further planning levels are Sales Officer, Location & Product. Territory Manager can change the demand with in his targets across Sales officers (i.e. he should be able to change the targets of Sales officers without exceeding or reducing the Territory targets).
Can anyone suggest how to fix the keyfigures at Aggregate Level without fixing it at detailed level. We tried FIX_CALC macro, but could not resolve the issue.
Thanks in advance.
SP

You need to create AGGREGATES in your PLANNING OBJECT STRUCTURE, right click on POS and create the following aggregates
(1) ALL TERRITORY characteristics
Now you will be able to fix at the top level and still be able to change at the detailed level.
Read the following:* Let me know if you have any questions*
Aggregate
Definition
The aggregates in APO are not the same as those in the Business Information Warehouse (BW), but they have the same purpose: to speed up data access and therefore increase performance. SAP recommends that you use aggregates in Demand Planning.
These aggregates are sometimes referred to as persistent aggregates, in particular when talking about detail and aggregate levels in interactive planning.
Use
An APO aggregate contains a subset of the characteristics in the master planning object structure. The creation and use of aggregates is optional. The data is always saved on the lowest level of detail. If aggregates exist, the system saves the planning data on the defined aggregate levels as well as on the lowest level of detail. The data is saved twice, but consistently; that is, the sum of the details equals the aggregate value.
SAP recommends that the aggregates you build in APO for planning data also exist in BW for actual data.
If you want to save fixed values at aggregate level ; that is not at detail level of the master planning object structure, in a planning book, you must create aggregates for this level. Otherwise the data is only saved at detail level.
You cannot form aggregates for navigational attributes
See also:
Fixing Key Figure Values
Aggregates are discussed in detail in OSS note 503363. SAP recommends that you read this note thoroughly before configuring your master planning object structures and aggregate hierarchy.

Aggregates in demand planning

HI guru's
Do we use aggregates on MPO's in demand planning, is there any difference which used in bw,
thanks in advance
regards
ravi

Hi,
The aggregates in APO are not the same as those in the Business Information Warehouse (BW), but they have the same purpose: to speed up data access and therefore increase performance. SAP recommends that you use aggregates in Demand Planning.
An APO aggregate contains a subset of the characteristics in the master planning object structure. The creation and use of aggregates is optional. The data is always saved on the lowest level of detail. If aggregates exist, the system saves the planning data on the defined aggregate levels as well as on the lowest level of detail. The data is saved twice, but consistently; that is, the sum of the details equals the aggregate value.
SAP recommends that the aggregates you build in APO for planning data also exist in BW for actual data.
If you want to save fixed values at aggregate level ; that is not at detail level of the master planning object structure, in a planning book, you must create aggregates for this level. Otherwise the data is only saved at detail level.
You cannot form aggregates for navigational attributes
Hope this will help you...
Regards
Sujay

BUSINESS SYSTEM GROUP

What is a business system group please explain in the simple words?

Hi,
BSG is concept used in SAP APO, as the APO is part of SCM server and this server in separate than the R/3 server. U can couple more than one R/3 server to one SCM server. It might possible that every R/3 server has its diffrent nomenclature system for Material so in BSG the similar nomenclature system are grouped for streamline processing.
Shekhar

WLS Dependent Objects

Currently i'm working on a provisioning system being developed in WLS 6.1, specifically
the entity data layer.
On a recent EJB training course I attended, the course tutor asserted that it was
possible to implelement dependent objects on the said system. However, all the documentation
I have read since doesn't seem to suggest this at all.
As a particular example, I have an Order entity with a one-to-many relationship with
an OrderItem entity. There is also Party information that I thought could be a dependent
object of the Order entity. In other words, the Order entity maps multiple database
tables. It seems i'll have this problem later on when I begin to model Products
and Features of the OrderItem (i.e. will these have to be modelled as seperate entities
as well, as opposed to mapping the tables within the OrderItem entity).
Any clarification you could give me would be greatly appreciated. Perhaps some of
your own experience in this area, or pointers to useful URLs/books.

WLS 7.0 supports one EJB mapping to multiple tables.
Emmanuel Proulx wrote:
Dependent objects as they were introduced in draft EJB2.0 specifications do
not exist in the final version of the spec. In WLS 6.1 CMP, you have to have
1 entity object for 1 database table.
There is the concept of aggregate entity (one entity representing many
database tables) but WLS 6.1 CMP doesn't support that. You can do this with
BMP though.
Also, other products enable you to obtain aggregate entities, like WebGain's
TopLink, which plugs right into WLS.
Good luck,
Emmanuel
"Steven Curtis" <[email protected]> wrote in message
news:[email protected]..
Currently i'm working on a provisioning system being developed in WLS 6.1,specifically
the entity data layer.
On a recent EJB training course I attended, the course tutor asserted thatit was
possible to implelement dependent objects on the said system. However,all the documentation
I have read since doesn't seem to suggest this at all.
As a particular example, I have an Order entity with a one-to-manyrelationship with
an OrderItem entity. There is also Party information that I thought couldbe a dependent
object of the Order entity. In other words, the Order entity mapsmultiple database
tables. It seems i'll have this problem later on when I begin to modelProducts
and Features of the OrderItem (i.e. will these have to be modelled asseperate entities
as well, as opposed to mapping the tables within the OrderItem entity).
Any clarification you could give me would be greatly appreciated. Perhapssome of
your own experience in this area, or pointers to useful URLs/books.
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

Authorization in APO: org level concept (parent role -- derived role) ?

Hello experts,
we want to introduce some authorization / roles in APO using the typical R3 concept of having a "parent role" and derive "single roles" from such a parent role and change the "org levels" inside the single role. Testing this with master data objects like C_APO_LOC (location in APO) it seems to me that APO doesn't know about "org levels".
Whenever I create a parent role (lets say "Z_PAR_ROLE_LOC_MASTER") to access /SAPAPO/LOC3 (Location master data) and create a single role out of it (derive it into Z_SINGLE_ROLE_LOCMASTER_1234") and enter the location ID 1234 ... regenerating and populating a change from the parent role "Z_PAR_ROLE_LOC_MASTER" does immediately wipe out the location ID 1234 maintained before in the single/derived role "Z_SINGLE_ROLE_LOCMASTER_1234".
My question: is this by design that APO does not know about "org levels" or is there something special I have to consider using PFCG correctly in SCM (I can see the "Org Level" button but it says there are no org levels) ?
Regards
Thomas

I got the solution - the profile generation was missing !

Standard Concepts: CVC and POS in APO

Hello All,
please con anybody explain me these standards concepts in APO: CVC and POS, in detail what is the links between these 2 concepts?
my client has given me a brief explanation that CVC is master data of DP, and POS is the principle structure where is based DP and contain the CVC.
is not clear for me these concepts and how should i do to control on the system these informations and the links.
thanks a lot
Bilal

Bilal,
Firstly refer to :
http://help.sap.com/saphelp_scm50/helpdata/en/8f/9d6937089c2556e10000009b38f889/frameset.htm
Now, let me try and explain to you briefly.
Consider a table. A table has a certain structure. This structure is defined by its fields. For instance a table for sales orders will have SO Number, Sold to Party, Ship to Party, Reference PO, Delivery Date etc... These fields, constitute the structure. Then there rae records. For the sales order table a record will be
So number=100001
Sold to Party = ABC
Ship to Party = XYZ etc
This is a record.
Now try to draw an analogy with POS. The Master Planning Object structure constitutes a structure. You assign characteristics to an MPOS, which are equivalent to teh fields in the table. For instance the standard DP MPOS 9ADPBAS conatins the follwoing characteristics:
9ABRAND     Brand
9ALOCNO     APO Location
9ALOCTO     APO Destinatn Loc.
9AMATNR     APO Product
9AVKORG     Sales Organization
This structure is called the MPOS. It defines the lowest level at which data is storeed and planned.
Now draw an analogy of teh table records to the CVC. A characteristic value combination is a record with values assigned to the characteristics of the MPOS. For instance one CVC could be:
9ABRAND     PEPSI
9ALOCNO     NEW YORK
9ALOCTO     PARIS
9AMATNR     PEPSI CAN 330 ML
9AVKORG     001
This is ONE CVC. similarl;y for the same MPOS you can have another CVC:
9ABRAND     PEPSI
9ALOCNO     NEW DELHI
9ALOCTO     BANGALORE
9AMATNR     PEPSI PET 500 ML
9AVKORG     002
Similarly you can have thousands of CVCs for the same POS.
So, MPOS is nothing but just the structure which defines what are the plannable characteristics. CVCs are records, or values assigned to MPOS characteristics...
MPOS: /sapapo/msdp_admin
CVC: /sapapo/mc62
I have tried to draw an analogy so that you understand better. hope this helps.
I would sugegst you to purchase "Supply Chain Planning in SAP SCM by Jorg Dickersback. Its an awesome book for starters.
Abhi

APO - Aggregate Forecasting and Best Practices

I am interested in options to save time and improve accuracy of forecasts in APO Demand Planning. Can anyone help me by recommending best practices, processes and design that they have seen work well?
We currently forecast at the Product level (detailed). We are considering changing that to the Product Family level. If you have done this, please reply.

Hello Dan -
Doing it at the Product level is very detailed (but it depends on the number of SKU's Available and that are to be forecasted).
Here for me on my project we have about sample size 5000 finished goods to start with and forecasting at that minute level wont help. For me i have classified a product group level where i have linked all the similar FGs. tht way when you are working with the product group you are able to be a little from assertive in your forecasting. After that you can use proportional factors that will help you in allocating the necessary forecast down to product level. This way you are happy as well as the management is happy (high level report) as they dont have to go thru all the data that is not even necessary for them to see.
Hope this helps.
Regards,
Suresh Garg

Forecasting in DP: At aggregate level or at detailed level?

Hello All,
I have selection ID in APO DP 4.0 comprising of may products. I forecast them as a whole using some forecast method (may be seasonality method). How SAP DP forecasts? Does it individually forecast for each product or does it forecast at aggregate level? Has someone analyzed and come across such situation?
Thanks and Best Regards, Manoj

Dear Manoj,
The concept of selection and aggregation is very impotant in APO. Take an example:
You have a selection for packsize "Display SKU's under packsize A. Say there are 10 SKU's. Now when you run the forecast in the background, you need to define the selection and aggregation level. So for the same selection, if you have defnied the aggregation as SKU, the forecast job will for each SKU. However if "packsize" is selected in aggregation, the forecast will run at packsize level.
In the case of the interactive planning, the selection defines the aggregation level. Suppose you have loaded the selection described above and loaded for all SKU, the forecast will run for the entire packsize (aggregation across all SKU's). However to forecast individually in interactive planning, you need to load the SKU's one by one and run the forecast.
Regards,
Kedar

APO DP Security - Securing by Characteristics (Sales Org & Plant)

We currently secure by Planning Areas and Planning Books, but now need to secure by Sales Org and Plant within Planning Areas.
Note 400434 refers to using exit EXIT_/SAPAPO/SAPLMCPR_015 and badi /SAPAPO/SDP_SELECTOR
but I need more info.
Has anyone implemented APO Security on Characteristics at their site, pls?

Simon,
One approach as you mentioned can be creating Z Table where in you set up disaggregation proportion from product group level to product level or product location level.
Product Group X 100 Product A@loc1 10
Product B@loc1 90
Download your planning area data into infocube C and then use BW routines to convert the data from group in infocube C to lower level refereing Z Table....into another infocube..
SAP also provides such standard functionality of spliting the aggregate Demand plan to detailed level
SNP plan..through functionality like location slit or product split.
Essential you will be using same concept in yor BW solution or you may also want to consider the
release your DP to SNP planning area its as solution of diaggregation of data to lower level.
Regards,
Manish

General Discussion - Why to choose APO over R/3 for planning?

Hi All,
Why do we choose APO over R/3 for planning? What are the inputs or other factors that make APO a better planning tool?
Are the factors which make APO a better tool not available foe R/3 planning?
Thanks in advance
Changed subject suitably.
Message was edited by:
Somnath Manna

I do aggree what other have mentioned .Here are specific inputs on newly desined process in APO in comparisosn with R/3
1. Existing Processes in SAP R/3
Forecasting
Forecasting enables companies to run statistical forecasting model, aggregate and disaggregate forecasts, as well as the capability to modify forecasting numbers manually
Newly-Designed Processes
Demand Planning DP (SAP APO)
Demand Planning adds to forecasting capabilities to manage promotions, product introductions and phase outs, as well as the impact o causal factors, like weather or macro economic data.
Additional forecasting techniques are available like Linear Regression (Causal Factors), Croston Method (Slow Moving Items) and Weighted Average
Consensus based Planning enables Marketing, Sales, Logistics to share and collaborate on their forecast and create a final consensus forecast
Forecasting based on characteristics instead of SKU for configured products
2. Existing Processes in SAP R/3
Sales & Operations Planning
SOP allows to consolidate forecast based on supply capabilities, through reporting and interactive planning capabilities.
Newly-Designed Processes
Supply Network Planning SNP (SAP APO)
Demand and Supply Plans can be intelligently balanced leveraging cost or/and revenue based optimization techniques
Trade-off Analysis to determine product-mix, inventory build ups for seasonal demand, capacity allocations for alternative manufacturing locations etc.
Web based information sharing and collaborative interactive planning environment
KPI Reporting
3. Existing Processes in SAP R/3
Distribution Requirements Planning
Traditional DRP logic allows to calculate requirements for a single stage distribution network
Newly-Designed Processes
Supply Network Planning SNP (SAP APO)
Supply Network Heuristic enables to run DRP across the complete supply network generating requirements (production and purchasing) at each node.
The planner can easily navigate through the network to view and modify demands and supplys in their different categories
Demand Planning Units and Stock Keeping Units mapping can be done on quotations.
4. Existing Processes in SAP R/3
Not available
Newly-Designed Processes
Deployment SNP (SAP APO)
The ability to deploy products through the supply network based on pull or push concepts. Different heuristics like fair share logics are supported.
Transport Load Building allows to combine different products to a single load, interactive, as well as via heuristic to create full truck loads.
5. Existing Processes in SAP R/3
Master Planning
Master Planning allows to plan production at an aggregated level including rough cut capacity planning.
Newly-Designed Processes
Supply Network Planning SNP (SAP APO)
Supply Network Planning allows to consider distribution, production and transportation constraints concurrently.
In addition to a generic SNP Optimizer based on Linear Programming and capacity leveling algorithms, industry specific optimization is available for
Campaign Optimization
Capable to Match
6. Existing Processes in SAP R/3
Material Requirements Planning
MRP calculates material requirements based on BOM structures, lead times, lot sizes etc.
Capacity Planning
CRP in a second step looks at the capacity requirements
Newly-Designed Processes
Production Planning PP/DS (SAP APO)
Production Planning allows to consider material and capacity constraints simultaneously to derive material, capacity requirements and dynamic lead times. BOMs and lot sizing will be also considered
Pegging relationships between customer order, production orders, purchase orders will be stored and enable bi-directional propagation if changes occur on the demand or supply side
7. Existing Processes in SAP R/3
Transportation Planning
Manual Planning of shipments, including predefined master routes.
Newly-Designed Processes
Transportation Planning TP/VS (SAP APO)
Transportation Planning enables companies to determine the right shipment mode and route based on demand and supply situation, considering transportation constraints and costs.
8. Existing Processes in SAP R/3
Shop Floor Scheduling and Assembly Processing
Planning Table to view in a Gant Chart the schedule.
Heuristics like forward/backward scheduling (infinite)
Manual scheduling
Newly-Designed Processes
Detailed Scheduling PP/DS (SAP APO)
Finite and infinite scheduling, considering material, capacity, time and market constraints.
Manual scheduling
Scheduling optimization via optimization algorithms, like
Genetic Algorithm
Constraint based Propagation
Kiran Kute

Key figure fixing in aggregate level partially locking

Hi Guys,
When fix the cell in the planning book, getting "One or more cells could not be completely fixed" message.
1. If a material having only one CVC in the MPOS those quantity can be fixed correctly without any issues.
2. If a material having more than 1 CVC combination and try to fix one of the CVC combination quantity, it is fixing partially and getting the above message.
3. Even, it is not allowing to fix the quantity in aggregate level also.
We are in SCM 7.0.
Is there precondition that need to fix the material having only one CVC combination.
Even a material having multiple CVC combination why it is not allowing to fix one CVC combination in detail level.
Is aggregate level key figure fixing is not allowed ?
Please clarify.
Thanks
Saravanan V

Hi,
It is not mandatory to assign Standard KF to be able to fix. However your custom infoobject that you created must be of type APO KF and not BW KF.
That said, Let us try and address your first problem.
You can fix at an aggregate level. However there a few points to remember.
Let us consider a couple of scenarios.
1) In your selection id, it is showing a number of products. You are selecting all the products at one go and load the data and try to fix at this level. This is not possible.
2) In your selection id, you have selected a product division. For a single product division you are loading data and try to fix at this level. This is the true aggregate level and it should be possible at this level.
Hope this helps.
Thanks
Mani Suresh

Schedule lines in APO

hi guys
when i run planning in PPDS for material in APO
its creating PR's instead of schedule lines.
when it should create PRs & when it should create Schedule lines
Doc type is LP
Ext planning ind : 1 i maintained.
is there any setting in external procurement relationship.
can you explain me am new to this APO concept.
thanks
nani

Dear Ritwik,
I guess you have done following steps already.
1. Created APO relevant Scheduling agreement. Ext, Planning Indicator.
2. CIF transfer of the scheduling agreements.
Now you check in External Procurement relationships, you need to ensure that you only have one active external procurement relationship for the products( which is Created by your APO relavant Scheduling Agreement CIF). It is possible that you have more than one procurement relationship active for the product and so it is creating PR's instead of Schedule lines.
Hope it helps.
Regards\
Kumar

Concept of Aggregates in APO

Similar Messages

Maybe you are looking for