Maintain Hierarchies in MDM

Hello all,
I've found some documents about creating and enhancing Hierarchies and categories in MDM repositories, but I still haven't understood if (and how) is possible to modify a hierarchy (from an xml file coming from SRM) even if there are records in the main table assigned to that hierarchy.
Thanks to all.
Marco

You should use an Inbound port in order to put there the XML file coming from SRM. You also need to create an import map using the import manager in order to have those hierarchies or categories modified. The name of those categories which already have items from the main table assigned can be changed, but the structure itself can not unless you first unassig them and after the change you assign them again to the correspondent categories.
I hope this helps

Similar Messages

  • Maintain hierarchies of GL Accounts

    Is there a way to maintain hierarchies of GL accounts in FI module? Is there a transaction code to do this?

    Hi,
    To create Financial Statement Version - OB58
    To Change                                         - FSE2
    To display                                          - FSE3.
    The Menu path is as under:
    SPRO >  Financial Accounting > General Ledger Accounting > Business Transactions > Closing > Document > Define Financial Statement Versions.
    Thanks
    Murali.

  • Maintaining Hierarchies in Production?

    Hello,
            Can someone tell me if it is possible/Okay to maintain to create a new heierarchy in production directly or is it to be transported?
    Thanks!

    Yes, thats very much possible, unless the hierarchy is being loaded.
    This is pretty much like master data. As we can create master data directly in production, similar is the case with hierarchy creation.
    Only change that may not be possible, if the system is locked, is in terms of hierarchy properties, such as type, intervals usage and external chars, as this would involve change to info object.
    Naveen.A

  • MDM for Retail Hierarchies

    Hello,
    We are planning to implement SAP-MDM as master data solution for retail hierarchy management.  By retail hierarchies, I mean, lcoation hierarchy, merchandizing (product) hierarchy, time hierarchy etc.  Each of these hierarchies have 4-8 levels, and have 10-40 attributes at each of the level.  The business requirement is to create, maintain, and distribute the hierarchy data. 
    1) There are requirements around validating the attribute values for required vs. non required (by business unit, for instance?), drop down vs. free form text field, text length, text vs. numeric;
    2) Then there are requirements around security that apparel user cannot update hierarchy for footwear products; an in-line user cannot update a promotional product; in-line and promotional are values of a node.
    3) Then there are audit requirements on who made what change when.
    Q1: Has anyone done retail hierarchies in MDM so far?  If so, any tips/tricks or learnings you had?  I know MDM can meet all the validation, security, audit requirements for fields; are the same available at taxonomy attribute level?
    I am also planning to use Retail artcile (out of the box) repository as the base, and add the retail hierarchy taxonomy on top of that. 
    Q2: Does anyone have field meanings, descriptions or notes for the tables and fields in the retail article repository?  f you have, could you please share them with me soon?
    My deadline for finishing the prototype and doing a demo is next Friday.
    Thank you in advance
    Savi

    Yes , Equipment master can be modeled in SAP MDM through the use of a custom repository as out-of-box business contents are not provided by SAP . Recently I came across an opportunity where they wanted to implement MDM for equipment master due to following reasons :
    Maintain a complete Equipment/Location wise hierarchy at a central place
    To be able to consolidate similar equipments across plants
    Cleanse existing Equipment masters
    Effective data management (Search , Author , Update etc.)
    Regards,

  • Make any changes in node doesnu2019t reflect in other alternative hierarchies

    I have two alternative hierarchies in MDM
    H1
    |--- N1
         |- N11
              |1005000
    H2
    |--- N1
         |- N11
              |1005000
    When i add N12 node (under Node N1) in first H1 hierarchy as mentioned below,  This doesn't reflect in H2 hierarchy automatically although N1 node already exist that should reflect this in H2 hierarchy too. 
    H1
    |--- N1
         |- N11
              |1005000
         |  N12
    Is there any workaround possible?

    Hi,
    Firstly one repository you should have one hierarchy. Anyways if you are maintaining two hierarchies then they exist independently as you see in your Main table there are two fields which are lookup to two different Subtables( Hierarchy table say H1 and H2) thts why they exist differently and you cant reflect one field made in H1 into H2. it could possible when you are maintaining two fields in your Main table and reference to same Subtable say (Either H1 or H2). Moerover i feel for same repository you dnt need to maintain more than 1 hierarchy.
    Hope it will Help you,
    Rewards if found Useful.......
    Thanks,
    Mandeep Saini

  • Buisness parter data in MDM

    Hi All,
    1. I need to maintain my buisness partner data in my repository. my buisness partner address are located in different geographies(IN, MX, US etc), and the same having differnt names like ABC ltd, ABC Inc, ABC etc.
    How can these be maintained in MDM?(without using any external interfaces)
    and why exaclty is D&B used in MDM, is it used to maintain hierarchies? how?
    Please help me understand.
    rgds,
    ve

    Adrivit ........ thanks for the quick reply............ let me explain in more detail.
    my Business partnes located in diffent geographies(IN, MX, US etc), and different names like ABC Ltd, ABC Inc etc
    so they are actually linked with some relationships.
    like ABC Ltd and ABC Inc are related to ABC group.
    so should this be maintaned using hierarchies, if yes..... can i maintain my hierarchies at a later stage.
    Meaning: i want to load all my data into the MDM repositoy without the vendor hierarchy data.
    and later on i want to import my hierarchy, because we have some issues with understanding this data. IF this is possible ........ HOW and What is the process followed and what is the impact?
    Also wanted to know .... what is D&B(Dun and Bradstreet) and why is used exacltly in MDM.
    pls reply.
    regards,
    ve

  • Creation of Hierarchie In BI.7

    Hi BI Experts,
    I searced the forums before posting but i did'nt get any answer as per my question .The data is coming from R/3 i need to create the hierarchie here the hierachie is not defined before . I know how to create hierarchie from flat file .Can any one suggest me how to create the hierarchie .
    1, waht are the steps i need to create in ECC.
    2,what are the stpes i need to create  in BI.7
    Regards
    RK

    Hi,
    Regarding the steps for creation of hierarchy in BI 7:
    1. Create a program in SE38
    in this program use a data target which stores information of node & its higher levels.
    In program
    Declare the hierarchy structure
    Declare the active table of data target
    Declare int tables, structures & work areas
    Get entire data from data target into internal table
    Store the main node in one variable & read all levels into another table
    append the levels into work area &
    write these levels along with main node into a flat file in application server.
    Once code is activated execute the program, you can have a selection screen for flat file name which will be generated in application server.
    Once program is executed successfully flat file can be viewed using tcode AL11, in tmp directory.
    2. Create an Infosource based on that main Infoobject of type flat file.
    3. Once you create the Infosource you can select the data source as <Node Obj name>_HIER and then activate the InfoSource
    4. Then create an Infopackage to laod that flat file into master data object i.e. the node object
    5. Right clicking on Hierarchy of that Info object you can select Maintain hierarchies & you current hierarchy will be listed below.
    Hope it helps.
    Thanks,
    Rashmi.

  • SAP MDM Vendor email addresses are not in order when sent to SAP R/3

    Hi Experts,
    We were trying to maintain vendor email addresses in this order in SAP MDM:
    E-mail address: massupa@nexus
    Sequence Number: 001
    E-mail address: win@nexus
    Sequence Number: 002
    E-mail address: satita@nexus
    Sequence Number: 003
    But when saving the record, its order get mixed up like below: (I believe it was arranged alphabetically automatically---> is this the standard MDM functionality?!)
    E-mail address: massupa@nexus
    Sequence Number: 001
    E-mail address: satita@nexus
    Sequence Number: 003
    E-mail address: win@nexus
    Sequence Number: 002
    When it gets syndicated to ECC, its order was maintained incorrectly with incorrect IDs:
    E-mail address             ID
    massupa@nexus        001
    satita@nexus              002   -
    > should be 003
    win@nexus                 003  -
    > should be 002
    we checked both the XML Files and the IDOC and found that it has the same order maintained in SAP MDM
    massupa@nexus        001
    satita@nexus              003
    win@nexus                 002  
    But how come the IDs were changed in R/3?
    Many thanks in advance!

    Hi Mike,
    As per your requirement, i feel that for ID either you can create a new field say sequence ID in this e-mail addresses table of MDM and thus can syndicate it or can also use ID as key using remote key concept. I mean for this e-mail addresses table, you can set property Key mapping = yes  in MDM Console and thus can use this IDs as key for this email address e.g. for massupa@nexus you can save ID as Key.
    So during syndication, map this field with target IDOC structure field and I mean Remote Key under e-mail addresses table with IDOC ID target field. In this way you can have correct IDs with their corresponding email addresses.
    Kindly let me know if you are looking for something else.
    Regards,
    Mandeep Saini

  • Does not get option to Create DS for Hierarchies

    Hi Everyone,
    I have created Hierarchies and trying to load data using a flat file. I am performing follwoing steps:-
    1] Create Hierarchies-Assign Nodes
    2] Goto Infosource> Right Click Create Infosource Direct Update for Master Data> Give The name Save it.
    3] Goto SOurce System Tree> Click on PC File Source System> Create DataSOurce> Here I get only Three optionsDS for TD, DS for Text and DS for Attr..
    In step 2] If I right click Infosource I get only two Options a] Maintain Hierarchies b] Create Transfer Rules.
    I am not sure which step am I missing?
    I have followed following link
    /people/prakash.bagali/blog/2006/02/07/hierarchy-upload-from-flat-files
    But in this When I come to Step b] I don't get that optiion of Assign Flat FIle SOurce system to the InfoSOurce.
    Can anyone please figure out what mistake I am making?
    Thanks

    Doesn't help..Still while creating Infopackage , in The second Tab "Hierarchy Selection" I cannot assign the hierarchy.
    The only difference  I could figure out is while creating Infosource, In "DataSource/Trans. Structure"  tab On the right hand side there is another small button " Hier.Structure" is not visible in my Infosource.
    I don't know why?
    Edited by: A S on Jun 18, 2010 3:55 PM

  • CCM 2.0 Catalog to SRM-MDM 3.0 Catalog during SRM 7.0 upgrade

    Hi,
    We are upgrading our existing SRM 5.0 system to SRM 7.0 and we are planning to deploy SRM-MDM 3.0 Catalog as it is more flexible & SAP is not going to support CCM 2.0 Catalog after 2013. Please let me know the upgrade steps/plan to upgrade CCM 2.0 to SRM-MDM 3.0 catalog. As per my understanding, there is no tool/method available to upgrade from CCM 2.0 to SRM-MDM 3.0 catalog available. We need to build it from scratch i.e maintain SAP supplied MDM repository, upload data from SRM/ERP, upload suppliers catalog etc.
    Thanks,
    AS

    Hi,
    I have migrated CCM to SRM-MDM Catalog.
    Steps are
    - Install SRM-MDM Catalog
    - Adjust Repository if you have custom fields
    - Import contents
    - Adjust view
    Migration itself is not difficult but you need to learn how to use MDM client tools.
    The SRM270 class room training is good one.
    http://www.sap.com/usa/services/education/catalog/globaltabbedcourse.epx?context=%5b%5bSRM_SRM_NA%7cSRM270%7c%7c%7c%7cUS%7c%5d%5d%7c
    Regards,
    Masa

  • Price History In MDM

    Hi All
    I am currently investigating into the possibility of showing price changes in the MDM Data Manager.  When items prices are updated in the Data Manager, we have a requirement to be able to view the old and new price.  I know that i can search for when the price has been updated, but i am unsure as to how i would be able to see the old price on the item.
    Is anyone able to help please.

    Hi Simon,
    However, i have hit another issue. The change tracker is good in the fact it shoes you the old and new values. However, it only shows me the entries from the price updated field in MDM, which are times and dates. It doesnt actually show me the old price and new price. Does anyone know why this is.
    According to me, maintaining versions in MDM is still a big challenge. You must be getting the updation time and date as the field may be the Time/Date stamp in MDM as they show the updated time and date when the particular field gets updated. They do not show the updated Values of the field.
    Just wanted to get to your notice that along with Change tracking , you can also try out the CCMS monitoring and check whether it fulfills your requirement.
    Hope this piece of info helps you.
    Thanks and Regards
    Nitin Jain

  • HR master data Hierarchies

    Hi Experts,
    I am implementing HR(Personnal Administation & Organizational Management) first time. For any master data Is it require to maintaine Hierarchies for masterdata. If require can u please give me the list of those.
    Regards,
    Sridhar

    Hi Sridhar.......
    It is not mandatory to maintain Hierarchies for masterdata.............Look there are three types of Master data............attributes , text and hierarchy..........now it is not mandatory that always there will be hierarchy......Moreover.......BI 7.0 does'nt support Hierarchy datasource........u hav to use BW 3.X datasource.........and 3.X data flow............u cannot Migrate it...........u can't even use emulated hierarchy datasource in BI 7.0.........
    There are seperate master data tables for hierarchy............/BIC/H -- Heirarchy Table  and
    /BIC/K -- Heirarchy SID Table.........
    In our case...........for Master data Organizational Management....we hav use the datasource 0ORGUNIT_HR01_HIER...........
    Regards,
    Debjani....

  • No Hierarchies for this InfoSource in the Source System

    Hello All,
    I want to find out how to get my hierarchy back in Bex (Query Designer).  We just got a new BW system.  The hierarchy was loading fine in the old system but unable to see it in the new system.  I have done the following and still no luck:
    Replicated the Datasource
    Replicated the Source System
    Maintain Hierarchies shows no hierarchies and when I click on create hierarchy (No values when you click on Hierarchy Name).  Whereas I get hierarchy  values in the old system.
    In the Infopackage, click on Hierarchy Selection => Available Hierarchies from OLTP, I get "There are no Hierarchies for this InfoSource in the Source System".
    Is there anything am missing?  My suspicion is may be the Hierarchies need to be maintained in ECC first and then I should replicate again and then load the hierarchy.
    Any suggestion would be appreciated.
    Thanks,
    Recca

    Thanks Sai and RDS.
    @ Sai:  Yes, the Datasource is present in BW as 3.x version which I assume is ok.  It is also present in active version in ECC in RSA6.  There is nothing to load for the hierarchy because when you click on the InfoPackage the "Hierarchy Selection" and then "Available Hierarchies from OLTP", in other to refresh the list, I get "There are no Hierarchies for this InfoSource in the Source System".
    @ RDS:  Yes, the connection of BW to the ECC Source System is good....checked out ok.  There is nothing to load for the hierarchy because when you click on "Hierarchy Selection" and then "Available Hierarchies from OLTP", in other to refresh the list, I get "There are no Hierarchies for this InfoSource in the Source System".
    Besides RSA6 to check the datasource in active version in ECC, do you have a T-Code to check where these following Hierarchies are maintained in ECC?  I need to compare it from the old system with the new system.
    1.  Fund
    2.  Fund Center
    3.  Commitment Item
    Thanks,
    Recca

  • SAP MDM features

    Hi
    Could someone tell me if SAP MDM has these features?
    u2022     Security
    u2022     Ability to maintain and assign security at Site level
    u2022     Ability to maintain and assign security at Area ( Logical Grouping like SNOP) level
    u2022     Ability to maintain and assign security at Role ( Logical grouping like SCDH, GMP) level
    u2022     Ability to maintain and assign security at Object ( Can be a page or a subset on a page) level
    u2022     Ability to maintain and assign actions-object combination to a role
    u2022     Ability to maintain and assign security at Row Level
    u2022     Ability to maintain and assign security at Column Level
    u2022     Ability to inherit role characteristics to another role
    u2022     Ability for one role characteristics to override the characteristics chosen for another role, while inherting ( Denial to update an Object for a role, should remain the same even if the role gets inherited
    u2022     Ability to audit any changes to Security on any Role/Object/Action (Will be tracked against BR5.1)
    u2022     
    u2022     Ability to handle Master Detail relationship
    u2022     Ability to handle MultiLevel data Hierarchy
    u2022     Ability to handle Dependency List
    u2022     Ability to maintain detail data in tabs on the same page
    u2022     Ability to mandate the need to enter Detail data for a new Master record, or tie a new Detail record to an existing Master record
    u2022     
    u2022     Ability to handle import and export of predefined formats
    u2022     Ability to import and parse CSV, XLS and TXT files
    u2022     Ability to import and parse XML files
    u2022     Ability to export data in PDF format
    u2022     
    u2022     Ability to handle Approval Process for data entered
    u2022     Ability to configure Approvers with Approval Levels at the time of object configuration
    u2022     Ability to prevent an Approver with lower Approval Level to approve data, before the higher level Approvals are obtained
    u2022     Ability to send an email to the required approvers, with the link to the page/object needing approval
    u2022     Ability to authenticate the NT login of the approver, accessing a page/object via a link on an email
    u2022     Ability to approve through email, by linking to a webservice
    u2022     Ability for the user to nominate a proxy for a given time duration
    u2022     Ability to control deletion of an approver through Admin access
    u2022     Ability to identify data that has not been approved and prevent database access to it.
    u2022     Ability to provide read-only access to data that has not been approved
    u2022     Ability to message out changes/addition on Master data to all Subscribers.
    u2022     Ability to message out potential changes on Master data to all Subscribers
    u2022     Ability to add an approver/subscriber to any step of the entire approval process
    u2022     Ability to prevent any further actions like export/import to data that has not been approved
    u2022     
    u2022     Ability to provide Historical Reports to identify how tool is used and highlight areas with most frequent changes
    u2022     Ability to capture and view all historical changes to user access
    u2022     Ability to capture and view all historical changes to data
    u2022     Ability to capture data range for all Master data, to indicate the validity of a data element.
    u2022     
    u2022     Ability to provide a Dashboard to display data entered
    u2022     Ability to provide read-only access to any data maintained throught the MDM
    u2022     Ability to capture each page/object added to the MDM, and provide it as a drop-down list for the user to choose from
    u2022     Ability to choose filter and view data for each page/object chosen
    u2022     
    u2022     Ability to access Help Documentation / List of Contacts for each screen
    u2022     Ability to maintain a Help document for each page/object
    u2022     Ability to maintain Tool Tips for each column in a Page
    u2022     Ability to provide a List of Contacts for each page/object
    u2022     
    u2022     Ability to access data via a Web Service
    u2022     Ability to access all data through Composite webservice
    u2022     
    u2022     Ability to provide Maintenance features
    u2022     Ability to provide Grid Feature which allows Search, Sort, Grouping and Pagenation capabilities for all maintenance screens
    u2022     Ability to provide Lookups for Standard Input fields like Date time. Lookup would be dependant on the client location
    u2022     Ability to provide timeout on inactivity, on the site
    u2022     
    u2022     Ability to add Favorites
    u2022     Ability to add Recently Accessed Pages as Favourites, at a Site Level
    u2022     Ability to choose views of a page and make it a Favourite, so that every consequent login, gives the same look for the same Object
    u2022     
    u2022     Ability to Support MultiLanguage
    u2022     Ability to provide Labels/Legends in Multilanguage
    u2022     
    u2022     Business Rules to Validate Data

    Hello mkhairi
    For more of your question answer -YES
    SAP MDM support trusted connection technology and LDAP
    SAP MDM has own user role functionality where you can set permissions for user security
    SAP MDM has JAVA,ABAP, COM, .NET(ver.7.1) API and you can use it for custom development
    SAP MDM has own web service for work with data in repository
    SAP MDM has own packages for development SAP NetWeaver Portal content
    SAP MDM has own workflow integrated with SAP NetWeaver Portal trough UWL
    SAP MDM has application for web publishing
    and many many other functionality from your list
    more about SAP MDM you can read here:
    http://help.sap.com/saphelp_nwmdm71/helpdata/en/index.htm
    Regards
    Kanstantsin Chernichenka

  • Maintain Hierarchy Using Programming in SAP MDG

    Dear SAP MDG guru,
    Can someone have an idea how to maintain/modify hierarchies in MDGF using a programming sequence?
    we have a requirement where in cost center we have a field cost center group, after the cost center created, we build an exit program in workflow to attach/move cost center to the appropriate cost center group,
    I already know how to maintain hierarchies using hierarchies processing menu, where we can remove or add cost center in cost center group, but i need to now what is the standard program/FM use to doing that,
    anyone have an idea?
    thanks

    Hi,
    there is no standard for that. You have to use collective processing.
    Best regards
    Michael

Maybe you are looking for