How to copy actuals data to planning for the chars. not in Aggr. level

[Former Member]

Hello experts,

We are doing Tax planning and for that we have created a Multiprovider on two cubes (Actuals and Planning), on the MP we have created aggregation level and Input ready query on the aggregation level.

Because of using MP our planning cube will be empty and data will be fetched from Actuals. We have some 50 characteristics in our cube. But in our aggregation level we have included only 10 characters from the cube ( as only we are doing planning on those).

Now, while saving the input values from the manual planning, we need to copy those remaining 40 characteristics data from Actuals cube to Planning cube by matching the planning values from query.

Is there any possibility to copy characteristics using Planning function/Fox formula which is not available in aggregation level form one cube to another. (i.e: I dont want to use a infocube read FM explicitely and copy the data, as that will affect the performence).

Please through some light on this.

Thanks,

kumar

[Former Member · Accepted solution]

Hi,

Your requierment is not clear to me ,while using 10 characteristics you are actually aggregating the data ,if you need to complete all other 40 characteristics then either you need to distribute the aggregated data ,or in order to remain with the 10 charracteristics aggregation you can use characteristic relationships to derive all other 40 characteristics according to some logic.

please provide example.

Regards,

Eitan.

[Former Member · Accepted solution]

Hi Eitan,

Thanks for the reply. Actually this is the requirement here that they wanted to have planning on some level (document level and tax code level) but my user is not ready to have all the 50 characters in the row of the query nor they dont want any disaggregation rules to be applied to derive the rest.

So If I use other 40 chars. in the free chars of a query and keep the required 10 in query, unless until I apply some disaggregation rule query is not input ready. Thats what I am creating aggregation level on 10 chars only.

And whenever they are doing document level planning, based on the document number they are planing I need to copy the remainng 40 chars to the planning cube by matching the document number.

Ex:

Comp code country Vendor doc. no pl.keyfig

2030 001 20001 D001 50.

when they enter the above planning for doc. no. D001 I need to read the actual cube and copy the rest of the 40 chars from there and copy that record to planning.

Hope I have clarified something on my requirement.

We have a solution of applying FM for cube read functionality in Char. Relationship and copying the necessary chars. But that will affect the performence. So expecting some other logic.

Thanks,

V.Senthil

[Former Member · Accepted solution]

Hi ,

Try to put all 50 characteristic in the row and hide 40 of them in the query designer property of the characteristic, i understand that the reason you are working with only 10 chars. is not a question of plan aggregation but not to show 50 fields in the planning layout?

Eitan.

[Former Member · Accepted solution]

Hi,

Yes the requirement is we can plan on aggregated value, but all the fields should no be shown in the row and also users dont want to have the disaggregation rule to be applied when saving the aggregated planning.

They want to save the adjustment as it is as per their entry.

Tell me, If I include all the fields in the rows and hide the fields not required, will the query be input ready still? and will I get the input ready new row at last?

Thanks,

V.Senthil

[Former Member · Accepted solution]

Hi,

Yes it will be input ready.

but the new line is a problem because fields that are hidden are # and there is no implicit derivation,so they will be saved blank,unless you perform some kind of function to read the existing and set the hidden (repost from blanks).

Regards,

Eitan.

[Former Member · Accepted solution]

HI Eitan,

I tried to have the unwanted characters in the row and hide those. Now my planning layout is giving input ready keyfigures only for the exising records, but I am not getting any new input ready rows at the bottom of the query result, I am not able to insert new records, only able to plan on the existing records..

Anything I am missing?

Thanks,

V.Senthil

[Former Member · Accepted solution]

V.Senthil,

I guess the new line gets lost when doing that ,please check what happens when you hide the MS Excel columns, if the new line remains.

Regards,

Eitan.

[Former Member · Accepted solution]

HI Senthil,

All Characteristics should be visible in order to have "News Rows". You cannot Hide even one. It does not matter WAD Or Analyzer.

What is problem , using Characteristics Relationships ? Otherewise you need build these characteristics through Distribution or Reposting.

Regards,

Peter

[Former Member · Accepted solution]

Hi,

Thanks for the reply.

Yes in characteristic relationship I dont want to use any cube read Function module to read the rest of the characteristics. If I include a FM then it will reduce the performence.

So, how to apply repost planning fucntion here? as I dont have all the characteristics of cube included in the aggregation level. I have included only 10 chars in aggregation level to make it input ready. ( If I include all the chars in aggr. level then my users dont want to apply any disaggregation rule.)

Need one clarification, Can I create a aggregation level with all the characteristics of the cube and planning function on that aggr. level. one more aggr. level with only 10 chars and I have my input ready query on that aggr. level. Now in the planning funciton can I access input ready query values?

Thanks,

V.Senthil

[Former Member · Accepted solution]

Hi Senthil,

You have to use "FOX" for reposting , using "For each loop".

To your question, Yes, you can refer to the records generated through your input ready query. You have use "#" in your FOX code for all the characteristics that were not included in Aggregation level linked to the query.

Regards,

Pete

[Former Member · Accepted solution]

Hi,

you can define an own planning function (type).

This planning function needs to be run on a aggregation level containing all characteristics.

Define those characteristics, you are planning on, as block characteristics. (all other as to be changed)

Select your ACTUAL data as reference data.

In the EXECUTE method get the characteristic combination from a record of the reference data and apply it to all records in C_TH_DATA.

This planning function has to be started before saving data.

Prerequisits:

All data for the characteristic combination, you are planning, on have the same combination for the other 40 characteristics. Otherwise you cannot define a unique valid combination.

You need some logic for records, where no ACTUAL data exist.

You need to know, how to set up own planning funktion (types).

Regards

Steve

[Former Member · Accepted solution]

Hi Lance,

sorry for the late reply. I am trying to implement a FOX for the same. But my FOX FOREACH loop is iterating for all the records combined in Actual and Planning cubes. So again it is like including a FM to read to Actuals data. Say if I am planing for only 5 records, this FOREACH loop should be iterated only for this 5 records and need to copy the data from Actuals.

Can you please give me a sample fox code with CUBE A and CUBE B as example.

Thanks,

V.Senthil