My Oracle Support Banner

Upgrade Siebel Database From Previous IP 2017 to latest Siebel CRM 18.x/19.x/20.x/21.x Lead To Workflows Definition Corrupted And Incorrect Version Compiled Into S_RR_WORFLOW (Doc ID 2764631.1)

Last updated on FEBRUARY 28, 2022

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.


After executed Siebel Database Upgrade from previous Innovation Pack  2017 version to later IP 2017 version such as Siebel CRM 20.x lead to standard workflow definition corrupted on Siebel Repository and corrupted version compiled on S_RR_WORKFLOW since a workflow must be unique on a given workspace versions. For example you can have multiple records in S_RR_WORKFLOW for a given workflow, but it will be one record per workspaces version. Multiple workflow versions are NOT supported in IP 2017 and higher for the same workspace version.

In Siebel CRM 20.6 and previous as the legacy Runtime Repository table for workflow S_WFA_DPLOY_DEF is used, only the Design Repository is affected, but the workflow still got executed since the legacy Runtime Repository is not touched by the Siebel Database Upgrade process.

In Siebel CRM 20.7 and later Workflow in Workpspaces for Runtime Repository was made available and now every time a workflow is delivered to a MAIN or Integration workspaces, a workflow record is created in S_RR_WORKFLOW for that specific workspaces version.  This way each workspace can work with his own "version" of the workflow indirectly by workspace version. So the Upgrade Merge is in charge on Siebel CRM 20.7 to compile the object into the S_RR_xxx tables as any other Siebel Repository object.

The behavior affects standard Siebel workflows that have been modified in pre IP 2017 version, for example standard workflow "ABO Bulk Request - All Exclusive Process Action Sub-Process Workflow" where multiple new version have been created in pre IP 2017.

The behavior can be reproduce if before the Upgrade the required steps to clean up multiple workflow versions from the Repository prior to upgrade has not been done, keep only the current workflow version been executed on design repository table (S_WFR_PROC) with Inactive flag unchecked.  This is describe on Bookshelf > Database Upgrade Guide > Chatper 9 Preparing Siebel Application Data for Upgrade > Preparing Siebel Workflow Processes for Upgrade > To prepare workflow processes for upgrade where it says:

If there are multiple versions of a workflow process, as in the case of customer modified workflow processes for example, then you must deactivate all versions of the workflow process except the most recent version with a Status of Completed in Siebel Tools.

In Siebel Tools deactivate means set the workflow Inactive flag to checked (S_WFR_PROC column INACTIVE_FLG='Y').

Customer who failed to set Inactive = checked for old workflow versions prior to Upgrade Siebel Database may observed that some standard Siebel Workflow end up with multiple records in S_WFA_DPLOY_DEF table with Status = Completed where the Version 0 has no workflow steps.





To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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