D&B | TRG | Monitoring Trigger Recipe

Step 1 – This recipe monitors a specified Amazon S3 folder path for incoming monitoring files from D&B. Files are checked every 5 minutes by default. The interval can be modified depending on the notification frequency set during monitoring registration.

D&B | PROC | Monitoring Main Recipe

Step 49 – Lists and reads the contents of the D&B monitoring folder in S3. Each file contains event data such as SEED, TRANSFER, DELETE, and UNDELETE statuses.

D&B | PROC | Process Monitoring Files

Step 12 – Iterates over monitoring records in batches of 3,000 to ensure stable and performant processing.

Step 22 – Deletes processed NOTIFICATION zip files from S3 after they are handled. This step may be modified if customers wish to archive them in their own buckets.

D&B | PROC | Process Monitoring Data in batch

Step 5 – Parses incoming JSON records for processing. The sample document must be updated if the D&B JSON structure changes.

Step 34 – Merges entity IDs from Reltio with the monitoring data based on the DUNS number. The SDK retrieves the current Entity ID for each DUNS using the GET Entity API.

Steps 35, 42, 46, 50 – Calls separate child recipes based on status type:

• Step 35 - This recipe will be triggered to Process DUNS with SEED status type.

  

• Step 42 - This recipe will be triggered to Process DUNS with TRANSFER status type. It passes the processed Retained DUNS details to a child recipe (Step 18), which writes them to the FileStorage file “Transferred_DUNS_File.csv”. The DUNS records in this file are then sent for D&B Batch enrichment through the recipe - D&B | PROC | Monitoring - Enrich TRANSFER DUNS Records.

  

• Step 46 - This recipe will be triggered to Process DUNS with DELETE status type.

  

• Step 50 - This recipe will be triggered to Process DUNS with UNDELETE status type.

  

D&B | TRG | Monitoring Exception File Trigger Recipe

Step 1 – Monitors an S3 folder for new D&B monitoring exception files (typically ZIP or TXT). Triggers automatically on new uploads. Polling frequency is configurable.

D&B | PROC | Monitoring Exception Codes – Main Recipe

This recipe handles exception files received from D&B. It parses the content, translates error codes, and prepares error status updates for Reltio.

Files processed include standard exception ZIPs containing DUNS numbers and their associated error codes.

Steps 43 & 45 – Clean up exception ZIPs and NOTIFICATION_HEADER files after parsing to prevent duplicate processing.

D&B | PROC | Process Exception file Data

Step 4 – Filters out exception code 21012 (indicating duplicate registration) from further processing.

Steps 6–14 – Removes valid exceptions from the Registration Master File.

Steps 15–24 – Removes matching DUNS records from the Ad-hoc Registration File.

Step 45 – Flattens crosswalk data exported from Reltio and filters out D&B source crosswalks.

These crosswalks are then used to populate the error status in Reltio through the child recipe — D&B | SYS | Update Registration Status - Reltio Load.