YTD or Periodic application

Hi all,
I must create a new application and I should choose whether to set it as Periodic or YTD.
Which one should you suggest to use? Is it only a matter of reporting or there might be other things to consider, such as performances of the db and so on? What are the main benefits with the different solutions?
Thanks a lot for your help
Francesco Gavarini

In a YTD app, YTD is the base member and Periodic is calculated. In a Periodic app, Periodic is the base member and YTD is calculated.
Think about how your users will enter data into this application and how data will be loaded through automated processes. Will users enter monthly or quarter balances or do they enter Year-To-Date balances? If they enter monthly balances and send those on an input schedule, then make your app a periodic app. If they enter YTD balances, then make it a YTD app. Keep in mind you can have a YTD app and a Periodic app in the same Appset, depending on what your requirements are.
Also, what is your logic going to run calculations on? Is it going to run calcs on YTD amounts or Periodic amounts?
Greg
Edited by: Greg Anderson on Jul 30, 2010 11:24 AM

Similar Messages

Custom formula YTD for PERIODIC Application - BPC 7.5 NW

Dear all,
The customer has 2 time hierarchies, fiscal year and calendar year. He would like to change the measures formulas to fix their fiscal year specification, their fiscal year begins in April instead of January. Some entities of the customer will input data based on fiscal year and someone based on calendar year.
Their application is a PERIODIC application. I cannot use the how to guide 'How to Create Customer measure formulas for Fiscal Periodic, QTD and YTD' because it's only for YTD application.
Can someone help me to understand how to modify the YTD formula for the entities that inputs based on the PARENTH2 (fiscal year hierarchy), please?
I will send you the code delivered from SAP for YTD measure formula for PERIODIC Application
MEMBER [MEASURES].[YTD] AS 'IIF([%KFSPL%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC",SUM(PERIODSTODATE([%PERIODS%].[LEVEL00], [%PERIODS%].CURRENTMEMBER),-[MEASURES].[/CPMB/SDATA]),IIF([%KFSPL%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="EXP",SUM(PERIODSTODATE([%PERIODS%].[LEVEL00], [%PERIODS%].CURRENTMEMBER),[MEASURES].[/CPMB/SDATA]),IIF([%KFSPL%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="AST",([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])),IIF([%KFSPL%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="LEQ",-([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])),-[MEASURES].[/CPMB/SDATA]))))';SOLVE_ORDER=3
Thanks
Regards
Rosa Alfonso

Hi Chandra,
Few things that you can check -
1. What is your fiscal canlendar period? April to March or Jan to Dec?
2. In Time Dimension, MONTHNUM whould be '1' for the month from which the fiscal year starts
3. In Time Dimension, ISBEGINING whould be '1' for the month from which the fiscal year starts
Please do these changes, process the dimension, refresh the dimension members in BPC-Excel and then see if you get proper values.
Hope this helps.
If problem still persists, please copy-paste the YTD formula from backend ... will check and let you know. Also what is the version, SP and patch level that you are working on?
Regards,
Rashmi

BPC Consolidation application - YTD or periodic

Hi,
YTD or Periodic - For legal consolidation (IFRS, USGAAP), what would be the best option for a customer with ECC, BW and BPC landscape. Are there any major issues in mapping specific consolidation process in YTD application (like reconciliation with ECC data ect).

Hello Lokesh,
The IFRS focuses mainly on the reporting aspects of financial results of an enterprise. Consolidated or not, for all listed companies, these requirements impose strict norms that need to be adhered to for reporting the financial results. Therefore, if an enterprise has many subsidiaries and the numbers are reported for the group as per the IFRS norms, it still presupposes that ALL the norms have been adhered to.
In respect of Business Objects Planning and Consolidation, SAP has come up with a Starter Kit for IFRS adoption. It is pre-configured with all reports, controls and rules for performing, validating and publishing a statutory consolidation in accordance with IFRS standards. An enterprise may have the desired setting for its Consolidation Definition. One of the settings is choosing a pre-defined variant that allows it to have either Periodic or YTD setting to be selected for a given category, data period and currency. For more information, follow this link:
http://help.sap.com/businessobject/product_guides/bofc10/en/FC10_SK_IFRS_ConfDesc_en.pdf
In my view, for legal consolidation, the consolidated financial information is valid only if it is YTD. The periodic values are needed only for calculating the movements - for Statement of Cash Flows. This aspect is well taken care of in the Consolidation Processing u2013 either Full Processing or Incremental processing.
If you want to reconcile the balances as per ECC, BI as well as BPC, you have to consider only the YTD values.
Hope this gives adequate information for clarifying your doubt.
Chakrapani

Periodic application, conversion on ytd value

Hi all,
I have SAP BPC 7.5.108 MS, I need to do a periodic application,but I would like to do a conversion applied on YTD value.
Do you know if it's possible in the business rules?
I know that it's possible, in the Ytd applciation, to apply the conversion on periodic value, would be very nice to do also the conversion applied on YTD values.
Thanks
Ciao
Chiara

Hi Chiara,
this is not possible by using the standard rules. However you should be able to achieve it by using an additional element in your flow dimension on which you (with a script) calculate the YTD value. Your conversion rule could then convert this amount and write the result onto the original flow.
BR,
Arnold

YTD view in Periodic application

Hi Experts,
I got an answer from SAP Korea, the YTD is only available for quarter in BPC 7.5 NW in periodic application.
IS IT TRUE???
If it is just for BS, sounds OK since usually we get BS quarterly, but for PL, it should support monthly YTD view. Could you please copy and paste the measure(MDX) that BPC 7.5 NW uses?
Regards,
YH Seo

Hi,
May be the message didnt come up properly or was intended for something else. You can definitely view the YTD values for months also. You can see the measures in the SAP Program "UJA_MAINTAIN_MEASURE_FORMULA".
There is a how to guide on SDN - "Create Customer measure formulas for Fiscal Periodic, QTD and YTD"
Hope this helps.

Strange behavior in Periodic application

I have a finance application with YTDINPUT set to u2018Nou2019 used for budgeting.
When I enter figures in one month i.e. February 2009, sales 4000, save the numbers and run a report. A total of -4000 is reported for March 2009.
Looking directly in the SQL fact tables there are no data for March 2009.
When I change my report to show the data source dimension in the Row the figures in March 2009 disappear.
What is wrong? How do I get rid of the figures in March 2009?

Hi Bjorn
Thanks for your quick reply.
To me the tblYTDFormula look wrong. Only YTD uses base level and the formula for Periodic is a lag calculation over time. This tells me that the formulas are to YTD applications.
I have an application set with both YTP and Periodic applications. I have made a full optimize of the application, without any effect on the data.
Currently I am only entering data on P&L accounts.
With basis in your example.
The figures that I see for March only exists on parent level if I look at bas level for account there are no data.
Jesper

YTD and Periodic

Hi Experts,
I have had a request from a client to build a balance sheet. The issue is that they have been using BPC 7.5 on a periodic basis for the finance application. They want a balance sheet to now be built and this has to be at YTD.
Their application parameters is not set to YTD.
Its is possible to build a YTD balance sheet with the application parameters set to periodic.
TIA
HHDJ

Hi there,
Are they currently loading balance sheet data on YTD or Periodic basis?
If they are already loading data to the B/S then you can just set the measure to YTD in instead of Periodic.
However if they want to start loading YTD B/S data into a Periodic application then that cannot be done because the application has been already setup as Periodic.
Could you create another App that's strictly YTD or convert the YTD B/S via an ETL process to make it Periodic?
HTH,
John

YTD or Periodic ? Also the impact of Force Closing parameter

Dear expert,
I have 2 question :
1. YTDINPUT in Application Parameter :
Is there any concern if i put the parameter with Periodic ? For Example : Any function in bpc that cannot run in periodic data, maybe carry foward function?
What is the major consideration when i have to choose the periodic or ytd parameter?
2. In automatic adjustment at the business rules detail.
There is column named Force Closing.
I put the Source Flow is F0440 = ( Closing Balance Type )
I Put Destination Flow is Blank ( From what i'm read, it will write same as the Sorce Flow )
And I put The Force Closing is Check
Is that any problem with that ? Like Double data ?
Thx
Suprapto

Dear Wandi,
Thanks for your answer, but i think i need to be clear with my question:
For case no. 1:
I see in BPC Documentation, the recommended value in YTDInput Paramter is YTD and not periodic.
Why the recommended value is YTD ?
Out of the customer needs, what is the best pratices in bpc to store data in Legal Application , YTD or Periodic ?
Because, BPC comes with great function ( store procedure, business rules, etc ) example : business rules can set up to carry foward the value ,
If the parameter set to periodic, is the function that created in bpc will have to re-script again to make the value carry foward ?
Please see my cases not just only in carry foward case, but the consideration if the periodic is setup then what features in bpc that i have to re-create again manually in script.
For case no 2:
My service patch is 7.0.112
IF my settings is like that ? is it will create a dupplicate value ?
Because the source value is the ending balance, the destination is ending balance and the force closing is check.
From what i'm read in document, the force closing will create value in the ending value. Am I will create dupplicate data if the source value is the ending balance, the destination is ending balance and the force closing is check ?
Thanks for your help.

Exporting YTD and PERIODIC data

Hi all,
I've adjusted a data manager package so that the YTD and PERIODIC measures are automatically selected for export to a flat file. Whenever I want to save the package the script automatically changes and removes either YTD or PERIODIC.
Any idea how I can change the script so that both YTD and PERIODIC measures are exported to a flat file?
Thank you.
DEBUG(ON)
'PROMPT(SELECTINPUT,,,,"%DIMS%")
PROMPT(SELECTINPUT,,,,"ENTITY,TIME,C_CATEGORY")
'PROMPT(MEASURELIST,%MEASURES%,"Please select measures")
'PROMPT(TRANSFORMATION,%TRANSFORMATION%,"Transformation file:",,,Import.xls)
PROMPT(TEXT,%FILE%,"Please enter an output application file",)
'PROMPT(RADIOBUTTON,%ADDITIONINFO%,"Add other information(Appset,Application,User,Time)?",1,{"Yes","No"},{"1","0"})
'PROMPT(TEXT,%TYPE%,"Please enter the Process Chain Type",)
INFO(%DIMVALUE%,E=24)
INFO(%TEMPNO1%,%INCREASENO%)
INFO(%TEMPNO2%,%INCREASENO%)
INFO(%MEASURES%,YTD,PERIODIC)
TASK(/CPMB/APPL_TD_SOURCE,DIMENSIONVALUE,%DIMVALUE%)
TASK(/CPMB/APPL_TD_SOURCE,MEASURES,%MEASURES%)
TASK(/CPMB/APPL_TD_SOURCE,OUTPUTNO,%TEMPNO1%)
TASK(/CPMB/APPL_TD_SOURCE,SELECTION,"%SELECTION%DIMENSION:C_ACCT||DIMENSION:C_DATASRC|INPUT,INPUT_DIFF_ECCS,INPUT_ADJ,INPUT_GW,MJ_MANJE|DIMENSION:FLOW|F_999|DIMENSION:GROUPS|N_GROUP|DIMENSION:INTCO|I_TOTAL|DIMENSION:RPTCURRENCY|LC|")
TASK(/CPMB/EXPORT_TD_CONVERT,INPUTNO,%TEMPNO1%)
TASK(/CPMB/EXPORT_TD_CONVERT,TRANSFORMATIONFILEPATH,\ROOT\WEBFOLDERS\Company\LEGAL\DATAMANAGER\TRANSFORMATIONFILES\SYSTEM FILES\Export.xls)
TASK(/CPMB/EXPORT_TD_CONVERT,SUSER,%USER%)
TASK(/CPMB/EXPORT_TD_CONVERT,SAPPSET,%APPSET%)
TASK(/CPMB/EXPORT_TD_CONVERT,SAPP,%APP%)
TASK(/CPMB/EXPORT_TD_CONVERT,OUTPUTNO,%TEMPNO2%)
TASK(/CPMB/TD_APPL_SERVER_TARGET,INPUTNO,%TEMPNO2%)
TASK(/CPMB/TD_APPL_SERVER_TARGET,FULLFILENAME,/interface/BIP/BPC_export/%FILE%)
TASK(/CPMB/TD_APPL_SERVER_TARGET,ADDITIONALINFO,1)

Sgt. Rock wrote:
Should I just break down and buy server space to exchange complete files?
This the way I do with my co-work production or when work in a team with guys who live out of my country. You can pack/archive the whole project folder into Zip or (Rar - I do that using my PC) which reduces the project folder content globally.
There are quite many "free hosts" in our days so you can manage your work via Email or Skype and use such servers if you can not afford to buy any hosting space. To my opinion it is best to provide the original project when you use same apps, plugins etc. Any tricky export, audio file compression etc will be time consuming for your partner...
!http://img59.imageshack.us/img59/4967/aglogo45.gif!

YTD to PERIODIC

Hi Experts,
IN BPC 7.0 do you thinks its posible to copy a YTD application (ex LegalApp) data to a Periodic application (ex Finance) or vise versa, having the same dimensions??
Can BPC'S Allocation engine do it??
Thanks,
Benniejay

I don't think there is workaround for converting one measure to another measure. You need to think about strategy to allocate your YTD to time periods. I think it is not too hard. But I do not have financial knowledge.
It is right that Periodic and YTD are calculating by OLAP, measure formula. But you still can use stored procedure to get YTD value. In very simple definition, YTD is latest value. So, for example, if you want to split 2008 value, you can query against to FACT table to get 2008.DEC value and split it to 12 months. And insert them into 2008.JAN to 2008.DEC of new application's FACT table. The you can get same value as Periodic.
I am not 100% clear about your question actually. Do you want to have new application that uses periodic and has same value as original application's YTD?

Retained earnings in Periodic application

Hi
I have a periodic application where I would like to post retained earnings on the balance sheet.
Below is the part of my default logic form my YTD application.
*WHEN ACCOUNTDIM.GROUP2
*IS "PL"
    *WHEN ACCDETAILDIM
    *IS "FLOW_CLOSING"
        *WHEN INTCODIM
        *IS "IC_ALL"
             *REC(ACCOUNTDIM="ACC_PROFIT_BS",ACCDETAILDIM="FLOW_RESULT",INTCODIM="IC_ALL",DataSrc="CalcPreAdj")
             *REC(ACCOUNTDIM="ACC_PROFIT_BS",ACCDETAILDIM="FLOW_CLOSING",INTCODIM="IC_ALL",DataSrc="CalcPreAdj")
         *ENDWHEN
    *ENDWHEN
*ENDWHEN
Re-using this in my periodic application result in only moving the periodic result to the balance sheet and not the YTD result.
What is best practice for moving retained earnings in a periodic application?

Hi
Thanks for the quick reply.
Are there any performance issues by calling SPRUNCALCACCOUNT in default logic?
For information I hav put myfull default logic is below:
*WHEN ACCOUNTDIM.GROUP2
*IS "PL"
    *WHEN ACCDETAILDIM
    *IS "FLOW_CLOSING"
        *WHEN INTCODIM
        *IS "IC_ALL"
             *REC(ACCOUNTDIM="ACC_PROFIT_BS",ACCDETAILDIM="FLOW_RESULT",INTCODIM="IC_ALL",DataSrc="CalcPreAdj")
             *REC(ACCOUNTDIM="ACC_PROFIT_BS",ACCDETAILDIM="FLOW_CLOSING",INTCODIM="IC_ALL",DataSrc="CalcPreAdj")
         *ENDWHEN
    *ENDWHEN
*IS "BS"
    *WHEN DATASRCDIM.DATASRC_TYPE
    *IS "I"
        *WHEN ACCDETAILDIM
        *IS "FLOW_CLOSING"
            *WHEN ACCOUNTDIM.CALCULATIONTYPE
            *IS "E"
                *REC(ACCDETAILDIM="FLOW_ERROR",ACCOUNTDIM=ACCOUNTDIM.ID,INTCODIM=INTCODIM.ID)
            *IS "A"
                *REC(ACCDETAILDIM="FLOW_VAR",ACCOUNTDIM=ACCOUNTDIM.ID,INTCODIM=INTCODIM.ID)
            *ENDWHEN
        *ELSE
            *WHEN ACCOUNTDIM.CALCULATIONTYPE
            *IS "C"
                *REC(ACCDETAILDIM="FLOW_CLOSING")
            *IS "E"
                *REC(FACTOR=-1,ACCDETAILDIM="FLOW_ERROR",ACCOUNTDIM=ACCOUNTDIM.ID,INTCODIM=INTCODIM.ID)
            *IS "A"
                *REC(FACTOR=-1,ACCDETAILDIM="FLOW_VAR",ACCOUNTDIM=ACCOUNTDIM.ID,INTCODIM=INTCODIM.ID)
            *ENDWHEN
       *ENDWHEN
    *IS "M","A"
        *WHEN ACCDETAILDIM
        *IS "FLOW_CLOSING","FLOW_ERROR","FLOW_RESULT"
        *ELSE
            *WHEN ACCOUNTDIM.CALCULATIONTYPE
            *IS "A","C","E"
                *REC(ACCDETAILDIM="FLOW_CLOSING",ACCOUNTDIM=ACCOUNTDIM.ID,INTCODIM=INTCODIM.ID)
            *ENDWHEN
       *ENDWHEN
    *ENDWHEN
*ENDWHEN
*COMMIT

Using variable 0P_FPER to calculate YTD Fiscal period

Could someone please explain the procedure for creating a variable which will use the value entered from the variable 0P_FPER - Period/Fiscal Year (Single Value Entry, Required) to calculate the YTD Fiscal Period.
Regards,
Craig Stephen

You have to create a Customer Exit variable for this :
<b>Customer Exit - > YTD from Fiscal Period</b>
<b>Let ZVCCYTDX be the tech name of Customer Exit Variable & 0P_FPER be the user entered variable for Fiscal Year Period.</b>
User Exit: ZVCCYTDX
Input: 0P_FPER
Output: Jan of Accident Year Range
Logic Description:
WHEN 'ZVCCYTDX'.
if i_step = 2.
clear loc_var_range.
loop at i_t_var_range into loc_var_range WHERE vnam = '0P_FPER '.
if sy-subrc = 0.
curr_year = loc_var_range-low(4).
concatenate curr_year '001' into jan_accidentyear.
CLEAR L_S_RANGE.
L_S_RANGE-LOW = jan_accidentyear.
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'EQ'.
append l_s_range to e_t_range.
exit.
**endif.
endloop.
endif.
**Coding is not required if you can enhance the Datatarget with Fiscal Year and Posting Period.

Loading data - YTD vs Periodic

Just to confirm...you cannot load some data as YTD and some as MTD, correct? Same app, same scenario.

Within a data file, you can mix records (different accounts) with YTD and Periodic. But I have not tried mixing YTD and Periodic records for same account and load it with "Accumulate within file" option.

Computing Consolidation Entries - YTD Vs Periodic

Hello Experts:
We are in the design phase of the project. Referring to the quesiton asked earlier by Sitaram (Periodic versus YTD computation of consolidating entries), Does any one has comparison between YTD Vs Periodic ?
We are in the process of determining which is the best approach to go for.
Any inputs is appreciated.
Thanks,
Ravi

the problem we encountered was a bug that SAP fixed for us.
For consols, ytd is the way to go. Planning can go either way.
Tara Sitaram

Balance sheet reports - YTD or Periodic

Hello Experts,
Had a question about how and what data needs to be loaded from BW to BPC NW version so that I can create balance sheet reports in BPC. Currently I am loading the periodic debit-credit activity to my planning application for all the accounts (Its the 0FIGL_O14 DSO and there is a custom cube created over it. We are not loading the 0BALANCE from the 0FIGL_C10 cube).
As an example, when we select in the current view both 2011.MAR and YTD, I though the report was supposed to return the values accumulated between 2011.JAN to 2011.MAR for Balance sheet accounts. Instead of that, the report returns only the 2011.MAR value.
But after reading a couple of threads on the forum I found that the above is the right behavior since balance sheet account values are always loaded as YTD.
I know I am doing something wrong out here but dont know the exact reason and how do I correct it?
Please give suggestions around how balance sheets are to be created and what data needs to be exactly loaded from BW...
Thanks
Gaurav

Hi Gaurav,
It is ideal to make all the custom changes in BW itself and feed it as-is to BPC, as to do this in BW it just requires some simple ABAP.
I am assuming that you are feeding data to BPC via 0figl_c10 cube(transaction figures) or a custom cube based on it. This cube should have 0sales(periodic balances) and 0balance(cumulative balances). So enhance this cube with a new key figure and populate this key figure based on the approach that i mentioned to you earlier. Just map this newly added field to BPC signeddata to meet your requirement. This is the best approach that i see.
PS: Please assign points if you find the answers helpful.
Thanks,
Vinay

YTD or Periodic application

Similar Messages

Maybe you are looking for