Behavior of the enrichOrgWithDnBData transaction

The Dun & Bradstreet enrichment process is implemented as a sample because it is hard to predict how the InfoSphere® MDM users will choose to use Dun & Bradstreet enrichment data. The sample enrichOrgWithDnBData transaction provides one example of how the data could be used.

The enrichOrgWithDnBData transaction is implemented as a custom proxy. This proxy extends the DWLTxBP base proxy and has a template pattern; the method execute() calls other template methods that process logical data from the Dun & Bradstreet enrichment feed. If the transaction logic for a data element needs to change, InfoSphere MDM users can write a new proxy that extends the EnrichOrgWithDnBDataCompositeTxnBP proxy and overwrites the appropriate method.
The enrichOrgWithDnBData transaction can be used to add or update following information:
  • organization entity (update only)
  • party identification
  • party address
  • organization name
  • contact method
  • hierarchies, and organizations that participate in a hierarchy
Each piece of Dun & Bradstreet data that cannot be represented by a corresponding InfoSphere MDM business object is stored as either a party miscellaneous value or an address miscellaneous value.
Note: For a more detailed description of how individual Dun & Bradstreet data fields are mapped to InfoSphere MDM business objects, see Enrichment inbound file layout.
The enrichOrgWithDnBData transaction has the following restrictions:
  • It can only update InfoSphere MDM business objects with Dun & Bradstreet data if the configuration parameter /CustomerSamples/DnB/Update/updateEnabled is set to true.
  • It can only create new InfoSphere MDM business entities if the configuration parameter /CustomerSamples/DnB/Add/AddEnabled is true.
  • It can only execute hierarchy logic if the configuration parameter /CustomerSamples/DnB/Add/BuildHierarchyEnabled is true.
  • It can only add new organizations, which is sometimes required to build a hierarchy, if the configuration parameter /CustomerSamples/DnB/Add/OrgInsertEnabled is true.
  • It can only update the names and addresses of organizations within a hierarchy if the configuration parameter /CustomerSamples/DnB/Add/UpdateHierarchyOrg is true.

You have the ability to customize the value of these configuration parameters in DunAndBradstreet_dwlConfig.sql.

Everywhere possible, the enrichOrgWithDnBData transaction marks the InfoSphere MDM business objects containing Dun & Bradstreet data using a source identifier code type corresponding to the value "D&B" from the CDSOURCEIDENTTP table.

InfoSphere MDM users have the ability to customized InfoSphere MDM code tables with each new InfoSphere MDM deployment. The code in the enrichOrgWithDnBData transaction never uses code type IDs directly from InfoSphere MDM code tables; rather, all the code type IDs are externalized as Configuration Manager parameters. For example, the hierarchy code type HIERARCHY_TP_CD from the CDHIERARCHYTP table is equal to 7000 and corresponds to the value "D&B". The enrichOrgWithDnBData transaction code uses the configuration parameter /CustomerSamples/DnB/HierarchyType to externalize the code type ID 7000. If the CDHIERARCHYTP code table is modified and the HIERARCHY_TP_CD for the value "D&B" is no longer 7000, then the /CustomerSamples/DnB/HierarchyType parameter must be updated to match the new values, but the transaction's code does not require modification.


Last updated: 13 Sep 2017