Artesia and MDM Integration

Has anyone enabled the link between Artesia digital asset management (DAM) tools and MDM? We keep all our product images in Artesia (tool is called TEAMS) and would like to point our MDM-based product info repository to Artesia so that we don't need to import images directly into MDM.
Also, we use Documentum for management of our product literature. Does anyone have experience integrating MDM and Documentum?
Thanks.
Mike Jakeway
Lead Technical Analyst
Whirlpool Corp.

Hi Michael,
I have come across the similar case once but not using DAM.
First let me understand your requirements clearly.
You dont want to import images to MDM repository. Instead you want to point the product data stored in MDM to its corresponding image stored in DAM.
This is simple if your environment is applicable to any my assumptions mentioned below.
My assumption 1:
You have implemented DAM tool for managing images newly and no application or data base linked with DAM.
My suggestion 1:
Artesia should be storing images in a database with a field for "image id" right? In that case we can add a new field for "Product id" in the DAM database (if not exists) and map the image in the DAM with the Product data using "Product id" field from source data (DAM) and "Product id" field in MDM. Syndicate MDM with DAM database. So that when ever you add a new product data, a new product id will be added in your DAM database.
My assumption 2:
You have already inplemented DAM tools and developed application (Say .Net) for managing the product data. Now you are planning to move the product imformation to MDM and view the product detail in the portal (Say SAP EP) iview.
My Suggestion 2:
If you are planning to view the product data and images in the portal, we can develop coustom iview which retrieves product data from MDM and image data from DAM.
Same case appicable to Documentum management.
Let me know in detail if have some other scnarios.
Thanks,
Prabhu

Similar Messages

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.

CC&B and MDM Integration

Dear Friends,
Currently we are using ccb 2.3.0 and MDM 1.6.0 versions
1.How we can integrate CC&B and MDM ,
2. what are various possible ways of integration and components required for the same
pls recommend the latest versions if integration becomes easier
thanks and regards
sivaram

The new MDM 2.0.1 version has some integration functionalities build in.
MDM 2.0 has introduced a concept called "Seeder" this is more or less an XAI Integration.
Since version 2.0.1 you have a Seeder for IMD import and master data synchronization.
You can review the documentation (Framework_Administration_Guide_v4_1_0) if you are interested in details.
Check chapter "External Application Integration".
The suggested way is to setup OSB for message routing and transformation and XAI to publish/subscribe the integration
messages.
/Markus

BI7 and MDM integration

hi..
I am working on BI7 and MDM(sp04) integration scenario through ABAP APIs. For this scenario what s/w( including support packs and which APIs) are needed to install on BI server. and where can I found that information.... plzz provide some documentation and some links which can guide me..
cheers,
Suman.

Hi Suman,
Check the following link, will get some information
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=bi7andmdmsupportpack&adv=false&sortby=cm_rnd_rankvalue
Thanks & Regards,
Hema

Bi 7.0 and MDM integration problem

will it be possible to do seperate application of MDM built on BI 7.0 application in the single server which will result to provide set of tables .
As per requirement in BI we have to consolidate and harmonise of master data as a whole.
Edited by: shaik sarfraz on Oct 15, 2008 10:26 AM

Dear,
Plz chk:
http://portal.acm.org/ft_gateway.cfm?id=355306&type=pdf&dl=GUIDE&dl=ACM
http://www.redbooks.ibm.com/redbooks/pdfs/sg246489.pdf
http://www.cio.sc.gov/SCEA/eap/All_Enterprise-Applications.pdf
http://www.sap.info/public/INT/int/glossary/int/glossaryletter/Word-38053d4a869829887_glossary/S
http://www.inforte.com/ideas/points_of_view/content/pov_integratedplanningbusinesscontent.pdf
http://www.esri.com/news/arcnews/fall06articles/sap-and-esri.html
Thanks

Brief discussion on SAP XI and its' Integration with SAP MDM.

Hi,
I have never worked on SAP XI.
I am discussing it on brief, please give your valuable replies.
SAP XI consists of System Landascape Directory(SLD).
SLD Consists of Business System and Techinical System.
Technical System contains all information about the software
component. The Business System consists of Inbound and Outbound Business
System which are used as logical names for data transfer.
There is communication Channel for Receiver and Sender Business System and n agreement
is signed between Sender and Receiver.
Outbound Interface defined for Business System Outbound and Techical System associated
with the Business System,
Inbound Interface defined for Business System Inbound and Techical System associated
with the Business System.
In SAP NetWeaver XI Integration Directory, we have defined the Integration Scenarios,
Actions, Interface Objects, Mapping Objects, Adapters Objects.
Mapping Object defines the Structure and Value Mapping.
Adapter Objects defines the Adapter program which implements RFC Adapter, FTP Adapter logic.
FTP Adapter is used for XI-MDM Communication.
RFC Adapter is used for XI-ECC Communication.
Integration Repository: Both Outbound and Inbound Interfaces are Mapped with Value mapping and
Structure Mapping inside Integration Repository.
The File Adapter takes the File from the Outbound port of MDM System
and sends it as IDOC to Receiver Business System.
Value Mapping must be done between Sender and Receiver interfaces.
Value Mapping is done by XSLT or Java based program.
SAP NetWeaver XI Integration Server at runtime:
Message Split, Interface Determination, Receiver Identifaction, Mapping, Techincal Routing
and Call Adapter Proccess are done.
In SAP XI 3.0 and MDM 5.5:
Step 1: Create busines system as service.
Step 2: Create communication channel for each business service. If the system can communicate
through different channels, then create all possible channel types if necessary.
Step 3: Create receiver agreement between the systems.
Step 4: Interface determination:
- Here you see for the first time the software component mentioned;
there are some special requirements regarding this software component in relation to the customizing ID mapping.
- To modify this software component, the customer needs to copy the SAP standard delivered software component
into its own namespace. The customer is able to modify to create archives
for the customized ID mapping.
Receiver determination.
Configure an FTP Server on the MDS.
Create a send folder for outbound messages using outbound port(s) for
remote systems(s).
Create receive folder inbound messages using inbound port(s) for remote systems.
This ia all about concept of SAP XI Infractsture and its' Integration with SAP MDM 5.5.
Regards
Kaushik Banerjee

Hi Kaushik,
You must be aware of File types that MDM Import Manager can Import i.e. we have XML, Excel etc. Now there are two transactions to extract data from R3
1. MDMGX -
         - For lookup table extraction
         - Output in XML format which MDM can import without using XI.
          - FTP can be configured to put the file in the desired folder which will be then picked by Import Server.
2. MDM_CLNT_EXTR -
          - For Main table records.
          - Output is in Idoc format which MDM doesn't understand hence we need XI in between which converts Idoc file received from R3 into XML which can then be imported using Import Manager or Import Server. For this we need to implement XI Scenario that consists of Source System, Receiver System, Type of Data etc.
Just a basic understanding...
Regards,
Jitesh Talreja

Test/Trial project on MDM and XI integration.

Test/Trial project on MDM and XI integration.
I want to try out a test case scenario where in i would be importing and exporting data to XI (Using XML files i guess)
I am a newbie in MDM integration.
Please help me out with my trial project.
What i already have:
I have MDM system and repository on which i have been learning basic MDM designing a (test)repository of my own.
What information i need:
-What all system requirements (XI system configuration and all) are needed to established. (What all should i be asking the XI and the system admin guys to be able to get the platform ready for me.*
*-The further procedure for actual integration to be done for importing/exporting data as in a real time project scenario

Hi Gaurav,
SInce you want to try a test scenario including MDM and XI, I would suggest you to try
ECC -> XI->MDM scenario
Wherein you can take the data from ECC in the form of IDOCs and convert them into XML.
You can then import the XML into an MDM repository. MDM repository can be a Customer, Material, Vendor etc repository. Hence extract the similar data from ECC.
Kindly follow the steps below:
1) Firstly you will have to extrcat the look-up table data from R3 using MDMGX transaction-
Please follow this link to know about the same:
How to Configure Master Data Management Reference Data Extraction -
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0740b31-a934-2b10-2e95-af2252991baa
https://websmp203.sap-ag.de/~sapidb/012006153200000394732006E/MDM554_GenericExtactor.pdf
2) For loading the main Table Data into MDM, kindly follow the link below, which will guide you to the config/prcoess that will be required for the data to be uploaded from R3 into MDM.
2.1) R/3-XI-MDM (Outbound Scenario)
You will have to extract the data from R3 in the form of IDOCS and then using XI, you will have to convert them into XML format as MDM understands that.
2.2) For the process of Data from MDM back to R3, kindly refer this link below:
MDM-XI-R/3 Integration
2.3) For general info about this scenario, kindly refer this link below:
MDM Mass data Integration with R/3 made easy
Please follow these links for additional info-
1) SAP Network Blog: XI Configuration for MDM Integration - Sample Scenario-
XI Configuration for MDM Integration - Sample Scenario
2) The below given blog can be used to understand the XI config done when data is sent back from MDM via XI to R3.
MDM->XI->R3
MDM-XI-R/3 Integration
3) MDM 5.5 data distribution using SAP XI -
MDM 5.5 data distribution using SAP XI
Hope this information helps.
Thanks and Regards
Nitin jain

MDM integrity between SRM and R/3

Hi All,
How MDM integrity of the process validations being made between SRM and R/3 for the creation of different documents.
Please share me any documents regarding MDM intergirty between SRM and R/3. This is not related to Catalogs,
1. Creation of documents like GOA in SRM and distributed to R/3. How MDM will validate that data.
2 If same material available in different backend system. while creating Contract in SRM, MDM should check the R/3 materials in MDM
3. How to integrity works for Vendors.
Thanks
ravi

Hi,
Take a look in these threads:
[Re: material master replication|Re: material master replication]
[Master Data Synchronization between SRM and ERP|Master Data Synchronization between SRM and ERP]
[Re: Material replication|Re: Material replication]
Rgs,
Pedro Marques

Metadata Integrator for ECC and MDM

Hi ,
Please help me choose the correct Metadata Integrator for the following:
1. ECC
2. MDM
Thanks in advance,
Munavar

HI Manoj,
Thanks for your reply. Yes, I am looking for integrators for ECC and MDM.
How do we pull metadata from ECC and MDM into BOMM?
Thanks,
Munavar

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

Cisco ISE 1.2 MDM Integration Question

I have a working Cisco ISE 1.2.1 install which I've performed the integration to our MobileIron server. The "integration test" reports that the integration is good, but whenever ISE verifies MDM compliance, registration, etc.. with MobileIron when a mobile device connects it always reports that all statuses are good even if they aren't.
My test phone is out of compliance on Mobileiron because of an unapproved app, but when the phone connects ISE believes the MDM compliance status is good. I'm not sure if it isn't really checking with MDM or if the Mobileiron server is reporting erroneous results.
I also saw in a video that the phone has to be registered with MobileIron through ISE. Is this correct? I don't plan to on-board devices with MobileIron through ISE, it will be done directly through MobieIron (not connected to the Wifi network).
I only want ISE to check the compliance status of the device against MobileIron and quarantine if it isn't compliant or MDM registered.
Any help would be appreciated

Saurav and others,
Unfortunately, on-boarding sets some attribute fields on the endpoints that will then allow them to participate in a policy. It is nice that we all have MDM integration working but we almost need another class of on-boarding for corporate devices that are already in the MDM of choice (where we prefer to manage them!)
There is a little documented feature in ISE.
It appears to me that;
the on-boarding turns on the following states for the endpoint;
BYODRegistration
No ( No becomes Yes)
DeviceRegistrationStatus
NotRegistered (becomes Registered)
( The device is actually registered in MobileIron - this means did ISE register with MI. )
No MI attributes will work without this magic. TAC engineers I have dealt with don't seem to understand this feature.
This is definitely an enhancement that is needed.

R/3 u2013 XI u2013 MDM integration scenario - Standard import Maps problem

Hi Data Masters,
We are working on R/3 u2013 XI u2013 MDM integration scenario for Vendor Object. We have extracted main table Data using u201CMDM_CLNT_EXTRu201D program. Now while importing the data in MDM we want to use u201CStandard business content i.e. Standard Import Maps (Name u2013 cremdm - 03 u201D but this maps are not mapping all the fields. So do we need to extend this maps..??
OK. Second, To create own maps we are facing following problems,
1) In source section many fields are reflecting twice means in two segments i.e. LFA1 and ADRMAS like Name, City, Street, country etcu2026 whereas in Target section we have one field for the same so how to maps this fields.
2) In source, There are few fields like ADRNR which have values but in target we donot have any fields to map for the same, so how to handle thisu2026
Helpful answers will be rewarded,
Cheers
RC

closed

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.

R/3 - Xi - MDM integration Scenario.

Hi experts,
We are working on R/3 XI MDM integration scenario for Customer master wherein requirement is to consolidate the u201CGeneral datau201D but at the same time we need to retain u201Csales area datau201D for each record as it is.
For example, In sap ECC system we have Master record (Which is duplicate) as mentioned below,
Id   Name           Sales Area.
1    Neethu      SA1
2    Neethu Joy     SA2
After merging two duplicate records general data we will have a single record in data manager. Further we want to link Sales Area Data to same consolidated record. Final picture in MDM data manager should look like this,
Id   Name           Sales Area.
1   Neethu      SA1; SA2
Can anyone suggest a solution? How we can u201Cappendu201D Sales area data to Consolidated General master data. How we can deal with u201CDelta Recordsu201D to achieve the same Output..??
Matter is most urgent...Points will be rewarded.
Cheers,
Rajesh Chavan

Hi Rajesh,
On merging two duplicate records, generally data merge as a single record in data manager.So i would suggest in this case
You have to change your Repository design and MAP. you can achieve this, Firstly For Sales Area you have to make this lookup field(Multi-Valued) in main table which will lookup to SubTable say SalesA for which Multi-Valued is YES.
Now come to Import Manager, Here during Map as you have
Id Name Sales Area.
1 Neethu SA1
2 Neethu Joy SA2
Map first Source Sales Area Field with Name(DF) when you select SalesA as your Current Destination Table then import Main table records as ususal here in which you also map Sales Area source field with Sales Area which is lookup field(Multi-Valued) in main table
IN Data Manager, During Merge Records when you select Sale Area field as SA1 in Merged Record for Id 1 then Right Click on SA2 for Id 2 here your append Option will get enabled using this you can get desired output as
Id Name Sales Area.
1 Neethu SA1; SA2
Rewards if useful....
Hope it will help you,
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 ones 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

Artesia and MDM Integration

Similar Messages

Maybe you are looking for