Contract financial mapping
- Last UpdatedMay 21, 2024
- 4 minute read
Communication templates can be assigned to communication template reporting categories. Each of these has an associated contract financial mapping that uses AVEVA Contract Risk Management's workflow engine to update financial reporting categories depending on the state of that type of communication.
The mapping workflow can also determine the reporting category of any communication linked in process chains (see Linked communications).
When a new communication template reporting category is created, a default mapping is created for it, with all reporting categories set to Not Applicable.
Note New mappings are not created manually on this screen. They are created automatically when a new communication template reporting category is created as a lookup list value (see Lookup lists).
See Workflows for further general information about workflows and workflow templates.
Warning If the user assigned to the Contract Owner contract role for the communication's contract is disabled, the mapping workflow will not trigger.
Communication reporting categories
The following table shows the communication reporting categories which can be assigned in a contract financial mapping to communication state changes.
|
Type |
Example use |
|
Potential Contract Change |
Contractor to Company communications Not expenditure Status of Approved, Awaiting Agreement from Recipient or Agreed |
|
Pending Contract Change |
Company to Contractor communications Not expenditure Status of Draft or Awaiting Agreement from Recipient |
|
Approved Contract Change |
Company to Contractor communications Not expenditure Status of Agreed or Approved |
|
Potential Contract Expenditure |
Contractor to Company communications Expenditure Status of Approved, Awaiting Agreement from Recipient or Agreed |
|
Pending Contract Expenditure |
Company to Contractor communications Expenditure Status of Awaiting Agreement from Recipient |
|
Approved Contract Expenditure |
Company to Contractor communications Expenditure Status of Agreed or Approved |
|
Not to Exceed Contract Value |
Internal communications which affect the Not to Exceed Contract Value Not expenditure Status of Agreed or Approved |
View contract financial mappings
-
Open the navigation bar. If necessary, click the Manage tab.
-
Under Organisation Setup, click Contract Financial Mapping.
The Contract Financial Mapping page is displayed, listing the mappings configured in the system and indicating if they have validation errors.
Note If a mapping has a validation error (checked when the mapping is saved):
• Communications cannot be created from communication templates which use this mapping.
• The state cannot be changed for communications created with communication templates which use this mapping.
-
Click the
Edit Workflow Template icon for the mapping you want to view.
The Workflow Designer opens in a new window. Sign in to CONNECT if required.
-
Double-click the Mapping area.

-
Double-click any of the communication states to see the log text and new reporting category to which a communication is assigned when it is updated to that state.
See Workflow activity types for more information.
Update contract financial mappings
-
Open the navigation bar. If necessary, click the Manage tab.
-
Under Organisation Setup, click Contract Financial Mapping.
The Contract Financial Mapping page is displayed, listing the mappings configured in the system and indicating if they have validation errors.
Note If a mapping has a validation error (checked when the mapping is saved):
• Communications cannot be created from communication templates which use this mapping.
• The state cannot be changed for communications created with communication templates which use this mapping.
-
Click the
Edit Workflow Template icon for the mapping you want to update.
The Workflow Designer opens in a new window. Sign in to CONNECT if required.
-
The mapping is displayed as editable.
If necessary, double-click the Mapping area.

-
Double-click any of the communication states to edit the workflow. You can edit the log text and the new reporting category to which a communication is assigned when it is updated to that state.
See Workflow activity types for more information.
Tips
-
Field values must be valid Visual Basic (VB) expressions.
-
Text must be enclosed in quotation marks, e.g. "Notification"
-
Numeric values should not be enclosed in double quotation marks, e.g. 10
-
You can include variable names in field values. Click Variables at the bottom of the screen to see a list, and type the name of the appropriate variable into the field; following the name, type a . to display a list of attributes. Double-click the attribute on the list to add it to the VB expression in the field, e.g. Contract.Name
-
Use & to concatenate separate strings of text and variable names, e.g. "Notification for " & Contract.Name
-
Use Environment.NewLine to include a paragraph break in a block of text, e.g. the Review Guidelines field for a Review activity.
-
Custom fields can be included as:
-
Contract.CustomFields.Item("Custom Field 1").FieldType
-
Communication.CustomFields.Item("Custom Field 1").FieldType
where Custom Field 1 is the name of the custom field and FieldType is the type of field. Possible field types are:
-
Text - Small Text Field, Full Width Text Field, Comments Box
-
Number - Number
-
Date - Date
-
DateAndTime - Date and Time
-
YesOrNo - Yes or No
-
PickListSelectedOption - the option from a PickList
-
Currency - Currency
-