Fiscal Year/Quarters

[Former Member]

Hi,

We mostly do BPS planning by Fiscal year Quarters.

In the system, there exists standard info objects for Calendar year/Quarters (0CALQUARTER), but there are no Fiscal year/Quarters.

This is important because our Fiscal year is not the same as the calendar year.

Also, SAP does not allow you to create/Edit new 'Time-characteristics' when we tried to create one for Fiscal year/Quarter.

Does anyone know of an info object for Fiscal year/Quarter, or how to get around this issue. We don't care about seeing or having it reflected at the Fiscal year/Period level.

Thanks for any help you can provide.

Regards

Ehab

[Former Member · Accepted solution]

Hello Ehab,

Why not pursue the option to choose period 3 for 1st qrtr, per 6 for 2nd qrtr and so on. By using the infoobject 0FISCPER3, you could substitute quarters with period based accounting.

Sunil

[Former Member · Accepted solution]

Hi Sunil,

The problem is, there other other divisions of the company who are still using Fiscal year/period to enter and analyze their plan data. So we can't really use period # 3, # 6 etc, to book all the quarter's plan data.

And '0FISCPER3' posting period, is automatically derived from the posting date, as well as users still reporting using this characteristic (which should reflect 12 periods, and not 4 periods for quarters. So we can't really change the definition of it.

But I do understand and appreciate your thought.

We basically need a Time characteristic to work the same way as the 'Calendar yr/Quarter', ONLY, based on the Fiscal year definition.

[Former Member · Accepted solution]

Hi Ehab,

I think by coding the logic to arrive at the Fiscal year/quarters, using VBscript in the two standard exits SAPAfterDataPut and SAPBeforeDataGet you should be able to achieve the same. But obviously the same can be done for Excel interface only.

[Former Member · Accepted solution]

Hi Anurag,

I'm not quite sure what you mean by that, because theSAPAfterDataPut and SAPBeforeDataGet scripts basically control the ability for a user to enter data from his own sheet, and make it update the standard BPS layout sheet, and vice version.

So I'm not sure how it do the conversions.

Another thought that came to mind is using existing '0calquarter', the calendar quarter info object, and since it's not currently being used here, I would create the logic in the update rules so that the actuals for the fiscal periods are mapped to the right fiscal year quarter, rather than have it based on the calendar quarter.....and in BPS, I would just plan on the appropriate quarter.... any thoughts or possible setbacks on that idea?

thanks

[Former Member · Accepted solution]

Hi Ehab,

<i>

"I'm not quite sure what you mean by that, because theSAPAfterDataPut and SAPBeforeDataGet scripts basically control the ability for a user to enter data from his own sheet, and make it update the standard BPS layout sheet, and vice version."</i>

you got it right, that is what I am saying, give the user a quarterly interface to enter the data as needed, whereas you could store the same at period level in the BPS layout(if it is ok with the user obviously). It would give the quarterly planning interface and the same could be stored in the last month of the quarter or distributed over the months of the quarter, if that is ok.

Hope it helps...

[Former Member]

Ehab,

If you define a custom characteristic to represent fiscal quarter, be aware that TMVL in FOX does not work since that only works with SAP deliver 0* time objects. You can have a Z time pseudo characteristics but you would have to do a lot more in FOX typically.

There has been some desire for additional SAP delivered time characteristics such as fiscal quarter especially in view that CPG / retail that are on a 4-4-5 calendar and some company have fiscal years starting at timeframes other than Jan. Currently that is not on SAP's development schedule so if that would be useful for your business, I suggest you work with ASUG or other influence council type environments to try to get this moved up in development priorities..