The GDSN data model with its standardized attributes and structure is preconfigured in MDM – Product 360 by using the GDSN accelerator. The standardized XML messages used to transfer item data or publications from MDM – P360 to the GDSN are stored as standard exports, allowing product information to be published from a central location to all target markets or to specific individual data recipients.
The GDSN data model with its standardized attributes and structure is preconfigured in MDM – Product 360 by using the GDSN accelerator. The standardized XML messages used to transfer item data or publications from MDM – P360 to the GDSN are stored as standard exports, allowing product information to be published from a central location to all target markets or to specific individual data recipients.
The GDSN data model with its standardized attributes and structure is preconfigured in MDM – Product 360 by using the GDSN accelerator. The standardized XML messages used to transfer item data or publications from MDM – Product 360 to the GDSN are stored as standard exports, allowing product information to be published from a central location to all target markets or to specific individual data recipients.
In addition, MDM – Product 360 also has the functionality to maintain the product information decentrally in the local organizations and publish it from there to different target markets or data recipients.
A decisive factor in this context is the validation of product information against the requirements of the GDSN data model. Products that do not meet these requirements, for example where required fields are not filled, cannot be sent to the data pool without correction.
Additionally the feedback from data recipients, the so-called GDSN CIC messages delivered by the b-synced GDSN data pool are imported by default and displayed in MDM – Product 360.
The GDSN data model with its standardized attributes and structure is preconfigured in MDM – Product 360 by using the GDSN accelerator. The standardized XML messages used to transfer item data or publications from MDM – Product 360 to the GDSN are stored as standard exports, allowing product information to be published from a central location to all target markets or to specific individual data recipients.
In addition, MDM – Product 360 also has the functionality to maintain the product information decentrally in the local organizations and publish it from there to different target markets or data recipients.
A decisive factor in this context is the validation of product information against the requirements of the GDSN data model. Products that do not meet these requirements, for example where required fields are not filled, cannot be sent to the data pool without correction.
Additionally the feedback from data recipients, the so-called GDSN CIC messages delivered by the b-synced GDSN data pool are imported by default and displayed in MDM – Product 360.
Data Maintenance in MDM – Product 360
In MDM – Product 360, the GDSN data model can be stored directly with additional attributes for the community profiles of the different countries and target markets in order to meet the different requirements for different target markets.
Individual data models (attributes and value lists) can also be defined in MDM – Product 360 and the mapping to the GDSN target format can be customized on a project-specific basis in the predefined export format templates.
Data Maintenance in MDM – Product 360
In MDM – Product 360, the GDSN data model can be stored directly with additional attributes for the community profiles of the different countries and target markets in order to meet the different requirements for different target markets.
Individual data models (attributes and value lists) can also be defined in MDM – Product 360 and the mapping to the GDSN target format can be customized on a project-specific basis in the predefined export format templates.
Publishing to the GDSN
Product information from MDM – Product 360 is published to the b-synced data pool via the GDSN standard message format CIN and therefore published directly to the GDSN. Publishing can be fully automated. Individual or multiple product hierarchies as well as static or dynamic assortments can be published manually with only one click. The release for specific target markets in the GDSN via the CIP message format can be triggered both automatically and manually.
Publishing to the GDSN
Product information from MDM – Product 360 is published to the b-synced data pool via the GDSN standard message format CIN and therefore published directly to the GDSN. Publishing can be fully automated. Individual or multiple product hierarchies as well as static or dynamic assortments can be published manually with only one click. The release for specific target markets in the GDSN via the CIP message format can be triggered both automatically and manually.
Communication with the data recipient
The comments on data quality by the data recipient (message format CIC) are categorized and summarized and can be viewed in the b-synced data pool, but are also transferred back to the MDM – Product 360 and then imported. There they are directly visible by the data maintainer and can be used to correct the data as required and to improve the data quality.
Communication with the data recipient
The comments on data quality by the data recipient (message format CIC) are categorized and summarized and can be viewed in the b-synced data pool, but are also transferred back to the MDM – Product 360 and then imported. There they are directly visible by the data maintainer and can be used to correct the data as required and to improve the data quality.
Informatica MDM – Product 360 with b-synced
Benefit from our experience
Contact us – no matter which project phase you currently find yourself in. We are happy to support you with our experience.