- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hello @PoonamBhardwaj
From what I can see - when the delivery starts processing, the entries are initially inserted to temp:forecastLog and nms:couponValue. The allocation of broadlogRcp-id (or the message-id in couponValue) is based on the running sequence (xtkNewId) and it blocks the next x (target) numbers.
Upon the delivery target, the entries will be inserted to broadlogRcp schema from temp:forecastLog.
In your case, maybe you could use an enrichment within the workflow to assign coupons and use targetData.coupon[x] in the delivery. Instead of using coupon module.
Hope this helps!
Views
Replies
0 Likes
Total Likes