Attibute mapping not defined for Hierarchy

Hi
I keep getting the above error message when trying to
access a cube - why?
I have validated the dimensions and cube and everything looks fine. I have created an AW based on the cube using AWM. But if I try to access the cube through BI Beans or OEM Cube Viewer I get the same error messages.
Below are some samples of the code used to create the dimensions:
CREATE DIMENSION nperd.BILLING_ITEM
LEVEL BILLING_ITEM IS DIM_BILLING_ITEM.BILLING_ITEM_ID
LEVEL BILLING_ITEM_TYPE IS DIM_BILLING_ITEM.BILLING_ITEM_TYPE
LEVEL BOOKING_GROUP IS DIM_BILLING_ITEM.BOOKING_GROUP_ID
LEVEL BOOKING_GROUP_TYPE IS DIM_BILLING_ITEM.BOOKING_GROUP_TYPE
HIERARCHY BILLING_ITEM (BILLING_ITEM CHILD OF BILLING_ITEM_TYPE)
HIERARCHY BILLING_ITEM_BOOKING_GROUP (BILLING_ITEM CHILD OF BOOKING_GROUP CHILD OF BOOKING_GROUP_TYPE)
ATTRIBUTE BILLING_ITEM DETERMINES (DIM_BILLING_ITEM.BILLING_ITEM_ID , DIM_BILLING_ITEM.BILLING_ITEM_NAME)
ATTRIBUTE BILLING_ITEM_TYPE DETERMINES DIM_BILLING_ITEM.BILLING_ITEM_TYPE
ATTRIBUTE BOOKING_GROUP DETERMINES (DIM_BILLING_ITEM.BOOKING_GROUP_ID , DIM_BILLING_ITEM.BOOKING_GROUP_NAME )
ATTRIBUTE BOOKING_GROUP_TYPE DETERMINES DIM_BILLING_ITEM.BOOKING_GROUP_TYPE ;
begin
cwm_olap_dimension.set_plural_name('NPERD', 'BILLING_ITEM', 'BILLING_ITEMs');
cwm_olap_dimension.set_display_name('NPERD', 'BILLING_ITEM', 'BILLING_ITEM');
cwm_olap_dim_attribute.create_dimension_attribute('NPERD', 'BILLING_ITEM', 'BILLING_ITEM_ID', 'BILLING_ITEM_ID','');
cwm_olap_dim_attribute.create_dimension_attribute('NPERD', 'BILLING_ITEM', 'BILLING_ITEM_TYPE', 'BILLING_ITEM_TYPE','');
cwm_olap_dim_attribute.create_dimension_attribute('NPERD', 'BILLING_ITEM', 'BILLING_ITEM_NAME', 'BILLING_ITEM_NAME','');
cwm_olap_dim_attribute.create_dimension_attribute('NPERD', 'BILLING_ITEM', 'BOOKING_GROUP_ID', 'BOOKING_GROUP_ID','');
cwm_olap_dim_attribute.create_dimension_attribute('NPERD', 'BILLING_ITEM', 'BOOKING_GROUP_NAME', 'BOOKING_GROUP_NAME','');
cwm_olap_dim_attribute.create_dimension_attribute('NPERD', 'BILLING_ITEM', 'BOOKING_GROUP_TYPE', 'BOOKING_GROUP_TYPE','');
cwm_olap_level.set_display_name('NPERD', 'BILLING_ITEM', 'BILLING_ITEM', 'BILLING_ITEM');
cwm_olap_level.set_display_name('NPERD', 'BILLING_ITEM', 'BILLING_ITEM_TYPE', 'BILLING_ITEM_TYPE');
cwm_olap_level.set_display_name('NPERD', 'BILLING_ITEM', 'BOOKING_GROUP', 'BOOKING_GROUP');
cwm_olap_level.set_display_name('NPERD', 'BILLING_ITEM', 'BOOKING_GROUP_TYPE', 'BOOKING_GROUP_TYPE');
cwm_olap_level_attribute.set_name('NPERD', 'BILLING_ITEM', 'BILLING_ITEM', 'BILLING_ITEM_ID', 'BILLING_ITEM_ID');
cwm_olap_level_attribute.set_name('NPERD', 'BILLING_ITEM', 'BILLING_ITEM_TYPE', 'BILLING_ITEM_TYPE', 'BILLING_ITEM_TYPE');
cwm_olap_level_attribute.set_name('NPERD', 'BILLING_ITEM', 'BILLING_ITEM', 'BILLING_ITEM_NAME', 'BILLING_ITEM_NAME');
cwm_olap_level_attribute.set_name('NPERD', 'BILLING_ITEM', 'BOOKING_GROUP', 'BOOKING_GROUP_ID', 'BOOKING_GROUP_ID');
cwm_olap_level_attribute.set_name('NPERD', 'BILLING_ITEM', 'BOOKING_GROUP', 'BOOKING_GROUP_NAME', 'BOOKING_GROUP_NAME');
cwm_olap_level_attribute.set_name('NPERD', 'BILLING_ITEM', 'BOOKING_GROUP_TYPE', 'BOOKING_GROUP_TYPE', 'BOOKING_GROUP_TYPE');
cwm_olap_dim_attribute.add_level_attribute('NPERD', 'BILLING_ITEM', 'BILLING_ITEM_ID', 'BILLING_ITEM', 'BILLING_ITEM_ID');
cwm_olap_dim_attribute.add_level_attribute('NPERD', 'BILLING_ITEM', 'BILLING_ITEM_TYPE', 'BILLING_ITEM_TYPE', 'BILLING_ITEM_TYPE');
cwm_olap_dim_attribute.add_level_attribute('NPERD', 'BILLING_ITEM', 'BILLING_ITEM_NAME', 'BILLING_ITEM', 'BILLING_ITEM_NAME');
cwm_olap_dim_attribute.add_level_attribute('NPERD', 'BILLING_ITEM', 'BOOKING_GROUP_ID', 'BOOKING_GROUP', 'BOOKING_GROUP_ID');
cwm_olap_dim_attribute.add_level_attribute('NPERD', 'BILLING_ITEM', 'BOOKING_GROUP_NAME', 'BOOKING_GROUP', 'BOOKING_GROUP_NAME');
cwm_olap_dim_attribute.add_level_attribute('NPERD', 'BILLING_ITEM', 'BOOKING_GROUP_TYPE', 'BOOKING_GROUP_TYPE', 'BOOKING_GROUP_TYPE');
cwm_olap_hierarchy.set_display_name('NPERD', 'BILLING_ITEM', 'BILLING_ITEM', 'BILLING_ITEM');
cwm_olap_hierarchy.set_display_name('NPERD', 'BILLING_ITEM', 'BILLING_ITEM_BOOKING_GROUP', 'BILLING_ITEM_BOOKING_GROUP');
cwm_olap_dimension.set_default_display_hierarchy('NPERD', 'BILLING_ITEM', 'BILLING_ITEM');
commit;
     CWM2_OLAP_METADATA_REFRESH.MR_AC_REFRESH;
     CWM2_OLAP_METADATA_REFRESH.MR_REFRESH;
end;

Can you please tell what was the solution? We are facing same problem

Similar Messages

  • My app went from working fine to: Id field not defined for cfc Path.to.my.ORMCfCPag when I restarted

    Hi everyone,
    I have a CF9 ORM problem that I haven't been able to figure out and thought I'd see if you had any idea. I have seen a few postings talking about a "similar" problem but none of them correctly resolved this particular issue. I appreciate any help you can offer.
    I recently created a CF9 app where I generated scripted ORM CFCs for my app using ColdFusion Builder. It worked great and my app was completely working. However, when I was adding some enhancements, I ran into an error when I restarted the CF app server. Here's the message I keep getting:
    "Id field not defined for cfc Path.to.my.ORMCfCPage. Either the table should have a PK column mapped to a cfc field OR at least one field should be specified as id."
    My App.cfc file only had orm enabled (no other mappings) when it was working. I've since tried specifying things like the cfc location etc. and it still hasn't helped.
    // MORE DETAILS:
    - When my app was working, I had moved it to 2 other servers. I had this error on both of those but not on my local copy. They all use the exact same database.
    - The last change I made before the error was adding a generator="identity" field to my generated ORM beans. Once I got the message, I tried changing it back and restarting again but still got the error.
    - I've also made sure all of the Adobe tags are in my web root (as suggested in a prior posting about this problem). I've search all over for a solution and nobody has a solution posted online that works so far.
    Do you have any idea why this is happening?
    Thanks!
    Jeff

    Quick thought and probably not relevant, but do you have this.ormsettings.savemapping set to true in your Application.cfc? I've fallen foul of this before - once CF has generated the hbmxml files and saved them to disk you can make all kinds of changes to your code which won't make a difference as it'll continue to read from the file versions, but only for certain properties and methods at times it seems.
    Long shot I know, but I found CF ORM to be a nightmare for seemingly random caching.

  • VERSION 0 IS NOT DEFINED FOR FISACL YEAR 2007,

    i am learning SAP PP and i hv ides 4.7,
    now WHEN SAVING ORDER i.e DURING COST CALCULATION I GET A MESSAGE THAT VERSION 0 IS NOT DEFINED FOR FISACL YEAR 2007,
    ON ANALYSING IT LEADS TO T.CODE OKEV BUT HERE SYSTEM DOES NOT PERMIT TO CHANGE THE VERSION, BUT IN ECC 5.0 IT ALLOWS ,
    WHAT IS THE PROBLEM, CAN ANY ONE PL. HELP ME,
    analysis of error gives following message:
    Activation of the indicator is not permitted
    Message no. KT253
    Diagnosis
    You activated an indicator (Plan, Actual, WIP/results analysis or Variance calculation ) in the basic settings for version 1 in controlling area 1000. However, a higher order of settings (general version definition) prevents you from setting this indicator in version 1.
    Note
    The following should be taken into account when maintaining a version:
    In general version definition you decide whether a version is allowed for
    •     Panning (with the Plan indicator)
    •     Actual data update (with the Actual indicator)
    Note: In Overhead Cost Controlling, actual data is updated in operational version 0.
    Actual versions different from 0 are found at present only for delta versions in Activity Based Costing (CO-ABC), and when you work with parallel assesment ( additional versions):
    •     A data version from results and WIP determination manages (indicator WIP)
    •     Another version from variance determination manages (indicator Variance)
    •     A version for exclusive use (field exclusive application)
    You must maintain the version basic settings for each controlling area in which you want to update transaction data. General version definition restricts the settings possible for the controlling area:
    •     If general version definition does not allow plan and/or actual data update for version, this applies to the version in all controlling areas. If plan and/or actual data updating is allowed for a version in general definition, this can be reset for each controlling area separately (unmark the plan or actual indicator).
    •     Delta versions in ABC may not be used for parallel valuations in the actual; the same goes for versions with exclusive applications. In both cases, the valuation fields may not be maintained.
    To set indicators WIP/Results- or Variance-determination the following conditions apply:
    •     Both indicators may be set only during setup for the controlling area, when they are already established in the higher level general version definition
    •     If either indicator is already active in the data bank, then the actual indicator may not be subsequently activated
    •     If the actual indicator is inactive and either of these indicators is active, then the valuations in the corresponding versions and in version "000" must agree
    •     If the actual indicator is active, then both indicators must be activated
    Versions 0 and 1 are used regularly for various purposes by the system, which sets the following limitations/restrictions:
    •     Version 0 must always be available. It cannot be used exclusively. The plan and actual indicators must always be active.
    •     The actual indicator may not be activated in version 1.
    If these conditions are violated during version maintenance, error messages are issued. There are three types of error message:
    1. While maintaining the general version definition, you can only make changes if they do not violate the conditions outlined above.
    2. While maintaining the basic settings in the controlling area, the entries must remain consistent with the higher level entries.
    3. You want to maintain version 0 or 1. The restrictions outlined above apply.
    Use the "Extras" menu option to display the structure of the entries in the complex data object version:
    •     Select a version and choose Extras -> Version use.
    The SAP System shows which controlling areas use this version.
    •     Select Extras -> Versions in CO area
    This displays all versions used in the current controlling area.
    The subordinate entries in the hierarchy (settings for each fiscal year, strategic Activity-Based Costing: transactions for a delta versions) will also be shown for both cases.
    Procedure
    Do not activate the indicator, or change the higher order of settings in the general version definition.

    Raj,
    What are you trying to change?
    To me you are not suppose to make any changes, you need to select the version "0" and then hit "Settings for each Fiscal year" subfolder.... here you copy the settings of 2006 and change the year to 2007. This should resolve the problem.
    Regards,
    Prasobh

  • Payment order are not defined for extended withholding  tax

    Hi Gurus,
    Would you please help me with the message below. It appears on F110 when I try to pay a vendor open item with extended withholding tax:
    Message FZ626 -Payment orders are not defined for extended withholding tax
    In my company payment orders are created in F110 for accounts payable, as we use another ERP system (Baan) to perform the local accounts payments, and now I've just activated Extended withholding tax functionality With accumulation (necessary in Brazil) but I get this error.
    Is it not possible to user payment order with extended withholding tax + accumulation? I find it hard to believe...
    I've tried to unflag the payment order only for the payment method I'm using in FBZP t.code, but then no payment order were created but instead a payment document were posted with the withholding tax accumulation, but this is not the way we are working, and nothing is sent to Baan
    any help is welcome

    The payment method "Y" the option "payment order only" was marked?
    For a withholding tax type with accumulation in a company code with extended withholding tax payment
    methods that create only payment orders can´t be used. Payment orders can only be created only if there are
    no tax types with accumulation involved in the paid items of the payment run.
    The functionality extended withholding tax works fine for Brazil
    however, you can´t use the payment order with this functionality.
    Please, review your customizing for payment method 'Y" in transaction
    FBZP.
    Best regards,
    Leonardo Vedovelli
    FI Support Engineer
    SAP Active Global Support

  • Error : Excise modvat accounts not defined for GRPO transaction and U1 exci

    I have Created Impot PO, After Planned Delivery cost MIRO I am trying to Perform GR then its giving Error "Excise modvat accounts not defined for GRPO transaction and U1 excise group
    Message no. 8I402"
          I have already maintained GL account in "Specify G/L Accounts per Excise Transaction" for Excise group U1
          This problem is coming when Additional Duty on custom condition type JADC is maintained in "Maintain Excise Defaults" node in the column "ADC Cond" . If I remove JADC condition type from this place the this error is not coming but AED column is not fetching any value while doing GR.
    Please help me in this issue , still No answer
    Edited by: shiwanshu singh on Jan 28, 2009 10:26 AM

    Dear sir
    For GRPO have you maintained sub transaction Type IP for your excise group U1. If you not maintained pl maintain . and assign G/L account to modvat clearing account , the G/l account should be same as company code CVD account.
    Regards
    jrp

  • ERROR in MIRO : An exchange rate type is not defined for country IN

    Experts:
    When I try to enter the invoice received from the vendor, I am getting the following message.
    An exchange rate type is not defined for country IN
    Message no. FF802
    Can anyone provide me a solution for this?
    Thanks,
    Vijai

    This is the explanation given in note 974619 for the above error message
    Summary
    Symptom
    When you post an FI document, the system issues error message FF 801 or FF 802.
    Other terms
    Plants abroad, FF 801, FF802
    Reason and Prerequisites
    You use the 'Plants abroad' function.
    See Note 882132 for more information about this.
    Solution
    If the 'Plants abroad' function is active, additional fields appear when you maintain the country global parameters (transaction OY01, table T005):
    - Country currency       (Field WAERS)
    - Exchange rate type     (Field KURST)
    - Net discount base      (Field XSKFN)
    - Net tax base           (Field XMWSN)
    You must maintain the fields 'Country currency' and 'Exchange rate type'.
    Otherwise, the system issues error message FF 801 or FF 802.
    thanks
    G. Lakshmipathi

  • Excise modvat accounts not defined for EWPO

    Dear Experts,
    when I click on 'Balance Choose' tab in J1IIN, it is showing an error message "Excise modvat accounts not defined for EWPO transaction and 60 excise group.Message no. 8I402" though I have maintain 'Excise account assignment table'  in "Tax on goods movement>India>account determination>specify G/L accounts per excise transaction". I searched in that forum, but I didnt get no proper solution.

    Hi
    Check your entries
    'Excise account assignment table' in "Tax on goods movement>India>account determination>specify G/L accounts per excise transaction
    EWPO          CR Credit     CLEAR CENVAT clearing account
    EWPO          DR Debit     RG23AED RG 23 AED account
    EWPO          DR Debit     RG23AT1 RG 23 AT1 Account
    EWPO          DR Debit     RG23BED RG 23 BED account
    EWPO          DR Debit     RG23ECS RG 23 ECS Account
    EWPO          DR Debit     RG23SED RG 23 SED account
    regards
    Prashanth
    Edited by: Prashanth@SD on Apr 12, 2011 2:00 PM

  • Excise modvat accounts not defined for GRPO transaction and 58 Excise group

    Hi Experts,
    When i am doing Goods receipts for Depot for Subcontracting
    i am getting this error message .Excise modvat accounts not defined for GRPO transaction and  Excise group. For Depot no modvat. is there any configuration setting for depot. Please do needful.

    Hi,
    Please maintain
    Hi,
    go to SPRO
    Specify G/L Accounts per Excise Transaction
    SPROLogistics u2013 GeneralTax on Goods MovementsIndia Account Determination  Specify G/L Accounts per Excise Transaction
    Enter excise group -58
    ETT_ GRPO
    and G/L account
    G.Ganesh Kumar

  • Excise modvat accounts not defined for DLFC transaction and excise group

    Dear Experts,
    Iam raising this question after checking all the contents related to Sub Transaction type in SDN.
    My prob is: for raw material sales scenario i have created order delivery and invoice. For Invoice i have done account determination with a different G/L in VKOA. Now i have to create an excise invoice and the accounting entry for central ED on sales should go to different G/L account. for account determination i have done the following settings:
    Maintained Sub transaction type in
    IMG -> Logistics - General -> Tax on Goods movement -> India -> Basic Settings
    ->Maintain Sub Transaction types
    IMG -> Logistics - General -> Tax on Goods movement -> India ->
    Account determination -> Specify Excise Accounts per Excise Transaction.
    Here against DLFC sub transaction Type is maintained..
    Also
    IMG -> Logistics - General -> Tax on Goods movement -> India -> Account determination -> Specify G/L Accounts per Excise Transaction
    Here maintained Excise group with DLFC Company Code subtransaction type, chart of accounts and all required GL Account .
    But when the iam creating Excise Invoice in J1IIN and clicking on Subtransaction type-F4, no entries are shown. No values found is the message in green. Message no. DH801
    If i use subtransaction type and enter billing document and enter, the following error message comes:
    "Excise modvat accounts not defined for DLFC transaction and excise group"
    Iam unable to understand why the subtransaction type maintained is not showing in TCODE J1IIN?
    Regards

    For the error message DH801, please check note 840911
    Excise modvat accounts not defined for
           DLFC transaction and excise group"
    Please check  your G/L assignments "Specify G/L Accounts per Excise Transaction"
    thanks
    G. Lakshmipathi

  • Excise modvat accounts not defined for CAPE transaction and TS excise group

    Hi Guys,
    Suddenly we are facing issue during exicse invoice capturing with MIGO
    system is giving following error
    "Excise modvat accounts not defined for CAPE transaction and TS excise group
    Message no. 8I402
    While in Excise account assignment table CAPE is Linked to Modvat Clearing Account which is further liked to correct GL
    Can any one explain the cause of this issue Points will be awarded
    Regards,
    Ashish

    Hi
    Pls maintain the following:
    1. SPRO->Logistics General -> Tax on Goods Movements -> India -> Account Determination -> Specify Excise Accounts per Excise Transaction
    Pls note the Sub Tansaction type is IP for ETT CAPE.
    ETT  <b>Sub Trn Type</b>   DC Ind                Account Name
    CAPE     IP           CR Credit     ONHOLD CENVAT on hold account
    CAPE     IP           DR Debit     ONHOLD CENVAT on hold account
    CAPE     IP           DR Debit     RG23AED RG 23 AED account
    CAPE     IP           DR Debit     RG23BED RG 23 BED account
    CAPE     IP           DR Debit     RG23SED RG 23 SED account
    CAPE       IP                   DR Debit             RG23ECS RG 23 ECS account
    2. SPRO->Logistics General -> Tax on Goods Movements -> India -> Account Determination -> Specify G/L Accounts per Excise Transaction
    Check the G/L accounts for Excise Transaction Type CAPE and maintain the same G/L accounts for ETT CAPE with <b>Sub Trn Type IP</b>.
    Hope this clarifies.
    Thanks

  • Error - Excise modvat accounts not defined for DLFC transaction and 01 exci

    Dear All,
    Getting below error while  doing J1IIN - Posting Excise invoice for Sale.
    "Excise modvat accounts not defined for DLFC transaction and 01 excise group"
    I checked with the settings GL are assigned to for DLFC and 01 excise group.
    Is anywhere else I need to mantain the modvat GL
    Regards,
    Rakesh

    Check if you are using any subtransaction type along with excise transaction type.
    Excise group, ETT, company code, sub transaction type (if any), Chart of account, Modvat account (pls maintain all the entries over here) search for modavat clearing field and maintain it.
    BR
    Edited by: Sujoy on Jan 15, 2010 9:45 AM

  • While creating sales order got error version "0" is not defined for company

    Hi,
    i got a error  while creating a sales order(va01) ,i got an error
    saying that "version 0(zero) is not defined for company code
    if there is any solution please provide....
    Thanks&regards
    kishore kumar

    Go to TCODE:OKEQ
    1)select version 0 here and ext select settings for each fiscal year under controlling area settings
    2)give your controlling area XXXX and version 0 then enter
    3)select new entries maintain data for new year 2008.
    Hope this will give u
    Sri

  • Error message TD427 (A text element is not defined for form J_1IEWT_CERT)

    Hello,
    Q> I assign the SAP script form J_1IEWT_CERT to 'SPRO=>Withholding Tax Certificates for Vendor and Customers' and was trying to see the print preveiw. But once I press printpreview button error comes "ELEMENT TITLEDET WINDOW TITLEDET IS NOT DEFINED FOR FORM J_1IEWT_CERT" and i can't see the printprview.
    Same thing I tried with the copy of J_1IEWT_CERT from 000 client to ZJ_1IEWT_CERT; but same error is coming.
    If i try the printpreview through SE71 it shows without error.
    Thank You.

    "test printing" via SE71 only prints what exists in the form. Here your form is missing TITLEDET window and element.
    The print program tries to print TITLEDET but it does not exist. Could you check SAP notes to get correct versions of print program and sapscript form.

  • Error  while creating PO --   Unit of measure not defined for lanuage  ZH

    Hi all,
    i  have created the PR with EA as UOM. Then while creating PO, i am getting error like
    '  Unit of measure not defined for lanuage ZH' .
    Then  I execute CUNI
    Then menu is GOTO > Translation > units of measure
    enter source language and target language . After this i am getting the below message
    --->  Language not available on server
    Please suggest what i should do. Thanks.
    Thanks
    pabi

    HI Pabi,
    Go to material master for material in purchase requisition, the Go to Additional data and maintained language as ZH in material master data.
    Also the other possibility, that if in your case purchase requisition are converted to purchase orders through background jobs,
    then check the background job execution in SM37 whether that background job has been triggered twice parellely in the background, which could have resulted in locking of same purchase requisition at same time and hence your are getting the Error.
    Br,
    Tushar

  • Error saying 'Posting period 000 is not defined for fiscal year variant K4'

    Hi All,
       When I try to add a new entry in the transaction OB52, I get an error message saying 'Posting period 000 is not defined for fiscal year variant K4'. The entry that I add is,
    Variant           :  0001
    Account Type: +
    From Period    : 1
    Year               : 1995
    To Period        : 12
    Year               : 2010
    From Period2  : 13
    Year               : 2000
    To period2      : 16
    Year               : 2010
    Please let me know what customising needs to be done to solve this issue.
    Thanks a ton.
    Best Regards,
    Jeff

    Hi,
    Hava you checked in OB52 screen, by default 0001 posting period variant will be there for +, A, D, K, S account types.
    If it is already existed in your OB52 screen, you won't create one more record with the same name. You have to edit the existing 0001 posting period with new values.
    Thanks
    Chandra

Maybe you are looking for