Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Groovy Warning in S/4 Import

VicyB
Regular Contributor
Regular Contributor

Hello everybody,

in our import from the S/4 HANA (we import accounts, roles, profiles and tcodes), we have good insights in the logs for the first 10mins of the job, then there is a warning in the logs which repeats until the job is finished:

WARNING [quartzScheduler_Worker-7] groovy.sql.Sql.asSql In Groovy SQL please do not use quotes around dynamic expressions (which start with $) as this means we cannot use a JDBC PreparedStatement and so is a security hole. Groovy has worked around your mistake but the security hole is still there. The expression so far is: Select ?, ENTITLEMENT_VALUEKEY from ENTITLEMENT_VALUES

Can you advise on what is going on that this warning is clogging the logs?

Thank you!

5 REPLIES 5

RakeshMG
Saviynt Employee
Saviynt Employee

Could you please confirm, what is set for "accountnotinfileactionin your configuration.


​Regards

Rakesh M Goudar

VicyB
Regular Contributor
Regular Contributor

Hello @RakeshMG ,

I looked in the connection for this field but didn't find it. Could you point me to the proper place in SAV to look for this configuration? Thank you!

VicyB
Regular Contributor
Regular Contributor

Hello @RakeshMG ,

we searched for the accountnotinfileaction parameter more broadly and found it in the SAV documentation as parameter of a generic DB connection: https://docs.saviyntcloud.com/bundle/Database-v2022x/page/Content/Configuring-the-Integration-for-Im....

Interestingly, we don't have a generic DB connection in our SAV instance.

Based on the warning, we assume that SAV poses internal queries that include quotes. It is possible, that SAV can't handle the import of data fields whose data contain quotes? We checked the data we imported from S4, some fields actually do include quotes, e.g. some description fields. 

VicyB
Regular Contributor
Regular Contributor

Hello Saviynt-Team,

any advice on this topic?

Thanks!

VicyB
Regular Contributor
Regular Contributor

Hello everybody,

via SME we received the feedback that the warning doesn't have a critical impact (is not a "special" warning, just a standard groovy warning) and can be ignored 👍