In a Sourcing Event or in a Contract Line Items Document, what is the difference between System Global, Local and Global terms?

System Global

• The default terms made available by the system. Custom terms are not stored under System Global.

Global

• When a New Term is created and published from a Sourcing Event Template, the term is available across the site for use in all other templates, events and contract workspaces.
  • If UP-5078 is enabled, the same is true for Contract Workspace template's Line Items Document by selecting Make this term available globally at creation.
• Custom terms created from an external system Contract Line Item Template cannot be made available globally to any other templates.
  • Note: Global terms can be added to an external system Contract Line Item Template, but custom terms created directly from a particular external system remain exclusive to that template.
• Global terms are reportable.

Local

• New Terms created and published from a Contract Workspace template's Line Items Document, by default, will only be available to Contract Workspace's created from that template.
• Custom terms created from an external system Contract Line Item Template persist in the system as Local terms
  • Note: A Line Items Document added to a Contract Workspace template is different from an External System Contract Line Item Template. The former is relevant when the workspace is not associated to an external system, and the latter directly corresponds to the associated external system.
  • Predefined terms generate from the respective template's line item definition. If any of these terms are removed from your event or workspace, they'll get stored locally in your event or workspace.
• New Terms created ad hoc from a Sourcing Event or Contract Workspace, are local.
• Local terms are not reportable.

• Any term at workspace or event level inherits it's template's Local or Global designation.
  
  
• If an external system is associated to your project/workspace, the terms generate from the external system template rather than generating from the line items added to your project/workspace template.
  
  
• If you need a term and it already exists Globally, then add it to your line item rather than creating a new term with the same name.
  
  
• All terms are stored in the database with a uniquename:
  • Terms prefixed with GITA indicate that the term is Global
  • Terms prefixed with RITA are classified as Local
• Creating duplicates, rather than re-using the same Global term, can cause issues with formulas, problems when awarding to the CLID and overall loss of scale. You cannot toggle an existing term from Local to Global or vise versa.

Guided Sourcing > Guided Sourcing Event
Strategic Contracts
Strategic Sourcing