Prior Period Calc

I am attempting to do a DSO calculation that checks to see if two account members are less than the total sales member back up to four months to make the calculation and am seeking any recommendations on how to accomplish this. I am pretty new at Essbase and this seems to be a complex calculation. Here is an example of the calculation in a generic sense:IF( (RecNet.TradeRec.Trade+RecNet.OtherRec.ProBill) <= SalesOC, ( (RecNet.TradeRec.Trade + RecNet.OtherRec.ProBill) / (SalesOC/DaysInCurrentMonth) ), IF( (RecNet.TradeRec.Trade + RecNet.OtherRec.ProBill) <= SUM('SalesOCCurrent-1':SalesOC), DaysInCurrentMonth + ( (RecNet.TradeRec.Trade + RecNet.OtherRec.ProBill - SalesOC) / ('SalesOCCurrent-1' / 'DaysInCurrentMonth-1') ),etc., back 4 months. We have periods in one dim and year in another.I made the following attempt, but I am sure my syntax is wrong:IF (("RecNet.TradeRec.Trade"+"RecNet.OtherRec.ProBill") <= SalesOC) ARDAYS = ((RecNet.TradeRec.Trade+RecNet.OtherRec.ProBill) / (SalesOC/DAYS_TOT);ELSEIF ((RecNet.TradeRec.Trade+RecNet.OtherRec.ProBill) <= @SUMRANGE (SalesOC, @CURRMBRRANGE (PERIOD, LEV, 0, -1, 0)) ARDAYS = DAYS_TOT + ((RecNet.TradeRec.Trade+RecNet.OtherRec.ProBill-SalesOC) / (@SUMRANGE (SalesOC, @CURRMBRRANGE (PERIOD, LEV, 0, -1, -1)) / (@SUMRANGE (DAYS_TOT, @CURRMBRRANGE (PERIOD, LEV, 0, -1, -1)));Sorry for the long post. Should I be using @PRIOR instead?

I can give you an example of why ABS is used in the divisor.
Imagine for a moment that you had profit last year of 200, and profit this year of 500. Your percentage change would be 1.5, or 150%, right? Pretty easy to calculate: (New minus Old) / Old = (500-200)/200.
But if last year's profit was a $200 LOSS, what would your percentage change be? "(New minus Old) / Old" would be (500 minus (-200)) divided by -200, or 700 divided by -200, resulting in negative 3.5, or a 350% loss. Huh? How in the world could that be right? We had a loss last year, a gain this year, and it shows up as a negative percentage increase?
To (partially) fix the problem, we use ABS in the divisor. So we go from -200 up to zero, that's a 100% improvment. Then we go from zero up to 200, that's another 100%, and from 200 up to 400 is another 100%. And then from 400 up to 500 is another 50%. So that's a total of 350%. Using ABS around the divisor does that for us, so that we're not dividing by a negative number.
Now, I firmly believe that if last year's number is a negative and this year's number is a positive, the result should be N/A. But that's not what the OLAP engine does by default. Why do I disagree with returning a numbe at all? Let's take that second example, where we had a $200 loss followed by a $500 gain, which would show up as a 350% return. What if our initial year had a $142.86 profit, followed in the next year by a $500 profit?. What would the percentage change be? Do the math, and you'll find that it's.... 350%.
So... an increase of $700 (from a loss of $200 to a profit of $500) calculates to the same percentage as an increase of $357.14 (from a profit of $142.86 to a profit of $500), which I find ludicrous. But there it is.
Anyway, that's why you use ABS in the denominator.

Similar Messages

Calc with Current and Prior Periods Data

Hi Everyone - I would like to come up with two types of calculations usingamounts from prior periods (dynamically) 1. "Net Sales" (current period) + "Net Sales"(current period - 3 months) + "Net Sales" (current period- 6 months) + "Net Sales" (current period - 9 months)i.e. If current period = June ... Net Sales Amount in June + NetSales Amount in March + Net Sales Amount in December of the yearbefore + Net Sales Amount in September of the year before. 2. Sum "Cash" for the past 12 months (current period tocurrent period - 11) In both cases, we'll need to handle getting amounts from the prioryear, as well. I can feed the "current period" in thru a sub var, yet(assuming that is the correct function, I am not sure how to set up@PRIOR with Current Period - n Periods... I appreciate your help. Grazie ...lb 

Hi David,
I'd suggest you use a Query filter (or a report filter) to retrieve only rows that match this criteria on years. Since you need two values, I may have to use the filtering operator 'in list'
Difference between those two is query filter will only retrieve to values where year = 2008 or 2009 from the datasource (so if you want to change the year values, you will have to refresh document), while report filters are active on the query output (which means that no refresh from the DB is required if you need to change values), which might bring a better experience if you need interactivity in the report. Moreover, if interactivity is important and you are working with WebI XI 3.1 SP2, you can embed these report filters into Input Control, and command the filter from a graphical widget like check boxes, to let user control which years he wants to view/ compare in the table (or chart).
Hope that helps,
David.

How to create logical columns for current period and prior period

Hello all.
Is there any way in obiee to create a new logica column in BMM layer that says "CURRENT PERIOD" AND "PRIOR PERIOD" OR ONE SINGLE COLUMN THAT SAYS "PERIOD".
In those columns what I need is if it a current period column it shoould have 03/01/2012-03/31/2012 (this month date range)
and in prior period column I shouldhave 02/01/2012 -02/29/2012(which is previous month date range).These columns I will be using in my reports.
Please help me if we can create any such columns with these conditions/requirements

Hi,I have already created he dynamic variables.But I am not getting how to use those variables and create the new logical columns in bmm layer.
this is what I am trying
case when VALUEOF("Current Month begin date"."Current Month begin date") ='..' and VALUEOF("Current Month end date"."Current Month end date")
='..' then 'current period' end
I don't really understand what I should write case when VALUEOF("Current Month begin date"."Current Month begin date") ='..'??

Customer Statement - PLD - Prior Period Balance

When one uses the standard Customer Statement, the prior period balance shows up. It is a field defined as TEXT field, Free Text and the text value is 9999999999.
When I copied (save as) this standard customer statement, the prior period balance no longer shows up. Further more, if I copy this field from the customer statement (F_033) to my new copy it doesn't work and if I manually create a new field it doesn't work either on the new statement.
How does one get a prior period balance to show when the field is a text field and not a formula field.
Any help would be greatly appreciated.

Hi Marli,
This is the norm of B1. Your client should be able to get used to it soon.
Thanks,
Gordon

Date issue in processing billing documents that shipped in a prior period

Date issue in processing billing documents that shipped in a prior period that is now closed:
SAP values those deliveries with the current document date in A/R when it should be the original delivery date. Baseline date needs to stay the delivery date, but is getting copied from the billing date in the new period. A user exit exists (& needs to be applied) to manipulate the baseline date when the accounting document is being created.
Any input is appreciated.

Hi
Try with Invoice Correction Request concept
Sale document Type: RK
Reference Document Type : Billing Number
for Understanding the Invoice Correction request check below link
[Creating Invoice Correction Requests|http://help.sap.com/saphelp_46c/helpdata/en/dd/55feeb545a11d1a7020000e829fd11/content.htm]
Regards,
Prasanna

Profit Center Group Organization Change - Effective for Prior Periods

Hi Experts,
A client wants to perform a horizontal organization change (profit centers) and see the effects retroactively to the prior periods. To achieve this, they plan to re-execute the consolidation tasks going back two to three years once the org change is made, so that they have comparative financial statements that take into account the change. The requirement is to re-post the group level postings to the updated profit center group after the change. For example, Italy related postings would occur under the group Central Europe instead of Western Europe as before. All the group level postings previously booked to Western Europe would now need to recorded under Central Europe going back prior periods.
Does anyone have any ideas as to how to meet the requirement without re-consolidating?
One option was the restatement feature but based on the SAP help description of the monitor required, it does not take into account consolidated postings, only uploaded PL00-10 data and translation.
Another option is to copy the version but then the results is in another version rather than the original 'actual' "100" version.
Any ideas would be appreciated.
Thanks
Eyal Feiler

Eyal,
I know of no other way to accomplish this than to re-execute the consolidation for the prior periods after the hierarchy has been changed.
I have used the restatement feature and like you have found it very limited.
The copy to another version would only work if you copied the existing data to the new version before re-executing the consolidation. The the version 100 can be re-consolidated for the previous periods and the existing reports do not have to be changed for a new version.
However, with the copy, it is important to set the cons group and cons unit hierarchies to be version dependent so the changes are only good for the version that is to be re-consolidated for previous periods. This allows you to report on the data before the change where the logic will read the old, unchanged version of the hierarchy.
Dan

How to post prior period depreciation into the current period

We accidentally missed a depreciation run in a prior month and so cannot move ahead until this is posted. We do not reopen prior periods once the GL is closed. Is there a way to post the prior month's depreciation into the current month? We are on ECC so I understand depreciation no longer posts via SM35. I have seen other posts that discuss similar issues but haven't seen this exact issue. I've been told there is no way to do this, our only option is to reopen the periods. Hoping that is not the case. Thanks.

Hello,
Since the depreciation didn't run in the previous month, the depreciantion of last month and current month to be booked in current period is possible. For example period 06 was the previous month, then in current month depreciation run AFAB > select 'Unplanned posting run' in the 'Reason for posting run' only for current month for e.g. period 07. From next month onwards, select 'Planned posting run' as normal.
Kind regards,
John Chin
Edited by: chinks on Jul 20, 2011 12:43 PM

What is the earliest prior period that you would like to enter into SAP B1

Can anyone please explain the need of gathering the following information in a BBP for SAP B1 2007B?
"What is the earliest prior period that you would like to enter into SAP Business One to allow for Comparative Financial Statements?"

If you want to be able to create year over year reports, create budgets based on history, etc. you can't just start with opening balances for your GL accounts. You need to create past periods and load history amounts. That's all.
My clients typically want to be able to answer questions like 'How much higher (or lower) are sales this month than sales in the same month last year?' So for a client who 'went live' with SAP on January 1, 2009, I would create 12 periods for 2008 and enter their monthly balances for their GL accounts.

Material ledger - closing prior periods

We have a need (currently in development environment) where material ledger closing is not in sync with material period closing. Is there a way to "catch up" the material ledger. this is in a development environment only at this point. Basically, does anyone know how to close a material ledger period for more than 1 month back in history. e.g. curr period 1/2009 prev period 12/2008 ..like to close for periods prior to 12/2008

Hi David
If you dont need to perform the close itself but would just like to get the periods in the correct status you can use the process outlined in note 645083.
In the material ledger, it may be necessary for different reasons to manually set the period status of materials in former periods to 70 ("Closing Entry Completed") without actually carrying out the closing entry.
It provides program Z_ML_SET_PP_STATUS_70 that will allow a manual update to the prior period status.
There is a pre-requisite regarding revaluation amounts, but this is all described in the notes.
/Elaine

PERIODIC CALC for Fiscal Year Aug - Jul

Hi,
I am currently having issues with my fiscal year. Our physical year is from AUG - JUL. The application is a YTD so the periodic measure is a calculation. On processing and optimizing the legalapp I noticed that the calculation for periodic resets to include NOT INSTR("TOTALQ1JAN",[TIME].PROPERTIES("PERIOD") as part of the calculation for each instance of my account hierararchy. On changing teh TOTALQ1JAN to TOTALQ1AUG directly in the MDX my periodic calcs work correctly again for those periods, however once an optimise is run again the calc is reset. This is now also possibly causing us problems with our account transformations for opening balances. I have had a look at appset parameters and application parameters and I can't seem to see where the first period of the fiscal year should be set.

There are no specific problems with this beyond the logic / stored procedures that rely upon the property. I suggest checking the logic you've implemented as well as any input schedules / reports that may reference the property to ensure they are working properly. If you need to store AUG as a property of August, then you can add another property to hold the propery month abbreviations.
Unfortunately, the YTD measures assumes that all apps are calendar year. The note from product support indicated that the issue is resolved in the 7.0M release. Once your client upgrades to 7.0, you should be able to change the property value back AUG.
Just a case of a developer making an assumption that didn't work in the real world.

Cant change delivery date on Sales Order posted in prior period

Hello All,
Scenario: A sales order which was processed in prior period but since then delivery date had changed due to request from our customer. When we try to go back and change the delivery date, we find it greyed out. To get around this, we have to open the period again, change date and then close the period. Problem is that not all dates get changed, so our late delivery report look bad, shows that 90% of our deliveries are late, when in fact they are on time, the new time which we could not record on the Sales Order. We have similar problem with our purchase Orders.
Is there anything in Administration we can do to enable us to easily chnage delivery dates on Sales order and purchase orders?

Hi,
Welcome you to post on the forum. What is your B1 version and PL?
Thanks,
Gordon

Import to prior periods using DTW

Is there any way to import transactions to a prior period? I have opened all prior periods and I continue to receive a posting date deviates from permissable range error message. The dates do fall within the posting date. I am able to change the date within SBO to prior posting period manually, any reason I can not bring them in through the DTW?

1. The posting period is defined correctly, also please make sure that the posting
date, due date and document date used in the document should be according to the current posting
period.
2. Also please check under administration --> System Initialisation --> Document Setting -->
Please make sure that the option : Block documents with earlier Posting Date is not checked.
On point #1, you say "should be according to the current posting period.", but in this case I am looking to import these to a period that is unlocked, for example is 10/10/2007. All of my dates fall within the ranges listed below. My current period that I am attempting to post to for example is set up as follows:
Period Code Period Name Period Status Posting Date From-To Due Date From-To
2007 2007 Unlocked 01/01/07 12/31/07 01/01/07 12/31/07
I confirmed point #2 as well.

HE 641 unlocking prior periods

Update on this - As an administrator I should be able to unlock any prior periods but I can not. There are no journal entries to unpost so the question is, how does one unlock prior periods once they have been locked? The option to do this through the Database module is grayed out.
Help, A user triend to run a Consolidation while another usere was in Data Entry and it locked up the Entity for 2 periods. Now we can not unlock it. Any suggestions?
Edited by: Foxman10 on Oct 2, 2010 7:07 AM

It is quiet an interesting solution, for it is the same effect as having the entity selected in the Database module(since it is base) so by selecting it from the dropdown box from the entity list will not be any different. However, this is hyperion enterprise, and the most strange things happen. I am glad you didnt have to reload, but sometimes is the only solution (although nobody likes it-I certainly dont) I'll keep that in mind since we still have enterprise around.

Getting Same Store functionality to work across prior periods, not just current

I have a basic Sales table, with a Store Key, Date Key, and dollar amount. I also have a SameStore table, which for every combination of StoreKey and DateKey, says whether or not that store should be considered "Same Store" (was operational
last year for the same time period) on a month to date, qtr to date, and YTD basis. The MTD Y/N, QTD Y/N and YTD Y/N are available via the same store dimension. Via my date dimension, I have all the usual date calcs, such as prior month, prior
year, QTD, etc...
It is very easy to query the totals for all of my stores as of Sept 2014 and get the current sales amout, as well as get the prior month, prior year, and so on. Now, if I only want to see the totals for stores that should be considered "same store"
as of Sept 2014, I can throw the MTD=Y up into my filter and then the current month's total will adjust to only show stores where their same store flag for Sept 2014 is set to a YES. All of the NO's for Sept 2014 get removed... however, if one of those
NO's was considered Same Store in August, their $$$ number is still being incldued in the Prior Month date calc. I don't want it there, becuase as of September (the focus of my report) they are not considered same store anymore.
I am getting this:
As of September 2014, Same Store=Yes
Store Current$
Last Month$ Last QTR$
1 (closed 8/15) $0.00
$100.00 $125.00
2 $50.00
$75.00 $60.00
3 $60.00
$65.00 $85.00
But I really want this:
As of September 2014, Same Store=Yes
Store Current$
Last Month$ Last QTR$
1 (closed 8/15) $0.00
$0.00 $0.00
(or this whole row can just be gone completely)
2 $50.00
$75.00 $60.00
3 $60.00
$65.00 $85.00
Just because Store 1 was considered to be a "Same Store" in August doesn't matter since I am running my report as of September. It is not "Same Store" as of September, so it should vanish from all my calculations.
Currently, dimStore, dimDates, and dimSameStoreStatus all hang off of the main Sales fact table. I know this is part of the problem. We are going to try and connect the dimSameStore to the dimStore and dimDates tables rather than the fact table,
but I not sure if my overall design is right for this or not in general.
Has anybody had to do something similar? If I get a solution from somebody (or a great hint that helps me solve it), I'll send you a Starbucks gift card.
Thanks in advance!
Mgr, Data Warehouse Svcs

Hi D,
The way I typically deal with this is to use a table, like you have, to mark whether the store was comparable for that Period. Then, when you run a query, you are comparing two or more periods. So, your query should restrict the scope to only
include stores that were marked as comparable in all periods.
For example, if you are comparing this month with same month last year, you should only include stores that were comparable this month and same month last year. If you have a query that is showing month on month growth for all the months this FY, you
should only include stores that were comparable for all months so far this year. This is more common for a rolling n period report.
I find it quite interesting that most retailers use some variant of "Same Store Sales" with the express purpose of being able to compare performance with other retailers. However every retailer has their own definition of what a comparable
store is.
Hope that helps,
Richard

Block Consolidation for Prior Period

Hello Experts,
I'm looking for option to block the consolidation for prior years. As for priors years we haven't closed the period(those are not in published stage), as of date system has changed alot.
We are finding a way to stop/block consolidation using rule or something like that.... Kindly suggest.
Thanks

If you wanted to block consolidations, you could modify your rules to run the sub routines only if it is greater then a specific year. You could get more elaborate, and use an HS.GetCell to test a condition like a trigger account to block consolidations. The consolidate option would still be there, but it wouldn't really do anything.
I would argue that it's possible at some point you will want to do a restatement, and you could have a larger mess in this process if the previous periods haven't been updated based on a rules change, but that's a preference of the specific business needs.
It would be something like the below, POV variable would have to be set early on to test the POV that you are currently using.
Sub Calculate
     If pov_year > 2011 Then
          All of sub calculate
     Else
          'Do Nothing
     End if
End Sub
Sub Consolidate
     If pov_year > 2011 Then
          All of sub consolidate
     Else
          'Do Nothing
     End if
End Sub
Sub Eliminate
     If pov_year > 2011 Then
          All of sub eliminate
     Else
          'Do Nothing
     End if
End Sub
Regards
JTF

Prior Period Calc

Similar Messages

Maybe you are looking for