Oracle Contracts supports the use of business variables (tokens) in both clauses and Contract Expert rules. During authoring, values from the business document replace the variables. Oracle Contracts supports the following types of variables:
System-defined variables: Represent contract document attributes, such as payment terms, customer name, and supplier name. You can embed system variables in the clause text, which will automatically be substituted with values when the clause is used in a contract. System variables are also available to be used in defining Contract Expert rules.
Table variables: Attach Table type variables to clause text to display product and pricing information as part of contract terms. The actual products and prices are sourced from the business document during contract authoring. Oracle Sales Contracts supports the following seeded table variables:
Lines
Modifiers
Price Lists
User-defined variables: User-defined variables are tokens that you define over and above the system variables. Users must provide values for these variables as part of the contract authoring process. You can define variables that are sourced or derived from contract data. User-defined variables can be used in clause text or for Contract Expert rules. You can indicate the variable source as:
Manual: If you set the variable source to Manual, users must provide values for the variable as part of the contract authoring process.
PL/SQL Procedure: If the variable source is set to PL/SQL Procedure, the variable value is sourced or derived from the contract data.
Variable Identification
The application can identify a variable only if the variable is enclosed within the following special characters:
[@VARIABLE_NAME@]
For instance, the Payment Terms system variable must be captured with the following tags:
[@Payment Terms@]
The Managing Variables section covers the following topics: