Oracle Contracts supports the use of business variables (tokens) in clause text. During authoring, these tokens will be substituted with values from the business document.
Oracle Contracts supports the following types of variables:
Note: Only system and user-defined variables are available for use in Contract Expert.
This section also includes the following topics:
These represent contract document attributes such as payment terms, customer name, and supplier name. You can embed system variables in the clause text, which will be automatically substituted with values when the clause is used in a contract. System variables are also available to be used in defining Contract Expert rules.
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.
Note: Table variables are only supported only for Sell intent clauses.
Oracle Contracts supports the following seeded table variables:
Lines
Modifiers
Price Lists
Attach Deliverable type variables to clause text to display deliverable information as part of contract terms.
Note: Deliverable variables are only supported for Buy intent clauses.
Oracle Contracts supports the following seeded deliverable variables:
Supplier Contractual Deliverable
Buyer Contractual Deliverable
All Contractual Deliverables
Supplier Negotiation Deliverables
All Negotiation Deliverables
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. For more information, see 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.
The application can only identify a variable if the variable is enclosed within the following special characters:
[@VARIABLE_NAME@]
For instance, the Payment Terms system variable needs to be captured with the following tags:
[@Payment Terms@]
When you define value sets in the FND value sets for variables and you set the Validation Type to Independent, you must set the List Type to:
Poplist: If you want to define less than 200 values for that Value Set in FND.
List of Values: If you want to provide more than 200 values for that Value Set in FND.
Multi Row variables are defined based on the user defined attributes.
For information about Defining Multi Row Variables, see Contract Terms Library Administration chapter of the Oracle Contracts Implementation and Administration Guide.