Status & Tracking for Integrated Planning

[Former Member]

Hi,

does anyone know if Status and Tracking still works with Integrated Planning? And if so, how, since there's no planning area any more? Or is the intention now to use workflow?

Thanks.

Heike

[gregor_dieckmann · Accepted solution]

Hello Heike,

the answer is more or less: yes.

- header selections for a basic planning area can be

reused for the corresponding basic InfoCube; in BI

Planning this has to be modeled as a exit dataslice;

just use the class CL_UPS_LOCK_DATASLICE in the

Planning Modeler as an exit dataslice

- one can use URLs to BI reports

- one can use planning seqence from BI Planning from

BI Planning (on status change).

This information is also contained in the documentation (for BW-BPS).

Best regards,

Gregor

[Former Member · Accepted solution]

Hi Gregor,

sorry, I don't get it. There's no dataslice in integrated planning (SP5).

Further, how would I set up the hierarchy for the subplan, as in order to specify the hierarchy you have to specify the planning area (required field) - and of course with integrated planning there is no planning area.

Thanks!

[gregor_dieckmann · Accepted solution]

Hello Heike,

the point is to reuse STS from BPS in BI Planning:

- a basic planning area always is assigned to a basic

transactional cube

- take this basic cube and open the planning modeler

(e.g. via transaction rsplan) and use the infoprovider

tab enter the cube; there you can see tab 'characteristic relationships, data slices, ...

Create an exit data slice and enter the above mentioned class.

So of course, BI Planning also supports characteristic relationships and data slices. Please consult help.sap.com for more details.

Regards,

Gregor

[Former Member · Accepted solution]

Hi Gregor,

we're working on a multiprovider since we want to keep actual and plan data in separate cubes. Therefore no dataslice.

So the question still remains, since I don't have the possibility to define planning areas (or data slices) how could I use STS, since the determination of the hierarchy is using planning areas?

Thanks.

Heike

Message was edited by: Heike von Borstel

[gerd_schoeffl · Accepted solution]

Hello Heike,

There are only minor changes in STS in the new release so it basically works as in the old releases.

Planning Area: BI Planning does not know a planning area, the STS on the other hand needs a planning area for the hierarchy. If you want to use the STS for data for say InfoCube1 in BI Integrated Planning you have to create a planning area for InfoCube1 in BPS. Just the planning area, nothing else.

Data Slice: In BI Integrated Planning you have to set this data slice type exit on InfoCube1. Now even if you use a Multi Provider still the data of InfoCube1 will be locked by this data slice. Thus you can use also MultiProviders in this scenario.

You cannot use the locking in STS in this scenario to lock plan data from several transactional InfoCubes in one STS session. This means you cannot use STS on MultiProviders if you want to lock more than one InfoProvider at a time.

Best regards,

Gerd Schoeffl,

SAPNetWeaver RIG BI EMEA

[Former Member]

Hi Gerd Schoeffl and Heike

Pl. use standard class CL_RSPLS_DS_EXIT_BASE as a super class to create your own class and please design a code into the IF_RSPLS_DS_METHODS~IS_PROTECTED method. We can always lock multiple transaction cubes from this code however it is all depends on how your STS hierarchy and layouts are designed (if based out of agg levels or cubes). Please refer to the UPS_LOCKS to get the lock entries and when check info provider name from N_BASIC_PROV parameter to see what data you or our end user is going to see before he or she opens a layout. You can see that data in i_s_data table. Idea is your data slice is always attached to transaction cube and not to the multiprovider so you always see that cube into the method that you wish t lock the data for.

Hope this helps.

Thanks

AG