query problem

[Former Member]

hi guys

I asked this one before but it didnot solve problem.So I am posting again.May be I will be able to explain better now.

We have many queries in BI. We have some ABAP programs wriiten,which when executed manually,will call some BI queries and output the data into some files.These files will then be uploaded into another application by another team.In one of the file this team is using,they are getting YTD value.But they want Monthly value.It means we have to change that in BI query,which is source for this file.

In went to my BI Query-Query Designer,found out,in infoprovider panel,we have some characteristics and only two key figures.i.e., Monthly Value,YTD value.In Keyfugres panel,we have at present only YTD value.In order to change query so as to get monthly values,its enough to drag MONTHLY VALUE keyfig from infoprovider panel to Keyfigure panel and remove YTD keyfigure from Keyfigures panel.

Dont you guys think it should be enough?

We have some other query which generates monthly value instead of YTD values.I thought I should check how it is built to get ideas.Its built strangely that I couldnot understand.

In infoprovider panel,theey have some characteristics and two key figures which are Monthly value and YTD value.In Key Figures panel,they have keyfigures...

Month1,

Month2,

.

.

.upto

.

Month12.

Monthly value(selection)(in this selection definition,they took monthly value key figure into selection panel and underneath it they have created one customer exit variable

Monthly value(formula)(donot have green keyfigure icon but its black in color)

Monthly value(selection)(in this selection definition,they have choosen only monthly value key figure into selection panel)(donot have green key figure icon but looks black in color)

when I tried to execute this....it didnot show any value....

Can you understand why they built like this?

Rgds.

[former_member186445 · Accepted solution]

first, If you have a monthly value in your query then in should be enough to put this columns to have the value per month. you put month in rows.

the problem now is, that you'll have one row per month per key... what you describe in the other query is according to me the following :

the monthly values needed to be ione next to the other in columns. So as you talk about customer exit, i suppose they biuld a 12 rolling back structure :meaning, that month12 is current month, month11 is current month - 1...and so on...so whenever you execute the query you get the values of the last 12 months...

as you also speak about formulas, maybe the values are adding up, meaning : month1 = month1, month2 = month1+month2...and so on...

however without knowing the exact setup and coding of the formulas and customer exit, this is a pure guess...

M.

[Former Member]

Hi there,

As far as the first question:

Dont you guys think it should be enough?

You're correct.

As far as the second question:

Month1,
Month2,
.
.
.upto
.
Month12.
Monthly value(selection)(in this selection definition,they took monthly value key figure into selection panel and underneath it they have created one customer exit variable
Monthly value(formula)(donot have green keyfigure icon but its black in color)
Monthly value(selection)(in this selection definition,they have choosen only monthly value key figure into selection panel)(donot have green key figure icon but looks black in color)

The Month1 through Month12 seems to be a selection, where inside (if you doulbe-click on it) you'll see each correspondent month restricted there Month = 1; Month = 2, and so on and the key figure monthy value, so you'll have twelve columns each corresponding to the month value of the InfoProvider for that key figure.

The monthly value formula and selection in grey colour, is a formula and a selection that is hidden of the layout of the query after executing, and might be used for other calculations inside the query.

Hope this helps,

Diogo.