Split hierarchy - syndicator

Hi,
    I am trying to do the spilt hierarchy by root/leaf operations in syndciator. For some of the lookup hierarchy table i seeing the root/leaf is grayed out. Not allowing me to the op's. The same is true for by value and others? I tried to it on Repository TE07_products_XXX provided by sap as sample repository. Its the same.
  Any idea why is it happening?  is there any chance that I can ONLY download the hierarchy lookup table records NOT the main  table used from lookup table by using "spilt hierarchy".
Thanks

Hi,
You cannot perform Split Hierarchy operation for the hierarchy fields which are Multi-Valued. In Products repository, you cannot split Hierarchy Fields Class Hierarchy and Category Hierarchy because for both the fields Multi-Valued is set to yes.
Regards,
Jitesh Talreja

Similar Messages

  • Better Practice - split dimension table or split hierarchy?

    Hi All,
    I have an Org dimension table that has geography and organizational structure within it (columns - state-city-etc.) and (columns division-department-etc.). Is it better to create a dimensional hierarchy with 2 trees (1 being geography sub-hierarchy from ALL and the other being ORG) or is it better to split table at BMM layer and create a logical geo and logical org tables separately. What do you think? Thank you

    Great help thank you. I was also leaning towards the same decision, but now I'm just sure. Venkat, when you're saying that OBIEE cannot handle 2 hierarchies, do you mean that a Fiscal Year / Calendar year model wouldn't work - and I think it's how it is in the OBI vanilla marketing app. I just want to make sure I understood your correctly. If yes, then are those 2 expected to have the same amount of children (i.e. I might have Week level in Calendar, but skip it for Fiscal). Thanks

  • Splitting hierarchy into a dimension

    Hi,Currently i have a "Clients" dimension (as one of my dimensions) with following hierarchy...Clients Personal Corporate ABC-Head ABC-Member1 ABC-Member2 : : XYZ-Head XYZ-Member1 XYZ-Member2 : : (etc)Normal process takes less than 20 minutes. (both loading & calculation)I want to modify this by moving the Client Heads(ABC-Head, XYZ-Head) and the members on a separate dimension. So what i did was the following :Group Clients {Client Type} ABC-Head (Corporate) XYZ-Head (Corporate) : : Member Clients ABC-Member1 ABC-Member2 XYZ-Member1 XYZ-Member2 : : Client Type Attribute Personal CorporateAfter these changes, my loading & calculation time took longer ( 2 hrs and still processing) obviously because of the new dimensions introduced.I would appreciate if anyone of you can help me minimize the processing time using the above format. Or anyone of you can suggest a new approach.Btw, my purpose of splitting the dimensions... inorder to present them in separate row (analyzer report), instead of drilling down into it.Rgds,

    This sounds like an attribute dimension, if you are on v6+ then utilise this functionality to provide cross tab reports.Hope this helpsAndy Kingwww.analitica.co.uk

  • Split hierarchy

    Hi Folks,
       Can I combine two hierarchies which are split hierarchies. The main idea would be I have hierarchy with the values and will want to merge the description also with that values which is again an hierarchy.
    Cheers,
    Triveni

    Hi,
    With this kind of source data , I don't see an option in the Import manager to merge these 2 hierarchies.
    What I would suggest is if your source data is like
    00          Wood
    00 77       Chairs
    00 77 7777  Flat
    00 88       Basket
    00 88 8888  Round
    You can have the hierarchy what you are talking about.
    I had the same situation in my previous project, for implementing UNSPSC categories, upto 4 levels.
    Then we did some macros in Excel to convert into the above format and then we imported the data  into MDM.
    Hope this helps
    Thanks and Regards
    Subbu

  • Can we import multiple language descriptions in Hierarchy tables of MDM

    Hello Experts,
    I am using MDM 7.1 SPS4 and working on the Vendor Repository standard content.
    My source file of Regions table contains data in multiple languages for each region record. All the required destination language fields have been mapped properly in the standard map. Import action is set to 'Create' for new records and 'Update Mapped only fileds' for existing records. Matching criteria has Name<English> filed defined in it.
    However, after importing these hierarchy records, in data manager only the Name description of English is populated while all other language descriptions for the same record is shown in Red (i.e not populated with the expected data).
    Is this a limitation of MDM itself or am I missing some setting?
    Thanks in advance,
    Elizabeth.

    Hi Elizabeth,
    steps for importing  into hierarchy tables
    To add new multilingual records:
    1 If necessary, create the hierarchy from the current language layer Name field that contains the hierarchy information (e.g. using the Split Hierarchy command).
    2Map the current language layer Name field and then Map/Add the entire set of hierarchy values.
    3 Map the other language layer Name field(s). No value mapping is necessary.
    4 Map the [Remote Key] field.
    5 Record match using: (a) the Name field; (b) the [Remote Key] field (if the Name field was not value mapped); or (c) the combination of both.
    To update the language layer of existing records:
    Map the other language layer Name field(s). No value mapping is necessary.
    Map the [Remote Key] field.
    Record match using the [Remote Key] field and set the import action to Update (All Mapped Fields).
    Just try and if you need any other info then please get back to me.
    Thanks,
    Sudhanshu

  • Created "Hierarchy Field" not saved in Import Mapping File

    Hello experts,
    I want to save the mapping created after having imported categories via MDM Import Manager.
    Everything works fine as I execute an initial import (In "Map Field" tab, I create a "hierarchy field" based on the three fields "Categorie Name, Categorie Name 2, Category Parent" and mapp the Split Hierarchy field consequently ).
    My problem is as I save the Mapping and try to reuse it for a new Categories import, the former "hierarchy field" does not appear anymore. I assume Saving Mapping does not save created hierarchy fields...
    Can anyone help me on this?
    Thanks in Advance
    Stephane Naigeon

    From XML, with fields "Category Name, Category Parent".
    Then in MDM Map Tab, I clone the Field "Category Name" and create the Hierarchy Field with name "Categories", parent field "Category Parent", Child Field "Category Name", and Node name field "Category Name Clone".
    Then I map the Split Hierarchy field with the destination field "Category Name [DF]", and the source field "Category Name" with the Remote Key.
    The matching field in Match Record Tab is "Category Name [DF]".
    I save then the mapping file but am not able to reuse it : as I said, the Hierarchy field disappears !

  • Error when Bulk load hierarchy data

    Hi,
    While loading P6 Reporting databases following message error appears atthe step in charge of Bulk load hierarchy data into ODS.
    <04.29.2011 14:03:59> load [INFO] (Message) - === Bulk load hierarchy data into ODS (ETL_LOADWBSHierarchy.ldr)
    <04.29.2011 14:04:26> load [INFO] (Message) - Load completed - logical record count 384102.
    <04.29.2011 14:04:26> load [ERROR] (Message) - SqlLoaderSQL LOADER ACTION FAILED. [control=D:\oracle\app\product\11.1.0\db_1\p6rdb\scripts\DATA_WBSHierarchy.csv.ldr] [file=D:\oracle\app\product\11.1.0\db_1\p6rdb\temp\WBSHierarchy\DATA_WBSHierarchy.csv]
    <04.29.2011 14:04:26> load [INFO] (Progress) - Step 3/9 Part 5/6 - FAILED (-1) (0 hours, 0 minutes, 28 seconds, 16 milliseconds)
    Checking corresponding log error file (see below) I see that effectively some records are rejected. Question is: How could I identify the source of the problem and fix it?
    QL*Loader: Release 11.1.0.6.0 - Production on Mon May 2 09:03:22 2011
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    Control File:   DATA_WBSHierarchy.csv.ldr
    Character Set UTF16 specified for all input.
    Using character length semantics.
    Byteorder little endian specified.
    Data File:      D:\oracle\app\product\11.1.0\db_1\p6rdb\temp\WBSHierarchy\DATA_WBSHierarchy.csv
    Bad File:     DATA_WBSHierarchy.bad
    Discard File:  none specified
    +(Allow all discards)+
    Number to load: ALL
    Number to skip: 0
    Errors allowed: 50
    Bind array:     64 rows, maximum of 256000 bytes
    Continuation:    none specified
    Path used:      Conventional
    Table WBSHIERARCHY, loaded from every logical record.
    Insert option in effect for this table: APPEND
    TRAILING NULLCOLS option in effect
    Column Name                  Position   Len  Term Encl Datatype
    PARENTOBJECTID                      FIRST     *  WHT      CHARACTER
    PARENTPROJECTID                      NEXT     *  WHT      CHARACTER
    PARENTSEQUENCENUMBER                 NEXT     *  WHT      CHARACTER
    PARENTNAME                           NEXT     *  WHT      CHARACTER
    PARENTID                             NEXT     *  WHT      CHARACTER
    CHILDOBJECTID                        NEXT     *  WHT      CHARACTER
    CHILDPROJECTID                       NEXT     *  WHT      CHARACTER
    CHILDSEQUENCENUMBER                  NEXT     *  WHT      CHARACTER
    CHILDNAME                            NEXT     *  WHT      CHARACTER
    CHILDID                              NEXT     *  WHT      CHARACTER
    PARENTLEVELSBELOWROOT                NEXT     *  WHT      CHARACTER
    CHILDLEVELSBELOWROOT                 NEXT     *  WHT      CHARACTER
    LEVELSBETWEEN                        NEXT     *  WHT      CHARACTER
    CHILDHASCHILDREN                     NEXT     *  WHT      CHARACTER
    FULLPATHNAME                         NEXT  8000  WHT      CHARACTER
    SKEY                                                      SEQUENCE (MAX, 1)
    value used for ROWS parameter changed from 64 to 21
    Record 14359: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 14360: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 14361: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 27457: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 27458: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 27459: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 38775: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 38776: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 38777: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 52411: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 52412: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 52413: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 114619: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 114620: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 127921: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 127922: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 164588: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 164589: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 171322: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 171323: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 186779: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 186780: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 208687: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 208688: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 221167: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 221168: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Record 246951: Rejected - Error on table WBSHIERARCHY, column PARENTLEVELSBELOWROOT.
    ORA-01400: cannot insert NULL into ("ODSUSER"."WBSHIERARCHY"."PARENTLEVELSBELOWROOT")
    Record 246952: Rejected - Error on table WBSHIERARCHY, column PARENTOBJECTID.
    ORA-01722: invalid number
    Table WBSHIERARCHY:
    +384074 Rows successfully loaded.+
    +28 Rows not loaded due to data errors.+
    +0 Rows not loaded because all WHEN clauses were failed.+
    +0 Rows not loaded because all fields were null.+
    Space allocated for bind array:                 244377 bytes(21 rows)
    Read   buffer bytes: 1048576
    Total logical records skipped:          0
    Total logical records read:        384102
    Total logical records rejected:        28
    Total logical records discarded:        0
    Run began on Mon May 02 09:03:22 2011
    Run ended on Mon May 02 09:04:07 2011
    Elapsed time was:     00:00:44.99

    Hi Mandeep,
    Thanks for the information.
    But still it doesnot seem to work.
    Actally, i have Group ID and Group Name as display field in the Hiearchy table.
    Group ID i have directly mapped to Group ID.
    I have created a Split Hierarchy of Group Name and mapped it.
    I have also made all the options configurations as per your suggestions, but it doenot work still.
    Can you please help.
    Thanks,
    Priya.

  • Is it possible to use MDIS to import to hierarchy tables?

    Hello everybody!
    Tell me, please,is it possible to import records into hierarchy tables using MDIS?
    The imported XML-file looks like this:
    <data>
    <row>
      <NAME>Some Name</NAME>
      <DATA_UPD>01.27.2006</DATA_UPD>
      <HIER>03000000000\03408000000\03408553000</HIER>
    </row>
    <row>
    </row>
    </data>
    The field HIER in my XML-file contains delimited values to build hierarchy. I tried to import, but MDIS blocks the port with Value Exception.
    P.S. I set MDIS Unmapped Value Handling option to "Add" to automatically add missing values to hierarchy table.
    Thanks,
    Vika

    Hi!
    Jasbir, Dilmit, thanks for your answers!
    But while configuring mapping of fields of my XML-file to hierarchy table fields in Import Manager I found an option "Set MDIS Unmapped Value Handling" which can be set to Ignore (default), Add, Map or Fail. If I set this option to Add, it offers to "Add Target Node for Unmapped Values in MDIS Mode". So, I expect that selecting some node shows MDIS to which node it should add all new unmapped values.
    The imported XML-file structure looks like this:
    <data>
    <row>
    <NAME>Some Name</NAME>
    <DATA_UPD>01.27.2006</DATA_UPD>
    <HIER>03000000000\03408000000\03408553000</HIER>
    </row>
    <row>
    </row>
    </data>
    1. I splited HIER field into hierarchy using "Split into Hierarchy" command.
    2. Then mapped HIER<Split Hierarchy> field to CODE field of my resulting hierarchy table.
    3. Then for CODE field I set "MDIS Unmapped Value Handling" option to Add and chose the node to which add unmapped values.
    4. Then I tuned matching fields.
    5. Saved the map.
    6. Configured port (of type Automatic).
    7. Added XML-file to the port.
    The result of import (using MDIS) into hierarchy table is that the CODE field is filled with hierarchical values, but all other fields are empty. And MDIS blocks the port with Value Exception.
    So, I embarrassed by this: on the one hand, MDIS imports some values and even builds the hierarchy correctly, but from the other hand, the import doesn't  finish.
    Can anyone explain this to me?
    Thanks in advance,
    Vika

  • Importing Hierarchy table in hierarcy struture, How?

    hi friends
    i am trying to import soure file(Acces), which contains three fields which contain data as shown below
    they are
        field1                                     field2                                   field3
                                                     10                                    Products
           10                                     1001                              Bateries,Power & Surge
          1001                                 100101                             Alkaline Batteries
          1001                                  100102                          Battery Backups
            10                                      1002                             Calculators & POS
          1002                                100201                        Basic-Display Calculators
          1002                                  100202                               Cash Registers
            20                                     20                                        Services
             20                                    2001                               Access & Security
            2001                           200101             Acccess Request-Application or Site
            2001                             200102                        Access Request-Chat/IM
    Now i want to convert this fields in to hierarch struture and i want to import this into hierarchy table which contain two fields(i.e.field1 and field2), in the data manager
    My problem is
    1) i want to import the data in the corresponding fields
    2) at the same time after importing, i want the data of the this fields should appear as a parent child relationship in the data manager.
    if any one know the solution for this , please explain in step by step process.
    if you have any PDF's on every Import operation in the MDM please provide to me.
    It  will be greatful for me.
    Thanks in Advance.......
    bharat.chinthapatla

    Hi bharat,
    if your source data is like this ex:
    1. Consumables & Maintenance Solutions;Cleaning, Freshening &  Softening;Cleaners;Cleaner Compounds
    2. Hand, Power, Machine, & Measuring Tools;Assembly & Fastening;Wrenches;Manual Wrenches;Manual Wrench Parts & Accessories
    you can follow this process:
    1. select the category and right click, in the context menu set the split delimeter, in that choose split hierarchy.
    2. select the category and right click, from the context menu select split into hierarchy.
    3. In Map fields/values tab, in source fields you will see new split hierachy field, map this field to corresponding destination cateory field.
    4. in values pane, you can see the source values in a hierarchy.
    5. Map these values to the corresponding destination values, other wise you can add to the destination in a new category, ( select the source values node and click on add button and you can selcect Add branch as child Or Add branch as sibling)
    6. Once value mapping is over, do the importing and you can see these results in Data manager Taxonomy mode.
    as you said: you have data like field1 field 2 field 3
    You have to select all the fields in Import Manager which u need to hierarchies and select the option “ Create Hierarchy field ”. You will see a new popup window in which you have to fill  the fields like ( parent field/ child filed and node) and your hierarchy will be created.
    hope this may help You,
    Regards,
    srinivas

  • Can "Create Internal Leaf" be done for multiple nodes of a hierarchy

    Dear all,
    Since MDM cannot associate main table record to non-leaf node in a hierarchical lookup table, I need to create internal leaf nodes for those non-leaf nodes. But the number of target non-leaf nodes is really huge. Is it possible to select all of them and create internal leaves all together?
    Thanks + Best Regards
    Jerome

    Hi
    I think if we can create hierachy by levels not thru parent-child way but split hierarchy creation, the the level 2 or level 3 (last level of any hierarchy)should become a leaf node.
    I tried that but it is creating 'Null' for leaf nodes. i.e. not stopping at level 2 or 3 while creating hierachy. If we can get a workaround to stop 'Null' creation , problem can be resolved. I am in sp4.
    I will be interested to know the resolution
    -reo

  • Publishing Hierarchy Nodes

    Hello All-
    Is it possible to publish (within Publisher) all of the nodes of the hierarchy to which a record is associated?
    Within Data Manager, I can export and choose an option to "split hierarchy fields into multiple columns". This will return the individual tree nodes. I would like to do something similar in Publisher in order to return each node but it seems to only allow me to publish the single node that the record is directly associated with.
    Any ideas?
    thanks
    Tim

    Tim,
    I don't think there is currently anyway to accomplish this with the Publisher, other than adding that data to another field. There is a way to pull the parent nodes in the Indexer, but that functionality does not seem to be in the Publisher. You may need to send SAP an enhancement request for this one.
    Thanks,
    Tim

  • Importing Hierarchy(UNSPSC)

    Hi all,
    I am bussy with an MDM 7.1 implementation.I need to laod UNSPSC Hierarcies (6 levels). Does anybody have an example of what the layout should look like for an import file.
    We use two fileds,  CODE field (DF)and Definition Field. Also could you highlight the steps to import.
    Thanking you
    Chris Huggett

    Hi Chris,
    As above replies - to create hierarchies during import you will need to use Access. If your source data (UNSPSC number & definition) are separated with delimiter(;):
    follow these steps:
    1. Select Source table & Destination table.
    2. In the Source Hierarchy pane, right-click on the Hierarchy node and select u201CSet Split Delimiter | Split Hierarchyu201D. You should see the inherit default Delimiter, you set the new delimiter.
    3. In the Source Hierarchy pane, right-click on the Hierarchy node and select u201CSplit into Hierarchyu201D
    4. You should see a new field Hierarchy node <split Hierarchy> has been created in the source Hierarchy pane.
    5. In the Source Fields pane, click on the Hierarchy node<Split Hierarchy> field to select it  and map this to  UNSPSC(DF).
    6. Do Value Mapping( here we will have 4 options - Add as Sibling, Add as Child, Add Branch as Sibling,
    Add branch as Child).
    follow this article:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30aa1447-80a1-2a10-e483-a76087bcb12f
    Hope this may help you.
    Thanks,
    Srinivas

  • Mapping problem with Multiple destination values

    Hi,
    I recently started to work on SAP MDM as a beginner. I am posting this message to get some help to solve the problems that I encountered as I run the SAP.
    For example, we can sub-categorize a 'Product' as Food>ProcessedFood>Frozen Food>Pizzas'. However, notice that there exist the sameNode name under the 'Commodity' as following two categories show.
    Product>Food>Processed Food>Frozen Food>Pizzas
    Commodity>Food>Processed Food>Frozen Food>Pizzas
    The Node name, 'Pizzas', under two different categories has fewattributes such as A, B, C, and D. When I tried mapping these attributes at Map Field/Values Tab under the import manager, I ended up getting warning messages due to the overlapping.
    The message says "One or more of the source values were mapped to multiplz destination values. Some of the mapped destination values may need to be unmapped before performing the import."
    Does anyone have an idea to solve this overlapping problem?
    I will really appreciate your answer.
    Edited by: coolpsy on Jun 8, 2010 4:27 AM
    Edited by: coolpsy on Jun 8, 2010 7:55 AM

    Hi,
    As per my understanding, there are two categories as shown by you
    Product>Food>Processed Food>Frozen Food>Pizzas
    Commodity>Food>Processed Food>Frozen Food>Pizzas
    and you want to link Attributes with specific correct Category say Product not with Commodity. So in order to avoid overlapping, try using option Split Hierarchy. For more details Please refer below Article: refer page 11-15/20
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/308c62a2-5faa-2a10-fda6-fa4aa7169734?quicklink=index&overridelayout=true
    Also refer, http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6090d0bd-1da7-2a10-468f-bdd17badb396?quicklink=index&overridelayout=true
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8090941f-a5a7-2a10-3ba6-b4af5ec6d97b?quicklink=index&overridelayout=true
    Just check and revert with Result if it helps..
    Regards,
    Mandeep Saini

  • Problem when import reference data Regions for Vendor

    Import status is:
    Action items:  Map 'Name_English <Split Hierarchy> <Regions>' field value(s)
    In Map fields/values tab
    I don't know how to do there.
    Thanks

    Thanks for you guys' reply.
    Yes I'm working on SAP business content.(standdard)
    Here's screen shot.
    [mdm|http://0dlsqa.blu.livefilestore.com/y1p1DZhGrGx5EsTtxsqNZNm-L0x4Cr0z3Wm2BXkelhWs20sIzFTRsRF1Y3qHM1l-TMs8sN6TE7YrfVcT855M9bqXSNlFTJNAQfs/maps.jpg]
    you can see that 'map' button is gray.

  • Import of Multilingual hiarchy

    Hello,
    I am facing the problem to import a two language hierarchy into a MDM hierarchy table. I used the Import Manager and a flat excel file with two columns. One for english one for german.  Each field holds three values seperated by semicolons. So I want to have a hierarchy with three levels.
    Splitdelimiter in my Import map is ";" and I split each column into a hierarchy and map it to my destination hierarchy table. Here are two fields to map to Name[eng] and Name[ger].
    After performing the import the hierarchy looks exactly as wanted in english, but there are no german values. These values didn't make it so only the green english values are displayed.
    What is the correct was to import this simple demand?
    Answers will be rewarded
    Nicolas

    Hello,
    I have the same problem. I'm working with MDM Version 5.5 SP5 ( 5.5.42.90)
    I need to import a second language into the Hierarchy
    -> I’m following the description (below) of the SAP Library
    -> the Import Manager shows on the import status tab that it wants to do the import of the second language
    -> no error appears for the import, everything seams normal, second language values are automatically value mapped
    => but it just doesn’t import the second language.
    In Import Manager the following configuration is done:
    Set the property for "Expand Multilingual Text Field" to As Multiple Fields
    In despair I tried different things :
    Import of both languages together , separated ;
    Matched over Hierarchy name alone, remote alone, the two together, also with the two languages.
    I even tried the import with changed hierarchy display field to “Hierarchy code” and not “Hierarchy name”.
    I did the import with system language and login language in the second language.
    No way to get the second language into the table, just manually in Data Manager.
    Has anyone experience with multilingual import into the Hierarchy?
    Thank you very much for helping me.
    Best regards
    Su
    SAPLibrary: Import Multilingual Data Into Lookup Tables
    If necessary, CREATE the hierarchy from the current language layer Name field that contains the hierarchy information (for example, using the Split Hierarchy command).
    Note: Hierarchy: Only one language layer Name field contains the hierarchy information.
    Map the current language layer Name field
    Map/Add the entire set of hierarchy values
    Note : Hierarchy: Now supports mapping of internal nodes
    Map the other language layer Name field(s)
    No value mapping necessary
    Note: Hierarchy: Map Value button previously could not be unchecked for hierarchy field and so Name field had to be value mapped.
    Map the [Remote Key] field
    Record match using:
    1)  The Name field
    2)  The [Remote Key] field (if the Name field was not value mapped)
    3)  The combination of both
    Note: [Remote Key] previously not available as a record matching field, and so Name field had to be used for record matching.
    To UPDATE one or more language layers of existing records
    Map the other language layer Name field(s).
    No value mapping necessary
    Note: Hierarchy: Map Value button previously could not be unchecked for hierarchy field and so Name field had to be value mapped
    Map the [Remote Key] field.
    Note: [Remote Key] previously did not exist, and so current language layer Name field had to be mapped.
    Record match using the [Remote Key] field and set the import action to Update (All Mapped Fields)
    Note: [Remote Key] previously not available as a record matching field, and so Name field had to be used for record matching. Hierarchy: Can use [Remote Key] field for record matching because Map Value button can now be unchecked for hierarchy field and so Name field no longer needs to be value mapped.

Maybe you are looking for

  • Problem with SSL and IAS 9.0.4.3.0

    Hi, I want to use SSL for my own webservice, but when I enabled SSL for my AS then I can't use my Forms-Applikation. I use a new installed Applikation Server Version 9.0.4.3.0 (Forms/Reports) on SLES 9 and the webservice is in a new OC4J-Container. W

  • Unable to install downloaded additional content in Windows 8

    I am trying to install additional content for Premiere Elements 10 running Windows 8.  I downloaded the additional content and when I extract the file, the Installwizard pops up and says; the installwizard will allow you to 'remove' Premiere Elements

  • Enlisting a JMS session as part of a distributed tx in SFSB

    Consider the following method in a SFSB (Seam 2.1.2, JBoss 4.2 AS, EJB 3.0, JPA 1.0, Hibernate as persistence provider). I am trying to enlist the JMS session as part of the distributed tx and testing this using both local-tx-datasource and xa-dataso

  • Difference between Active DCs and Inactive DCs?

    Difference between Active DCs and Inactive DCs?

  • UC 520 not broadcasting.

    I have gone into global config mode.  Turned off/re-enabled the wireless device and it still does not broadcast.  CCA says that it is broadcasting.  any help would be greatly appreciated.