Defining Source
The source indicates the name of the system that has produced the given set of data that is being pushed into TIBCO MDM. Typically, in a given enterprise the data might come from various systems such as SAP, ORACLE, JD Edward, Salesforce, and so on. To compute the precedence, you must record or tag the data along with the source information (name of the source as an identifier) within TIBCO MDM.
If a source is not defined, precedence does not apply to data coming from that source.
- Enable
Attribute HistoryandPrecedence Managementproperties in TIBCO MDM Studio for the repository that you want to deploy. See TIBCO MDM Studio Repository Designer User's Guide. - Apply the precedence rulebase action to a repository. See TIBCO MDM Studio Rulebase Designer User's Guide.
- Procedure
- In TIBCO MDM, click Precedence Management.
The Precedence Management page is displayed. - On the Source Definitions tab, click Create.
-
On the Precedence Management - Source page, perform the following actions:
-
Enter details in the following sections:
Section Name Description Source Details Enter source ID and description.
For example,
Source ID Description SAP SAP ERP JDE Main JDE instance If the source ID is null, the default source is assigned as UI. The default source is required to track the attribute history. Attribute history does not need the source to be defined, but the precedence cannot be computed.
Attribute Quality Definitions To add related records, see Defining Attribute Quality Definition Repository.
- To link records from existing repositories, see Linking Records from Existing Repository.
- Change the value of selected records by inline editing or selecting the Edit Selected Records option.
Precedence Definitions To add related records, see Defining Precedence Definition Repository.
To link records from existing repositories, see Linking Records from Existing Repository.
Change the value of selected records by inline editing or selecting the Edit Selected Records option.
- Click Validate to validate records.
A consolidated list of errors is displayed. The validation errors are displayed for the incorrect values. This validation uses thecatalogvalidation.xmlfile where validation rules are defined. If errors are found, correct the values according to the message. - Click Save.
A confirmation message is displayed and the record is saved in the Source Definitions repository.