Discovery Box and MDM Scenarios

Hi,
What scenario's are available on the discovery box ? Especially interested in the MDM stuff : What repositories are loaded, any scenario's like mdm harmonization implemented... )
Thx,
Dirk

Hi Dirk,
The Discovery System uses SAP MDM to store the suppliers and products master data of the “CoolCorp” company. The supplier and product master data are used by the purchase order business scenario that is part of the box.
We have an exercise, in which we assume that the “CoolCorp” company acquired another company named “SmartComp”. As a consequence a new list of suppliers and products needs to be consolidated into MDM.
For purchase order business scenario (http://sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3aecc59c-0d01-0010-d0ad-b7133a8e49d8)
supplier and product data has been extracted from the backends, mapped and uploaded to MDM.
Of course you have all freedom to realized additional scenarios in MDM on your own.
Hope that helps,
   rAimund

Similar Messages

  • Can we create a local client copy for the RFID Client in discovery Box

    Can we create a local client copy for the RFID(400 Client) in the Discovery Box,and if created which profile we have to select for the client and also at a time we can work on these both client or not  .

    This isn't possible with Live Mail.  Acrobat has an add-in for Outlook (which you've used), but there is no similar function for Live Mail.

  • How to configure the XI  and PLM in discovery box

    How to configure the XI (SLD, Integration repository, Integration Builder ) in  SAP discovery system.
    And also i want to configure the PLM and xRPM within R/3 of discovery box.
    Regards,
    Nilesh Damle

    Hi Frank,
    well, first of all, your application provides log configuration information using an XML file at deployment time. This file is called log-configuration.xml (you can see the DTD description here: http://help.sap.com/saphelp_nw04/helpdata/en/48/ef8748caed894bb4b3ae953a60c592/frameset.htm). There you can set configure log controllers, which could be two types: location and category. So, you can specify your location and severity there. This is described here: http://help.sap.com/saphelp_nw04/helpdata/en/35/671c0136b4714c9e1b16b68211287b/frameset.htm.
    Then, after the application is deployed, the log configurations you provided for it are registered with the Log Configuration tool I mentioned about. Using this tool you can later on modify your configurations at runtime (for example, change the severity level) without having to redeploy the application.
    I hope it's clearer now? I guess it was me not getting your first question correctly that caused your confusion.
    Greetings,
    Ivo

  • Central Contract, MDM Catalog, and classic scenario

    Dear SAP experts,
    We are in SRM 7.01 with backend ECC 6.05 deploying classic scenario. We are using Central Contract Management in which we negotiate contract in SRM and later distribute it to ECC. We also plan to use SRM-MDM Catalog.
    We notice that if we are using classic scenaro, the contract that is used as reference is the contract number in ECC (the one distributed from SRM). So at first we assume that if we want to push the contract data to MDM, we should have pushed the ECC Contract number. However we find out that actually SAP block the ECC Contract coming as distribution from SRM to go to MDM.
    Our second option is to use distribution of contract from SRM to catalog. It does using SRM contract number. We create SC and then we pull the catalog item from the catalog (which contain SRM contract number) and then we order. However we end up with 'error in process' in which the system try to create a PR instead in the ECC (meaning that the contract number cannot be read).
    We're puzzled with this. How can we use the combination of central contract, MDM catalog and classic scenario? Can we use the combination?
    Best regards,
    John

    Maria
    If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
    Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
    Then local contract data should pick as SOS from the vendor list.
    If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
    Let me know if the above works or not.
    PS : Reward points if helpful.
    Regards
    Jagadish

  • SRM, ROS and SUS scenario question

    Hello Experts,
    We are in the process of implementing MDM, ROS, EBP and SUS scenario in our present project. I went through the documentation. I have couple of questions.
    1. Do we need to have seperate clients for ROS and SUS. What is the best practise.
    2. Since we have SUS, once I transfer BP from ROS to EBP, check the portal vendor box, I would like to know how the registration code will be sent to supplier. Do we need to create the userid in EBP or with the receipt of registration code supplier will be able to create his first initial userid? Also how we can implement this with CUA and EP as part of landscape?
    3. Also since we have MDM, how the new BP information can be migrated or mapped in MDM and how new BP can be sent to backend system? I understand there is BP monitor to check and approve the changes, but how the new BP will be transferred? Do we need to develop new XI message for this? if Yes, from where that can be managed? from EBP or MDM?.
    I searched through help.sap.com for any documentation but no success.
    Thanks in advance
    Vijay.

    Hi,
    1.Refer the foll thread:
    Re: Supplier Registration without SUS or XI?
    2.For supplier registration,SUS is not mandatory.You need to configure ROS for this scenario.The extrenal vendors will register in ROS and then be replicated to R/3.
    You can use EBP only for Supplier registration.
    SUS,ROS and Bidding engine make up the SRM server 5.5/EBP component of SRM 5.0.
    Pls refer the foll link for the complete process:
    http://www50.sap.com/businessmaps/8F152C1AE8F1426FA3B442F905815F54.htm
    For detailed settings/config  of supplier registration,refer the foll threads:
    Re: Not able to transfer suppliers from ROS to EBP
    problems with ROS_PRESCREEN application for screen suppliers and manage bp
    Re: SUPPLIER DIRECTORY (ROS) link not appearing in EBP in "SCREEN SUPPLIERS"
    Supplier Directory
    Re: Supplier Self registration
    Re: SRM Supplier registration config
    Re: External Web Service setting for Supplier Registration ROS to EBP
    Re: Problems when transferring supplier from ROS to EBP...
    3.Not worked on MDM so cant help you on this.
    BR,
    Disha.
    Do  reward points for useful answer

  • Technical requirements of  Discovery box

    Hi,
    I would like to know what are the s/w and communication requirement for implementing discovery box with enrichment controller.
    What is the advantage of using GP instead of workflow,MDM
    Thanks for the response,
    -reo

    Hi Reo,
    comparing GP with MDM workflow is probably a bit like comparing apples with pears. The MDM capabilities focus on executing tasks around master data management specifically.
    GP is more suited for integrating activities from heterogenous systems into a single process flow with a harmonized user interface. The process can be about anything and does not need to be related to a specific system, use case or functionality.
    Does that make sense?
        rAimund

  • ISE 1.2 and MDM integration.

        What kind of device information I can collect by MDM integartion with ISE.              

    Hello,
    ISE  Release 1.2 delivers integration between Identity Services Engine and  MDM platforms, which can ensure that all mobile devices are compliant  with security policy before they are allowed to access the network. This  feature enables posture compliance assessment and network access  control of mobile endpoints attempting to access the network. The  solution also performs ongoing posture checks to ensure that devices  remain compliant and that the correct network access level is  maintained. The specific posture attributes collected by MDM partner  platforms for compliance and access policy enforcement in the Identity  Services Engine are:
    • Is the mobile device registered with MDM?
    • Does the mobile device have disk encryption enabled?
    • Does the device have PIN-Lock enabled?
    • Has the device been jail-broken/rooted?
    In  terms of global compliance, posture compliance decisions may be made by  the MDM platform instead of the Identity Services Engine. In this  scenario, additional attributes such as blacklisted applications or  presence of an enterprise data container may be checked. The MDM  platform simply informs the Identity Services Engine if a device is in  compliance, then the Identity Services Engine enforces the appropriate  network access policy.
    This  integration brings great value to MDM customers as it automates to the  device registration process. As MDM solutions are network-blind, they  can't detect a new device when it connects to the wireless network, so  the administrator needs to send a notification to the users who wish to  enroll their devices. With ISE integration, device enrollment is done  automatically when users connect their device to the Wi-Fi network.
    SNS appliances are now available with ISE 1.2 in SNS-3415-K9 and SNS-3495-K9 appliances.

  • JAVA aplication and MDM

    Hi forum,
    We've created a XI 3.0 scenario in order to make an integration between JAVA applications and MDM
    The JAVA application needs the Message Type "XML Namespace" field to be filled, but MDM doesn't import the sent xml messajes through this scenario because "doesn't accept" those xml with this field.
    We think we could eliminate this field in Message Mapping through XSLT Mapping, is this possible?
    how could we do that?
    any idea?
    King regards

    Hi
    I understood this is ignoring one source field.. in mapping to target message using XSLT .
    it is possible..just don't write this field in target message output generation module.
    thanks,
    venu.

  • SRM to MDM scenario

    Hello Guru's,
    I need to verify somethings because I am getting a bit lost.
    I need to have a scenario from SRM to MDM with XI. Only there is a problem because the MDM server is Linux. Linux only supports secure FTP and XI only supports FTP(s). So the solution was to implement a J2SE adapter plain engine, because its very basic to install. This is done and now comes the point where I am getting lost:
    For the part for XI to MDM I have created a receiver XI adapter in XI:
    - tranport protocol HTTP 1.0
    - message protocol 3.0
    - Adapter engine: Integration Server
    - Addressing Type: URL Address
    -Target host: http://aaa.bbb.bbb
    - Service number 62001
    - Path prefix: /file/Receive
    - Authentication type: Use logon data for Non-SAP system, with username and password
    On the MDM server for the J2SE adapter plain engine, I have configured a file_receive adapter:
    File adapter java class
    classname=com.sap.aii.messaging.adapter.ModuleXMB2File
    version=30
    mode=XMB2FILE
    ##Adress for XMB endpoint
    XI.httpPort=62001
    XI.httpService=/file/Receiver
    ##File Adapter specific parameters
    file.createDir=1
    file.targetDir=/usr/sap/CA1/trans/data/
    file.targetFilename=xmb_output.xml
    #file.writeMode=append
    #file.writeMode=overwrite
    file.writeMode=addCounter
    file.counterMode=immediately
    #file.counterMode=afterFirst
    file.counterSeparator=_
    file.counterFormat=00000
    file.counterStep=1
    The question is, do I need to have a SOAP receiver adapter in XI and a FTP receiver on the J2SE side, like a described above?
    Best regards,
    Guido Koopmann
    Edited by: G. Koopmann on Jun 24, 2008 3:11 PM

    Hi,
    One way I would look at solving this problem would be -
    If there is a common file server in the landscape which both XI and MDM system could reach. If that is the case, I would not write an J2SE adapter but would simply place the files from XI using a file adapter or FTP adapter. From there MDM can poll them (if possible).
    I am not sure if it helps. But just a thought.
    VJ

  • Message is not going to XI in SRM- MDM scenario

    hello,
    We are doing SRM_MDM scenario.
    We have installed SRM-MDM Catalog 2.0 Business Contents on XI.
    But i couldn't see any Outbound Interface in these standard contents.
    I want xsd for CatalogPublicationRequest_Out.............. where will i get that (transaction) ???
    Also when i execute the Report ROS_SUPPLIER_SEND_TO_CATALOG in SRM, I could see my message( CatalogPublicationRequest_Out ) in SXMB_MONI of SRM.
    But its not going to XI...............I can't see it in SXMB_MONI of XI.
    That message in MONI of SRM have Sender but Receiver field is blank.
    May be because of this is it not going to XI.
    Please tell me the steps that i need to follow.
    Help will be highly appreciated.............. its urgent
    Thanks in advance
    Maheshwari.

    Hi Hi Maheshwari,
    Sap has shipped the preconfigured proxies for the transaction.
    ROS_SUPPLIER_SEND_TO_CATALOG.
    you can get the complete business Pack and related docs for SRM_MDM Catalog on the Service market place.
    you need to Import of PI Business Content for SRM-MDM Catalog in Integration Repository
    For that Place PI content file (XI_7_0_SRM_MDM_CATALOG_1.0_00_00.tpz) in directory “/usr/SAP/xid/sys/global/xi/repository_server/import”. This Content file can be found in Business content Import of PI Business Content for SRM-MDM Catalog in Integration Repository.
    But first before importing above file.
    You have to configure SLD Connections in which:
    1.Defining Technical System for SRM Server, MDM and SAP PI.
    2.Creating Business systems for SRM, PI and MDM
    u also need to do Configuring Setup for ABAP Proxies:
    1. use Transaction SM59 for creating RFC destination for HTTP( TYPE H) where u Specify Host Name of the PI server, Service Number and Path Prefix  in Technical Settings tab.
    2. u also need to configure SRM System as Local Integration Engine. For this enter transaction SXMB_ADM .
    HOPE IT WORKS,
    Thanks,
    Mandeep Saini

  • MDM 3.0 and MDM 5.5

    Hi All,
    Can any body tell  what are the differences between MDM 3.0 and MDM 5.5?
    Regards,
    Nikhil

    MDM 3.0
    Strengths
    • Supply chain expertise
    • Global metadata synchronization expertise – especially important to Consumer Packaged
    Goods and Retail industries
    • 3rd generation hub architecture with near term 4th generation features (image/content
    management of A2i)
    Weaknesses
    • Few production references
    • Early ramp up sites included: Deutsche Telekom, Dorel/PacificCycle, ENEL, General
    Electric Consumer and Industrial, Heineken, Kingfisher Group, Nestlé, Nokia, Pemex,
    Purdue University, Rubbermaid, Shell Europe, Tesoro Petroleum, Weyerhauser,
    Whirlpool
    • Can be purchased only “on approval of SAP executive management on case by case
    basis”
    • Batch emphasis; on-line capability not suitable for high transaction rates in large-scale
    B2B or B2C scenarios
    • Emphasis on product/supplier capabilities rather than customer/employee
    • Lack of strong SI channel (the number of SIs promoting NetWeaver is a good channel,
    however, the subset that are catering to SAP MDM is far smaller)
    • Under invested in marketing
    • No longer supported after 2012
    MDM 5.5
    Strengths
    • Support for single view of all major objects – customer, product, supplier and employee
    (albeit lightweight customer and employee)
    • Focused on interactive cleansing and distribution of Material, Supplier, Customer, and
    Employee master data within (SAP R/3-based) ERP environment; note that several large
    organizations are using it outside of a SAP ERP environment such as GE and
    Rubbermaid
    • Global metadata synchronization expertise
    • Product information management focus
    o Fully integrated electronic and print publishing
    o High performance parametric search across rich content
    • Hierarchical management
    • Integration with SAP infrastructure
    • 4th generation data hub features (image/content management of A2i)
    • English, French and German initial support; Japanese 3Q2005
    Weaknesses
    • Minimal references (Whirlpool)
    • Currently only supports “master data harmonization” – no automated central authority for
    master data and therefore cannot enforce centralized/corporate data quality standards
    • Focused on interactive cleansing and distribution of Material, Supplier, Customer, and
    Employee master data within (SAP R/3 based) ERP environment (n.b. = Not a typo – this
    is either a strength or a weakness depending upon one’s requirements)
    • Batch emphasis, e.g. customer data is typically replicated in batch mode among
    participating systems; however, enterprises can propagate customer data using the same
    common architecture that is used by the product hub for replication/distribution via SAP
    NetWeaver Exchange Infrastructure or directly via APIs
    • Lack of strong SI channel (the number of SIs promoting NetWeaver is a good channel,
    however, the subset that are catering to SAP MDM is far smaller)
    • Under invested in marketing (if SAP was true believer at the executive level in the
    strategic nature of enterprise master data management, then the SAP MDM product
    would be much more prevalent in the overall SAP marketing mix)
    • Emphasis on product/supplier capabilities rather than customer/employee
    Hope this will be helpful.
    Reward points if found useful.
    Regards
    Sravan Velamury

  • SRM One Client + Portal and MDM system on top of SAP EHP4 system

    Hi!
    we successfully upgraded SAP ERP 6.0 system to SAP EHP4.
    Now we would like to extend the functionality by adding the following components:
    - SRM One Client
    - Portal and MDM
    Question:
    1) Can some one explain  the procedure to do this?
    2  Where can I find the Installation files and documentation?
    Any helpful information will be very appreciated

    Hi!
    Thank you very much for your response!!
    My actual situation:
    I have a EHP4 for SAP ERP which has only ABAP stack.
    Questions
    1) Should/must I install a Java-Add In Instance?
    a) Is it possible to install a Java Add In Instance for EHP4 ERP system or do I need only a extra/new Windows server for this?
    b) what are the must usage scenarios I have to choose for the Java installation (Portal, MDM, PI)?
    2) what is the exact installation sequence (SRM One Client, SRM MDM, NW Portal)?
    Thank you very much!

  • A2A and B2B Scenarios

    Hello Friends,
                  Can any one explain what is A2A and B2B Scenarios and please explain what is asynchronous and synchronous communication.
    Thnks&Rgds,
    Dinesh

    Hi Dinesh,
    1. A2A integration involves configuring your system landscape, designing your integration scenarios, configuration of the scenarios, handling messages. In which you communicate at application level.
    2. B2B Integration
    Its something in which two business are integrated like: we develop scenario like legacy system to  MDM using XI.
    Now two businesses are communicating. See the link:
    http://resources.ecommercetimes.com/search/keyword/ecommercetimes/Definition%20B2B/Definition%20B2B
    3. Asynchronous communication:
    Means you will send the data but no response will come from the receving end called Asynchronous communication. You will just send, disadv: your data may lost.
    4. Synchronous:
    Every time sender will send the data, receiver will give a response say acknowledgement to the sender that data received.
    Adv: if data is not going to receiver it can be delivered again.
    Rewrads if found helpful.
    BR,
    Alok Sharma

  • MDM Scenarios involving XI

    Can any one list the MDM Scenarios involving XI?
    -Naveen.

    Hi,
    There are already some good links are given by Bhavesh and Satish.
    To my knowledge where ever you need to do some Harmonization, Data Deduplication, catlog management you will go for MDM. MDM generally reads reads XML files(may be CSV & some formats but definetly not RFC or IDOCS) and gives out XML files. Lets take up some ORGN for example say DHL. DHL is spread across the globe and obviously they would be using diverse systems. But DHL would like to maintain a centeralised HR data say all Employee details. That is a single a single point where I am maintaining my master data, as we say master data we know there should be duplicates and it should be harmonized. SAP's solution for that is MDM which would help in Harmonize and remove duplicates. But the question is how MDM would collect data from all these diverse systems spread acroos the globe and at the same time how do MDM post those data into some centeralized HR system say SAP HR. So XI comes into picture to collect all different format of data and they might also use XI to convert those data into a uniform XML structure and it is loaded into MDM. MDM does its job and obviously it cannot post a IDOC into SAP HR. So it gives out a file and XI again picks up and post the IDOC into SAP HR. Simillarly think of all the master data like Product/Material master etc...
    So in most of the cases MDM & XI joins together to give a solution.
    Regards,
    Prakash

  • BI7.0 and MDM(sp06) Integration

    Hi,
    I am working on BI7 and MDM(sp06) integration scenario through ABAP APIs. For this scenario which support packs and API's need to install in BI server and where can I found complete information about integration..... plzz provide some documentation and some links which can guide me..
    Thanx in Advance.
    Rgds,
    Ram

    Hi Reddy,
    Go to [http://service.sap.com/swdc] --> Support packages and patches --> Entry by application group --> SAP NetWeaver --> SAP MDM
    You will get JAVA APIs and Portal Content there.
    go through this link...
    [How to define portal system to access MDM server;
    For a pretty good introduction to MDM workflow, see the following article: [https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9180cbaf-0801-0010-f882-f2af6dc975d0.]
    [MDM Workflow - Please help a student!;
    regards,
    NR

Maybe you are looking for