Collection BP Tasks Use Case

This use case describes a realistic scenario using the Collections BP tasks: deduplicating and enriching incoming EDI 850 Purchase Orders before routing them to an ERP. 

Business Process: "PO_Intake_Enrichment"

1. Dictionary - Create → initialize an empty vendorLookup Dictionary at the start of the BP. This will hold vendor-code-to-internal-ID mappings pulled from a reference file or database query earlier in the process.
2. List - Create → initialize an empty lineItemErrors List to collect any line items that fail validation as the BP loops through the incoming PO.
3. Loop over each vendor record returned from a lookup query (e.g., a JDBC or file read task upstream):
   • Dictionary - Put → for each vendor row, put the vendor code as the Key and the internal customer/vendor ID as the Entry into vendorLookup.
4. Now loop over each line item in the incoming 850 document:
   • Dictionary - Has Key → check if the line item's vendor code exists in vendorLookup. If not found, this flags a data issue.
   • If Has Key is false: List - Add → add the problematic line item (or an error message string) to lineItemErrors.
   • If Has Key is true: Dictionary - Get → retrieve the correct internal vendor ID from vendorLookup using the vendor code, and use it to overwrite/enrich the outgoing record before mapping it to the ERP's expected format.
5. After the loop:
   • List - Size → check the size of lineItemErrors. If greater than 0, branch the BP to send an email alert or write the errors to an exceptions folder/table for someone to review.
   • List - First / List - Get (index 0, 1, 2…) → pull specific error entries to include in that alert email body.
   • Dictionary - Size / Dictionary - Keys → optionally log how many vendors were matched, or output the full list of vendor codes processed for an audit trail.
6. If no errors, the enriched document continues downstream to the ERP connector (e.g., a NetSuite or D365 connector task) for final delivery.

Why this is realistic: Dictionary tasks are the natural fit for lookup/mapping problems (vendor codes, currency codes, UOM conversions) that come up constantly in EDI/B2B integration, while List tasks fit error/exception collection and iteration patterns - both extremely common patterns in CIC Studio BPs that sit between trading partner documents and back-end systems.