Query for Future period on a non cumulative cube

Hi Colleagues,
I have a non cumulative cube. It has data till June,2006. When I query on the cube to report the balance with period as "July,2006" it doesnot return anything. What I expected is that it would show me the balance value as of June,2006 which is the last period for which there is data.
Am I missing anything ?
Regards,
priyadarshi

If you filter by jul06 and there is no data in cube, no matches with selection happens. You need to select any data to apply calculation of balance, try to select a range of months, with an offset.
Maybe if you put the month in free characteristics instead in filter section ir worked.

Similar Messages

Urgent : Query on Non cumulative cube

Dear BI Experts,
I have a non cumulative cube to help me report Stock Balance. It has stock entries from Jan till June,2006. When I query on the cube to report the balance as of Current Period (July,2006) it doesnot return anything. What I expected is that it would show me current stock balance (from Jan till June,2006) though my selection date is in July where there is new stock update done in July.
I tried compression on the cubes as well but didnot change the result.
Can anybody help.
Kind regards,
priyadarshi

Hi Riccardo,
Thanks for your very useful answer. I have "Company" , "SetOfBooks" , "Material" & "0CALDAY" in my validity table. Here For every combination I see a record in the validity table with "Fixed To Time" set with the last transaction dates for the combination. But I would like to preset the "Fixed To Time" for each record to some value like "31-12-9999" .
Should this be possible & how ?
Regards,
priyadarshi

Validity slice is not correct for non-cumulative cube

Hello Expert,
There are two non-cumulative cube, say cube1 and cube2. Cube2 has only one more dimension of PLANT than Cube1.
Cube2 is copied from cube1 and change the char of validity.
Cube1 & cube2 use the same fill data source. That is, first load with opening balance and second with delta.
char of validity for cube1: calendar day & material
char of validity for cube2: calendar day & plant.
The query based on cube1 works well. To say cube2, the validity slice(in TXN RSDV or TBL /BIC/TCUBE2) is not correct. There is only one record which contains BLANK plant.
There are plants in F table.
I tried the following steps to recovery the validity slice, however, it made no sense.
1) PGM RSDG_CUBE_VALT_MODIFY to rebuild the validity slice structure
2) FM RSDV_VALID_RECREATE with I_REBUILD_FROM_FACT = 'X' to create validity slice from fact table.
Would you please suggest?
Thanks
XY

Hi XY,
For sure, running the RSDV_VALID_RECREATE function module in SE37 will recreate the validity table. And you can use the parameter "X" in the parameter I_REBUILD_FROM_FACT if the entire fact table should be read.
Also, to change the validity slice manually in tcode RSDV you should:
- overwrite the column 'To mode' with a 'F', which mean Fixed
- & then the 'Fixed to time' with your new value.
There is a program which allows you to modify it: Program > RSDG_CUBE_VALT_MODIFY
At
Nadja Xavier

Posting run request for future period; check your entry message no.AA697

Hello Guru's,
I have below error while Depreciation run in T.Code AFAB
"Posting run requested for future period; check your entry" message no.AA697
Request help
thanks in advance
Regards
Chintamani

Hello Chintamani,
Why you want to post the depreciation for future period?
Is the future fiscal year in open or is the posting period open for that? If no, please open that period with AJRW T code if you want to post the depreciation for future period but it is not recommendable.
Check the posting period once again because the given posting period belongs to future year? So please do re-chk and give correct period according to your current fiscal year.
You can get your fiscal year details and assignment of fiscal year variant to the co,code details in OB29 and OB37 t codes respectfully.
Check the OSS Note: 1150235 - Preventing depreciation posting run for future
I hope it helps else revert us with your query.
Thanks & Regards,
Lakshmi S

Can't Run AFAB - Posting run requested for future period

Hi,
While taking depreciation run for company code in AFAB system is generating the error message "Posting run for future period requested (check entry)" SAP error AA697
Diagnosis
There was a check of your entries in the company code and posting period fields for the current system date. The result of this check is that you requested a posting run for company code xxxx for a future fiscal period.
Please help me, cause I must close the period.
Thanks

Hi
Check Table TABA, whats your last posted period for depreciation
If you are executing depreciation for last period + 1, then this error is not justified
If you are doing it for last period + 2, then its justified
Br, Ajay M

Depreciation error - Unplanned posting run allow for future period

Dear ,
Need urgent advice for depreciation error happen in our production system.
FYI, our fiscal year variant 2013 = Feb 2012 - Jan 2013 ( We are now at month-end close for Pr 1 2013 ).And fiscal year close 2012 AJAB and Carry forward ARJW have successfully run for new FY 2013.
In short, in our asset accounting user was accidentally run unplannned depreciation for future period 12/2013 of one particular asset, while we are now in Pr 1/2013. And, Pr12/2013 is open for asset posting.However, no FI posting posted into the system.
Just a curiosity as to why system allow user to run unplanned depreciation for future posting without giving an error message to follow the posting cycle.
The impact/error of above unplanned depreciation run:
User is not allowed to execute AFAB depreciation run for Pr 1/2013. Even worst, in the AFAB program shows from Pr 1/2013 - 12/2013 is already posted when we do depreciation test run. We can't perform any planned,repeat,restart for Pr1/2013.
Because of only one asset had accidentally run for Pr12/2013, all of our asset (96,773 asset) cannot proceed with depreciation run for Pr 1/2013 in the new fiscal year.
This is high priority as it will impact the entire depreciation run for 12 month of our company.
Your early reply on this issue is greatly appreciated.
Thank you,
Regards,
Latifah

Thank you for the response.
FYI, the asset posting actually has been executed but no document was posted as there's no value.
I've check the 2 tables below:
ANLC - No numbers of run for any period in FY2013
ANLP - No depreciation run was posted in FY13 (all periods).
Is there anyway for us to do normal planned run for Pr 1/2013? As i understand SAP has no function to perform reversal depreciation run in AFAB. How
With regard to the posting period 12/2013 that is open for user, I already highlighted this to the respective custodian.
Thanks.

Work around for including Non cumulative cube in an infoset.

Hi Experts,
I have 4 non cumulative infocube in my production, for another reporting purpose I have to use those non-cumulative cubes combining another DSO in an infoset, but the infoset is not allowing me to include non cumulative infocube in it.
The non-cumulative infocube contains 2 non cumulative keyfigures, those keyfigures are needed for my new reporting, to get the infoset logic(inner join) is there any other possible way to get the data ?
Please let me know. your valuable input will be appreciated. Thanks in Advance.

Hi Kalpana,
Try with multiprovider.
Otherway round could be creating DSO and creating transformation from DSO as well as non-cumulative infocubes (full update) and report on newly created DSO.
Hope that helps.
Regards
Mr Kapadia
*Assigning points is the way to say thanks*

Posting run for future period requested (check entry)

Hi,
While taking depreciation run for company code in AFAB system is generating the error message "Posting run for future period requested (check entry)" SAP error AA697
I checked in OB52 postings periods are open for 2009(all periods)
SAP note 1150235 (all corrections) and 1153718 are completely implemented.
Still the problem is not resolved.
Regards,
Sankar

Hi Sankar,
I would like to refer you to the already implemented note 1153718 which states :
After you implement the changes, the system issues error message AA 697
"Posting run for future period requested (check entry)" immediately when
you use a fiscal year that is in the future. In principle, you can
customize this message. However, in this case, no settings are taken
into account; the system always issues an error message.
Regards Bernhard

Posting run for future period requested

Dear Team,
While taking depreciation run for company code in AFAB system is generating the error message "Posting run for future period requested (check entry)" SAP error AA697
please help to reslove the issue.
Regards,
MAhendra

Hi,
look into the Threads,
Can't Run AFAB - Posting run requested for future period
Regards
Andi

Depreciation for future period

Hi Guru's,
Could anyone tell me how we can get dep report for future period is there any standard report in sap or what is the option.
Thanks
Ravi

Hi Ravi,
You can use the below Standard Report Provided by SAP for Depreciation Simulation for future period.
S_ALR_87012936 - Depreciation on Capitalized Assets (Depreciation Simulation)
While executing the report specify the future report date to view the deprecaition amount of future periods.
Hope the above helps.
Regards
Nitin

Time Card entry for future period

Hi ,
We want to enter time cards for future period ,like now we're in jun and we want to enter time cards till sep 2012 but the self service screen allowing me to enter till aug 2012 only. Can any one explain me what could be the reason. anything we need to enable for this? please advise. Thanks
Regs
RG

Yes it is possible , but it is not advisable in production system.
Open ur time schema using PE01 and comment the line
ACTIO TD10 End if daily WS still active
Then the sys will allow u to run time eval for future period

Compress non-cumulative cube

Hi Gurus! I'm working on a retail project. I've created an infocube based on 0RT_C36 to keep the stock movements. It is a non-cumulative cube.
After the load of the initialization data (2lis_03_bx) the compression with the option "no marker update" unchecked runs fine. The process compress about 300.000 records in a few minutes.
But after the load of historical movements, the initialization of 2lis_03_bf, the compression with the option "no marker update" checked runs for more than 10 hours. There are 400.000 records loaded in the fact table (F table). I've checked in ST22, ST21 and no errors or dumps appear. In SM50 the process was running and the number of inserted records was 250.000. After that the basis gay kill the compression...
Is it normal? Is there anything I can check to speed up the process?
Thanks!

Hi Federico,
This a common problem.
You can find also another message in this Forum section with the same problem.
You need to restrict the number of the request that you are going to compress for every job. Try also to enlarge TableSpace, in particular the temporary TableSpace, that you can subsequently reduce.
Consider that any other job, like query from user or other uploads, reduce the speedof the compression.
Ciao.
Riccardo.

Problems with Non-cumulative Cube

Dear All,
I have a cube with non-cumulative key figures. An DSO supply data for that cube.
The query on that cube will gets wrong results sometimes. But after removing all the data from that cube and uploading again from the DSO, the query presents the right result.
Is there anybody knows why and how to fix it?
Thanks.
Bolun

Hi
Non-cumulative Cubes to be defined correctly with Inflow and Outflow because it depends on Which option you choose depends on how you want to evaluate the non-cumulative key figure, and also the Marker Update you are dealing with.
The key figures for non-cumulative value change or for inflows and outflows are normal cumulative key figures that have u2018summationu2019 both as aggregation and exception aggregation. Generally, Non-cumulative key figures always have summation as standard aggregation.
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/frameset.htm
Hope it helps and clear

Can I use return table in non-cumulative cubes upd rules?

hi,
Is it possible to use return table in non-cumulative cubes upd rules?
What I mean is:
In non-cumulative cubes I need to use Automatic Time Conversion for time chars and when I use return table I have to map fields from comm structure to return table.
I am designing stock cube (with granularity on storage bin and quant level) where material movement data is took from Transfer Order docs. Data for source and target storage bin are in one document item, so I have to split each record.
Regadrs,
Andrzej
ps. Maybe somebody has some technical documentation on Automatic Time Conversion?

Hello Andrez,
May be this code will be useful for you.
*data decleration
data: num type i,
      num1(2) type c,
*variable for fiscper
      lv_fiscper type RSFISCPER,
*variable for the calendar month
      lv_calmonth type RSCALMONTH,
*variable for the period
      lv_period type T009B-POPER,
*variable for the fiscal year
      lv_year type T009B-BDATJ,
*variable to find out the calendar quarter
      lv_month TYPE RSCALMONTH,
      lv_calquarter type RSFO_CALQUARTER.
*ICUBE_VALUES contain data for cube.Put these value into RESULT_TABLE
RESULT_TABLE = ICUBE_VALUES.
*add 12 times entry into result_table for 12 months
do 12 times.
append RESULT_TABLE.
enddo.
*processing for the split the value into 12 periods
loop at RESULT_TABLE.
num = num + 1.
num1 = num.
*divide the value by 12 for each month
RESULT_TABLE-/BIC/ISMPLNRV = COMM_STRUCTURE-/BIC/ISMPLNRV / 12.
RESULT_TABLE-CRM_CURREN = COMM_STRUCTURE-CRM_CURREN.
case strlen( num1 ).
WHEN 1.
concatenate RESULT_TABLE-fiscyear '00' num1 into lv_fiscper.
RESULT_TABLE-fiscper = lv_fiscper.
WHEN 2.
concatenate RESULT_TABLE-fiscyear '0' num1 into lv_fiscper.
RESULT_TABLE-fiscper = lv_fiscper.
endcase.
lv_period = lv_fiscper+4(3).
lv_year = lv_fiscper(4).
*find out the calendar month from the period and year
CALL METHOD CL_RSAR_FUNCTION=>FISCPER_CALMONTH
EXPORTING
    I_FISCPER = lv_PERIOD
    I_FISCVRNT = 'Z9'
    I_YEAR     = LV_YEAR
   I_CASE     = 0
IMPORTING
    E_CALMONTH = lv_calmonth
RESULT_TABLE-CALMONTH = lv_calmonth.
*find out the calendar quarter from the fiscper
concatenate lv_fiscper0(4) lv_fiscper5(2) into lv_month.
*find out the calendar quarter
if not lv_month is initial.
    CALL METHOD CL_RSAR_FUNCTION=>MONTH_QUARTER
      EXPORTING
        I_MONTH   = lv_month
      IMPORTING
        E_QUARTER = lv_calquarter.
    if sy-subrc <> 0.
      lv_calquarter = '00000'.
    endif.
else.
    lv_calquarter = '00000'.
endif.
RESULT_TABLE-CALQUARTER = lv_calquarter.
modify RESULT_TABLE.
endloop.
Regards
Gopal

More than Non-cumulative cubes in one MultiProvider

Hi There,
I have got two non cumulative cubes and want to build a MultiProvider on them.
Got information at couple of places on help.sap.com at one place it says MultiProvider can have more than one non-cumulative cubes at other place it says it can't. What is the right suggestion?
Thanks
Vikash

Hi,
From the performance perspective you should not use more than one Non Cumulative Infocube in a Multi Provider. If you user more than one the query will not execute parallel and execute in sequential which leads to delay in query run time.
This is a recommendation from SAP not to use morethan one Non Cumulative Cubes in a MP.
Cheers

Query for Future period on a non cumulative cube

Similar Messages

Maybe you are looking for