Hi Laura,

Suggest you Google copy and paste with chrome…. Many replies there.

P.S. A little care with Sites….  
  Be sure to evaluate its operation in your DEV environment – and backup the DB before you start.  Once enabled you can’t turn Sites off.
  Also, if you’re using Oracle EBS, the data from “Sites” comes through as “ORG”s  With Master BOM and extraction to the ORG.
     So, Oracle requires additional configuration as well.
 
The BOM for your assembly is created as one Giant BOM.  Each item with unique Site requirement will seen in in-line after the master item.
    Only the single unique item for a single site is entered on the BOM – otherwise the master item is used. If one site in unique, the other Sites use the master item
   Also, for ease of use you can select to view the Master BOM that shows all sites, or, can select a single Site to view it’s individual BOM.

These are two separate but joined configuration settings.  In Workflow settings the Manual Next Status for an example would be used if for some reason you would allow the CO to move from Submit to Release – that would be a manual next status.  Then you would need a Change Status privilege with the settings in From and To.  You would need both to enable the action.

In your settings Release comes after CCB so that action is preset – but the user still needs, and has, a privilege to Change Status from CCB to Release.  If you were to disable that privilege you would not be able to move the CO.

Also, to note, Change Analyst typically have an Override privilege to would allow that role to move the CO as needed (also without approvals) so, be sure of which roloe you are using to validate the configuration settings.

Hi Gykumar,

The Workflow assignments work well if the $approver is more constant.

Or, you could give Add Reviewer / Remove Reviewer permission to their Roles and they can assign them on an ad/hoc basis.