SQLServerException Occurs When Using ProcessRequirements + AddRequirement Attached Business Rules (ABR) On The Same Activity (Doc ID 2975032.1)

Last updated on OCTOBER 02, 2023

Applies to:

Symptoms

On : 11.3.1.9 version, Requirement

When attempting to use the ProcessRequirements ABR + AddRequirement ABR on the same Activity,
the following exception message is reported:

ERROR
-----------------------
Internal Exception: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'null'.
Error Code: 156
Call: SELECT AsRequirement.RequirementGuid,
  AsRequirement.RequirementDefinitionGuid
 FROM
  AsRequirement
  JOIN AsRequirementDefinition ON AsRequirement.RequirementDefinitionGuid=AsRequirementDefinition.RequirementDefinitionGuid
  JOIN AsRequirementPolicy ON AsRequirement.RequirementGuid=AsRequirementPolicy.RequirementGuid
WHERE
 AsRequirementPolicy.PolicyGuid=? AND AsRequirementDefinition.RequirementName=? AND AsRequirement.StatusCode NOT IN null
  bind => [9012762C-96AE-4ACF-898F-B70200F09FC8, Reversal Initiation]
Query: DataReadQuery(sql=" SELECT AsRequirement.RequirementGuid,
  AsRequirement.RequirementDefinitionGuid
 FROM
  AsRequirement
  JOIN AsRequirementDefinition ON AsRequirement.RequirementDefinitionGuid=AsRequirementDefinition.RequirementDefinitionGuid
  JOIN AsRequirementPolicy ON AsRequirement.RequirementGuid=AsRequirementPolicy.RequirementGuid
WHERE
 AsRequirementPolicy.PolicyGuid=? AND AsRequirementDefinition.RequirementName=? AND AsRequirement.StatusCode NOT IN null")
  at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:342)
  at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:700)
  at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:567)
  at org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:2105)
  at org.eclipse.persistence.sessions.server.ServerSession.executeCall(ServerSession.java:603)
  at org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:265)
  at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:275)
  at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:261)
  at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeSelectCall(DatasourceCallQueryMechanism.java:345)
  at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeSelect(DatasourceCallQueryMechanism.java:327)
  at org.eclipse.persistence.queries.DataReadQuery.executeNonCursor(DataReadQuery.java:199)
  at org.eclipse.persistence.queries.DataReadQuery.executeDatabaseQuery(DataReadQuery.java:154)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create an Activity that Adds a Requirement to a Policy using the AddRequirement ABR.
2. On the same Activity also have the ProcessRequirements ABR where you provide the RequirementName that you want it to process.
3. Attempt to this Activity.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.