Restrict on Navigation attribute in Integrated Planning

Hello,
I have created an Aggregation Level on the Multiprovider(combines Actual and Plan) and I have created a ready to input query on the multi provider. The query works fine for planning.
However, I would like to restrict the query to show only few accounts. Account type is the navigational attribute on the Sold to party and I want to restrict only the Sold to party of Account type 1 2 3 & 4. When I restrict that in the query the Planned values are not editable. I am not able to input the planned values. I am able to input when I take the navigational attribute away in the query.
Could anyone of you please help me with this. Could anyone please let me know the steps to use the navigational attribute in the input ready query or Integrated Planning
thanks,
KK

Hi,
As Sven has mentioned has mentioned you can lock each record by having a characteristic "0createdby".
But you have to create a characteristic relationship of type "Exit" where in you write a small piece of ABAP code to generate the value of "0createdby", when the end user tries saving a reocrd in to the planning cube.
Kindly refer to the following link for more details on characteristic relationship,
http://help.sap.com/saphelp_nw70/helpdata/en/43/1c3d0f31b70701e10000000a422035/frameset.htm
Regards,
Balajee

Similar Messages

InfoSET - Characteristic restriction by navigational attribute.

Created an infoset on 3 ODS's
Checked the navigational attributes i wante in ODS. (eg 0country as attribute from ZVENDOR)
When building the query it is not possible to have the field as a navigational attribute,only as attibute.
When I want to use it as navigational attribute I have to add it to the ODS.
Only then it is available as Navigational attribute in the query.
When I Add ZVENDOR in characteristics restrictions and create a variable with replacement path "Attribute value" I get the message Replace variable with INFOOBJECT.
"Value 'I' is invalid for property 'Replace Variable With' of element 'ZVENDOR_ATTR'"
Define a valid value for property 'Replace Variable With' of element 'ZVENDOR_ATTR'
How do I resolve this variable error ?

navigational attributes are not visible in infoset, you need to include those nav-attrubetes physically in to your ods-data part to be able to navigate/filter.

Integrated Planning - Navigation attribute not shown for Planned figures

Hello,
I have created a Input ready query to get the actual figures from previous years and enabling users to enter the planned figures. I have created Planning functions to copy and revaluate.
Reg   Account    Actual         Planned
US         123000     $3000         $4000
US         124200     $5000         $6000
I have one more report where it shows the Actual & Plan comparision.
In the Actual & Plan comparision report I have an additional Navigational attribute SIC code to be shown for each account.
My Actual & Plan comparision report should ideally be seen like below.
Reg   Account    SIC Actual         Planned
US         123000      3026         $3000         $4000
US         124200      4325         $5000         $6000
But it is showing as below where it has # for Planned figures and it shows blank.
Reg   Account     SIC   Actual         Planned
US         123000      3026         $3000         <blank>
US         123000      #              <blank>       $4000
US         124200      4325         $5000          <blank>
US         124200      #              <blank>        $6000
SIC Code is a navigational attribute of account. What changes do I have to do to make the SIC code to be shown for planned figures.
Any help would be highly appreciated and rewared.
Regards,
KK

I figured it out. I didnt assign the navigation attribute to the plan cube in the multiprovider. Thanks!!
Edited by: KK on Feb 19, 2008 10:12 PM

Unable to Restrict Navigational Attribute in Query Designer

Hi BI Experts,
I had a Requirement to restrict on navigational attribute.......
i have checked in every levels such that
1.at info object level ....checked type as navigational
2.at info cube level checked the navigational on.
still iam unable to restrict on navigational attribute................in the context menu its giving the options cut, remove and where used list .........its not giving option to restrict...........
its very urgent ...........please give any suggestions how to restrict on navigational attr

Dear Ram,
Dont expand the InfoObject and see the Attributes ( They r Dis Attrs )
Just expand the Dimension --- Nav Attrs are available ?
Dont put them in Filter pane..( if available )
Drop them under Rows.
But restrict them under Default values ( By clicking on Filter pane ).
Regards,
Ram.

Navigation Attributes & Planning Characteristics

Hi,
We plan to maintain some of the characteristics as Navigation Attributes. We understand that there are performance issues if we use navigation attributes in planning area.
I have a query: If we do not navigate data based on navigation attribute in interactive planning, even then the performance be low or only when we select navigation attribute in interactive planning?
regards,
Mohit

By definition, nothing is stored in live cache against navigation attributes. So if you load a selection containing navigational attribute or drill down by navigational attribute, in theory this should be much faster vis a vis reading from live cache (not withstanding the general computing theory of memory resident processing). This statement (of mine) is contra positive to SAP warnings on performance when using navigational attributes. There are a dozen notes on this to scare users.
There is no definitive answer I guess... at least empirically. It depends eventually on the query size. When query is large, it is hard to blame navigational attributes alone (if you are using some). It can be more so because of transaction time (SQL>LC routine > SQL) in the live cache as well. Sometimes reading a simple relational table (if indexed) can be much faster than reading non-relational (live cache) tables.
I am not a techspert and authority on this. This response is based on my painful experiences. For me anything more than couple of seconds on interactive DP is a waste of time.
Thanks
Borat

Navigational attribute and FOX in IP

Hi,
I have experienced a strange behavior of a FOX.
This is a copy from ACTUAL InfoCube to PLAN InfoCube, keyfigures are different.
In the ACTUAL one, we have only cost center and profit center as navigational attribute. In plan, we have both. Here is the fox (operand is KF, infoprovider, profit center) :
{KF1, ACTUAL, PC01} = {KF3, PLAN, #}.
I doesn't work in IP (no data are read from the reference). We tested it in BPS and it works.
For me, this is the right syntax since profit center is not is the ACTUAL cube.
After that, we removed profit center from the operand (PC01 is a constant in the filter).
Here is the new fox (operand is KF, infoprovider) :
{KF1, ACTUAL} = {KF3, PLAN}. This fox is not supposed to work because it should try to read reference data with profit center PC01. But it works !!!
After saving data, we noticed that the fox copies every records from the ACTUAL cube with navigational attribute profit center = PC01.
Did you ever experience that or I missed something ?
The system seems to take into account the value of the navigational attribute.
Thanks

Hi Jaques,
I guess you have a MultiProvider and you have mapped the Characteristic PC from the plan cube and the navigational attribute from the actual cube both to the characteristic in the multiprovider.
Then it is correct, that the sytsem does the selection on the char in plan and the nav in actual.
regards
Cornelia

Attributes & Navigation attributes

Hi experts,
I want to know why do we use attributes and navigation attributes in demand planning?
Please explain with some example.
Regards,
Umesh

Hi Umesh,
Please check below 2 links and
if you have any further question , please let us know .
Manish
Attributes & Navigation attributes
http://help.sap.com/saphelp_scm50/helpdata/en/80/1a63e7e07211d2acb80000e829fbfe/content.htm

Integrated Planning on Navigational Attribute

Hello Experts ,
We are using BI 7.0 integrated planning.
We have a Report that is input enabled on Service . Service info Object is a characteristics in the info provider and is in the rows area of the Report . Input enabled was fine .
But I would like to bring Service which is navigational attribute of Fund center ie 0funds_ctr-bservice in the report(rows area) and want to plan against that service.
But when I bring this navigational attribute , now the query is not enabled for input . Do i have to any thing else in the Planning to make it input enabled .
Any ideas please .
Thanks

Andrey, indu,
Thanks for your reply.
Andrey,
I have put navigational attribute(Service) in the rows area and restricted with a variable . Still query is not enabled.
The query is not enabled as soon as i select Fund center in the Aggregation levels in IP.
If I remove(un check) fund center in the aggregation level , the query is input enabled . But i got to enable Fund center at aggregation level so that I can bring in Navigational attribute(service) of func cener.
Any ideas please .
Thanks

Use of planning characteristics vs navigation attributes in APO DP

I am using APO DP V5.
I have a product characteristic.
Products are grouped into 'product groups'.
I want to be able to run stat forecasts at the 'product group' level, and also adjustments via key figures at the 'product group' level.
For the 'product group', I could set up a planning characteristic or a navigation attribute.
What are the pros/cons of setting up a planning characteristic or navigation attribute, bearing in mind the need to forecast and make adjustments at this level?
Thanks in advance...

Hi,
The pros for using navigatyion attribute are quite easy: it will give you far more flexibility.
For example in case of change of hierarchy, you will not need to run realignment.
It simplify in the same way the data loading.
Now the cons: there is still some limitations: you can without any problem run stat forecast and adjustment for a navigation attribute. The only limitations I can remember are for promotion and store the assigment of a forecast profile to a selection (see /SAPAPO/MSDP_FCST2 - Assign Forecast Profiles to a Selection ).
this point might, or not, be the issue for you: do you plan to use the automatic forecast profile selection? If yes, then I suggest you to test it with navigation attributes; but as far I know it will fail. (note: I think there is workaround with a badi implementation, but can't remember which one now)
I hope it helps
Julien

Integrated Planning - No ability for restrictions on Aggreg. Level ?

Hi there,
I have noticed in the new Integrated planning that it is only possible to restrict data at the filter level.
In comparison to the old BPS, where you could restrict data at both the Planning Level and Planning package is this not a slight reduction in functionality ?
This will mean that it will be necessary to repeatedly assign variables / static restrictions to many filters which have similar selection criteria rather than maintaining them once at the Aggregation Level
Does anyone know if it is envisaged that selection will be possible on aggregation levels in upcoming support packages?
thanks
Mark

Hi SR,
thanks, so it will be available in BI 7.1 ? (which is SP12 isnt it?) or in a later release ?
Many thanks.
Mark

Using navigation attributes in planning queries

Hi all!
In one of the SAP demos I saw something like: we've got a "Store" char in planning query, and Region, Format and Climate added as free characteristics. Region, Format and Climate are navigation attributes of the Store characteristic. And when user drags, for example, Region into the planning table, he or she can enter the values on region level, and when saving the data it's being automatically distributed by all the Stores that have that Region as an attribute.
I have a somewhat similar task - I have a "Branch" characteristic that has "Country" as a navigation attribute. I have to plan data for that navigation attribute, the country, and I expect the data to be distributed by all the branches that have that country as an attribute. But when I add it to the planning query, I've got repeating rows for each branch in each country even though I don't see the branches.
What should I do to accomplish this task?
Thanks!
Best regards,
Andrey

Hi Gregor!
Thanks a lot for your help!
It's almost working as I want it to work.
But there's something I'm probably doing wrong.
I'm selecting B as a "free characteristic" in the query and hide it, and put B__C in the rows section, then choose "Master Data" for both "Access Type for Result Values" and "Filter value selection..." for both characteristics. After that I execute the query and see that everything seems to be as it should be, and after I enter data for something, it automatically distributes by the branches that have that country as an attribute.
That's weird. Because when I do as you told me to, using the flag "Characteristic Rel-ps" for "Access Type for Result Values", put B__C and B in rows (B is hidden) and execute the query, I get multiple repeating rows for each branch that has the selected country as an attribute. And system tells me that "3 characteristic combinations generated successfully" (that is correct - I have 3 branches for the selected country).
I've tried setting "Char rel-ps" for both of the characteristics, then for only one each of them - and I still get the same picture.
Could you please tell me what I might be doing wrong here? And why it seems to be working with "Master data" chosen for "Acc. type for result values"?..
Thanks!
Best regards,
Andrey
Edited by: Andrey Makeev on Feb 3, 2012 6:45 AM

APO Demand Planning - Navigational Attributes BADI

Hi,
I have an issue in that I need a Navigational Attribute to be able to store the GUID for a Forecast Profile to a Selection. In standard, only a selection with Key Characteristics can do this. It is not practical for us to use a Key Characteristic because the realignment would take to long therefore it needs to be a Navigational Attribute.
Having read the note "Use of planning characteristics vs navigation attributes in APO DP " dated 19/10/2009 in SAP Solutions » SCM - APO Forum, it indicates that there is a BADI work around to enable this to be done but cant remember which one.
Does anyone know the BADI can be used to achieve this?
Thanks
Mark

Prabhat
Please refer to OSS note 413526 for a comparison of Navigational Attributes v/s basic characteristics. While most planning tasks can be done with navigational attributes there are a few limitations.
Rishi Menon

Create restricted key figure with navigation attributes

Hi,
I need to create a restricted key figure using attributes of 0BP_COMPET.
On my report is :
Competitors (0BP_COMPET)
Quantity
Active Competitors = Expiry Date of Minority Status greater than or equal to system date
Inactive Competitors = Expiry Date of Minority Status less than to system date
Note : Expiry Date of Minority Status is a navigation attribute of 0BP_COMPET and system date is generate by variable 0DAT - Current Calendar Day (SAP Exit).
How can i apply the formula?
Thanks

Here's a good How to Document that explains what you are trying to do ....
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/72f4a790-0201-0010-5b89-a42a32223ffc
It is called How to.... Calculate with Attributes.
Brian

Navigational Attribute Problem in Input Query

Hi,
I am having a problem in input query implementation which uses a navigational attribute. I have, for eg, only one char 'customer' in rows; i want to exclude the customers with the status D (deleted) from displaying (Status is nav. attr. of customer). I tried this by restricting in filter, Status D-"exclude". But as soon as I do this, query no longer remains input ready! (I also tried putting the same restriction in Default Values area rather than Filter, but ended with the same result )
I discovered that if, furthermore, I put Status in rows (with the above said restriction still remaining), query is again input ready.
Can't we exclude values in the filter on an input query? I want to know if this is a restriction with IP or a bug?

Hi Gregor,
Thanks for the explanation. But this makes me wonder, because due to this restriction one of the BIG advantages queries had over the planning layouts of BPS, seems to be gone. I mean, using navigational attributes for filtering; if we have to always have a single value restriction on a nav. attr., this will really be restricting. Is it expected that this will be changed in a later SP?
And there is another problem that is coming due to this. When I use the exclude filter and also the nav. attr. Status in rows, then the query becomes input ready, but there are warning messges displaying when the query opens saying -
Characteristic Customer has no master data for "C1"
Characteristic Customer has no master data for "C2"
etc... (these are the customers with status D). We are on SP15.
Please suggest what should I do to get rid of these messages?
Edited by: Mayank Gupta on Apr 10, 2008

Selection of charateristic value by using a navigational attribute

Hello all.
I'm working on BW 2004s with the integrated planning. I have this case: 0material has a navigational attribute - 0customer.
I have a variable on the navigational attribute (ocustomer) which prompts the user to select a customer. on the next step I would like to allow the user to forecast the values for the customer's relevant materials. this issue has a problem - since a BEx query acts as a filter - and if there's no suitable data in the cube - I won't be able to see the values in the rows so the user can perform planning.
Do any of you experts have a suggestion regarding a solution to that issue?
Thanks,
Tomer.

Tomer,
As Andrew suggested what you would need is "Master Data" option as compared to "Posted Values" option.
Hope this helps.
Cheers
Srini

Restrict on Navigation attribute in Integrated Planning

Similar Messages

Maybe you are looking for