DECLARE and BEGIN. Yes, this is normal behavior, as these are functions, procedures, or views where the underlying DML operations are the reason the corresponding SQL statements are being captured.
Please try updating the policy as outlined below and verify whether it produces the expected result.
go to global Objects - General dictionay group - create the group with the required commands
Ex
in the policy add the match criteria -> General dictionary and add/select the above created group . locations:select "Parsed Query"
------------------------------
Revn
------------------------------