cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

No option to select request ID while releasing data fron cube to PA using /SAPAPO/TSCUBE

Former Member
0 Kudos
249

hi

we have a requirement where we have to release data from DP planning area backup Cube to Planning area.

And in Backup Cube we keep multiple request.

so went to release data which is loaded latest means only data of request which is loaded last but when we using /SAPAPO/TSCUBE we don't have option in "Restriction for data selection from InfoCube" to select data request ID wise.

please guide if there is way for it

View Entire Topic
RahulHanda
Active Contributor
0 Kudos

Hi Kapil

What do you mean by below is still not clear?


And in Backup Cube we keep multiple request.

so went to release data which is loaded latest means only data of request which is loaded last but when we using /SAPAPO/TSCUBE we don't have option in "Restriction for data selection from InfoCube" to select data request ID wise.

I am assuming this what you are doing or want to achieve:

  • Loaded initial data, let's say for period Jan to May.
  • Then you load Delta for the month of June (let's say end of month)
  • Then in this case you need to add data for June to PA, if yes then follow below:
    • Define your variant for TSCUBE
    • Put dates on a rolling basis while saving the variant
    • In definition of key figure don't click on add data
    • Map the characteristics accordingly
  • When you will execute the same it would copy automatically all data accordingly to PA.
  • Compare both and they should be in sync.

Let us know if it resolved your issue,

Regards

Rahul

Former Member
0 Kudos

Hi Kapil,

There are lot of questions to be answered before we go for good solution.

Request ID in conjunction with SID ID will act as change pointer when loading data into the BW Cubes.

With Delta update Current Request ID will pull the data from your datasource which are new/changed when compared to your last Request ID

  • How often the data loaded into your back up cube, if you're taking back up on a daily basis then you can load data into PA based on dates instead of Request ID.
  • Or you can copy the cube to another cube then delete all the remaining data other than the latest Request ID using respective date of uploads happen.
  • Or you can load the PA Backup data parallely to a new cube such that it holds only the current/latest Request Data, next day when new request gets generated your existing cube data can be deleted (previous request's data) and only the current day (next day) request data loaded into your cube, This can be achieved using a process chain on a daily basis. -->Delete Cube data -->Load current Request's Data into cube.
  • Or you can use any BI Routines to achieve this.
  • How often you want to load the data into PA from Cube.
  • How this process adds value to your Business.

I would suggest you to discuss with a BW consultant who would guide you on your requirement.

Regards

Vinoth

Former Member
0 Kudos

thanks Rahul and Vinoth...thanks for reply..

I will explain again my requirment..

we take backup of our full DP planning area at weekend and we keep atleast 3 request in our cube.

but when i have to load back planning area from backup cube,i want to select request id data to be loaded to PA..if i don't give request ID it will sum data of all request id in cube and load (3 request in cube means data will be 3 times of actual data).

presently we delete all other request from cube before loading but i want way out so that i don't have to delete other request before loading planning area?

Any enhancement is available for /SAPAPO/TSCUBE for Restriction for data selection from InfoCube?

i have that in mind we can load data to another cube and delete data and load to PA but its looks noy very feasible as loading new cube from backup cube will again take lot of time..

Former Member
0 Kudos

Kapil,

Add a routine/formula in the BW transformation of the back up to map the 'Version' field as the current date (for example). This way you will have a unique identifier (Planning version) for each request in the back-up cube which can be used in the data load from Info Cube to APO Planning Area.

Hope this solves your issue.

Regards,

PN