Iam loading historical data from my infocube to APO planning area...
MY Planning will be done in apo for weekly based..
for thatmy client has configuired Fisc VArnt which is
specific for 48 periods but not 52 periods...
My clinet will be planning in week which will will be like it starts from 07.01.2010,
but for testing purpose we are taking thisfrom a flat file andloaded into the infocube..
and created gen export datasource into scmapo system and loaded into cune from that cube iam feeding itto planning area..
when I execute the transaction /n/sapapo/tscube tha data copied was successful,
but the keyfigure amnt when I saw in the planning area Transaction /n.sapapo.sdp94which will be distributed across the week.
lets say my keyfigure values is 100 in the infocube for the jan month and week 1
and the value which i CAN SEE IN THE PLANNING AREA IS week1 25 week 2 25 week 3 25 and week 4 25
which will be 100 total for amonth,
but it should not be like that 100 should go into a particular week and should display 100 for that particular week..
I have calmonth calday, fiscper(posting period) which we have maintained in ob29 as 48 periods
when i derived calweek in the transformation iam getting 48 weeks but
when i try to load it to planning area iAM GETTING AN ERROR LIKECOMBINATION IS INCONSISTENT..with the calmonth
CODE WHICH i HAVE DERIVED CALWEEK FROM CALDAY:
DATA: lv_year(4) TYPE c,
lv_month(2) TYPE c,
lv_day(2) TYPE c,
lv_result(6) TYPE c,
v_poper TYPE poper.
lv_year = SOURCE_FIELDS-calday+0(4).
lv_month = SOURCE_FIELDS-calday+4(2).
lv_day = SOURCE_FIELDS-calday+6(2).
SELECT SINGLE poper FROM t009b INTO v_poper WHERE bumon = lv_month
AND butag = lv_day.
IF sy-subrc = 0.
CONCATENATE lv_year v_poper+1(2) INTO lv_result.
RESULT = lv_result.
gURUS CAN ANY BODY THROW SOME LIGHT ON THIS.. iWILL BE HIGHLY OBLIGED
when i load the data from infocube to planning arae using /SAPAPO/TSCCUBE, the copy was succeeful.. But the issue is the keyfigure value is dis aggregating..
For ex If my sales hostory for week 1 001.2010 and for calmonth 01.2010 is 100, but it is disaggegating the values for whole month 4 weeks as 25,25,25,25 but it needs to b written as 100 for week 1.rather it should be aggregated on the highlevel as 100 for week 1.
Do I need to check any Charecterstics combination but all are consistent....
Even the periodicities in the planning area and infocube are consistent , since i am able to copy in to planning area..
I dont have calweek in my infocube i have derived calweek with logic provided in my earlier thread, but as of now iam going with calyear and calmonth, fisper3 (postig period), since 48 posting periods are maintained in the 0b29 or t009b tables.
whether I need to implement any oss notes for this, If I include calweek and calmonth and try to copy in to planning area Iam getting an error periodicities are not matching SAP Note 1408753 - /sapapo/tscube wrong error message
The forecast data is uploaded at a month level (100) because of which when you look at the weekly view, you see disaggregation of data(25,25,25,25) which is the standard system behavior.
You need to upload the data from the infocube at a week level to achieve your desired requirement.
The same fiscal year variant with 48 posting periods will need to be specified in the PLANNING OBJECT STRUCTURE(STOR BKT Profile) and Planning Book-data View(Time Bkt Profile)
In the BW infoprovider, you will probably need to use 0FISCPER3(Pls check with the SAP BW/BI forum)