@DhanasekarC0202 I checked the solution provided to you in INC-C7576

Analysis by our support team:

Solution type: Explanation " As previously mentioned, it is standard for platform and strategic applications, including customer service upgrades, to trigger column population jobs following an upgrade. Typically, these jobs operate in the background without impacting your environment. However, for larger tables, the completion of these jobs may take some time. Additionally, on February 21st, they deployed changes to production that included schema modifications for two tables. They observed that column population jobs were triggered again for approximately 40 other tables. We conducted a debugging session via call to determine the cause of these column population jobs being triggered. Upon reviewing the PDC and logs, we noted that their deployment included two RDIs for the relevant classes, which explains the execution of these jobs. Whenever updated RDIs are imported, Property Optimization jobs are scheduled for the relevant classes. Please note: Automatic column population will be triggered for schema changes to existing tables, when new RDIs are imported, when classes are migrated to new tables with differing columns (such as new columns on the target table or incompatible data for columns in existing tables), and when the Upgrade Application Schema adds new columns to child tables (i.e., columns added to shipped tables during the upgrade and propagated to child class tables via UAS)."

Therefore we believe your question was answered.

If you need further help can I ask that you engage with the engineer who helped you with that ticket?