Single Task Siebel Update Server Components
The update server components are part of the Dun and Bradstreet Enterprise Component Group. This group and each of its D&B Batch Components must be enabled. After enabled, each component can be run as a batch task. The following image shows how the staging tables are mapped to the D&B Account tables.
In this image, there are:
Three staging tables: S_DNB_SIC, S_DNB_Update, and S_DNB_MRC.
Four D&B Account tables: DNB_ORG_SIC, S_DNB_ORG, S_PRSP_CONTACT, and S_DNB_CON_MRC.
Two one-to-many mappings, between staging and D&B Account tables, as follows:
From S_DNB_SIC to S_DNB_ORG_SIC.
From S_DNB_MRC to S_DNB_CON_MRC.
Four one-to-one mappings, between staging and D&B Account tables, as follows:
From S_DNB_UPDATE (via D&B Update Manager) to S_DNB_ORG_SIC.
From S_DNB_UPDATE (via D&B Update Manager) to S_DNB_ORG.
From S_DNB_UPDATE (via D&B Update Manager) to S_PRSP_CONTACT.
From S_DNB_UPDATE (via D&B Update Manager) to S_DNB_CON_MRC.
Three one-to-many mappings between D&B Account tables as follows:
From S_DNB_ORG to S_DNB_ORG_SIC.
From S_DNB_ORG to S_PRSP_CONTACT.
From S_PRSP_CONTACT to S_DNB_CON_MRC.
The following image shows how the D&B Account tables are mapped to the Siebel Account tables.
In this image, there are:
Three D&B Account tables: DNB_ORG_SIC, S_DNB_ORG, and S_PRSP_CONTACT.
Three Siebel Account tables: S_ORG_INDUST, S_PARTY (includes S_ORG_EXT, S_ORG_EXT_X, and S_CONTACT tables), and S_ADDR_ORG.
Three one-to-one mappings, between D&B Account and Siebel Account tables, as follows:
From S_DNB_ORG_SIC (via D&B Update Manager) to S_ORG_INDUST.
From S_DNB_ORG (via D&B Update Manager) to S_PARTY.
From S_PRSP_CONTACT (via D&B Update Manager) to S_ADDR_ORG.
Default table mapping exists from the D&B Account tables to the Siebel Account tables that are used by the D&B Update Manager (Siebel) server component. For more information, see Field Mapping for the D&B Update Manager Process.