Dear @Abir Messaikeh@Zein Trabelsi@Ayed Bada,

We've observed an issue where the exchange value is not being populated for subscriber 6500 in both the fn_fiber_trail_mv and fn_copper_trail_mv materialized views.

To resolve this data gap, can we implement a VLOOKUP (or equivalent join/query logic) to retrieve and map the correct exchange for the subscriber?

The proposed mapping logic would be:
1. Look up the subscriber ID (e.g., '6500') within the fn_fiber_trail_mv and fn_copper_trail_mv views.
2. Use the retrieved subscriber ID to join with the master fn_subscriber table.
3. Extract the corresponding exchange from the fn_subscriber table and use it to update/reflect the correct exchange for the subscriber records in the trail views.

Please let me know if this approach is feasible and when we can expect the fix to be implemented.