Why does Golden Gate perform SELECT operations while applying updates to the target?

It has been identified during the replication of Golden Gate, specific postulates are executed on a table that have high response times, on the one hand an UPDATE, but on the other hand a SELECT (With Full Table Scan) is observed, and when these queries increase in the number of executions by Golden Gate in the database, it begins to present high waiting times and high CPU consumption.

Why is Golden Gate executing SELECT operations?

What logic or configuration causes the product to perform SELECT operations against the target database?

Here the SQL executed by OGG:

SELECT decode("U2ACCT", :1, NULL, ', "U2ACCT"')||decode("U2ACCTG", :2, NULL,