FAQ
Monitoring Service
General Questions
Customers are currently notified of any non-backward compatible changes in the existing version of each service. New functionality and version additions are documented on the Release Notes page.
Please contact Dun & Bradstreet Customer Support or your Technical Account Manager for more than 15,000 D-U-N-S Number registrations in a single day.
Yes, as per the contract, Queries Per Second (QPS) will be set for the customer/ subscriber number. Any requests beyond the QPS will return the SC006 Error Code: Transaction not processed as the permitted concurrency limit was exceeded.
The following parameter can be used every hour for pulling the unread notices: ReadChangeEventIndicator=false
Transfer Cases
Registration will fail during the activation process and the D-U-N-S Number will not be included in monitoring.
Change Notices include transfer events, after which the transferred D-U-N-S Number will no longer be included in monitoring notices.
In order to receive change notices on the transferred D-U-N-S Number, customers must register the new D-U-N-S Number for monitoring; this will incur a billing charge.
NOTE: Change Notices for D-U-N-S Number transfer events are only supported for the following products: Detailed Company Profile, Alternative Detailed Company Profile, Detailed Company Profile - WB1784, Compliance Verification Report.
NOTE: Change Notices will only be delivered for Custom Products if the D-U-N-S Number transfer elements have been configured as part of the product.
Change Notices will be delivered about the deleted event, and notices will no longer be generated for the deleted D-U-N-S Number.
NOTE: Change Notices for D-U-N-S Number deleted events are only supported for the following products: Detailed Company Profile, Alternative Detailed Company Profile, Detailed Company Profile - WB1784, Compliance Verification Report and Custom Products.
Understanding Service Version Number
Set up the Monitoring Profile without specifying the service version number of the product. For all subsequent monitoring operations do not specify the service version number of a product in the request. Providing a service version number in the request will result in incorrect or failure response.
Change Deduction and Notices are always generated using the latest service version of a product.
When a new service version of a product is introduced the following can be expected:
- Change Notices will be generated for any new elements under an aggregate that is monitorable as "Newly Added".
- Change Notices will not include new individual element changes introduced in that version of the product. However, all new changes will be included in Level 2 reports.
To receive Change Notices for new element changes of a product, please update the Monitoring Profile.
Set up the Monitoring Profile by specifying the service version number of the product. For all subsequent monitoring operations use the same service version number of the product in the request. Providing a different service version number of the product in the request will result in failed response.
Change Deduction and Notices are always generated using only the specified service version number of the product unless the customer changes to a different version using Update Monitoring Profile operation.
Billing
Yes, there will be a charge if the same D-U-N-S Number is registered again using a different Monitoring Profile or Notification Profile within the contract period.
Yes, contract renewal will be billed for all registered D-U-N-S Numbers.
