Dimension attribute relationship Data different

Dear all,
I read that I should create attribute relationships for all dimensions which have a hierarchy. Now I created the relationship from the lowest to the highest level and saw that the Dimension Data I got after creating the attribute relationship is dfferent. Before
I had 12 Data records in 1 Attribute of the Dimension and now I just have 6. Therefore my report shows different data.
In my case it is an item dimension with item category and item brand category. Now I releated ItemID with Item No, then with Item Brand Category and then Item Category. But then I just get 6 Brand Categories instead of 12. My relations are until now flexible
and the cardinality is many (I read on MS side it does not matter and is not used, just for future implementation).
Does anyone know, what I am doing wrong or what I have to do?
Thanks a lot.

It looks like you probably have ProductID setup as your key attribute. The key attribute has to be unique as it defines the granularity of your dimension. So based on the data you have shown ItemID should possibly be the key attribute. 
http://darren.gosbell.com - please mark correct answers

Similar Messages

  • 'dimension attribute was not found' error while refresing the cube in Excel

    Dear All,
    Thanks for all your support and help.
    I need an urgent support from you as I am stuck up here from nearly past 2-3 days and not getting a clue on it.
    I have re-named a dimension attribute 'XX' to 'xx' (Caps to small)in my cube and cleared all dependencies (In Attribute relationship tab as well).
    But while refreshing the data in excel client (of course after processing the full cube) I get an error
    'Query (1, 1911) the [Dimension Name].[Hierarchy Name].[Level Name].[XX] dimension attribute was not found' error.
    Here I am trying to re-fresh an existing report without any changes with the new data.
    Does not it re-fresh automatically if we clear the dependencies or there something that I am missing here (Like order of the dependencies).
    Cube processed completely after modifications and able to create new reports without any issues for same data. What else could be the reason?
    Can some one help me here?
    Thanks in Advance and Regards,

    Thnaks alot Vikram,
    In se11  ,when i was trying to activate the  /BIC/FZBKUPC , it is showing the warnings  like
    Key field KEY_ZBKUPCP has num. type INT4: Buffering not possible, Transport restricted.What it means.
    In PErformance Window it is showing like:
    A numeric type was used for a key field. A table of this sort cannot be buffered.When buffering, the table records for numeric values cannot be stored in plain text.
    Procedure
    You can enter "no buffering" as an attribute of the technical settings and then repeat the activation process. The table is not buffered.
    If you want to buffer the table, you must replace the type in the key field by a character type, i.e. that you must modify the table.
    Please adivice with your valueable suggestyions.
    Thanks Vikram.

  • Defining Dimensions, Attribute Hierarchies for a Link Table(Many to Many)

    I have 3 Tables in the Database
    Table 1: Transactions (Fact Table) - PK(TransactionId)
    Table 2: Relationship (Dimension1) - PK(Relationship Id), FK_TransactionId, FK_CompanyId, RelationshipType
    Table 3: Companies (Dimension 2) - PK(CompanyId)
    Table 2: Relationship table is a link table between Transactions & Companies to facilitate many to many relationship. 
    I defined Fact and Dimension tables accordingly but having issues defining Dimension & Attributes for Relationship tables
    Relationship Dimension:
    I have 3 hierarchy groups defined
    Hierarchy 1 - Relation -Relationship Type,Relationship Id(PK)
    Hierarchy 2 - Transaction - Transaction, Relationship Id(PK)
    Hiearchy 3 - Company - CompanyId, Relationship Id(PK)
    Defined the attribute relationship in the following way
    RelationshipID(PK) ---> CompanyId , RelationshipID(PK) ---> TransactionId, RelationshipID(PK)
    ---> RelationshipTYpe
    I am getting incorrect results when I deploy the cube. Not all the types are being displayed only 4 types are being displayed out of 27 types though there exists Transactions for all the Types.
    To fix the incorrect results, I tried to break the Relationship Dimension into 2 dimensions seperating Transaction(Relationship Dim) & Company,Type (Companies Dim). I tried to configure a many
    to many Relationship type between my  Companies Dim & Fact Table Transaction. But I get the error that says 
    "Companies Dim many to many dimension in the Tansaction measure group requires that the granularity of the Relationship dimension is lower than that of the Relationship measure group "
    Any help regarding how to difine Dimensions & Attribute Hierarchies on a Many to many link table is appreciated.

    Hi Jaya,
    According to your description, you are experiencing the issue when implement many to many relationship by using a bridge table in your SQL Server Analysis Services project, right?
    Generally, a bridge table will have a surrogate key for the dimension and a surrogate key to the fact table or a degenerate dimension based on the fact table. Here are some blogs which describe how to implement many to many relationship using a bridge
    table.
    http://bifuture.blogspot.com/2011/06/ssaskimball-modeling-nm-relation.html
    http://www.sqlchick.com/entries/2012/1/22/data-modeling-tip-when-using-many-to-many-bridge-tables-in-s.html
    http://social.technet.microsoft.com/wiki/contents/articles/22202.a-practical-example-of-how-to-handle-simple-many-to-many-relationships-in-power-pivotssas-tabular-models.aspx
    Regards,
    Charlie Liao
    TechNet Community Support

  • Dimension usage relationship between dimensions

    Hi,
    please I have a case where an attribute of a dimension is part of the measure in a report, How can I establish a dimension usage relationship between this table and other dimension that is related as below( whereby the supposed fact table primary key is
    appearing as foreign key in the dimension table). Thanks  
    ACCOUNT TABLE
    accid -PK
    EXTRAS TABLE
    accid -FK

    Hi 14QR1A,
    According to your description, you want to build the relationship between dimension tables. Right?
    In Analysis Services, it can have relationship between dimension like some snowflake schema. In BIDS, you can direct build the relationship between dimension tables in Data Source View. For example, the ProductCategory has relationship with
    ProductSubCategory in AdventureWorks sample.
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou
    TechNet Community Support

  • IP - characteristic relationship/ data slices

    Hi Guys,
    I am very new to IP and would like to have some help regarding the following with some simple example
    1) characteristic relationship
    2) data slices
    3) locking
    Some examples with the above is much appreciated.
    where can i get some good document explaining this ?
    Thanks in advance...

    Hi,
      Please find below the examples for characteristic relationship and data slice,
    1. Characteristic relationship:
                 Consider that you have characteristics called "Country" and "Continent" in your report (also in aggreagtion level).
    You cannot always expect the end user to enter the correct continent for a country. In this case, you can create a char rel
    based on the relastionship between these two characteristics (attribute, hierarchy or relationship data loaded to a DSO),where the source is "Country" and the target is "Continent". So when ever the user enters country and continent the char rel validates the entry based on the reference data (master data, hierrarchy or DSO data) and throws error if it s wrong. Apart from this by creating "With derivation" char rel, you can even derive continent value from country with out the user even entering the value in thye report.
    2. Data Slice:
              Consider that your planning requirement is you need to plan on a monthly basis which is like during current month you caa plan for the next month. In this case all other months except the next month should not be available for planning. In this case you can create a daat slice of type "Selection" where in you select '0CALMNONTH' and then filter it to the variable '0CMONTH' +1
    where in you "Exclude" this selection. So now all the other months except next month at any point of time will be disabled for planning.
    You can go through the following links for your reference,
    Char rel - [http://help.sap.com/SAPHELP_NW04s/helpdata/EN/43/1c3d0f31b70701e10000000a422035/frameset.htm]
    Data slice - [http://help.sap.com/SAPHELP_NW04s/helpdata/EN/43/1c3d0f31b70701e10000000a422035/frameset.htm]
    Hope this solves your doubt.
    Regards,
    Balajee

  • Dynamically rollup dimension and aggregate data based on diferent measures

    Hi,
    I am facing an issue while rolling up the dimension based upon measures. I have a dimension which is defined at 3 levels - Level1 (L1), Level2  (L1), Level3 (L1). There is a unique code for each of these dimensions. It might be possible for a L1, there is no L2 and L3 or for a L1 there is L2 but no L3.
    Universe structure looks like:
    Table1--Table2Table3Table4Table5Table6
    Table1 is my master table that gives heirarchy i.e. has Level number, Code, ParentCode and Name.
    Table2 is a fact table which has Amount and Code. Amounts are present at the most granular level L1 or L2 or L3.
    Table3 and Table5 are tables joined to Table 2 and Table 4 through some IDs which are used as user prompts.
    Table6 is a fact table which has L1Code,L2Code,L3Code and Targets.
    So table1 and table2 has all the codes in one column and Table 6 has codes in 3 different columns depending upon level (hierarchy) along with targets.
    My requirement is to show Names from Table1 for which targets are defined in Table6 along with the Amount.
    1. If target is at L3 then Show Name of L3, Amount and targets.
    2. If target is at L2 then show Name of L2, 
        a) Sum of all L3 Amounts under that L2 aggregated to L2 and Target for L2.
        b) Sum of L2 Amount (if L2 is most granular level) and Target for L2.
    3. If target is at L1 then show Name of L1,
        a) Sum of all L3 (or L2 depending upon more granular level for that L1) Amounts under that L1 aggregated to L1 and Target.
        b) Sum of all L1 (if L2 is most granular level) Amounts and Target.
    We are able to achieve Roll up of dimension based upon Targets but aggregation of Amounts from L3 to L2 or L2 to L1 based upon these rollups is not happening.
    Please Help.

    Hi ,
    As you mentioned you need such aggregation in SSRS and you are using SSAS datasource.
    so you can achieve this using MDX Query.
    I have done this in my environment . I took below for achieving this
    Dimension : Category
    Relationship : There should be Facttable relationship with Dimension table Category.
    Measure : Unit Price (in your case sale)
    Please find below solution using MDX Query.
    Please share if you have any doubt.
    Thanks

  • Is it possible to sort dimension values in order different from alphabetic?

    Is it possible to sort dimension values in order different from alphabetic. То use this sorting in BI Beans. In 10g r2 with awm 10.2.0.2. I try to add attribute like it was show in this forum, but nothing changes.

    Could be usefull if you use java AW api... here's the java code I'm using to create the sort_order attribute
    Dimension myDim = yourAW.findDimension("DIMNAME");
    Attribute myAttr = myDim.createAttribute();
    myAttr.setName("freename");
    myAttr.setClassification("DEFAULT_ORDER");
    myAttr.setIsDefaultOrder(true); // TO NOT FORGET
    myAttr.setDataType("INTEGER");
    myAttr.Create(AWConnection);
    globalAW.Commit(AWConnection);
    It creates a variable - integer - that defines the default order of the dim values. I'm viewing it with AWM and BIBeans. The order is respected with Level-based and Value-based hierarchy but my hierarchies are really simple and unique for all the dimensions.
    BUT !!!! Be carefull, if you don't have any hierarchy in your dimension, you must have at least one level - the default NONE level. Otherwise, it won't work ???

  • Error occurred while creating dimension attributes.

    Hi All,
             I have restored the back up file in the NW 10.0 environment (In BW 7.3 system using UJBR tcode the backup file was colleted from NW 7.5 system). In this process I have got an error "Error occurred while creating the dimension attributes via Admin API" and I have tried to resolve this with the program execution "UJA_ASSIGN_INFOOBJECTS_CATALOG". I am not able to open the Environment after this restore process completion. Could you guide me in this to resolve the issue. Please Let me know if you need more information to understand the issue.
    Thanks and Regards,
    Krishan.

    Hi Nilanjan,
                      I have logged into the BPC system and able to open the APSHELLENVIRONMENTSHELL. When I tried to open a new environment which I have restored in the BW system error like "500-server ". Is this related to Service Pack ? or need to apply any new one to this system. And one more log I have observed in the process of DATA. When I have executed the UJA_DATA_CHECKER there is a message what I have got in this process " InfoObject catalog /CPMB/ENVIRONMENTSHELL_CHAR is not available in version A".
    BW System Details:
                                   SAPK-80102INCPMBPC
    Thanks and Regards,
    Krishna.

  • BAPI or FN. MOD to change Relationship Data in HRP1001

    Hello Gurus,
    Is ther any BAPI or Function Module to Change the Relationship Data( in HRP1001).
    Iam using BDC to Change(Update) the Data.In SHDB, the PO13 transaction is OK but while Loading the Records(or running the program), its totally different.
    If anyone has come across such an Issue and resolved it, Please help.
    Thanks

    Thanks Suresh,
    I could not test it but as our Client has asked us to cont. with the BDC's only
    I have gave you the points.
    This is very helpful for me though as Iam working in Org. Management currently

  • Multiple LDAP Servers and Attribute-Based Data Partitioning

    Hello
    We currently want to implement following szenario on Netweaver 2004s. From the
    following SAP Help documentation we want attribute based data partitioning:
    http://help.sap.com/saphelp_nw70/helpdata/EN/4e/4d0d40c04af72ee10000000a1550b0/frameset.htm
    The difference to the SAP document is that we want a distribution of attributes over
    multiple LDAP servers. So we tried to fit that concept into xml. see attached xml source.
    The Portal finds both LDAP Systems but it is NOT that the useres are beeing merged
    but they appear as two distict users in the portal UME. If you do a lookup in the portal
    usernamagent system you get and see two users.
    User1: unique ID = USER.Datasource1.uid
    User2: unique ID = USER.Datasource2.uid
    Obviously the UME system was not able to merge that information of the two distict
    LDAP Systems. MSADS and Lotus Notes.
    Hence my questions:
    1) is it possible to distribute attributes over multiple ldap data sources
    2) any ideas why UME constructs two different users based in Datasource ID's specified in XML
    Thanks for any contributions or ideas,
    Ulrich Scherb
    <?xml version="1.0" encoding="UTF-8"?>
    <dataSources>
        <dataSource id="PRIVATE_DATASOURCE"
                    className="com.sap.security.core.persistence.datasource.imp.DataBasePersistence"
                    isReadonly="false"
                    isPrimary="true">
            <homeFor>
                <principals>
                     <principal type="group"/>
                     <principal type="user"/>
                     <principal type="account"/>
                    <principal type="team"/>
                    <principal type="ROOT" />
                    <principal type="OOOO" />
                </principals>
            </homeFor>
            <notHomeFor/>
            <responsibleFor>
                <principals>
                     <principal type="group"/>
                     <principal type="user"/>
                     <principal type="account"/>
                    <principal type="team"/>
                    <principal type="ROOT" />
                    <principal type="OOOO" />
                </principals>
            </responsibleFor>
            <privateSection>
            </privateSection>
        </dataSource>
        <dataSource id="NOTES_LDAP"
              className="com.sap.security.core.persistence.datasource.imp.LDAPPersistence"
              isReadonly="true"
              isPrimary="true">
              <homeFor/>
              <responsibleFor>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user"/>
                             <attribute name="logonalias"/>
                             <attribute name="j_password"/>
                             <attribute name="userid"/>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal"/>
                       </nameSpace>
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname" populateInitially="true"/>
                             <attribute name="lastname" populateInitially="true"/>
                             <attribute name="email"/>
                             <attribute name="uniquename" populateInitially="true"/>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER"/>
                        </nameSpace>
                   </principal>
              </responsibleFor>
              <attributeMapping>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user">
                                  <physicalAttribute name="uid"/>
                             </attribute>
                             <attribute name="logonalias">
                                  <physicalAttribute name="uid"/>
                             </attribute>
                             <attribute name="j_password">
                                  <physicalAttribute name="unicodepwd"/>
                             </attribute>
                             <attribute name="userid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal">
                                 <physicalAttribute name="uid"/>
                            </attribute>
                       </nameSpace>                    
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname">
                                  <physicalAttribute name="givenname"/>
                             </attribute>
                             <attribute name="lastname">
                                  <physicalAttribute name="sn"/>
                             </attribute>
                             <attribute name="uniquename">
                                  <physicalAttribute name="uid"/>
                             </attribute>
                             <attribute name="loginid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                             <attribute name="email">
                                  <physicalAttribute name="mail"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER">
                                  <physicalAttribute name="sapusername"/>
                             </attribute>
                        </nameSpace>
                   </principal>
              </attributeMapping>
            <privateSection>
                   <ume.ldap.access.server_type>MSADS</ume.ldap.access.server_type>
                   <ume.ldap.access.server_name>ldap1</ume.ldap.access.server_name>
                   <ume.ldap.access.server_port>389</ume.ldap.access.server_port>
                   <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
                   <ume.ldap.access.user>xxxxx</ume.ldap.access.user>
                   <ume.ldap.access.password>xxxxx</ume.ldap.access.password>
                   <ume.ldap.access.base_path.user>O=SMT_TEST</ume.ldap.access.base_path.user>
                   <ume.ldap.record_access>TRUE</ume.ldap.record_access>
                   <ume.ldap.unique_uacc_attribute>uid</ume.ldap.unique_uacc_attribute>
                   <ume.ldap.unique_user_attribute>uid</ume.ldap.unique_user_attribute>
                   <ume.ldap.access.context_factory>com.sun.jndi.ldap.LdapCtxFactory</ume.ldap.access.context_factory>
                   <ume.ldap.access.user_as_account>true</ume.ldap.access.user_as_account>
                   <ume.ldap.access.ssl_socket_factory>com.sap.security.core.server.https.SecureConnectionFactory</ume.ldap.access.ssl_socket_factory>
                   <ume.ldap.access.objectclass.user>person</ume.ldap.access.objectclass.user>
                   <ume.ldap.access.objectclass.uacc>person</ume.ldap.access.objectclass.uacc>
                   <ume.ldap.access.naming_attribute.user>cn</ume.ldap.access.naming_attribute.user>
                   <ume.ldap.access.auxiliary_naming_attribute.user>uid</ume.ldap.access.auxiliary_naming_attribute.user>
                   <ume.ldap.access.naming_attribute.uacc>cn</ume.ldap.access.naming_attribute.uacc>
                   <ume.ldap.access.auxiliary_naming_attribute.uacc>uid</ume.ldap.access.auxiliary_naming_attribute.uacc>
              </privateSection>
         </dataSource>
        <dataSource id="CORP_LDAP"
              className="com.sap.security.core.persistence.datasource.imp.LDAPPersistence"
              isReadonly="true"
              isPrimary="true">
              <homeFor/>
              <responsibleFor>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user"/>
                             <attribute name="logonalias"/>
                             <attribute name="j_password"/>
                             <attribute name="userid"/>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal"/>
                            <attribute name="realm"/>
                            <attribute name="domain"/>
                       </nameSpace>
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname" populateInitially="true"/>
                             <attribute name="displayname" populateInitially="true"/>
                             <attribute name="lastname" populateInitially="true"/>
                             <attribute name="fax"/>
                             <attribute name="title"/>
                             <attribute name="department"/>
                             <attribute name="description"/>
                             <attribute name="mobile"/>
                             <attribute name="telephone"/>
                             <attribute name="streetaddress"/>
                             <attribute name="uniquename" populateInitially="true"/>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER"/>
                        </nameSpace>
                   </principal>
                   <principal type="group">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="displayname" populateInitially="true"/>
                             <attribute name="description" populateInitially="true"/>
                             <attribute name="uniquename"/>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE"/>
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.bridge">
                             <attribute name="dn"/>
                        </nameSpace>
                   </principal>
              </responsibleFor>
              <attributeMapping>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user">
                                  <physicalAttribute name="samaccountname"/>
                             </attribute>
                             <attribute name="logonalias">
                                  <physicalAttribute name="samaccountname"/>
                             </attribute>
                             <attribute name="j_password">
                                  <physicalAttribute name="unicodepwd"/>
                             </attribute>
                             <attribute name="userid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal">
                                 <physicalAttribute name="samaccountname"/>
                            </attribute>
                            <attribute name="realm">
                                 <physicalAttribute name="*null*"/>
                            </attribute>
                            <attribute name="domain">
                                 <physicalAttribute name="*null*"/>
                            </attribute>
                       </nameSpace>                    
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname">
                                  <physicalAttribute name="givenname"/>
                             </attribute>
                             <attribute name="displayname">
                                  <physicalAttribute name="displayname"/>
                             </attribute>
                             <attribute name="lastname">
                                  <physicalAttribute name="sn"/>
                             </attribute>
                             <attribute name="fax">
                                  <physicalAttribute name="facsimiletelephonenumber"/>
                             </attribute>
                             <attribute name="uniquename">
                                  <physicalAttribute name="samaccountname"/>
                             </attribute>
                             <attribute name="loginid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                             <attribute name="mobile">
                                  <physicalAttribute name="mobile"/>
                             </attribute>
                             <attribute name="telephone">
                                  <physicalAttribute name="telephonenumber"/>
                             </attribute>
                             <attribute name="department">
                                  <physicalAttribute name="ou"/>
                             </attribute>
                             <attribute name="description">
                                  <physicalAttribute name="description"/>
                             </attribute>
                             <attribute name="streetaddress">
                                  <physicalAttribute name="postaladdress"/>
                             </attribute>
                             <attribute name="pobox">
                                  <physicalAttribute name="postofficebox"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
                                  <physicalAttribute name="memberof"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER">
                                  <physicalAttribute name="sapusername"/>
                             </attribute>
                        </nameSpace>
                   </principal>
                   <principal type="group">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="displayname">
                                  <physicalAttribute name="displayname"/>
                             </attribute>
                             <attribute name="description">
                                  <physicalAttribute name="description"/>
                             </attribute>
                             <attribute name="uniquename" populateInitially="true">
                                  <physicalAttribute name="cn"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE">
                                  <physicalAttribute name="member"/>
                             </attribute>
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
                                  <physicalAttribute name="memberof"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.bridge">
                            <attribute name="dn">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                        </nameSpace>
                   </principal>
              </attributeMapping>
            <privateSection>
                   <ume.ldap.access.server_type>MSADS</ume.ldap.access.server_type>
                   <ume.ldap.access.server_name>ldap2</ume.ldap.access.server_name>
                   <ume.ldap.access.server_port>389</ume.ldap.access.server_port>
                   <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
                   <ume.ldap.access.user>yyyyy</ume.ldap.access.user>
                   <ume.ldap.access.password>yyyyy</ume.ldap.access.password>
                   <ume.ldap.access.base_path.user>O=SMT_TEST</ume.ldap.access.base_path.user>
                   <ume.ldap.access.base_path.grup>O=SMT_TEST</ume.ldap.access.base_path.grup>
                   <ume.ldap.record_access>TRUE</ume.ldap.record_access>
                   <ume.ldap.unique_uacc_attribute>samaccountname</ume.ldap.unique_uacc_attribute>
                   <ume.ldap.unique_user_attribute>samaccountname</ume.ldap.unique_user_attribute>
                   <ume.ldap.access.context_factory>com.sun.jndi.ldap.LdapCtxFactory</ume.ldap.access.context_factory>
                   <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
                   <ume.ldap.access.flat_group_hierachy>true</ume.ldap.access.flat_group_hierachy>
                   <ume.ldap.access.user_as_account>true</ume.ldap.access.user_as_account>
                   <ume.ldap.access.dynamic_groups>false</ume.ldap.access.dynamic_groups>
                   <ume.ldap.access.ssl_socket_factory>com.sap.security.core.server.https.SecureConnectionFactory</ume.ldap.access.ssl_socket_factory>
                   <ume.ldap.access.objectclass.user>User</ume.ldap.access.objectclass.user>
                   <ume.ldap.access.objectclass.uacc>User</ume.ldap.access.objectclass.uacc>
                   <ume.ldap.access.objectclass.grup>Group</ume.ldap.access.objectclass.grup>
                   <ume.ldap.access.naming_attribute.user>cn</ume.ldap.access.naming_attribute.user>
                   <ume.ldap.access.auxiliary_naming_attribute.user>samaccountname</ume.ldap.access.auxiliary_naming_attribute.user>
                   <ume.ldap.access.naming_attribute.uacc>cn</ume.ldap.access.naming_attribute.uacc>
                   <ume.ldap.access.auxiliary_naming_attribute.uacc>samaccountname</ume.ldap.access.auxiliary_naming_attribute.uacc>
                   <ume.ldap.access.naming_attribute.grup>cn</ume.ldap.access.naming_attribute.grup>
              </privateSection>
         </dataSource>
    </dataSources>

    Hi Ulrich,
    Hope your problem is resolved. We are using EP7 and SP18. We are doing some study on your first issue. i.e. Distributing a user attribute into multiple LDAPs. Can you please let me know the feasibility? If yes, what are all step do I have to follow? Expecting your valuable answer. Thanks in advance!
    Regards,
    Kabali

  • Dimension Attributes

    Hi
    I'm designing a fact table and a dimension table, but the dimension tables are having many level and each level is having many attributes, pls see the following data and pls help me in how to go ahead with this kind of dimension attributes.
    A00001 - All
    BALANCE_SHEET - Balance Sheet Accounts
    ASSETS - Assets
    [110000 - 150317]
    [151610 - 151620]
    [A12110 - A13999]
    [A14214] - Short Term Prepaid Assets
    [A14999] - Capital Leases
    [A15214] - Short Term Prepaid Amort
    [A15999] - ACD Capital Leases
    FIXED_ASSETS - Fixed Assets
    PURCHASED_ASSET - Purchased Assets
    PFURN_MACH_EQ - Purch Furniture Machinery Equi
    [A14001 - A14003]
    [A14099] - Pre-Paid, Maintenance
    [A14100 - A14213]
    [A14500 - A14900]
    PACD_FURN_MACH_EQ - Purch ACD Furn Mach Equip
    [A15001 - A15003]
    [A15099] - ACD: Pre-Paid Maintenance
    [A15100 - A15213]
    [A15300] - ACD: Building Improvements
    [A15500 - A15900]
    LEASE_ASSETS - Lease Assets
    LLAND - Capital Lease Land
    [A14004] - Capital Lease Land
    LINFRA_NONDEP - Capital Lease Infra Non Deprec
    [A14005] - Capital Lease Infra NON DEP
    LCIP - Capital Lease Cnstruct In Proc
    [A14006] - Capital Lease CIP
    LBUILD_IMPROVEMENTS - Capital Lease Building & Impro
    [A14007] - Capital Lease Bldgs & Improv
    LFURN_MACH_EQ - Capital Lease Furn Mach Equip
    [A14008] - Capital Lease Furn Mach Equip
    LINFRA_DEP - Capital Lease Infra Deprec
    [A14009] - Capital Lease Infra DEPREC
    LACD_BUILD_IMPROV - Capital Lease ACD Build Improv
    [A15007] - ACD Cap Lease Bldgs & Improv
    LACD_FURN_MACH_EQ - Capital Lease ACD Furn Mach Eq
    [A15008] - ACD Cap Lease Fur Mach Eq
    LACD_INFRA_DEP - Capital Lease Infra Deprec
    [A15009] - ACDCap Lease Infra DEPREC
    LIABILITIES - Liabilities
    [201000 - 203000]
    [L00001 - L21179]
    FUND_EQUITY - Fund Equity
    [351000] - AR - WRITE OFF
    [370000 - 388890]
    [F00007] - Fund Balance: Restricted,State
    INCOME_STATEMENT - Income Statement
    REVENUE - Revenue
    GENERAL_REVENUE - General Revenue
    [400100 - 496600]
    [900001] - Appropriation Transfer
    STATISTICAL - Statistical
    [S00001 - S00017]
    EXPENSE - Expense
    [E10000] - All Expense Accounts
    PERSONAL_SERVICES - 1 Personal Services
    [E19999] - Point 1 Roll Up
    [E51000] - Roll Up For Personal Services
    SALARIES - 510100 Salaries
    [510100 - 510101]
    [510200 - 510201]
    thanks

    Hi,
    Assuming that when you say " have make BP as DIM ID" it means that you have included it in a dimension. Correct?
    You can make it as "line item" and you will still be able to report with its NavAttr and even with time dependance (ratings) provided you time dependant attr is NAV.
    The only difference between line item dimensions and normal dims is that no dimension table created and you can only have one char in it.
    You should do that for a characteristic having very high granularity (number of records posted of your characteristic divided by the total number of records in your fact tables (F and E) ). Usually document/item numbers are in that case (granularity is more than 50%; other will say 20% but I personally think that with 20 the DIM table still reduces the query time).
    By not having the dimesion table, a query using this kind of characteristic will select the data directly form the cube fact tables instead of first going to the DIM table, gather DIMIDs and go to the E/F tables...
    hope this helps...
    Olivier.

  • Distinct count of role-played dimension attribute

    Needed distinct count of AccountGroup attribute of AccountB dimension which is a role played dimension of Account.
    Added measure distinct count of the dimension attribute (AccountGroup). In dimension usage added the main fact table as intermediate for other dimensions with many2many relationships.
    The two role played Account dimensions must be related to the new AccountFact table with fact relationship.
    But then how will I be able to count distinct attribute of
    certain Account dimension (out of the two role played dimensions)???
    Namnami

    Thanks for the links, they are useful. But still they do not explain how to manage a distinct count of
    certain role played dimension attribute. 
    I gave up on this and added that dimension attribute to the fact table so now I do a regular distinct count on a cube fact measure. 
    Thanks
    Namnami

  • One Dimension with Facts at different levels

    I currently have a single dimension with 5 levels. I have two fact tables that both connect to the dimension table but at different levels.
    For example. If we have a Dimension Country -> Region -> City and then two fact tables. One that has facts at the Region level and one that has facts at the City level.
    Is there a way to be able to have an answer that contains facts from both fact tables. So if there was a fact from City and the Region level? Everything I seem to try does not work. Would I have to create an additional aggregate table that aggregates the City level data up to the Region? Or is there a way to show the data at the lowest level and show either nulls or duplicate values for the additional records.
    Any help is greatly appreciated

    This has helped a little. I am now getting values from both levels. However, because i am summing the two values. The value from the upper level is now summing duplicate values. For example.
    Value 1 on its own
    Level1 Level 2 Level 3 Value 1
    1234 10 10 13.05
    1234 20 10 70.00
    1234 20 20 70.00
    1234 30 10 105.00
    1234 30 20 105.00
    Value 2 on its own
    Level1 Level 2 Level 3 Value 2
    1234 10 10 0.50
    1234 20 10 2.00
    1234 20 20 2.00
    1234 30 10 3.00
    1234 30 20 3.00
    What I am getting
    Level1 Level 2 Level 3 Value 1 Value 2
    1234 10 10 13.05 0.50
    1234 20 10 140.00 2.00
    1234 20 20 140.00 2.00
    1234 30 10 210.00 3.00
    1234 30 20 210.00 3.00
    Desired Outcome
    Level1 Level 2 Level 3 Value 1 Value 2
    1234 10 10 13.05 0.50
    1234 20 10 70.00 2.00
    1234 20 20 70.00 2.00
    1234 30 10 105.00 3.00
    1234 30 20 105.00 3.00
    Now, the problem with this is that Value 1 is a fact at Level 2 and Value 2 is a fact at Level 3. I have one dimension table and two fact tables. The join between the fact table for Value two and the dimension table is the same as the join between the dimension table and Value 1 only it is missing the last level of detail.
    I have then set the logical table source content tabs for each fact table to the corresponding levels.
    I thought this would be enough but i still don't get the desired result. I am not sure if this is possible with one dimension table.
    Any ideas would be greatly appreciated.
    Edited by: user10800227 on Jan 11, 2010 12:43 PM

  • SSAS Tabular: Show balance on latest dimension attribute

    Hi,
    I have a fact with transactions over time eg.
    20140101, 1000
    20140105,-400
    In SSAS Tabular, I want to add a balance (saldo) measure, that shows the balance on any given date from my date dimension
    Balance 20140106: 600
     I can do this by using SUMX (or summarize)
    Saldo:=SUMX(
    VALUES('Date'[Date])
    ,CALCULATE(
    SUM(Fact[Amount])
    ,DATESBETWEEN('Date'[Date],BLANK(),LASTDATE('Date'[Date]))
    ,ALL('Date')
    The issue arises when I want to show the balance for an attribute from a dimension related to the latest fact entry. I can calculate this on dates that has transactions like this:
    Saldo_MaxFact:=MAXX(
    VALUES('Fact'[FactId])
    ,CALCULATE(
    SUM(Fact[Amount])
    ,DATESBETWEEN('Date'[Date],BLANK(),LASTDATE('Date'[Date]))
    ,ALL('Date')
    ,ALL('Fact'[FactId])
    ,ALL('Dimension')
    But on dates with no transactions, this measure is empty (which makes sense, since there is no FactId to roll-up the sum to).
    How would I go about creating a measure that rolls up to any given date AND the attributes on the latest fact entry?
    I have created a sample snapshot: http://1drv.ms/1ly4o6a
    Sample Excel Power Pivot model: http://1drv.ms/1jy2nkX
    Any help would be much appreciated!

    Hi Greg,
    Finally I found the problem why the query goes out of memory in tabular mode. I guess this information will helpful for others and I am posting my findings.
    Some of the non-key attribute columns in the tabular model tables (mainly the tables which form dimensions) do not contain pretty names. So for the non-key attribute columns which I need to provide pretty names I renamed the columns to something else.
    For an example, in my date dimension there is a non-key attribute named “DateAltKey”. This is the date column which I am using. As this is not pretty to the client tools I renamed this column as “Date” inside the designer (Dimension
    design screen). I deployed the cube, processed the cube and no problem.
    Now here comes the fun part. For every table, inside the Tables node (Tabular SSAS Database > Tables) you can view the partition details. You have single partition per dimension table if you do not create extra partitions. I opened the partitions screen
    and clicked on the “Edit” icon and performed a Syntax Check. Surprisingly it failed. It complains about the renamed column. It complained “Date” cannot be found in source. So I realized that I cannot simply rename the columns like that.
    After that I created calculated columns (with a pretty name) for all the columns which complained and all the source columns to the calculated columns were hid from the client tools. I deployed the cube, processed the cube and performed a
    syntax check. No errors and everything were perfect.
    I ran the query which gave me trouble and guess what... it executed within 5 seconds. My problem is solved. I really do not know who did this improve the performance but the trick worked for me.
    Thanks a lot for your support.
    Chandima

  • CRM Relationship data

    Hi All
    Does anyone know how i could get relationship data from CRM Interaction centre 4.0. eg: I have 1000 Sold to BP's and need the relevant SHIP to / contact persons linked to them.
    I think it will probably be stored in a table similar to SE16N in R3 but have no clue where to get this data.
    Any help will be appreciated and points awarded.
    Regards
    Avi Patel

    Hi Avinash,
    The shipment details/ related attributes will be available in order level. if you want to do something in IC Web with that.. I think you have to check the entity named something like shippingset ( in 4.0 ).
    Regards, Sudeep..

Maybe you are looking for

  • Error in starting the Managed Server.

    Hi, Weblogic Version : 10.3.6. I got the below error while i tried to start my Managed server. I followed the link Starting/Stoping Weblogic Managed Server - weblogicexpert to start my managed server. I have provided my AdminServer user name and pass

  • Submit job in background

    Hi All I have a program with selection screen. The selection screen has Job name as one of the parameters. When I press F8 (Execute), this program should get scheduled in the background with the job name taken from selection screen. How to submit a p

  • Dynamic taget directory usinf Filename

    Hi all I have a requirement in which I have to Dynamically choose target directory depending on the filename?? Example If File name is FI08.txt ,it should be posted to following folder server\Test\<FileName>. If it has deiiferent file name it should

  • I can't get my filters to render

    I am running Final Cut Pro 7 and I have a clip that already has RGB Balance filter and Key filter on it. I am adding Brightness Contrast or any of the other Gamma Correction type filters to the clip, It lets me adjust the filter but when I render it

  • I have a macbook pro 2012 2.5ghz i5, i want to know would  Ddr3 1600mhz So-dimm Cl9 be compatible?

    I have a macbook pro 2012 2.5ghz i5, i want to know would  Ddr3 1600mhz So-dimm Cl9 be compatible?