BPC Transport - variation in dimension tech name.

Hi,
After transporting the appset to Qa it is observed that one of the dimension ENTITY the technical name is different from Dev and hence the transport failed with RC 8 in Qa with error "InfoObject /CPMB/XXXXXX does not exist in version A",
InfoObject /CPMB/XXXXXX not found, Failed to create dimension attribute.
This appset is already available in target system and we are transporting the same into Qa.
Want to understand how come the technical name would be different from Dev to Qa? if at all new dimension is created by deleting the existing dimension then when we collect the appset in TR then all the new objects have to be moved to Qa and should replace the older one or add a new one - iam not sure how does it happen in BPC.
All the necessary transport rules have been followed.
does some one faced this issue?
Regards

Hi,
If you recreate the dimension then the transport would fail with the error return code == 8. This has been fixed in SP04. The note which you specified address this issue (Note: 1357520).
Probably you may try something like this:
If you are doing the transport to Dev system if the Dimension already exists on the Dev system. The probable solution could be to this is to delete the dimension from the Dev and then do the Transportation. But deleting the Dimension would affect the cube data.So before deleting the dim its better if you take the backup of the cube data and the once the Transportation is completed , then you can reload or import the data into the cube through data manager. And if the Import fails then please run the UJS_ACTIVATE_CONTENT with just Activate Appset option. You may try this.
Also if you have enabled the Audit Activity then you may try checking the system reports and see if someone might have worked on the dimension which is in question.
Thanks and regards

Similar Messages

  • Change of DTP tech name in transport causes error in Process chain

    Hello people,
    This message was posted before and I do not think there was an answer.  I hope I have better luck.
    When we transport DTP and process chain, the DTP tech name is changed in the target system while the DTP specified in the transported process chain remains as the source system.  This causes an error in the process chain in the target system because it cannot recognise the DTP specified in it.  To rectify it, I modify the process chain in the target system to point to the DTP with the new tech name.  Is there another way such that I do not need to modify the target system.
    I am currently trying to find an answer and I will share if I find one.  Thanks.
    HWS

    Hello again,
    My problem is resolved.  I am in SP17 and I applied a few SP18 notes:
    0001002791
    0001077030
    0001139653
    0001147587
    0001147766
    I then re-transport the request with the DTP and process chain.  The expected result is the dtp in the process chain should be pointing to the new dtp.  CHeers.
    HWS
    Edited by: Ho Wei Siong on Aug 14, 2008 3:35 PM

  • Value in input field of Hier.Node variable displays tech.name of the IO

    Dear all,
    we are facing an issue with Hierarchy node variable(auth.) in the selection screen of webReports.
    After selecting a hierarchy node value,it is displayed along with + sign and tech.name of the Infobject in input field .
    example: lets say we have Country Hierarchy and i have selected Country group 'NAM' node..This is displayed as "+NAM(ZCOUTRYGRP)". where ZCOUTRYGRP is tech.name of the InfoObject Country group.
    Expected value is just "NAM" which is Key .Does anyone have solution for this? This Problem occuers when we select Level 01 value of hierarchy and we do have hierarchy node values from same INfoObject.
    Regards,
    Murali.
    Edited by: Muralidhar c on Aug 1, 2009 1:24 PM
    Edited by: Muralidhar c on Aug 3, 2009 10:40 AM

    it works as designed.found in sap help.

  • Reading data from a text file into PAS - Dimension member names truncated

    Hi,
    I created a procedure to dump variables and data into a text file to load into another model. I used a semicolon as a field seperator.
    The data, measures and dimension members are dumped properly into a text file and no dimension member names are truncated .
    However when I read the data into  a measure, and I issue a peek command, dimension meber names are read in truncated
    and remain full names in the text file. Any reason for this? What do I need to do to prevent this from happening?
    THanks.
    Lungile

    Hi Lungile,
    The problem that you're likely having is that you haven't created a file description for the file from which you're reading.  When loading data into Application Server from a text file, you would normally go through three steps:
    1. Enter the ACCESS EXTERNAL subsystem
    2. Specify the name of the file to be read
    3. Specify the format of the file field names, types, widths, and positions.
    If you go into the Application Server help, select "Application Server Help", then "Application Server at the command level", then "Variables and reading in data", and then "Reading an external file", you will have the process of the steps you need to follow outlined for you, including links to the help topic for each command you need to issue.
    So what I think you need to do is use the DESCRIPTION command to specify the names of your fields, their type, and also their width, in order to ensure no truncation of data on the load.
    The same DESCRIPTION statement is required if you want to use your text file as the source of a dimension.
    Hope this helps,
    Robert

  • SAP Variable Tech Name in MDX

    Hi Friends,
    I have a question related to SAP Variable usage in MDX statement.
    I have a hierarchy node variable, which is mandatory and has a default value..
    When technical name of this variable is something like ZXYZ_SM, it appears differently in MDX, as !V0000017..
    Problem is, i have to use this variable in two seperate queries and this MDX technical name changes query to query..
    Eg.: when it is !V0000017 in Query A, it is !V0000015 in Query B.. I need them to be identical across queries, because this is a global filter of a huge dashboard..
    Can you please help me how to proceed? I need solution on Bex side..
    Thanks in advance,
    Sunil
    ====================================================
    SAP Variable tech name needs to be shorter than 10 chars in order to be supported by MDX. So, changing variable name fixed the issue...
    ====================================
    Edited by: SunilKmr on Nov 29, 2010 1:27 PM

    What Rohit is trying to say is that the technical name of the BEX variables is not shown to an end user,
    and also not used to combine user input, only the prompt text is.
    (BTW, the technical name is determined by the position of the variable prompt in the BEX query,
    so the first variable shown will be !V000001, the second !V000002, etc.
    So in your case the order in the two BEX queries is different)
    So if you have two BEX queries, this means two universes.
    Now when you want to report data out of these two universes you will build a query in the WebI report on each universe.
    Both queries will ask you for input for their respective BEX variables,
    but to do that they using the prompt text, not the tech name.
    By default this prompt text will be the name of the BEX variable,
    but you can change the text in the universe without implications.
    As long as the two prompt texts are the same for these two different tech name variables,
    BO will give just one prompt and feed it to !V0000017 in the query on the universe for BEX query A
    and !V0000015 in the query on the universe for BEX query B.
    Hope this is clear enough,
    Marianne

  • Change Source system Tech.Name

    Production :   PRE -
    >  PRB
    PRE-Production    :   PPE -
    > PRE
    We make a copy of our production BI to Preproduction BI (PPB) we follow note # 886102. We want to connect this system to our pre production ERP (PPE).We already run BDLS change the logical system name we created new RFC created which is pointed to new R3 system .Problem is when we are going to run Tcode RSA1 in source system it shows old Tech name PRE600. We are unable to activate the source system.
    We can create new source system (PPE),but All our BI objects mapped with old source System (PRE600). I am afraid to change thousands of BI objects ( change source system from PRE600 to PPE600).
    Is there any work around we can change the Logical Source system Tech.Name? or some batch job which change the source system name for all BI objects.
    Appreciate your earliest reply.
    Nawab

    Hi
    Can you please check the Tcode BDLS
    Check the document it will be helpful
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
    Regards

  • Transport user error: invalid object name while starting CMS in CCM

    Hi Experts,
            I'm not able to start the CMS in CCM.It was working fine. Suddenly it went down due to some data base access failure. After that Iu2019m not able to start the CMS.
    Kindly find the event viewer error and information.
    Error: The root server reported an error Initialization Failure.
    Error: Failed to register object..   Reason: Transport user error: invalid object name..
    Information: Central Management Server stopped
          Could you please tell me how to start the CMS in CCM? Since I can able to setup CMS Database and audit database successfully.
    Regards,
    Sridharan

    Hi ,
            Thanks for the response.I have trace the CMS.I found some error in log file.any idea on the following errors,
    trace message: CNSClientManager::VerifyConnection() : search fails(37) - Transport user error: object with the specified name not found.
    trace message: CNSClientManager::VerifyConnection() : Failed to query for APSs.  Empty cluster list returned.
    trace message: TheAPSServer::RegisterApsInNameServer: Fail to register the current APS(Transport user error: invalid object name.)
    trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS  from m_ActiveMembers and adding to m_InactiveMembers
    trace message: SIServerController:run: Fail to initialize or uninitialize.  Reason is The root server reported an error Initialization Failure.:
    Regards,
    Sridharan

  • Which table containes dimension member names in planning database

    I want know which table in Planning database contains dimension member names. I have tried looking at the HSP_ACCOUNT and HSP_ENTITY tables but those have member IDs only and not the member names.
    Any help on this please

    Might be worth having a look at http://camerons-blog-for-essbase-hackers.blogspot.co.uk/2012/04/stupid-planning-queries-9-entity_3054.html and the related posts on extracting planning metadata.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • SAP BW Query in CR2008: only tech names displayed when query is changed

    Hello Experts,
    we have the following constellation / problem:
    SAP Query BW 7.0
    a report built upon this query with Crystal Reports 2008
    the report is currently not using any of the Database fields, is just consists of the layout
    Now we want to change / add the underlying query. But either if we add the new query or replace the old query by the new query, the result is the same:
    only the technical names of the query structures (UIDs) are shown, neither the descriptions nor the technical names (concerning SAP BW) are shown.
    The 'new' query is a slightly changed copy of the old query, I don´t think that is has to do anything with the query.
    As mentioned, everything seems to be perfect as long as we just do 'Create Report upon query', then the descriptions and technical names (not the UIDs) are shown, but not if we add / replace the existing query through another.
    Many thanks for your help in advance !
    Frank

    So the solution seems to be:
    Open the Query Designer and tick 'Allow External Access to this Query' on the Advanced Tab to allow access with OLE DB for OLAP to the query.
    Then the query appears in Crystal Reports under the source system and 'Queries' whereas before it is only accessible directly under the source system.
    If a query is accessible under the source system, the BW Query Driver is used, which seems not to be able to cope correctly with the technical names.
    If accessed via 'Queries', the BW MDX Driver comes into action and not only the tech names but also the description etc. is displayed.

  • MDX: Selecting specific dimension member and its descendants from parent child dimension where dimension member names can be same in dimension hierarchy

    I'm creating a SSRS report using SSAS cube as a source.
    When creating a dataset for the report, I'm having trouble with MDX to select a specific dimension member and its descendants from parent child dimension where dimension member names can be same in dimension hierarchy.
    Lets say for example that I have an account dimension where,
    In level 02 I have company ID:s 101, 102, 103 and so on...
    In level 03 I have Balance sheet
    In level 04 I have some account groups, Assets, Liabilities and so on... and In level 05 I have individual accounts
    How can I select for example company 102:s Assets from level 04 and its descendants?
    Normally in adventure works I would do this if I've wanted Current Assets and its descendants:
    SELECT NON EMPTY { [Measures].[Amount] } ON COLUMNS, NON EMPTY
    { (DESCENDANTS([Account].[Accounts].[Account Level 03].[Current Assets]) ) } ON ROWS
    FROM [Adventure Works]
    But in my Account dimension at level 04 I have Assets member as many times as I have companies in level 02.
    Tuomo

    Hi Tuomo Helminen,
    To this requirement of yours, I would recommend you use Cascading Parameters in Reporting services, you can refer to this FAQ How do I create cascading parameters when using cube database in Reporting Services at this link
    http://blogs.msdn.com/b/sqlforum/archive/2011/04/11/forum-faq-how-do-i-create-cascading-parameters-when-using-cube-database-in-reporting-services.aspx 
    Thanks,
    Challen Fu
    TechNet
    Subscriber Supportinforum
    If you have any feedback on our support, please [email protected]
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Find the tech names of all query's present in a workbook

    Hi,
    I need some materials  on workbooks.
    How find the tech names of all query's present in a workbook. I had an issue from end user and they just send me the workbook. So now i need to find out all the querries present in workbook.
    Please let me know steps to find out and some materials on workbook.
    Thanks,

    Hi
    Check in metedata repositroy.., when you click on th query here, it will show you which infoprovider it is created and list of workibooks created on the query etc.....
    Hope it helps you.... else get back
    Regards
    Rajesh

  • How to find R/3 field  tech name with the help of BW fields.

    Hi ,
    How will i come to know that particular R/3 field is mapped to BW field.
    for .e.g
    I have BW Fields in Cubes , how can i see the R/3 field tech names for that .I can see in Infosource , but for few areas i am not able to find the infosource in sap help.com.
    Pls let me know how to find the R/3 Fields for BW Fields?
    Regards,
    Nithi.

    Hi
    These are the following approaches used
    1.) Check the SAP BI Content website "http://help.sap.com/saphelp_nw70/helpdata/en/3d/5fb13cd0500255e10000000a114084/frameset.htm". From here find your datasource . here u can get a list of fields in the datasource along with your R3 field and infobject.
    2.) Go to Transfer rules structure of the cube or DSO, there u wuld  be able to see all fields in Datasource structure fields, See the left pane and right pane. there u will se ur R3 fields and Infoobjects of BW along with their mapping.
    3.) Follow this process
    in R/3 system - use tcode SE11 ->ROOSFIELD -> GIVE Extract Structure & Field Name > Check Records with Version D and A.
    NOTE : Make sure the fields of the datasource in R3 are not hidden , otherwise you wont be able to vierw ur data.
    From
    ManesH

  • Using query ID how we can find query tech name in BW 3.5

    Using query ID how we can find query tech name in BW 3.5
    I got this querry ID from RSDDSTAT table for one user.
    Thanks

    SE16 --> RSRREPDIR --> give your id and get the tech name of the query and other info.

  • Routines Tech name...

    Hi,
    Pls let me know how to find the tech names of:
    Characteristics Routine
    Start Routines
    Update Rule.
    Thanks

    hi aadil,
    here are the steps which'll help u in case of Start Routines &
    Update Rule.
    Open T-code se12
    open table RSAABAP
    see the contents of RSAABAP
    In EDIC: Program editor line enter the piece of code from start or update routine (like smallline_or_code)
    execute and see the entries.
    copy the ABAP id's (say ABAP1)and look up in another table RSUPDROUT.
    See the contents of RSUPDROUT ,executing it for the ABAP id (ABAP1) u'll get technical name of update rule.
    hope this helps u.
    regards,
    Arvind.
    Edited by: Arvind Tekra on Feb 8, 2008 11:02 AM

  • BPC Transport Too many characteristics (024) are assigned to dimension

    Hi Gurus,
    We are implementing BPC Consolidation for NetWeaver 7.5, and we're facing the following situation:
    Too many characteristics (024) are assigned to dimension /CPMB/Q6IW0EVD
    Diagnosis
    Too many characteristics are assigned to the given dimension.
    For a "normal" InfoCube, the database table to be created for a dimension may contain a maximum of 249 fields. This means that no more than 248 characteristics may be assigned.
    However, if the property "DIMIDs One-to-One" is set, a unique index on the characteristics of the dimension is created. In this case each dimension may not contain more than 16 characteristics.
    Any suggestions?
    Thanks in advance
    Best Regards
    Abraham Méndez

    Hi Sheldon,
    Thanks for answering my question.
    I already ran that full optimization you talked about but i dont see some changes in BW, what i can see is the shadow cube that the full optimization creates but i cant see how the full optimization solves that bunching of too many BPC dimensions on one BW cube dimension afterwards.
    The fact is that when the transport order generated by BPC transaction UJBPCTR is imported into the Productive environment the error still raising, with the same description:
    u201CToo many characteristics (024) are assigned to dimensionu201D
    Could you help me by telling me how full optimization solves that dimension bunching? Another question is Why does the error appear until the transport order is imported and not when you are working in development?
    Thanks in advance.
    Regards.
    Abraham Mendez.
    Edited by: Abraham Mendez on Apr 29, 2011 5:13 PM

Maybe you are looking for