Display MDM key mapping information in EP Item Detail iViews

Hi,
in my repository I have the main table 'customer' including key mapping information for several client systems (master data consolidation scenario).
The customer data is diplayerd in EP using the Item Details iView. I'd additionally like to display the key mapping information in Item Details iView, for example as a separate tabstrip. Is this feature already supported by the Item Details iView? How can I implement it?
I'm using MDM 5.5 SP3 / EP6.0 SP14.
Thanks in advance,
Martin

Hi Martin,
Currently iView do not support the functionality to disply the key mapping information.
Workaround I implemented is that, added a field "source system" to main table with type lookup. Added lookup table "source systems" with list of names of client systems. This helps user search data based on client system name.
I hope this is helpful.
Abhay

Similar Messages

  • Key Mapping Information

    Hello All
    We have a case where we would like to move a selected set of materials from repository 1 to another repository 2 and still maintain the Key Mapping information that those materials have from the original Import into repository.
    Any suggestion?
    all help greatly appreciated
    C

    Hi Con,
    I just want to summarize if I understood you right: you have a category that has some products. You want to migrate both into a second repository. Migration of the category is working but the key mapping information is lost or incomplete?!
    How do your products look like? Do they have multiple key mapping entries? The syndicator would be able to distribute multiple key mappings (you can add multiple target systems in the destination properties of your map). But Import Manager is currently able to import only one key mapping records for a single remote system during an import run. This would mean that you have to syndicate your products for each remote systems and you have to do the same amount of imports.
    BR Michael

  • MDM Item Details iView modification

    Hello,
    We have a requirement to implement custom functionality for some of the fields when using the standard Item Details iView. Is there a way to do the following:
    Currently the field in question has a popup functionality that is standard for the iView.
    Instead of this popup we need to have our custom WebDynpro iView show up and integrate it to the calling main Item Details iView. In other words, we need to replace the standard popup for a field with our own custom popup.
    Keep in mind that we are using MDM 5.5 SP05 where Item Details iView does not support custom eventing.
    Thanks in advance,
    Boris

    Hi Jitesh,
    Thank you for your answer. You are right, in order to have custom eventing with Item Details iView I need to have at least SP06 and this is one of the restrictions we are facing.
    Although our servers for the project are SP05, I have a local trial copy of SP06 on my PC and I have to say that it still doesn't give me the flexibility that I need. The Item Details iView can trigger the event only upon Saving. In other words, there is no custom eventing on click of a popup or anything else. The purpose of this custom eventing is to only give the ability to do additional custom validations.
    Thanks again,
    Boris Todorov

  • MDM 7.1 Business Package -- Item Details iView eventing

    We are using MDM 7.1 Business package in portal. We have requirement where we need to make the fields clickable /mouse over on the item details iView so that when the user clicks/mouse over on the field it should popsup a custom webdynpro application. I was checking the business package documentation and it seems there is only one epcf event for post save which can trigger custom webdynpro when user clicks save button but nothing else on field levels. Can anybody shed some light on this. Any other approach other than custom development of whole details view?
    Thanks

    Any ideas on this?

  • Custom Event Trigger from MDM Item Detail Iview

    Hello,
    We are using EP 7.0 EHP 1, MDM 7.1 SP04.
    EP & MDM trusted connection is activated.
    We want to trigger UWL iview once record is saved from MDM Item Detail
    Iview.
    Following steps are performed but still no results were observed.
    --> Open Item Detail Iview
    --> Click on Custom Details
    Enter Following Details:
    Custom Event Name: UWL
    Event Type: EPCF POST SAVE EVENT
    Target (URL or Event Name): http:/<portalURL>:<port>/UWL/
    Namespace: urn:com.sap.netweaver.bc.uwl.ui.UWL
    Parameter Format: Standard
    Quick Link name to uwl iview is stored in project folder is given as
    "UWL" and hence target url is http:/<portalURL>:<port>/UWL/
    Could you pl guide us on what settings are missed??
    Supporting Link used:
    http://help.sap.com/saphelp_mdm550/helpdata/en/45/c89e544c52570be10000000
    a114a6b/frameset.htm
    Regards,
    Purav

    Please check out below link. It might be of some use.
    [http://help.sap.com/saphelp_mdm550/helpdata/en/45/c87d0243e56f75e10000000a1553f6/frameset.htm]
    (Go to Configuring Data Exchange)
    Regards,
    Abhijeet

  • Create/Edit button on Items Detail Iview very very slow

    Hi,
    I created a MDM resultset iview and MDM Item Details Iview for a very large table. When I click on the create or edit button on the Item Details iview, it keeps running and never finishes. This table has many fields and has many records but on the iview itself I am just displaying not more than 10 fields.
    When I created an item details iview for another small table, I can create and edit the records in no time. But for the above table, it takes for ever to Edit/Create.
    Can anybody tell me what the issue could be?
    Thanks
    MLS

    Hi Laxmi,
    The portal is just the front end replicating the processes of the backend system in your case the MDM system.
    Using the MDM repository with large number of records will cause a delay in creting or editing or even selcting records when operatings these functions from the MDM Data manger it self.
    In that case EP is just replicating this issue on the front end.
    As you have rightly mentioned that for smaller number of records in the MDM rep the function swork faster.It clearly indicates that even if you select less number of fields to be displayed on the front end,the backend still contains the large set of fields which needs to be processed,and this consume stime.
    To fasten your process on both the backend end and the front end systems you need to correctly design the data model and the fields properties which will improve the performance.
    You can refer the below link to better design your MDM data model:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/eb7447b1-0c01-0010-8d90-a2e004cad537
    Hope It Helped
    Thanks & Regards
    Simona Pinto

  • How to control lookup table's attributes using 'item details' iview???

    Hi Friends,
    Using 'Item Details' iview we have an option to edit, visible or non-visible. But there is no option to control visible, editable or non-editable at attribute level of the lookup table.
    Does any one know any solution for this scenario apart from custom development using Java Api.
    Thanks,
    Raghavendra

    Hi Raags,
    I know that, at moment, is not possible in MDM standard iView to control  visible, editable or non-editable at attribute level of the lookup table.
    May be it will be possible in the future. More flexibility you can obtain using Java API.
    Regards,
    Vito

  • Using externalRequestEvent with Item Details iView

    Hi gurus,
    I am using the Item Details iView and calling it with syntax like that:
    externalRequestEvent=com.sap.pct.mdm.appl.masteriviews.events.externals.SetSelectedIdHandler&id=
    I have the Item Details iView showing up correctly, but I have to click on the Edit button to change the rocord.
    Is there any way that it directly goes to Edit mode when the Item Details iView gets open? An option perhaps?
    Thanks,
    Boris

    Hi Raags,
    Even I am trying to implement the same example. I have created the MDM Item Details iView in one of the PCD folders. But I am not sure how to extract the URL for the same to use it in my webdynpro code. Can you please advise me how get the URL for the iView? How did you construct this long URL?
    Your help would be greately appreciated.
    thanks
    SBK

  • Reg: About Item details iview

    HI,
    I have a MDM item details iview. When i choose edit button, create is getting disabled. Actually i want to create a new record by editing some fields of the existing record. How can i do this customisation.
    Thanks,
    Prasanthi.

    Hi,
    Please clarify on following points to answer your query regarding MDM item details iview:
    a) Is it standard SAP content?
    b) create is getting disabled - Is create button visible for you or not visible to anybody? If not, check in PCD what are the authorizations required
    c) customisation - What do you mean by this?
    If you want to create custom details screen, it is possible. Steps to be followed for this :
    i) Go to result set view of the respective entity
    ii) create 'on row select' event and pass id through the event
    iii) subscribe to the event in your custom developed application
    iv) capture the id and fetch the data from MDM based on data fetched
    regards,
    ganga

  • Item Details iView and Custom Event

    Dear experts,
    I need to implement a custom validation using a BAPI call to external R/3 system.
    I am planning to use the Item Details custom event as a trigger for my custom web dynpro and have my BAPI call there. My question is, can I do that? The reason I'm asking is because the event says it's a post-save-event. What I need to do is to prevent the actual Saving and display an error message if the
    BAPI call returns "false".
    Thanks for your help,
    Boris

    I see that there are too many answers to this thread
    OK, here is how we solved the issue. We are subscribing in a custom Web Dynpro to the Post-save-event of the Item Details iView and we are performing the BAPI call.
    Based on the result of the call we are setting a flag on the record and this flag is used as a syndication block.
    Hope that helps someone ...
    Boris

  • Cannot save data in item details iview (validations, calculation problem)

    Hello,
    I'm unable to save data in an item details iview. It complains about validations or calculated fields according to error message below.
    I am however able to save data directly in data manager and I have no automatic excutions (set to None) on my validations.
    So I guess I have to check calculations, or?
    #1.5#00144F1E87AC0066000000B1000059190004769A5679B69E#1256305154700#com.sap.pct.mdm.appl.masteriviews.ItemDetails$ItemDetailsDynPage#sap.com/irj#com.sap.pct.mdm.appl.masteriviews.ItemDetails$ItemDetailsDynPage#MDO1#41676##gcomdev_GEQ_35915650#MDO1#720b5f90bfd911de9b3100144f1e87ac#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#/System/Server#Java###taxonomies has invalid elements<fieldNameenabledpriorityfieldName1enabled1~priority1...>##
    #1.5#00144F1E87AC005D000001F2000059190004769A74192B38#1256305651690#System.err#sap.com/irj#System.err#MDO1#41676##gcomdev_GEQ_35915650#MDO1#748f4b50bfd911deacb000144f1e87ac#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: A runtime error occured while evaluating an Validation or calculated field#
    #1.5#00144F1E87AC005D000001F3000059190004769A74194266#1256305651696#System.err#sap.com/irj#System.err#MDO1#41676##gcomdev_GEQ_35915650#MDO1#748f4b50bfd911deacb000144f1e87ac#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###     at com.sap.mdm.validation.commands.ValidateNewRecordValuesCommand.execute(ValidateNewRecordValuesCommand.java:121)#
    #1.5#00144F1E87AC005D000001F4000059190004769A7419431A#1256305651696#System.err#sap.com/irj#System.err#MDO1#41676##gcomdev_GEQ_35915650#MDO1#748f4b50bfd911deacb000144f1e87ac#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###     at com.sap.mdm.admin.utils.MdmUserCommandUtils.validateNewRecord(MdmUserCommandUtils.java:321)#
    #1.5#00144F1E87AC005D000001F5000059190004769A741943B5#1256305651696#System.err#sap.com/irj#System.err#MDO1#41676##gcomdev_GEQ_35915650#MDO1#748f4b50bfd911deacb000144f1e87ac#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###     at com.sap.pct.mdm.appl.web.ValidationService.execute(ValidationService.java:73)#
    #1.5#00144F1E87AC005D000001F6000059190004769A741944DC#1256305651696#System.err#sap.com/irj#System.err#MDO1#41676##gcomdev_GEQ_35915650#MDO1#748f4b50bfd911deacb000144f1e87ac#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###     at com.sap.pct.mdm.appl.web.Record.update(Record.java:2009)#
    #1.5#00144F1E87AC005D000001F7000059190004769A74194574#1256305651696#System.err#sap.com/irj#System.err#MDO1#41676##gcomdev_GEQ_35915650#MDO1#748f4b50bfd911deacb000144f1e87ac#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###     at com.sap.pct.mdm.appl.masteriviews.ItemDetails$ItemDetailsDynPage.saveRecord(ItemDetails.java:2139)#
    #1.5#00144F1E87AC005D000001F8000059190004769A7419460F#1256305651697#System.err#sap.com/irj#System.err#MDO1#41676##gcomdev_GEQ_35915650#MDO1#748f4b50bfd911deacb000144f1e87ac#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###     at com.sap.pct.mdm.appl.masteriviews.ItemDetails$ItemDetailsDynPage.onSaveRecord(ItemDetails.java:1920)#
    #1.5#00144F1E87AC005D000001F9000059190004769A741946AA#1256305651697#System.err#sap.com/irj#System.err#MDO1#41676##gcomdev_GEQ_35915650#MDO1#748f4b50bfd911deacb000144f1e87ac#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###     at com.sap.pct.mdm.appl.masteriviews.ItemDetails$ItemDetailsDynPage.onSaveRecord(ItemDetails.java:1828)#

    Hi Olof,
    From the error message, it seems that the new created record is " Failing a Validation".
    From the Data Manager you can save a record , when automatic executions set to None.
    But the same will fail when it is added to a validation group and that group is used in the Item Details Iview while creating a record.
    Please update the status.
    Regards,
    Nimal

  • MDM key mapping: multiple fields?

    Hallo,
    is it possible to base key mapping on more than one fields?
    From what i see key mapping is based on one field only...
    Regards,
    Marco

    Hi,
    is it possible to base key mapping on more than one fields?
    From what i see key mapping is based on one field only...
    yes, for that your field in Maintable should be Display field. So if you have two fields in Maintable then both of these fields can be used as key mapping in import manager while importing Data, in Match records tab,  you can also have option of using these fields as Split or Combine as per your requirement on the basis of which you want to insert data into MDM Data Manager.
    Hope it will Help you,
    Rewards if Useful.....
    Mandeep Saini

  • MDM Key Mapping

    Hello Experts,
    Please help me to understand the Key Mapping concept in context to SAP MDM.
    How the key mapping values get created while importing the data through the import manager and what role key mapping playes while importing the reference or look up data for the first time.
    Thanks.

    Hello Rajan,
      As all of us one of the main functions of MDM is to eliminate duplicates ok?
      now let consider that you have 2 offices one at US and another in India. lets say that you use citi bank both in india and US to do the transcations, of course there are also some other banks that you deal with.
    As you know any transcation that you do with  CITI bank(US) is not same as CITI bank(IND). Which means even though the bank is same these two are 2 different entities.
    know lets built a table for list of banks that you do transcations both in india and US
      BANKS-US
       bank num - 1     bank name - barkalays
                - 2                 south american bank
                - 3                 millenium bank
                - 4                 Citi bank
                - 5                 american express
      Bank - IND
       bank num - 1        bank name - sbi
       bank num - 2                    ING Vysa
                  3                    citi bank
                  4                    punjab national bank
    now when we are import all these data into MDM citi bank will be always a duplicate records. BUT IT IS NOT ACTUALLY DUPLICATE since it record1 of citi bank belongs to US and other belongs to IND.
      So inorder to over come this one what I create tha remote system ( we can create this in remote systems table under admin node ) in MDM where  i name all the data coming from US as BANK-US and from IND as BANK-IND
    now when we import data into MDM we log in into respective remote system for example if I am to import data from US i specify my remote system as BANK-US and similarly with india and import data. So now when  you see the data in data manager you can find only 1 records of CITI bank.
      now if you want to see which citi bank it is right click press "edit key mapping" there you can citi bank record of both the systems.
    Similarly the same concept applys for objects also i.e when similar record belongs to two different objects

  • MDM Log / EPCF Eventing in Result and Item Details Iview

    Hi,
    I have EP7 with SP15 and MDM 6.0, recently upgraded. Before upgrade we have an application which uses the MDM iviews and maps the fields of one table to other and displays in some other iview.
    The application was working fine before upgrade of MDM. But after upgrade, the mapping seems not working.
    My scenario is as : Using MDM Search iview, I search records from MDM repository, Main Table. This result is displayed in MDM Result iview. From this result iview, I select a record. From this selected record, a field is mapped to the other table. The mapped record, then, is displayed in MDM Details Iview.
    After MDM upgrade, whenever we select a record from the result of table 1,the mapped iview throws erros :
    Error occurred: Error performing search. com.sap.mdm.internal.protocol.manual.ServerException: Illegal value for parameter, com.sap.mdm.internal.protocol.manual.ServerException: Illegal value for parameter (see log for details)
    when serached log : Key is not found in table:<Table1>-KeyMappings it may have been deleted or renamed, please use editor to fix the problem##
    We have used EPCF eventing for MDM iviews.
    I have written some code to check the values passed from Result Iview and seen that the values are being passed correctly...Now think, i should also have a check in MDM how the values are recieved and mapped...
    Any idea how I can use MDM log service to do this? Or any idea how I can enable MDM log to monitor what comes in and what goes out?
    has anyone out there faced same issue ?
    Please let me know your views.
    Regards,
    Abhijeet

    Solved at my own. The MDM SP6 needs the subtable key field to be TEXT type.

  • Item Details iView on Open/Object crashes with Portal Runtime Error

    Hi there,
    I am getting a crash attempting to Open/Object on the Vendor / Item Details object or a delta linked iView or a full copy iView from that same source.  I can get data from the Repository with other iViews, ... But I can't get this particular iView to work. 
    2 entries in log as below.  Any ideas?
    Thanks,
    --Amy Smith
    --Haworth
    Argument Objs : com.sapportals.portal.prt.component.PortalComponentException:
    Error in service call of Portal Component
    Component : pcd:portal_content/com.sap.pct/specialist/com.sap.pct.mdm.appl.mdm_550/....
    com.sap.pct.mdm.appl.templates/com.sap.pct.mdm.appl.templates.iviews/...
    com.sap.pct.mdm.appl.item_details_editor
    Component class : com.sap.pct.mdm.tech.editors.ItemDetailsEditor
    User : WASE
    at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException
    (PortalRequestManager.java:973)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent
    (PortalRequestManager.java:343)
    Argument Objs : java.lang.NullPointerException
    at com.sap.pct.mdm.tech.editors.panes.ItemDetailsMainEditorPane.
    updateQualifierAndRelationshipList(ItemDetailsMainEditorPane.java:1351)
    at com.sap.pct.mdm.tech.editors.panes.ItemDetailsMainEditorPane.init
    (ItemDetailsMainEditorPane.java:1079)

    Work-around was to create a new iView from the template.  That works fine.
    --Amy

Maybe you are looking for