Beruflich Dokumente
Kultur Dokumente
STATUS CHANNEL
DRIVEN SPECIFIC
MERGE TRUSTED VALIDATIONS
QUALITY CONTINUOUS
DRIVEN QUALITY
ONBOARDING PROFILING
Universal MDM
Why PIM and MDM together?
Rich Product Data Ability to store and Link and Track Share reference
consume Product Cross Entity data across the
(PIM to keep authoring
and enriching Product Relationships and Relationships business
Data) Classifications (Product-Customer, (Publish to Multi
(Market Segment, Product-Supplier, targets and
Cross/Up-sell) Supplier-Location,) Multiple channels)
PIM and Informatica Demo
Build rich, consistently high quality
product content, including cross-
sell & up-sell relationships
TRUSTED
DATA PRODUCT MULTI-
INTEGRATION MASTER CHANNEL
ATTRIBUTE
ATTRIBUTE MATCH & AUTO COMPLETENESS / TERMINOLOGY FIELD VALUE
EXTRACTION MERGE CLASSIFICATION ALLOWED VALUE CHECKS STANDARDIZATION
CHECKS
MDM Data model (Conceptual)
Source Systems
SourceSystems
Analytics
CustomertoStore
CustomertoProduct
Classification
CustomertoEmployee
Relationships
CustomertoCustomer
StoretoLocation
StoretoEmployee
EmployeetoEmployee
Article(Product)toLocation
Article(Product)Reference
SupplierArticle
CRM CustomerRelationshipManagementsystem
ERP EnterpriseResourcePlanningsystem
ecommerce ecommerceApplication
Social SocialMediachannels socialapplications,pluginsetc.
POS PointofSalesystem
PIM ProductInformationManagementsystem
AnalyticsSystem(forinformationsuchasCustomer
Analytics Segmentation)
Integration Design - Batch
An export template of PIM defines the layout and content of the CSV files for the data transfer. The export engine of
PIM provides the article data according to the templates definition as a delta for the articles changed since the last
MDM update (or alternatively a full load for the initial transfer).
A set of Power Center mappings brings data from PIM into MDM landing tables. These mappings
process the data files and transform the records as necessary before inserting them in MDM landing tables.
A set of custom scripts invokes MDM batch jobs (stage, load, match & merge) in sequence (parent first)
and supply the necessary parameters to the batch jobs.
Custom scripts are used to identify the newly inserted and modified and merged records in MDM which
are then exported back to PIM system via Power Center mappings.
The incoming CSV files are recognized via a hot folder plugin and automatically transferred to the PIM repository by
the import engine. A previously defined import mapping on side the PIM is used for that.
Integration Design Near Real Time
Composite Service
Composite services developed on MDM-MDE can execute CRUD operations asynchronously. These
services are built using MDM-MDE SIF API and Data Services and transactional. Composite service
includes operations to perform Read, Create, Update, and Delete operation for each of the main
entities. The composite services can be executed in a synchronous or asynchronous manner.
PIM to MDM-MDE interface
A set of triggers in the PIM System monitor data changes. Custom implementations of these triggers
invoke appropriate MDM-MDE composite service and propagate changes to MDM-MDE.
MDM-MDE to PIM interface
Message triggers are also configured in MDM-MDE to monitor data changes in MDM and place an XML
document containing the changes to a JMS queue. A custom JMS plugin developed on PIM consumes
these messages, processes them and makes appropriate changes in the PIM system.
Integration Design Real Time
Duplicate Prevention
While a user adds a new Supplier or Customer using the PIM console a fuzzy search is
executed using the composite services on MDM-MDE and potential duplicates are identified
and displayed to the user. The user can choose to import the duplicate record directly from
the MDM-MDE hub into PIM.