SAP BPC 10.1 : Copying comments fra DSO (direct update)

[jrgen_dalbyandersen]

Hi,

i'm struggling with two dso'es, which contain comments. I'm using characteristic as keyfigure for storing the comments.

I just wanna copy comments from one dso to the other.. The source dso has 3 primary keys (key field) and the target dso has 4 primary keys.

When using a simple standard copy, all lines within my target are overwritten with "#", if they are "within" my 3 primary keys.. If i create fox formula, no data is copied from source to target..

So now to my question, is there something special for direct update DSO'es in BPC ?

I made a workaround copying data through an APD, this work - but is not a usable workaround..

Thank,

Joergen

[gregor_dieckmann · Accepted solution]

Hi Joergen,

the standard planning function type COPY should work; the question is how you configured this function and how you want to fill the additional key field in target DSO.

1 The additional key field can be initial: In this case you can use a MultiProvider with an aggregation level that contains all 4 key fields; the additional key field of the target is not mapped in the MultiProvider.

2 The additional key field can be filled using a derivation rule based on characteristic relationships. In this case the MultiProvider only may contain the 3 common key fields, also the aggregation level.

In both cases the aggregation level has to contain the 'comments' as a key figure; don't forget to map this key figure from the DSO to the MultiProvider. In the planning function configure characteristic 0INFOROV as characteristic to be changed and use the source DSO in FROM and the target DSO in the TO (parameter of the planning function) and use the target DSO in the filter used to execute the planning function.

This should do the job.

FOX does not allow to do something with 'characteristics as key figures'.

Regards,

Gregor

P.S.

Implement notes

2267813

2205174

[jrgen_dalbyandersen]

Hi Gregor,

thank you. Using the standard copy with my 4th keyfield marked as "changed" and set to "#" in both source and target fixed it. (I doesn't need to be filled in my target)

Though i'm using fox on existing planning models (infoproviders) with great succes. Primarily setting status field green/red for status and tracking. Works fine when i use SID values for populating the value.

Regards

Jorgen