Central Master Data DSO

Hello everybody,
I'am building up an EDW and actually have some problems on loading some master data in a DataStoreObject on the harmonization layer.
I try to explain the szenario with an example:
DataSource 1 (Sorts of icecream):
ID (let's say I have 20 sorts of Ice -> So the ID would have an range of 1-20)
Text
ColorID (ID for the color of the icecream, let's say there are five different colors)
example
ID: 1
Text: Vanilla
ColorID: 1
DataSource 2 (Colors of the icecream):
ColorID (1-5)
Text
example:
ColorID: 1
Text: yellow
Problem
On the harmonization layer, I want to have a DSO with the following structure:
ID (1-20; Key)
ColorID (1-5; Key)
Text (Sort of Icecream)
Text (Color)
example:
ID: 1
ColorID: 1
Text: vanilla
Text: yellow
The problem is, that he is always writing two rows for values like in the example. Of course understand why: The Color don't have the ID (Sort of the IceCream) as a key. So the Systems is doing the following:
ROW 1
ID: 0
ColorID: 1
Text:
Text: yellow
ROW2
ID: 1
ColorID: 1
Text: vanilla
Text:
After I long way of trying I try to find an answer on this way.
Thank you in advance!!
P.S.
Rule on the harmonization layer: No InfoObjects with MasterData are allowed!

I'm guessing that you have two transformations right now, one from DS 1 to the DSO and one from DS 2 to the DSO, right?
To do this right, you need only one transformation from DS 1 (flavors) to the DSO. In the end routine of that transformation, you can look up the corresponding text for the color and populate the DSO field.
Another way to do this would be to give the color infoobject text and you can load DS 2 into the color iobj text instead of to the DSO. You could also drop the flavor text from the DSO and make it text of the flavor iobj. This is the recommended approach especially if you may need to translate your texts to other languages in the future.

Similar Messages

  • Difference between Consolidation, Harmonization and Central master data man

    Hi ..Expertise
    Consolidation is use to identify duplicate records and merge them into one record.
    Harmonization is the process of pushing the new cleansed data back out to your partner systems.
    Central master data management means you create records within MDM and then you distribute (Syndicate) this centrally created data to your Remote Systems.
    My Question is her after Consolidation both Harmonization and Central master data management is doing the same thing i.e. sending the clean data to the other system. What is the difference between these two? Please explain me with an example or scenario..

    Hi Yugandhar,
    There are three basic scenarios that we follow in MDM:
    Data Consolidation
    Data Harmonization
    Central Master Data Management
    Consolidation :
    Conolidation (matching , normalization, cleansing) and storage of master data imported from client system. Entails capabilities to identify identical and similar objects spread across the local systems , build consolidated master data.
    Key Capabilities:
    1. Cleansing and de-duplication
    2. Data normalization including categorization and taxonomy management
    3. New interactive consolidation capabilities
    Data Harmonization :
    In case of Harmonization we generally aim at reaching high quality master data within heterogeneous system landscapes. Here the main focus is on ensuring high quality of master data within the connected systems and then distributing the Master data
    Key Capabilities:
    1. Automated synchronization of globally relevant master data information
    2. New Interactive distribution capabilities
    Central Master Data Management :
    In case of CMDM, it is not always the scenario that the Client wants to go for the above two scenario`s, but CMDM is always required as it helps us to maintain the Business data effectively and efficiently.
    After MDM is put into the business scenario all the operations related to the Master records are done in MDM only. For Eg: Creating a record, Deleting a record, Distributing a record etc.
    Now it is the work of CMDM to centrally maintain the data and check that no duplicate enteries can be created.
    And all the various systems that are attached to MDM gets the updates from CMDM with the help of Syndication Process or Distribution Process.
    Key Capabilities:
    1. Central creation and maintenance of data
    2. Ongoing master data quality
    Hope this would be helpful !!!!!!!!!
    Regards,
    Parul

  • Central Master Data Management

    Hi All,
    Can anyone tell me about central master data management ?
    In what way it is difference from consolidation and harmonization?
    I have gone through several documents but i did n't get any idea on that topic.
    If anyone have knowledge on CMDM, Please explain in their own words.
    Thanks
    Narendra

    Consolidation and Harmonization procedures are very different from CMDM (central master data management), however often times CMDM is not very useful without considering the other two as well. 
    Consolidation essentially means creating identity around your master data across your landscape.  More specifically you want to identify duplicate records and merge them into one record.  Harmonization is the process of pushing the new cleansed data back out to your partner systems.
    Central master data management is the process of creating and managing enterprise level attributes in one place.  One common mistake that people make is that central master data management means having one place to create your records and containing ALL data.  This is not correct, MDM focuses on enterprise level attributes.  In other words, which attributes are KPI's, shared across multiple processes in scope, shared across multiple systems, important for reporting, need ultimate quality, etc.  Once you have determined your data model then you begin developing the workflow (if needed) around the creation of master data.  This way you can easily keep your data clean and free of duplicates moving forward following a consolidation and harmonization process.

  • Central Master Data using Guided Procedures

    Hello Experts,
    I am working on a scenario where we have to create master data centrally using Guided Procedures. I don't have any idea about GP. We have to implement an approval mechanism using GP for our custom repository.
    I have read the PDF document available on sdn regarding this. But its for MDM5.5 SP04 and the files are also not available for download.
    We are currently working on MDM5.5 SP06 Patch2.
    Is anybody working on the same scenario?? Any help regarding this, as to how to implement this scenario will be really appreciated.
    Thanks in Advance,
    Becky.

    Hi Markus,
    Thanks for your response, but unfortunately i have already referred to that link.
    I am actually having problem in locating (or creating new ones), those 2 files which are deployed through SDM in the scenario given.
    Can anybody help me with this part?? I am working on MDM5.5 SP06 Patch 2.
    Regards,
    Becky.

  • How to lock R/3 master data transatcions when using Central MDM Scenario?

    Hello Colleagues.
    We are implementing a Central master data management scenario, all master data will be created / changed within MDM; so we need to block create/change for fields that are considered in MDM for the master records within R/3.
    In a previous project we used authorization profiles to achieve this task. I supose an other option is to use the field status configuration.
    However, I was wondering if SAP has something standard to achieve this blocking within R/3?
    Thank you for your answers.
    Regards,
    Jorge.

    Hi Jorge,
    SAP MDM has released Central Master Data management as standard already.  Also SAP MDM SP04 has more features which will have easy integratoin for standard R/3 Repositories for CRM, SRM etc.  You have a facility in MDM Repository for creating your customized Roles which will help you to block certain access to users.
    Hope this answers your requirement.
    Regards
    Veera
    Note : Please mark the Points if this reply is helpful to you

  • Replication of Customer master data from R/3 to CRM.

    Dear Friends,
    If i want to replicate customer from R/3 to CRM what are the prerequisites and how to execute a campaign for the replicated BP's(target groups).What is the load object that we use in R3AS.
    REgards,
    Prabhu.

    CUSTOMER_MAIN is the object used to download customers from R/3 to CRM.
    For CRM 5.0 you can use the link below:
    http://help.sap.com/bp_crmv250/CRM_DE/BBLibrary/html/BBlibrary.htm
    You then need to read the instructions for:
    CRM Generation
    CRM Connectivity
    CRM Customizing Replication
    CRM Organization Model
    CRM Master and Transaction Data Replication
    Those steps will provide on how to setup the middleware for customers.
    You then will need the to read the following building blocks for marketing:
    CRM Central Master Data
    CRM Marketing Master Data
    CRM Lean Campaign Management.
    Good luck,
    Stephen

  • Hi masters , Actually maintain the master data in BI also then why the spec

    HI masters ,
    Actually maintaing the master data also we can do in BI, then why we have to need MDM.
    What is special purpose with mdm.  please tell brefily,

    Hi Surya,
    In MDM we maintain only master data
    The goal of MDM to make master data unique and accurate.
    BI is used to analyze data from diverse source to support decision  making. In BI  transaction data are placed  in a table named Fact table .This fact table or transaction data are connected to master data /dimension table using some foreign key. Example of different transactions data are :-  Quantity sold, sales revenue .In BI /BW we can analyze transaction data i.e. we can calculate total quantity sold for a particular region .
    There may be different sales representative for different region. And every sales representative have different and unique ID.
    To calculate total quantity sold we have to do the following things
    We have to select sales representative Id of the specified region.
    Based on sales representative Id (which is master data) for a particular region and the summarized quantity sold by them we can get the total quantity sold for a particular region.
    So this master data sales representative Id should be correct and unique based on which we will analyze transaction data otherwise the result would be wrong.
    These sales representative ID is maintained in MDM.
    Basic scenarios of MDM are
    1)     Consolidation
    2)     Harmonization
    3)     Central master data management
    MDM assures following things
    u2022     Accuracy - Does my data adhere to defined formats and standards?
    u2022     Validity - Does my data contain incorrect information?
    u2022     Completeness - Does my data contain all the necessary information?
    u2022     Consistency - Does my data contain contradicting or duplicate information?
    SAP Master Data Management (SAP MDM) is a component of SAPu2019s Net Weaver product group and is used as a platform to consolidate, cleanse and synchronize a single version of the truth for master data within a heterogeneous application landscape.
    Thanks
    Dola Aich
    Edited by: DOLA AICH on Oct 14, 2008 10:34 AM

  • What is Master Data Hormonization?

    Hi dear friends,
    1) What is Master Data Harmonization?
    2) please explain me with one good example? please...
    3) What are the SAP NetWeaver MDM  six core and business scenarios? Explain each with one example

    Hi,
    SAP provides six scenarios u2014 or approaches to working with SAP NetWeaver u2014 to help companies maintain their master data while at the same supporting a flexible, innovative IT environment. These are as follows:
    1. Master Data Consolidation u2014
    In this scenario, users use SAP NetWeaver MDM to collect master data from several systems at a central location, detect and clean up duplicate and identical objects, and manage the local object keys for cross-system communication. With this consolidated data, users can access the information they need to perform company-wide analyses and consolidated reporting.
    2. Master Data Harmonization---
    This scenario enhances the Master Data Consolidation scenario by forwarding the consolidated master data information to all connected, remote systems, thus depositing unified, high-quality data in heterogeneous system landscapes. With this scenario, you can synchronize central data contents u2014 that is, globally relevant data u2014 based on your results. For example, you can assign the same address to all occurrences of a particular customer.
    3. Central Master Data Management---
    Whereas the emphasis in the Master Data Harmonization scenario is on local data maintenance, the Central Master Data Management scenario focuses on cleansing data in the central data repository. It then distributes the cleansed data to the connected application systems.
    4. Rich Product Content Management---
    This scenario is intended for the product information management (PIM) market, as it offers many functions for managing product data and corresponding image files centrally via SAP NetWeaver MDM. It can also be used to prepare for publishing product catalogs, either in electronic Web format or in print.
    5. Customer Data Integration---
    The Customer Data Integration scenario lets you harmonize customer master data records across heterogeneous systems.
    6. Global Data Synchronization---
    Through Global Data Synchronization, unified object information is synchronized with data pools, such as UCCnet and Transora, in a standard industrial format, then provided
    to trading partners.
    Through these different ways of using the capabilities of SAP NetWeaver MDM, companies can structure a master data strategy around their data unification goals u2014 based on their unique business processes, organizational structure, or industry.
    Regards
    Richa

  • What is Master Data Consolidation?

    Hi Friends,
    what is Master Data Consolidation?
    please explain this procedure with one good example?
    please....

    Hi,
    Master Data Consolidation means:
    1. Load master data from client systems
    2. Identification and consolidation of similar or identical objects
    3. Provision of key mapping for unified, company wide analytics and     business operations.
    4. It aggregate master data across SAP and non- SAP systems into    a centralized master data repository. Once data is consolidated, you can search for data across linked systems, identify identical or similar objects across systems, and provide key mapping for reliable company wide analytics and reporting.
    In this scenario, these are the following steps:
    1. Users use SAP net weaver MDM to collect master data from several systems at a central location,
    2. Detect and clean up duplicate and identical objects, and manage the local object keys for cross-system communication.
    3.With this consolidated data, users can access the information they need to perform company-wide analysis and consolidated.
    For example: Suppose Wipro have different branches like: Wipro Technologies, Wipro Limited, Wipro Infotech and each branch is  doing business with the same customer. Each branch has its own name and is own id but overall it's a company called Wipro.
    So, now if you see all these records are duplicate and hence give inconsistencies when this data is distributed in different departments of an organization. So we consolidate this data by sending it to MDM where all the information is consolidated, updated and managed properly.
    Regards
    Richa

  • Data load stuck from DSO to Master data Infoobject

    Hello Experts,
    We have this issue where data load is stuck between a DSO and master data infoobject
    Data uploads from DSO( std) to master data infoobject.
    This Infoobject has display and nav attributes in it which are mapped from DSO to Infoobject.
    Now we have added a new infoobject as attribute to the master data infoobject and made it as NAV attri.
    Now when we are doing full load via DTP the load is stuck and is not processing.
    Earlier it took only 5 mns of time to complete the full load.
    Please advise what could be the reason and cause behind this.
    Regards,
    santhosh.

    Hello guys,
    Thanks for the quick response.
    But its nothing proceeding further.
    The request is still running.
    earlier this same data is loaded in 5 mns.
    Please find the screen shot.
    master data for the infoobjects are loaded as well.
    I can see in SM50 the process at P table of the infoobject the process is.
    Please advise.
    Please find the detials
    Updating attributes for InfoObject YCVGUID
    Start of Master Data Update
    Check Duplicate Key Values
    Check Data Values
    Process time dependent attributes- green.
    No Message: Process Time-Dependent Attributes- yellow
    No Message: Generates Navigation Data- yellow
    No Message: Update Master Data Attributes - yellow
    No Message: End of Master Data Update - yellow
    and nothing is going further in Sm37
    Thanks,
    Santhosh.

  • Master data upload to DSO

    Dear all,
    We have a legacy system to maintain and face a problem.
    The system have two DSO,one(DSO_04) is store the transaction data(Navigation atrribute link to master
    data),Due to to accelerate the report on DSO,we build other DSO that is store the transaction data
    from DSO_04->DSO_06 and change the DSO_04 navigation atrribute to DSO_06  data fields.
    Problem:  When user modify the master data and upload to BW,the DSO_06 isn't show the modify
    report,beacause the "change the navigation atrribute to data fields in DSO_06 ".One way to solve this
    problem is reload data from DSO_04->DSO_06 , but user would updata the master data frequently ,so
    it isn't a good method.
    Could you give me some advices to solve this problem?

    Hi,
    While loading the data into first DSO maintain one more field called Update Date( as current date). Do full load from DSO1 to DSO2 using DTP filter on Modified date.
    In DTP filter write a small code to filter data for current date as follows :
      l_t_range-sign = 'I'.
      l_t_range-option = 'EQ'.
      l_t_range-low  = sy-datum.
      l_t_range-fieldname = '/BIC/YNV_CH014'.  " Updation date
      APPEND l_t_range.
      p_subrc = 0.
    hope it works...
    regards,
    Raju

  • Problem updating infoobject master data from a dso.

    Hi all,
    i'm updating the master data of an infoobject from another ods, the two table have the same key.
    When i update the infoobject with full repair i get errors about duplicate records and the data load stops, when i delete the request and launch the infopackage again all goes well but it seems it doesn't insert any new record in the master data, what could be the problem?
    If you need more info ask me.
    Thanks a lot.
    Stefano

    Hi Sadeesh,
    i checked the master data table and it seems it has been updated, i check some order number with recordmode N added today in the dso and the entries were in the infoobject, though i don't know why in the request tab it shows 0 added records.
    To be completely sure tomorrow i will check again the number of entries in the 'p' table of the infoobject.
    Anyway this is the exact error message i get:
    7 duplicate record found.     6478 recordings usedin table /BIC/XZDOCDSO
    7 duplicate record found.     6478 recordings usedin table /BIC/PZDOCDSO
    After that i run the change run for the IO and when i launch again tha data load it goes well.
    Regards
    Stefano

  • Using Attribute of a Master Data InfoObject as a characteristic in the DSO

    Hi
    I have "ARBPL" field in the DataSource. And i map this source filed to "0WORKCENTER" Infoobject in the DSO.
    This "0WORKCENTER" has an attribute '0WRCT_CATG" . I want this attribute "0WORCT_CATG" needs to use as a characteristics in the DSO.
    So how can i populate the data for this attribute "0WORCT_CATG" from it's master data infoobejct "0WORKCENTER" in the DSO .
    So please let me know
    kumar

    Hi Ravi Kumar..
    U have ARBPL field in ur datasource and u r maping this field to a system defined infoObject  “0WORKCENTER” koooool……and the same time u mentioned 0WORKCENTER have a attr “0WORCT_CATG”…..is their any field in ur datasource that defines(maps ) this infoObj “0WORCT_CATG”. Map that field with the attr infoobject at info source level.
    If u don’t have any relevant field in the datasouce to define this 0WORCT_CATG object….. proceed with update routine……..or start routine(transfer rules/update rules) according to ur convenient.

  • Master Data is loadable in DSO with Delta Update?

    Hi!
    1) It is possible to load data from Master Data Datasource to a DSO in DELTA MODE and after (always in DELTA MODE) into an InfoObject?
    In other words:
    Datasource for Master Data (SAP ECC) --> DSO (SAP BI) --> InfoObject (SAP BI) [ALL IN DELTA MODE]
    ****I have doubt about the load of record with the same key in master data during activation***
    2) It is possible also to use a DSO Write Optomized?
    Points to useful answers!!
    Thanx in advance!!
    Claudio

    1) It is possible to load data from Master Data Datasource to a DSO in DELTA MODE and after (always in DELTA MODE) into an InfoObject?
    In other words:
    Datasource for Master Data (SAP ECC) --> DSO (SAP BI) --> InfoObject (SAP BI) [ALL IN DELTA MODE]
    ****I have doubt about the load of record with the same key in master data during activation***
    yes it is possible to load to DSO and than to a IO. and regarding the mastrerdata with same key, it woudl be overwritten in both the ODS and IO.
    2) It is possible also to use a DSO Write Optomized?
    It is possible but the whole purpose iof delta is defeated as the write optimised wouldnt have a change log table, and is as good as a full load every time.

  • Reporting on Alternate Hierarchy master data (HR-BW)  thru DSO object

    I have a quick question. I would appreciate if you know of any direction to approach this.
    We have a hierarchy in a external system that we want to bring into BW as alternate hierarchies. The hier nodes are a bunch of leagacy hierarchies and the leaves will be 0COSTCENTER (R/3 values). After loading this hierarchy in BW, we need to manipulate and add 0POSITIONS to the 0COSTENTER hierarchies from R3 and store this back as another hierarchy (with 0POSITION as leaves below 0COSTCENTER). Now we need to report on this hierarchy and get stats like # vacant position, occupied position, etc.
    Have you seen anybody doing this kind of manipulation, reading hierarchy data into DSO object, reporting, etc?
    Any idea will be appreciated.
    Thanks
    Raj

    Hi,
      To provide you with further information
    i need the following data in my BW report
    HRP1000 - OBJID, OTYPE, STEXTBEGDA
    HRP1007-STATUS
    HRP1011-SOBID, RELAT
    HRP1005-TRFGL
    PA0002 –NACHN, VORNA
    <b>PA0007 - WOSTD ( Number of hours per week)
    HRP1011 - MOVAG (Number of hours per month)</b>
    Some one in HR Fourms told me that these tables are master data tables and i am reporting on master data
    So Anil,Quick question if the data i need is master data can i use the cube u suggested
    Please update me on this
    Thanks a lot

Maybe you are looking for