一体化平台设计mdm主数据配置手册

一体化平台设计mdm主数据配置手册内容摘要：

d Port 属性设置 ：Remote System：选择远程系统Map: 选择在 Syndicator 中定义的 MapProcessing Type: 选择自动还是手动。 Processing Interval：仅仅 Processing Type 设置为 Automatic 时设置此参数。 这个参数是指自动处理的间隔时间，可以理解为后台作业多久执行一次。 Xml Schemas 管理 管理 Repostiory 需要用到的 xml Schema 文件。 Xml Schema 是指Repository 与远程系统进行数据交换的格式文件。 schema 文件从客户端上传，保存在 MDM 服务器中。 在 port 管理时需要用到 xml schmeas 文件。 Repository 其它操作Repository 可以进行验证，验证包含检查和修复二个功能。 操作如图所示: 当 Repository 无法 Loading 的时候可以通过 Verify Repository 来查看和检 江苏省电力公司信息化登高项目 MDM 培训手册第 32 页 共 85 页查 Repository 是否包含错误。 通过 Check 可以查看错误，追踪问题并解决。 某些错误可以通过 Repair 功能来进行修复。 Repository 复制功能操作如图所示: 江苏省电力公司信息化登高项目 MDM 培训手册第 33 页 共 85 页Repository 属性设置是设置 Repository 的多语言以及运行端口，每个Repository 需要设置不同的 port,如果设置相同则会导致 Repository 无法加载。 如图所示:Repository 多语言设置步骤如下: 江苏省电力公司信息化登高项目 MDM 培训手册第 34 页 共 85 页Repository 的详细设置界面如下： Repository Modelling　Repository 建模主要利用 MDM 交付的表类型、字段类型来进行模型构建工作。 一个 Repository 必须由一个或一个以上的主表(main table).　一个主表包含某个业务对象的主要信息，例如产品、物料、客户等等。 Repository 默认的主表名称是 Product，可以进行修改。 主表之间可以共享数据，比如供应商和客户可以共享国家这个表。 MDM 表类型可以参考下图:MDM Data Table TypesTable Type Description Main and subtables Main A main table is a flat table containing the primary information about a business object. For example, an MDM repository of product information would include an individual record for each product and an individual field for each piece of information that applies to all products, such as SKU, product name, manufacturer, and price. New MDM repositories include a main table named Products. Flat A flat table has the standard, rectangular SQL structure consisting of records and fields (rows and columns). A main table in an MDM repository typically contains some fields whose possible data values are limited and can therefore be selected from a list, rather than entered manually. For example, a Country field would naturally have a limited set of possible values. These values can 江苏省电力公司信息化登高项目 MDM 培训手册第 35 页 共 85 页be stored as records in a separate, flat subtable associated with a Country lookup field in a main table. New MDM repositories do not include any flat tables. Hierarchy A hierarchy table anizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records. The main table in an MDM repository typically contains some fields whose data may be hierarchical in nature. For example, a Manufacturer field may need to acmodate division and subdivision information for manufacturers. This hierarchical information is stored in a separate, hierarchy subtable associated with the Manufacturer lookup field in the main table. Note that a hierarchy table is useful even when it is flat (. only leaf nodes below the root), because it stores the ordered sequence of sibling records, allowing you to override the unordered sequence of values in a flat table and instead put the values in a fixed order. New MDM repositories include the following hierarchy tables: a default taxonomy table, the Masks table, and the Families table. Table Type Description Taxonomy1 Predefined. A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various anizing, searching, editing and publishing purposes. A taxonomy table in MDM stores a hierarchy of categories and subcategories and also supports attributes, “subfields” that apply to particular categories rather than to the entire collection of records. MDM supports multiple simultaneous taxonomies. New MDM repositories include a single taxonomy table named Categories. Qualified Flat Subtable. A qualified table in MDM stores a set of lookup records, and also supports qualifiers, “subfields” that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables. Qualified tables can be used to support product applications and applicationbased search, and also to store any large set of subtable records that contain fields whose values are different for each main table record, such as multiple prices for different quantities, divisions, regions, or trading partners, crossreference part numbers, and 江苏省电力公司信息化登高项目 MDM 培训手册第 36 页 共 85 页additional distributor/supplier/customerspecific information for different distributors, suppliers, or customers. New MDM repositories do not include any qualified flat tables. Object tables Images A single table named Images. Stores image files, where each image is stored as a record in the table. Sounds A single table named Sounds. Stores sound files, where each sound file is stored as a record in the table. Videos A single table named Videos. Stores video files, where each video file is stored as a record in the table. Binary Objects A single table named Binary Objects. Stores other binary object files, where each binary object file is stored as a record in the table. Text Blocks A single table named Text Blocks. Stores blocks of text, where each text block is stored as a record in the table. Copy Blocks A single table named Copy Blocks. Stores blocks of text interpreted as copy, where each text block is stored as a record in the table. Text HTMLs A single table named Text HTMLs. Stores blocks of text interpreted as HTML, where each text block is stored as a record in the table. PDFs A single table named PDFs. Stores PDF files, where each PDF is stored as a record in the table. Special tablesImage Variants A single table named Image Variants. Used to define t。