Create Navigational attribute from R/3

Hi All,
I have got requirement for one cube...
"Create Navigation attribute from R/3 CCIHT_IA-DAT as Year, Month and YYMM with selection variable, range, optional"
What does that mean ? how to create attribute from R/3 ?
can anyone give me the steps ?

Looks like this is a generic datasource (Z* object). Look at definition of the datasource in RSO2 and see how the data is extracted. If the extract structure is built of a VIEW, then check if the view has the required table that has CRDAT???
If yes, then add CRDAT as a field to the datasource, unhide it and start the extraction. Else add this table to the view, define proper join conditions (if possible) and then include CRDAT in the extract structure. Once this is done, map CRDAT to a corresponding field in BW (0calday or Zcalday) in the transfer structure of the infosource. Hope this helps.

Similar Messages

  • Read Navigational Attribute from Mulitprovider

    Hi Gurus,
    I need to read a navigational attribute from the Multiprovider in the user exit.  Could you please tell me in detail with coding how to do this ?

    Hi,
    Navigation attributes data exists in master data and not in multiprovider. If you want to use navigation attribute value in EXIT then check which is the base Infoobject and read the Infoobject table, from there you can read the value of required attribute.
    Regards,
    Durgesh.

  • How to create OID attributes from command line in unix system

    Hi,
    I have to create OID attributes through ldif files in unix system. I dont know how to run it in unix system under which folder. I already have ldif files for creating OID attributes. Please help.

    Hi,
    unser the /your_ODI_HOME/agent/bin folder.
    Excute this
    sh startscen.sh REFRESH_ID 001 GLOBAL 5 -NAME=agent_ODI
    REFRESH_ID=Your Scenario name
    001:Version
    GLOBAL:Context name
    5=Log Level
    agent_ODI=Your agent name
    Regards

  • Cannot access Created Context Attribute from Component Controller

    Hello All,
    I have added a new attribute to a node in my component controller 'LOGONUID' and I cannot access it within my windows within the WDA application.
    DATA lo_nd_url_param TYPE REF TO if_wd_context_node.
      DATA ls_workset TYPE wd_this->element_workset.
      "DATA ls_logonuid TYPE wd_this->element_logonuid.
    I get an error as soon as I try to activate this code in my method in my W_MAIN
    In my component controller I do not see it reference in the SAP generated code in my WD_THIS IF_COMPONENTCONTROLLER?
    * Intf.: ig_componentcontroller
    * Purp.: programming interface for access of this controller within
    *        other controllers of the same component
    *        controller:  <COMPONENTCONTROLLER> of
    *        component:   <zhr_wd_mss>
    * UDate: 20111207 145441
    *=====================================================================*
    interface ig_componentcontroller.
      interfaces: ziwci_hr_wd_mss .
      constants:
        wdctx_context type string value `CONTEXT`.
      constants:
        wdctx_cuifcontext type string value `CUIFCONTEXT`.
      types:
        begin of Element_cuifcontext,
          USERID  type String,
          LASTEVENTOPERATION  type String,
        end of Element_cuifcontext,
        Elements_cuifcontext type
           standard table of Element_cuifcontext
           with default key.
      constants:
        wdctx_messages type string value `MESSAGES`.
      types:
        Element_messages type ZHR_S_MESSAGE,
        Elements_messages type
           standard table of Element_messages
           with default key.
      constants:
        wdctx_workset type string value `WORKSET`.
    I want it to be declared as the constant 'WORKSET'
    thank you
    Edited by: Keith Warnock on Dec 7, 2011 8:55 PM
    Edited by: Keith Warnock on Dec 7, 2011 8:56 PM

    > I have added a new attribute to a node in my component controller 'LOGONUID' and I cannot access it within my windows within the WDA application.
    >
    >
    >
    > DATA lo_nd_url_param TYPE REF TO if_wd_context_node.
    >   DATA ls_workset TYPE wd_this->element_workset.
    >   "DATA ls_logonuid TYPE wd_this->element_logonuid.
    >
    > 
    >
    This declaration is not right. There is no element logonuid, you  have the attribute inside a node. workset is a node and thats why you can declare that way.
    easiest way is to declate
    data lv_logonuid type <ddic type> or
    data lv_logonuid type wd_this-><node name>-logonuid.
    You can also use the code generator in (CTRL +F7 ) to get/set attributes.

  • Virtual infoprovider with services - Navigational attributes

    Hi all,
    I have a basic cube in BI system- X , and created a virtual cube in another BI system Y with services to read data from basic cube of BI system X . In BI system Y we built a report on virtual cube. This report (on virtual cube in BI system Y) is using a characteristics say Product group ( which is a navigational attributes of prodect in BI system X).
    DataFlow is as under:
    Basic cube in BI system X:
    Product
    Year
    Amount
    and Product group is switched on as navigational attributes in this basic cube.
    Virtual cube in BI system Y:
    Product group
    Year
    Amount
    Report in BI system Y:
    Product group in rows
    Amount in column
    This report is not working.
    If I do the the following changes as follows then it works:
    1.Use Product instead of product group in report
    2. Switch off navigational attributes in basic cube.
    We are in BW 3.5 and navigational attributes option is ticked on for virtual cube.
    In summary, If I do not use navigational attributes in report and switch off navigational attributes from basic cube then report shows data.
    Could you please help me to figure out the issue.
    Thanks,
    Harry

    Thanks Naga,
    Yes, I tried adding product in virtual cube as well but it did  not work. Secondly, we do not want to add product in virtual cube because of data aggregation.
    Most strange thing is that, once we switch on any navigational attributes on basic cube, function module stop working (paasing any data to virtual cube report). report says no appropriate data found. We are using sap standard function module "RSDRI_INFOPROV_READ_RFC". I debegged this code and no data in internal tables.
    If we switch off all  navigational attributes from basic/source cube this function module provide data to internal tables in code.
    Why function module is behaving like that.
    You guys experience/support/any clue will be appreciated highly.
    Thanks,
    Harry

  • Navigational Attributes in InfoSets[based on InfoCubes] - BI 7.0

    Hi Gurus,
    I am using BI 7.0. We tried creating a MultiProvider based on three SD Cubes[Orders/Billing & Delivery] but since the result was being displayed in 3 rows instead of 1, we tried using an InfoSet to see if this would get the results to be displayed in a single line.
    In the MultiProvider, we had mapped some of the 'Navigational Attributes' from the underlying InfoCubes after turning them 'ON', but in the InfoSet, I am not able to view the Navigational Attributes of the Cube anywhere.
    Are we not able to add 'Navigational Attributes' to InfoSets? Is there a work around for this?
    Thanks
    Arvind

    Hi Arvind,
    Check note 1124036 @ www.service.sap.com . Check if you need to apply this.
    Also you can add infoobjects themselves in the infoset and join them by keys.
    Regards,
    Sunmit.

  • Navigational Attribute in Reporting

    Hi experts,
    Suppose I have created one attribute as navigational attribute in my infoobject characteristic.This Characteristic is in Infocube.
    Now after executing query on this infocube,Can I drilldown from thic characteristic to Navigational attribute to analyse my results more?To achieve this,is it necessary to Switch On my navigational attribute in Infocube?or Can I achieve this even without switching navigational attribute in my infocube?
    rgds,
    P Olin

    Hi experts,
    Thanks for your replies.
    Suppose if I donot want to create Navigational Attribute,how can I do technically,so I can drilldown to this characteristic from my original characteristic infoobject in the report to see more analysis...
    I am thinkiing of creating hierarchy manually from top to bottom by creating one characteristic and adding it as 'external characteristic' in hierarchy tab of my infoobject characteristic which has this hierarchy..Is this an option?Can I still drilldown and see detailed analysis in my reports?
    Thanks for your replies.
    P Olin

  • Navigational Attribute Clarification

    Hi all,
    I have gone  thru the forum for this concept.
    Still i have little bit confusion on this.
    Wat i understood is, Nav Attr behaves like a characterstic in Reporting, wat my doubt is instead of creating Nav Attr why don't we go for Creating that as a characterstic.
    If we create a field as a navigational attribute from where it fetches the data during the reporting.
    If i created a fiels as a characterstic from where it fetches the data during reporting.
    Please
    Regards,
    Madhu

    Hi,
    A NAV is already a characteristic.
    I believe that your question is more: why don't we store the characteristic directly in the InfoProvider instead of reporting on a NAV.
    Suppose you sell articles (the basic char; CAMCORDER XYZ)
    Suppose each article has an attribute "STATUS" = LIVE or DISCONTINUED.
    Now you load your sales in a sales cube; you post the selling date, the article ID and it's status. When the article has been just listed (in JAN) to your shop it has the status LIVE, so you'll post something like
    JAN__CAMCORDER XYZ__LIVE__$100
    Now the status is set to discontinued by a buyer in FEB. Still you sell the remaining pieces:
    FEB_CAMCORDER XYZ_DISC_$2000
    Interesting to see that your cube can tell the turn over of this CAMCORDER depeding on its status over time.
    Now the buyers might be interested to report only on LIVE articles.
    Obviously filtering a query on STATUS = LIVE will still show $100 turn over in JAN, even if the article is now discontinued.
    This is when the NAV enters into the into the game. If you enable the attribute STATUS as NAV of MATERIAL in your provider and filter you query ON MATERIAL__STATUS = LIVE, the CAMCORDER XYZ won't show up anymore.
    just adding: during reporting, the X table of your basic char will give the SID of your NAV. Reporting with NAV add joins between tables, which can impact performance if not tuned properly.
    hoping this clear you doubts...
    Olivier.
    Edited by: Olivier Cora on Apr 9, 2008 10:10 AM

  • Adding navigational attribute in multiprovider

    Dear All,
    I've created multiprovider.  When I try to drag and drop the navigational attribute from the infoprovider available in the multiprovider to the navigational attribute folder, it does not move so.  Please tell me how to add navigational attribute, dimensions in the multiprovider.
    Plz reply soon as possible...
    with Regards,
    Jerald

    Hi ajerald.89
    You need move first the Characteristic. the navigational atribute will be add automatic.
    this question is about BW, maybe you need select much better the forum on the next time.
    regards.

  • Transports issue regarding navigational attribute

    Hi,
    I used to have some navigational attribues in somecubes and Multiprovider but as per the latest requirement from the customer again converted them as display attributes in masterdata so that automatically removed from cubes and multiprovider with out even our interventions as we know..
    So assigned to transport request and transporting into further systems then we r getting error as
    "Navigation attribute XYZ  does not (actively) exist
    Message no. R7748"
    but when i do check of cube it does not give any error but when i am transporting it is again loooking for those navigational attributes in target system..
    I am not sure why it is giving problem like this ...Just i am guessing is it because i did not remove navigational attribute flag first from cube instead of just master data directly ...but that should not be a problem as per my knowledge...
    Can any experts reply to me asap if you come accross this kind of problem ....
    Thanks & Rgards,
    BRK

    Editted as I understand the solution now.
    If you want to delete navigational attributes from a multi provider, cube and master data it needs to be done in the order:
    - remove navigational attribute from MultiProvider
    - remove navigational attribute from Cube
    - set navigational attribute to be display attribute on InfoObject
    If you don't follow this order e.g. just set navigational attribute to be a navigational attribute on master data then you get problem where every time you transport cube it says nav. attribute is inactive even though (as far as you can see) the nav. attribute does not exist.
    btw, if you have dug yourself into a hole then you need to re-create the navigational attribute on the InfoObject and then add it back to the cube and multiprovider - transport this and then follow correct order.
    Edited by: Mark Roberts on Oct 15, 2008 6:49 PM

  • Using navigational attributes in selection for a forecast profile

    Hello All,
    I could understand that the forecasting can be done on navigational attributes.
    But when I goto transaction /SAPAPO/MSDP_FCST2, I could not create a selection on navigational attribute.
    Because I could not see the navigational attribute field in the selection screen for selection criteria/profile creation.
    Does anyone have any idea of how to do this?
    Also I saw the method SEL_CHANGE of BADI /SAPAPO/SDP_FCST5. But the documentation is confusing, since it says that using this method, we could delete the navigational attributes from the selection condition. Could any one suggest me how to use this BADI if I cannot create a selection with navigational attribute?
    Thanks,
    Suresh

    Hi Sunitha,
    Thanks a ton for your reply.
    The real problem is the OSS note is confusing.
    OSS Note for this method says "This method can be used to change the selection to be stored in
    in the generated selection table. Navigation attributes can be removed, such as the function of assigning a forecast
    profile to the selection can also be allowed for selections with navigation attribute without a basic characteristic."
    I am really confused what it says.
    If we can't create a navigational attribute for a selection, how could we delete it from a selection?
    Thanks,
    Suresh

  • Navigational Attribute data is not display in Cube level and reporting

    Hello ALL
    Iam facing a problem like,I created Navigational attribute and I selected that navigational attribute in cube level also but data is not display in cube level.
    What will be the problem?Pl help me out.
    regards
    balaji

    Hi Dinesh
    You mean base characteristic means loading data after creating Navigational attribute?Is it this way,(orelse can u tell me about this base characterstic)
    Yes after making that particular attribute as a navigational attribute I loaded data in master data tables.
    How to run Attribute change run?can u give me steps
    regards
    balaji

  • 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

  • Navigational Attributes are not shown in query

    Dear all,
    I have a problem in a query. I need to present values using by using Navigational attribute in the query, the thing is that it does not recognize my navigational attribute. I have checked the characteristic in the Multiprovider and Infocube as navigational. And in the Multiprovider I have identified the navigational attribute from the right source.
    What I think is strange is that I can see the navigational attribute when I see the data in infocube but not in the query. Does anyone knows what I might be doing wrong?
    Best Regards and many thanks,
    Mazzz

    Hi
      plese try to find out the data for this fields through LISTCUBE,if you gets data here for that navigation attr then it has to appear in your query designer also.
    and also once again check your idetification for the navigation attr in multi provider  whether its taken from write souce or not.and plese chk through your cube also for the navigatin.
    in cube navigational attr has to mark then in the same way in the multi provider also
    mahesh
    Edited by: Mahesh Kumar on Jun 2, 2008 10:47 AM

  • Question on navigational attribute ?

    Hi all ,
    we have turn-off some navigational attributes from 0MATERIAL ,
    my questin is is it necessary to reload the full data or not ?
    or
    is it enough to run the attribute change run ?
    Thanks

    When you turn on Navigation Attributes , the additional fields are included into the X and Y tables and hence especially when you transport these changes to an IOBJ which is very large - you will need to make sure you have enough undo table space etc..
    The same this applies to removing Nav Attributes... the X and Y tables will get rebuilt and if the IOBJ is very big - I would recommend taking additional precautions like monitoring unto tablespaces etc when transporting the same.
    Also as an additional step - run the attribute change run once the transport is done - you need not reload any master data.

Maybe you are looking for