on 2014 Apr 28 1:42 PM
When querying against a DP remote cube, either via LISTCUBE or Bex, you must always specify the planning version. If you don't specify the correct planning version then no data can/will be returned.
Hope this resolves.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
In the transformation you are mapping source to target field. When you read the planning area data via a remote cube then you must stipulate the required planning version in the Bex or LISTCUBE variables e.g.
This is required as you may have more than 1 planning version in the planning area used as the data source for the remote cube.
Regards
Hi Alan,
I got a requirement to to create virtual cube based on APO datasource which is supported for direct update. so i have created the flow and while viewing the data i'm getting same error. i tried to filter out the planning version in Bex and at start routine(by deleting unwanted versions) but still i'm having same issue. Please help in solving this issue
Hi Prabhakar,
Perhaps this comes a little bit late. However I had a similar problem and this fixed it.
Insert the following lines to the start routine of you transformation:
c_th_fields_inbound = i_th_fields_outbound.
c_r_selset_inbound = i_r_selset_outbound.
c_exact = rs_c_true.
The correct place is in the inverse_start_routine part:
This is the original post which helped me:
User | Count |
---|---|
11 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.