Disaggregation issue

Hi All,
actually I've a requirement where the standard disaggregation function seem to bring no success. Here my requirement:
In the Planning Query I've a row Hierarchy with a structure and two Characteristics:
e.g.
Structure:
Region I
Region II etc.
Characteristics:
Subregion and Respons. Person
Original Values:
Region I: 1.000
-> Subregion I: 1.000
> Musterman I: 500
> Musterman II. 500
The structure Element is locked for manual Planning. The user should be able to plan values for Subregions and Respon. Persons. The only way to do get the cells inputable was using the disaggregation function in the query. But the function should not do a normal disaggregation. Here a few examples how it must work:
Entering 1.500 for the Subregion I:
Instead of:
Region I: 1.500
-> Subregion I: 1.500
> Musterman I: 750
> Musterman II. 750
...the result should look like:
Region I: 1.500
-> Subregion I: 1.500
> Musterman I: 500
> Musterman II. 500
> #: 500
On the other hand, changing values of the responsible persons, lead to
1)
Region I: 1.000
-> Subregion I: 1.000
> Musterman I: 500
> Musterman II. 500
2)
Region I: 1.500
-> Subregion I: 1.500
> Musterman I: 1000
> Musterman II. 500
Doe's anybody has an idea how this issue can be solved? I already searched in the forum for a while...

Hi Christopher,
posting the difference of a higher level to # is not really a disaggregation (or even a planning function). It's standard functionality. Create a planning level and query that do not contain resp. person and enter the values there. Then they will appear as # in the query you already have.
Regards,
Marc
SAP NetWeaver RIG

Similar Messages

APO DP SCM 5.0 Disaggregation issue + performance guide

Hi All,
I am again facing a u201Dsmallu201D disaggregation calculation issue. What I am trying to do is to calculate Corrected sales history to the most detailed level through disaggregation.
KF1: Sales history
KF2: Correction
KF3: Corrected Sales history
Situation:
The calculation is performed via background job:
Aggregation level:
Country
Sales org.
Product
Selection:
Country: 001
Sales org: 2000
Product: 12 & 13
I use macro for the calculation:
Start
Step1: KF3 = initial
Step2: KF3 (redisaggregation) = KF1 (Values) u2013 KF2 (Values)
End
Planning Area:
KF3: I (if initial, based on a another keyfigure) u2013 KF1 , Time based disaggregation (not relevant)
How can I get KF1 based disaggregation for KF3? Is it even possible with the above solution or should I come up with a totally different approach to this? Calculating in the most detailed level is not possible because the system canu2019t handle so many CVCu2019s. Although I kind of wander that, the system is almost a beast and it can only calculate 50000 CVCu2019s in a 5 hour? Any suggestions on this one also?
Thanks in advance,
Juha

Hi Manimaran,
I just tested your suggestion and the results are:
Sales history KF1:
SUM: 1000
Product: A: 750
Product: B: 250
Product A for Customer 1: 325
Product A for Customer 2: 325
Product B for Customer 1: 125
Product B for Customer 2: 125
Correction KF2:
SUM: 1000 (automatically split via disaggregation, this number is inserted in planning view and after this the background job is executed)
Product: A: 500
Product: B: 500
Product A for Customer 1: 250
Product A for Customer 2: 250
Product B for Customer 1: 250
Product B for Customer 2: 250
Corrected Sales history KF3 (after background job and disaggregation):
SUM: 2000
Product: A: 1250
Product: B: 750
Product A for Customer 1: 625
Product A for Customer 2: 625
Product B for Customer 1: 375
Product B for Customer 2: 375
As I analyzed this it seems like it is disaggregating it evenly? I have checked that the planning area settings are:
KF3: P - (based on a keyfigure) Keyfigure: KF1
so on that basis there should be no even disaggregation. I also tried with different aggregation level settings but the results are the same.
BR,
Juha
Edited by: Juha Pajarinen on Aug 12, 2011 11:37 AM

APO DP Disaggregation issue.

Hi All,
Dis-aggregation issue in Demand planning forecast execution. History 3 material, CVC Combinations 6 material, Matching
History and CVC 3, when i execute Forecast, disagrregated to all 6 material. i want only 3 materila dis-aggregation APPODPDANT
i used for Disagrregation,please help me

Hello,
If I understand correctly, you want to use proportional factor to disaggregate the calculated forecast, right?
Please first make sure that the proportional factor APPODPDANT is correctly calculated based on the history key figure.
Make sure the APODPDANT's values are zeroes for those CVCs without historical data.
(You can check APPODPDANT key figure's value by putting it into a certain dataview.)
If the proportional factor is not correct, please recalculate it in /sapapo/mc8v.
Then please make sure that the disaggregation type of the forecast key figure is correctly set. It shoud be:
1)Disaggregation type should be 'P' instead of 'I'. ('I' is also OK, but for testing purpose, 'P' is better.)
2)Disaggregation key figure is set as APODPDANT.
3)Time based disaggregation should have the same setting as structural disaggregation.
At last, the forecast run in foreground should be run at aggregated level.
Best Regards,
Ada

Displaying data on a different level then the allocation check

Hi
we are creating sales orders in R/3 and executing a sales order check based on a planning area in APO.
this check is done on Product / sold to, because that is the level where teh forecast is entered.
However, one sold to can contain different ship to's. so because of disagregation, it is randomly done over the ship to's.
What we want to obtain is that the when the allocation check is done and the orders is in APO via the CIF, the data is displayed on product sold to, ship to like in the sales order while the check to see if there is enough quantity can remain on product sold to.
Do you have any ideas?
Tommy

Tommy,
Please elaborate on your problem.
I assume you are talking about the Planning book used for Allocations; please confirm. If the only CVCs in your Allocation planning book and your Product Allocation Group are 'Product' and 'Sold To', then 'ShipTo' (and ShipTo disaggregation) is irrelevant. Product Allocation only considers the CVCs that have been created. In this case, multiple ShipTos against a single SoldTo are 'first come first served' until the SoldTo Incoming Orders qty reaches the SoldTo Allocation Qty.
It is possible to include ShipTo in your Allocation Group and Allocation Planning Area in addition to SoldTo; this is a fairly common solution. If you do so, you will THEN have to consider ShipTo Disaggregation issues. Since this seems to be a negative issue for you, I would recommend against it.
Best Regards,
DB49

Issue with Disaggregation Type A

I am seeing some strange behavior with respect to Disaggregation type A.
We have region and product as characteristics and when we use the Dissagregation type A for KF A,
Lets say Region A has 10,000 products under it and Region B has 15,000 products under it. Most products for Region A and B are common. We load decimal numbers like 1.11, 1.0, 1.2 and.94 for 36 months in KF A by Region only (not by region and by product into APO).
So according to Disag type A, I would expect all the products under Region A to have the same numbers as 1.11, 1.0, 1.2 and 0.94. But I am seeing some different numbers with slight difference when I load Region A and product 1004 or a bunch of products (lets say).
What could be the reason for this behavior and how to correct it ? Would really appreciate any inputs on this from the experts.
Thanks
Alicia

Alicia,
You mention that you see "s;ight difference" in the values. Could you let me know what values you see? A slight difference can occur in disaggregation due to decimal settings fo rthe KF and rounding effects.
Also is this somrthing that has happened all of a sudden and used to work correctly earlier? Is this issue along all the regions/CVCS or only some?
Abhi
Edited by: abhishek sharma on Apr 12, 2010 10:35 AM

Time based disaggregation

Hi All,
The requirement is to dis-aggregate from months to weeks for the current month plus next month, based on last months historical data.
There are two data views
1. having the data in (forecasting is done in this data view)
2. having data in months and weeks. ( last months history is available in weeks and the current & current +1 month in weeks)
The forecast that is in months needs to be disaggregated into weeks for the first 2 months based on last months history.
I have created another KF to copy the last month history into the current and current +1 month in the weekly view.
Also no calendar is defined.
during disaggregation based on the KF the system is throughing unexpected values especially when the last and the next month overlap.
Ex: these are the disaggregated values
W 31.2010 W 32.2010 W 33.2010 W 34.2010 W 35.2010 M 09.2010
3747 2214 2554 3406 14258
here in W35 the value is 14258 which is wrong as the value for M092010 is also added into this week.
Kindly through some light on this weird behavior.
Regards

Hello Nitin,
Sorry to intrude into this old thread that I read with much hope but I find this unanswered as I just happen to post a ditto issue.
Would you recall how this was resolved :-). Pardon if this sounds irritating and unrelated to you know :-)
This is what I asked a while ago
http://scn.sap.com/message/14565886#14565886
My settings for KF1 are P-KF2 and K-KF2 but in my case KF2 has 0 values for some selections (new products). In human language, I am trying to disaggregate an "adjustment" to the statistical forecast that is 0 for new products. The adjustment itself is done in month buckets. Simple solution though is to do the adjustments in weeks but that is like multiplying effort by 5 times.
SAP is doing some dumb thing here as this is a logic of convenience. To me it doesn't appear to be a storage bucket setting issue as I am only expecting a sane result in week buckets and I do have week (and also month) checked in storage bucket profile
Here is what is happening. Hoping some consultant from SAP looks into this and acknowledges this as a bug as I didn't manage to find a note. I will have to grope for key words all night. This is such a common unavoidable scenario.
Step1: System finds the COUNT of week buckets (NOT calendar weeks- just the weeks that FALL in the month) in EACH calendar month separately. E.g. Feb 2014 has 5 weekly buckets, incl.1 partially in Jan and 1 partially in March. The week of 27th Jan 2014 is a “week bucket” for BOTH Jan 2014 and Feb2014.
Step2: It then divides the monthly value of KF1 by the number of weeks in Step1 to calculate EQUAL values per bucket week belonging to respective calendar months, IRRESPECTIVE of whether the week is a WHOLE or PARTIAL week.
Step3: It then simply adds the EQUAL values of resp. week buckets of step1, WHENEVER, the week is spread across months. e.g. In the week beginning 27th Jan 2014, that transcends to next month (Feb 2014), it adds up the results calculated in step2 for W-1 and W+1.
Thanks
BS

Issue with Product Allocation Scenario

I am Trying out Product Allocation in APO (SCM 5.0).
Relevant setup in SPRO - Product Allocation Object, Group, Procedure, Sequence etc., Planning Object Structure, Planning Area, CVC generation, Connection between Planning Area and Product Allocation object in GATP, assignment in Location Product Master (at Customer Location) Product Allocation Procedure, Check mode, ATP Group has been done in APO.
After entering data in appropriate keyfigures (Allocated Qty) it shows up under GATP>> Reporting >> Product Allocations >> Time Series per CVC
Have carried out ATP Simulation to check that for a given product at Customer the Product Allocation against a Required Quantity takes place correctly.
Now trying to carry out the Product Allocation check by creating a Sales Order in ECC. In that case during the material availability check screen in APO, the product allocation does not show up.
I believe it is related to master data settings for the product in ECC. My questions are as follows:
1. In ECC the product exists at the manufacturing plant only (and not at customer as in APO). There in MRP3 tab Strategy Group is maintained. Is this along with Availability Check field responsible for determining the check instruction (combination of check mode + business event) in APO for the Product Allocation check.
2. If so (which I guess it is) I can see the check instruction picked up in APO while creation of sales order in ECC is different from the check instruction I ran simulation with. How can I ensure the same check instruction is chosen (in which case I believe the availability check result will be same as the ATP Simulation carried out in APO).
3. In APO I ran simulation for the product at customer location (and maintained the required ATP settings in the product master). In case of Sales Order creation in ECC how does system pick up the Check Mode and Business Event for the product (having Sold-to as customer and Supply Plant as the plant code) and use it in APO.
4. Any other setting/configuration that is missed causing this behaviour.
I guess some of the questions is a bit hazy but I would appreciate if someone can outline the Product Allocation Scenario. I am trying out based on Building Block S59 Demand Planning for Product Allocation but of course it does not detail out enough.
Disclaimer: My knowledge of GATP is almost nil but am exploring.
Thanks,
Somnath

Hi Somnath,
It will be a pleasure to help you out.
Firstly I will list out all the steps which I can think of:
(1) R3-You have moved all the ATP customizing from R3 to APO via ATP integration model.
(2) APO- goto SPRO>APO>GATP>General Settings>Maintain Check Instructions
Here go to Check Mode- 041 and Business Event- A and maintain the following settings manually in development and migrate it all the way to Production
I am assuming here that you want to first do an allocation check and then availability check**
Product Allocation: Change from NO CHECK to First Check
Product Check: Change from First Check to Second Check
This check mode and business event is the most common one which is triggered while placing a sales order
See the following blog for DETERMINATION OF CHECK MODE
http://solution-timezone-issue.blogspot.com/
There might be other check modes( 030, 050) which might also require this change. However you can judge that while placing a sales order and when you go to the availability screen, You have the tab - SCOPE OF CHECK CONTROL where you can see the Check Mode + Business Event
Following guidelines can be used to modify Check Instrctions after Customizing Import from R/3
1. Business Event A* is Sales Order Entry (The main scope of GATP) so define check instructions for all check modes since it is not possible to identify the requirement class that may come over on an order. For Business Event A* if availability check was being done in R3, then define check instructions with Allocation as first step, then Availability check as second step. Else if no availablity check in R3 then define check instructions with no availability and no allocation checks.
2. Business Event B* is normally for deliveries but is also required for Rush Sales Orders. An R/3 configuration showed that 041 is the only requirement class that will come across for this business event. Hence defined only for 041 check mode. For Business Event B* if availability check was being done in R3, then define check instructions with Allocation as first step, then Availability check as second step. Else if no availablity check in R3 then define check instructions with no availability and no allocation checks.
3. Business Event 03 required for Inventory Transaction availability check such as MB1C. For such transactions, the APO Product Master Check Mode is used. Hence check instructions for all Check Modes are maintained. For Business Event 03 if availability check was being done in R3, then define check instructions with Availability check as first step. Else if no availablity check in R3 then define check instructions with no availability checks.
(3) Maintain the Product Alllocation Procedure:
a- Create a Product Alloc Object -- Example: PAO-001
In this step, we define the product allocations objects - product allocations are saved per object for a characteristics combination in the product allocation group.
Product Allocation Procedures can be used to maintain different Product Allocation Objects for different time validity periods.
Generally Product Allocation Objects are used to model the different reasons for the need for allocation material shortage, capacity constraint, etc.
b- Product Alloc Group--PAO-1234
A product allocation group defines a group of characteristics against which allocation checking is done.
 Creating a Product Allocation Group creates a characteristics directory in the APO database and an area in Live Cache where the key figures are maintained.
 If Check Planning Area is set to No then allocation and incoming order quantitiy data can be seen in table /SAPAPO/QTTAB. If the Check Planning Area is set to Yes then no data is stored in this table and the allocation check is done directly against the data in the Planning area.
 Detials of allocationconsumption by sales orders are maintained in table /SAPAPO/QTVB in APO and in QTVB in R/3.
If Check Planning Area is set to Yes and if there are users are in the change mode in the Planning Book, Sales Order Entry can get locked out.
If Check Planning Area is initially set to yes and then deactivated later you will no longer see data in /SAPAPO/AC42.
Settings:
Check Planning Area Yes. The reason being that users are not expected to lock planning books as they would be defaulted into the display mode (through a development object). Also most allocation uploads will be through batch jobs. Setting it to Yes reduces one step of moving data between the planning area and the allocation group.
Check Date - Material Availability Date. Consumption of allocation quantity and checking of available allocation quantities is determined by the check date.
Time Bucket Profile Week
Characteristics Product Allocation Object (1), Product (2), Plant(3), Customer(4)
Consumption Period Bwd Consumption 1
Meaning that first the order will consume from current week allocation and then go 1 week backward to consume.
c- Product Allocation Procedure --- PAO-4567
Step Sequence:
Step -
Step Name- -
Prod Alloc Group -
Wild card
1 First Step PAO-1234 9
Alloc Procudure - PAO-4567
Prod Alloc Step -1
Control
Valid from -
Valid to---- -
Object -
Active -
Factor
 12/31/2037 PAO-001 Check the Box 1
d- Maintain Connection to Planning Area (APO)
In this step, we maintain the assignment of the planning area to the product allocation group. We must make this assignment because characteristics of the product allocation group have different names from the info objects of the planning area.
All characteristics of a product allocation group must be assigned to an info object. But multiple info objects can be assigned to one info object. It is not always necessary to assign every info object to a characteristic. It is possible for aggregation and disaggregation (depending on the direction of transfer) to take place with info objects that are not assigned.
Product Alloc Group -
Planning Area -
Version -
Time Buckets
PAO-1234 xxxxx 000 W
Characteristic
KONOB - Prod Alloc Obj
MATNR --- Material
WERK -
Plant
XXXXX---- Customer
Key Figures
Order Qty - AMENGE
Alloc Qty - KCQTY
e- Check the Product Alloc Settings
This is only a check- Everything should be green and OK .
(4) You have planned the Characteristic Combination on which you want to do ALLOCATION.
Create a new POS- Which has your chracateristics as PRODUCT, PLANT,CUSTOMER, Product Alloc Object ( 9AKONOB)
Planning Area,- Key figures required are Alloc Qty, Order Qty( Sales Order Qty)
PLannig Book, Data View which has the following characteristics- Product, PLant
Assuming you are allocating at the following CVC level- Product, PLant,Customer
Step 1:
/n/sapapo/MC62-Create Time Series- Basicallly your CVCs -
Example: Product 1234, Plant INDIA, CUstomer WALKART
Step 2:
Move Characteristic Values Combination to Allocation Group (APO)
/SAPAPO/ATPQ_PAREA_K
INput :
Planning Area: xxxx
Prod Alloc Group: PAO-1234
(5) In the INtegration MOdel - Activate the ATP CHECK Integration model for the Plant and material
THis is the KEY which decides whether availability should be done in R3 or APO
Material Active in the integration model -- Means Availability( GLOBAL AVAILABILITY: Prod Alloc+Prod Availability) is done in APO
Material not active in the integration model --- Means Availability Check is done in R3
(6) APO MASTER DATA SETTINGS:
Material Master: On the ATP Tab, Assign Loc Dep Procedure ( Prod Alloc Procedure)
Location Master: Calendar Tab> Create a shipping time stream calendar
Additional Info: Please contact your R3-SD people as this involves a lot of understanding and I have not listed all the details here.
This config shown here is a very basic one which not even 25% of the companies might be using.
If you have any questions on this part- please see my business card and email me**
(7) SCHEDULING: This is a major task which determines the route and transit times for calculating the
Material Availability date
Goods Issue Date
Delivery Date
on the sales order line item- schedule line
I dont know whether you need info on this**There are many ways of doing this
a- Configurable Scheduling
b- COndition records
c- User Exit
You can find documentation in SPRO or else let me know*
For simplicity- Let me take the easiest to create and difficult to maintain master data- Condition Records
Step1 --Define Field Catalog for Condition Table (APO)
/SAPCND/AU01
Require Plant and Route defined here in the field catalog
Step 2- Define Condition Table for Scheduling (APO)
/SAPCND/AU03
Create a new table- 901
901 - Pick Time based on Route with key as Route
902- Route Time based on route
Step 3- Maintain Access for Scheduling (APO)
/SAPCND/AU07
Take the important ones- PICK and TRAN
I am assuming again as I dont know what kind of Scheduling is maintained on R3 Side. Mostly 80% companies have only two lead times- Pick and Route Transit time.**
PICK- Select pick and click on accesses > Acno-10-- Table-901
 >> Then save it > and go in again
Select PICK and click on Fields> A popup will appear > Enter the access sequence as PICK--- Enter the access as 10 and click on the GREEn ARROW and save it
TRAN- Select TRAN and click on accesses > Acno-10-- Table-902
 >> Then save it > and go in again
Select TRAN and click on Fields> A popup will appear > Enter the access sequence as TRAN--- Enter the access as 10 and click on the GREEn ARROW and save it
Now coming to maintaining the Condition records in APO EASY ACCESS
/SAPCND/AU11
Create SCheduling Step for PICK : Enter condition type- PICK
Enter Route- USCAN --- Duration -24:00 (Hrs)
Create SCheduling Step for TRAN: Enter condition type- TRAN
Enter Route- USCAN --- Duration -48:00 (Hrs)
Now Let me answer your questions:
(1) Question 1- In ECC the product exists at the manufacturing plant only (and not at customer as in APO).
I did not undertsand what you mean here. As we can create a Material at the following locations in APO( Dist Center(DC), Manu Plant(PL), Cusomter, Vendor, etc)
For GATP all we need is the material at a PLant location
STrategy Group on MRP3 tab: This is purely used for determining the CHECK MODE value on APO Product Master.
When this is blank on R3, the check mode will be blank on APO.
However SAP recommends Putting in a strategy group value on R3 Material Master
or
a default Check MOde value for all those Products who have blank check mode- 041 is the best value * This piece SAP hasnt recommended but I found that there is No harm in anyway and it is MANDATORYfor inventory transactions like GOODS ISSUE otherwise you will get a QUEUE in SYSFAIL **
Even if this is blank this has no effect on the GLOBAL ATP as the Check mode for a SD transaction is determined as follows
98% of the SD transactions will generate a CHeck mode of 041 and Business Event- A ***
Through the item category and the MRP type in the MRP view
The item category is derived from the item category group in the Sales view of the material master record and from the order type of the sales document. Together with the MRP type in the MRP view of the material master record, the item category determines what requirements type is selected. The advantage of this method is that the selection of the requirements type depends on the business process (such as quotation, sales order, or repair).
(2) Question 2 - I guess now you must have understood why when you do a simulation in APO, it is taking the Check mode from APO product Master
and when you do a ATP Check from R3, the check mode(041) is different
You dont need to ensure that they are the same- It doesnt matter in anyway.
(3) Question 3- In APO I ran simulation for the product at customer location (and maintained the required ATP settings in the product master).I
When you run ATP simulation- AC04, you generally run it for the plant as that is the supplying location and not the customer.
In case of Sales Order creation in ECC how does system pick up the Check Mode and Business Event for the product (having Sold-to as customer and Supply Plant as the plant code) and use it in APO.
PLease look above for this answer.
(4) Question 4 - Any other setting/configuration that is missed causing this behaviour.
To my best knowledge, whatever I could remember I have listed out. However there are some more steps which might be needed.
Follow all the steps as I have mentioned and whenever you get struck somewhere, shoot me a message and I will help you.
ONe more pointer here to what you have mentioned
Relevant setup in SPRO - Product Allocation Object, Group, Procedure, Sequence etc., Planning Object Structure, Planning Area, CVC generation, Connection between Planning Area and Product Allocation object in GATP, assignment in Location Product Master (at Customer Location) Product Allocation Procedure, Check mode, ATP Group has been done in APO.
After entering data in appropriate keyfigures (Allocated Qty) it shows up under GATP>> Reporting >> Product Allocations >> Time Series per CVC
Have carried out ATP Simulation to check that for a given product at Customer the Product Allocation against a Required Quantity takes place correctly.
Somnath, I believe you might have a wrong picture here. The concept of allocation is Controlling Supply against huge Demand which is in this case coming from SALES ORDER
When you place a sales order, the supplying location is your plant and that is where you would like to put in allocation quantities
Say for example for a material 12345 - You have stock of 100 Qty in Plant KING fo this week and it shows as follows in the planning book
Customers say are WALKART, GE-FUG, MACROGUN
The CVCs which we have to create are as follows
Similar to Demand PLanning**
Material 12345 -PLant KING-Cust WALKART-Prod Alloc Obj
Material 12345 -PLant KING-Cust GE-FUG-Prod Alloc Obj
Material 12345 -PLant KING-Cust MACROGUN-Prod Alloc Obj
And this is how it appears in the planing book when you go into DETAILS ALL
You basically enter the Allocation Quantities just as how you enter forecast quantities in DP Book*
 Wk1 | WK2 WK3 WK4 WK5
Alloc Qty |
Material 12345 |
Plant KING |
Cust WALKART 50 |
Cust GE-FUG 30 |
Cust MACROGUN 20 |
Incoming Order Qty |
Material 12345 |
Plant KING |
Cust WALKART 50|
Cust GE-FUG 25 |
Cust MACROGUN 20 |
50 : Say the Cust WALKART has ordered 250 for this week, however only the allocated quantity -50 will be confirmed for him and the remaining 200 qty will be confirme at a later week when he is given the allocated amount.
25 :Similarily say this customer GE-FUG has ordered 20 qty. So his remaining allocation is basically 5 which cannot be used by any other customer.
20 : Say this customer MACROGUN has ordered exactly the allocated amount of 20. So his remaining allocation will be 0.
This is the basic idea of how Allocation Concept is used in GATP.
Ofcourse you can add the other functionalities like
Rules Based ATP(LOcation Substitution, Product Substitution)
Multi ATP( BOM-COmponents)
Check Aginst Forecast
Etc Etc
Like any other module of SAP- this module has much to offer which unfortunately I cannot list here**
GOOD LUCK and let me know If you need additional help.
Regards
KUMAR AYYAGARI
Message was edited by:
 Kumar P Ayyagari

Disaggregation of Key figure not in proportion at monthly bucket

Dear Expert,
Please find the below case.
Here Key figure 2 is disaggregated based on Key figure 1 (Calculation Type P) also we maintained Time based disaggregation K.
The issue is - if you check total, it is 13 for both key figures as shown in below screen shot.
But region wise (Detail level) if you checked, it is not in 1:1 proportion and it is causing problem for us.
For example Region 2 having value in KF1 as 2 for Week 11.2015 but after disaggregation it got nothing on KF2.
(The reason is Key figure 2 is having value in week 12 and week 13 and nothing in Week 11)
We tried 2 different approach to get 1:1 proportion in Monthly bucket, but it could solve our problem.
Approach 1-After Key figure2 calculated in Weekly bucket, Reset Key figure 2 at total level in Monthly data View and enter the Total of Key figure 2 at Total level in Monthly bucket.Check the result at detailed level.
But in this case it is calculated for week 10, 11, 12 and 13 as 0, 9, 3, 1. (We want Key figure2 as per original calculation i.e it should be 12 and 1 in week 12 and 13 respectively)
Approach2 -
Approach 2 - Add another New Key figure as Key figure 1 Total- which sum the Key figure1 at detailed unit at Month level and then disaggregation of Key figure2 based on this new KF.
Its working for this scenario but different scenario is not working.
For example- here region 3 and 4 affected.
If disaggregation at Month level is corrected, our issue will be resolve.
Waiting for your feed back.
Thank you
Sachin

Hi,
In Planning Area u2013 Key Figure settings, did you try to use u2018N - No disaggregation in timeu2019 for KF2 key figure ?
This will mean that copying will occur in technical periods of the storage bucket profile and not the way it happens now.
Other option:
Now, you storage bucket profile and also the planning bucket proifile are in Days/Weeks/ .Months
Is it necessary for your user to view data in daily buckets ? Can the user view the data in weekly buckets only (and not in daily buckets) ?
Your planning bucket profile can be in Weeks/..Months .
This way your displayed data will be in weekly buckets.
Regards
Datta

Key figure incorrect disaggregation

Hi All,
Please help me in resolving the issue regarding incorrect key figure disaggregation in the planning book. The key figure value which is disaggregated is based on another keyfigure. The calculation type and disaggregation type set up in the planning area for these two key figures are
 Calculation type Based on KF Time based disaggregation
KF1 S P
KF2 P KF1 P
I am providing an example as below.
You select one SKU (50058801807) in the planning book. These three characteristic value combinations exist for the SKU: CVC1, CVC2, and CVC3. You enter 100 pieces as the actual impact of promotional events quantity (KF2) in the month of May (month five).
You save the data. The system first performs time-based disaggregation. In other words, it first disaggregates the 100 pieces of the SKU level into technical periods based on the number of workdays in each period. In this example, factory calendar has been defined in the planning area, so there are five workdays in each week. The month of May has 22 workdays (one day public holiday). No proportional factors exist.The calculation is as follows:
Level1: The system collects the rounding differences from all the periods.
Technical Number of DaysCalculation Result Brought Forward
Period in TP
5/1-5 5 100 * 5/22 = 22.727 23 -0.273
5/8-12 5 100 * 5/22= 22.727 23 -0.273
5/15-19 5 100 * 5/22 = 22.727 23 -0.273
5/22-26 5 100 * 5/22 = 22.727 23 -0.273
5/29-31 2 100 * 2/22 = 9.090 9 0.090
Total: 101 1
Level 2: Distribution of the difference -1
Technical Number of Days Calculation Result Brought Forward
Period in TP
5/1-5 5 -1 * 5/22 = -0.227 0 -0.227
5/8-12 5 -1 * 5/22 = -0.227 0 -0.454
5/15-19 5 -1 * 5/22 = -0.227 0 -0.681
5/22-26 5 -1 * 5/22 = -0.227 0 -0.908
5/29-31 2 -1 * 2/22 = -0.090 -1 0
Total: -1 0
The result:
Technical Result
Period
5/1-5 23
5/8-12 23
5/15-19 23
5/22-26 23
5/29-31 8
Total: 100
As an example, the 23 pieces, which are to be distributed in several technical periods (5/1-5, 5/8-12, 5/15-19, 5/22-26 and 5/29-31), are calculated below for the three characteristic value combinations:
CVC Calculation Result Remainder
CVC1 23 * 1/3 = 7.666 8 -0.334
CVC2 23 * 1/3 = 7.666 8 -0.334
CVC3 23 * 1/3 = 7.666 8 -0.334
Total: 24 -1.002
The remainder -1.002 is distributed to the three characteristic value combinations:
CVC Calculation Result Remainder
CVC1 -1.002 * 1/3 = -0.334 0 -0.334
CVC2 -1.002 * 1/3 = -0.334 0 -0.668
CVC3 -1.002 * 1/3 = -0.334 -1 0
Total: -1
The following table shows which of the seven characteristic combinations the system assigns how many pieces:
CVC Result
CVC1 8
CVC2 8
CVC3 7
Total: 23
Calculation for 8 pieces:
CVC Calculation Result Remainder
CVC1 8 * 1/3 = 2.666 3 -0.333
CVC2 8 * 1/3 = 2.666 3 -0.333
CVC3 8 * 1/3 = 2.666 3 -0.333
Total: 9 -0.999
The remainder 0.994 is distributed to the five characteristic value combinations:
CVC Calculation Result Remainder
CVC1 0.999 * 1/3 = -0.333 0 -0.333
CVC2 0.999 * 1/3 = -0.333 0 -0.666
CVC3 0.999 * 1/3 = -0.333 -1
Total: -1
The following table shows which of the seven characteristic combinations the system assigns how many pieces:
CVC Result
CVC1 3
CVC2 3
CVC3 2
Total: 8
This means that each characteristic combination is assigned the relevant proportion from the table for each technical period for which the system can distribute 8 pieces. In the period 5/29-31, eight pieces are distributed to the three characteristic combinations.
The results are displayed schematically in the following figure:
Technical periods in which data is saved:
5/1-5 5/8-12 5/15-19 5/22-26 5/29-31
23 23 23 23 8
Disaggregation in technical periods at SKU level:
For value 23
 23
8 8 7
For value 8
 8
3 3 2
Disaggregation in technical periods at detailed level:
Now according to the above calculation,
CVC 1 gets value 35
CVC 2 gets value -35
CVC 3 gets value-30
The planning book values are:
CVC 1 33.623
CVC 2 -50.276
CVC 3 -16.101
Please note: 3 decimal places set for the key figure in the planning area, but this calculation is based on one decimal place.
Even then the differences should not be this high.
Please provide me some examples on disaggregation of kf based on another kf with no proportional factors maintained.
Thank you in advance for your help and support.
Kind Regards,

Hi
Your calculations seem to be in line with the <a href="http://help.sap.com/saphelp_scm50/helpdata/en/26/53f1f3758211d398490000e8a49608/content.htm">SAP help for rounding and disaggregation</a>
If there is no preexisting proportions in both KF1 and KF2 what you expected should be the values comng up. It is possible that there is any other proportions that are existing in the KF1 that dont appear in your selections but are causing this to aggregate in KF2. (if you have a remote cube you can LISTCUBE whats in the planning area and check all the CVCs)
it would be also a good idea to check both KF in a details( all) mode for the CVCs and also have the time buckets in technical periods and see if that matches your calculations
to see the planning book in technical periods, from the planning book ... go to the period structure settings and choose 9ASTORAGE. (you cant use this permanently in the planing books though)

BPC 7.5 NW -- Allocation Issue -- Good Illustration

Hi all,
I've been struggling with a fundamental issue with the way the Allocation process works on the Netweaver platform. But, this might be an easy way to illustrate the problem.
This data is typical representative what has been loaded to a test area for 2007.APR:
ACCOUNTGL     CO_CODE      FUNC_AREA              COSTCENTER      2007.APR
A54442000     N001                     S413201                CC01000                           -
A54442000     N001                     S413264                     CC01004                  97,436
A54442000     N001                     S413264                     CC01027                    9,588
A54443000     N001                     S413266                     CC01004                         33
The basic goal of the allocation is to distribute in some of those GL Accounts and Costcenters to other company codes/subsidiaries. These are mostly general-purpose services accounts, such as legal services that are provided by the parent, etc.
The problem is that after the allocation is run, the amounts in ACCOUNTGL, COSTCENTER, and FUNC_AREA are spread to essentially all base-level members and not just the ones that had data initially, this (A.) generates so many records as to almost render allocations unusable, and (B.) duplicates a lot of data. Here's a sample of after the allocation is run:
                   CC01000 CC01004 CC01027
S101011             6,256.31 6,256.31      6,256.31
S101021          6,256.31 6,256.31      6,256.31
S101031          6,256.31      6,256.31      6,256.31
S104001          6,256.31      6,256.31      6,256.31
As you can see above, all the cost centers got an allocation of about 6% of the total (which is the correct value), but it should have been in proportion to what they had originally. Meanwhile the FUNC_AREA/S-Accounts all got this value written to them as well.
Beyond the How-To Guides, does anyone have any specific pointers on how the allocation engine works on the NW platform? It seems to behave a bit differently than on Microsoft.
Thanks,
Garrett

Hi Garrett,
It would be helpful if you could provide the allocation script that resulted in this data. Then maybe we can recommend changes that will help you or better understand what you are attempting. I realize you have shared your scripts in other threads, but it would be best to get the script and the example data together in one place.
It seems clear that you don't want the value duplicated across the accounts, but you can probably control that in your allocation script. Further, it should be possible to allocated based on existing data by using a USING/TOTAL factor, but Gersh has indicated that there might be a problem here, and possibly a BPC bug.
Regarding differences between NW and MS allocations, yes, the statement behaves differently in the two systems. The biggest difference is that the NW version allocation functionality only works for disaggregation, not for driver-based allocations. What that means is that in the NW version, if you have multiple members in the WHAT= section, the values in these members will be added up and allocated out to all the members in the WHERE= section. I believe this differs from the behavior in the MS version which would run the allocation separately if lists of members were provided in the WHAT and WHERE sections.
If you want to do a driver-based model in the NW version, you will need to use MDX or WHEN/IS/*REC statements, but in this case it seems you are trying to distribute overhead costs to subsidiaries, which is a disaggregation activity and should be possible using NW version allocations.
Ethan

APO DP: Disaggregation to product&plant level from higher levels.

Hi.
We do demand planning on groups of products and for country/region in general, we have around 48.000 CVC's in our current setup. It works very well.
A new situation has arisen where we need to have the forecast split down to product and plant level.
As is we simply don't have the information at this level of granularity.
I don't see how we can add for instance product to our setup, we have around 20.000 products so the number of CVC's in DP would become massive if we did this.
I was thinking that perhaps something could be done by exporting the relevant key figures to a new DP setup with fewer characteristics (to keep the number of CVC's down) via some infocubes, perhaps some disaggregation could be done via some tables and the BW update rules. This still leaves the issue of how to get the figures properly disaggregated to plant and product though.
Does anyone have experiences on how to get the figures split to lower levels from DP when you're planning on a higher level?

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

Custom Disaggregation for SNP

Hi,
We are doing Aggregated Planning in SNP.
We are facing some issues in disaggregation of Header Products to Sub products production orders.
Letu2019s say we have 3 sub products and a header product.
Forecast is aggregated to header level and header product production order is created which is covering x days forecast of Header product.
When we disaggregate Header product planned order to Sub products and if Sub product 3 doesnu2019t have any forecast for x days (it has forecast after x days);it should not create planned order of sub product 3.
Only Sub product 1 and 2u2019s planned orders to be created.
I would like to know how can perform custom disaggregation in SNP?
Is there any BADI?
Thanks and Regards,
Vipul Shah

Hi Vipul,
Did you try to use /SAPAPO/CL_EX_SDP_DISAGG ?
Check details on note 1352836.
Regards,
Michel Bohn

Getting struggle on BAPI_IPAK_START, Plz help SCM issue

HI Folks,
I have a requirement: Uploading .exl file contains Quaterly buckets (Example Quater 2007001) to info cube then same copy from info cube to live cache.
after processing i am able to see the data in correct data in info cube in weekly (13 weeks data) and able to see live cache in Weekly and also able to see quaterly (multiply by 13).
Requirement: In Live cache should be show the data as quaterly (exp: 13), in weekly data should show devide by 13 (13/13) value '1' same in all 13 weekly,
issue: when i take data in quaterly in .xls file as quaterly buckets (Example 2007001), after processing i am able to see the data in infocube as quarterly and live cache, but when i am checking WEEKLY in live cache it is not deviding by 13.
it is showing in the first week the same data as quaterly and also the remaining 12 weeks showing empty.
before this function module FM BAPI_IPAK_START i am spliting the quaterly data by 13 and doing the same do 13 times.
in my programe debugging passing
once process the FM FM BAPI_IPAK_START passing info package i am able to see updated info cube data, here is the problem. if i get data as weekly here then the same should copy from cube to live cache.
Could you please suggest on this. where can i see.
Thanks in advance.

Hi
How are you copying the data from infocube to Planning area?? Or are you using some other function module?
Whats the time bucket profile you are using to copy?
In the planning area design details check what you have set up as time disaggregation for the KF. If its P you should get a equal split.

SNP disaggregation - not working

we are working on aggregation and disaggregation of SNP demand based on hierarchies for location product,
we are facing issue while disaggregating the quantity on our Aggregated product generated by heuristics back to the main sub products.
The disaggregated quantity on sub product ( Aggregated distribution receipt (planned) key figure)
is coming in only for 1 product of the hierarchy. we also set the transportation lanes and have run the LLC.
It is not disaggreagting based on demand or either by quotas

Hello Umesh
we have maintained all the items mentioned in your reply. ( copy of standard planning book , LLC run no errors,assigned hierarchy to planning area, orders are at header product before disaggregation, we also are trying based on Quotas at sub products in hierarchy)
orders generated by heuristic at header material for the location does not get disaggregated to the sub products. Same is for all other locations.
we have location hierarchy based on regions (east, west ,north,south) and a common set of products.
we are using disaggregation method based on Demand

For this issue Is there any solution in Standard solution or any Developmet

Hello Friends,
I have one issue that is
When ever the forecast is release from DP to PPDS (Monthly - days) of a material quantities should be bucketed into Monthly bucketed quantities and split into day level ( e.g: Product1 1st week 1000ton, 3rd week 2000ton , when it releases system aggregates the quantities and depending upon the product profile and setup time it shold give me result as product1 -3000ton in day 1 and product2 --2000ton on day 2 ...so on) .Standard SAP APO release of Monthly forecast quantity to daily bucket is divided into 30 or 31 days and split the quantities equally( e.g: Product1 1st week 1000ton, 3rd week 2000ton , when it releases system aggregates the quantities and divides in 30 days in a month and split the quantities equally).
For this issue Is there any solution in Standard SAP or any Developmet is required in APO-DP.
Pl Through me some lights on me .
Regards,
sivaram76.

Hi
If you are using u201C/SAPAPO/MC90 for releasing the FCST , I think you can define different Planning Buckets Profiles according your requirement for example according your needs for disaggregation of your FCST. A planning buckets profile contains the periodicities or a subset of the periodicities that you defined in the storage buckets profile.
Once you maintain the planning bucket profile you can put it in tab Daily Buckets Profile while releasing the FCST.
It will be nice if you please cross check it its meet you requirement.
Thanks
Amol

Disaggregation issue

Similar Messages

Maybe you are looking for