High- Level Specification
| Parameter | Value |
|---|---|
| Application System | Icertis |
| Business Process Reference | Agreement Approval |
Functional Overview
This enhancement enables automated calculation and tracking of the Total Contract Value (TCV) for agreements in Icertis, including all amendments, to support DOA approval workflows. The TCV is defined as the sum of the original contract value and the values of all amendments. The system will ensure that DOA approvals are always based on the latest TCV, even as amendments are added.
Scope and Objectives
Scope:
- Automate the calculation of TCV as:
TCV = Original Contract Value + All Amendment Values - Ensure DOA approval routing is based on TCV, not just the original contract value.
- Support both agreement creation/update and amendment (supersede) events.
Objectives:
- Eliminate manual calculation or entry of TCV by users.
- Ensure compliance with DOA policies for both new agreements and amendments.
Step | Description | Comment |
|---|---|---|
| 1 | User creates or updates an Agreement | Contract Value in Euro is entered/updated |
| 2 | On "Next" (UI) or Save, system copies Contract Value to TCV | UI-level customization |
| 3 | User creates an Amendment | Amendment Value is entered |
| 4 | Custom Task on Supersede Event triggers | Event Custom Task |
| 5 | System sums Parent Agreement TCV + all Amendment Values | Automated calculation |
| 6 | System updates Agreement’s TCV field | TCV reflects all amendments |
| 7 | DOA workflow uses updated TCV for approval routing | Ensures correct approval level |
Assumptions
- All contract values and amendment values are maintained in Euro.
- Amendments are always linked to their parent agreement.
- The custom fields for TCV and Previous TCV exist and are available for use.
- The system can trigger custom tasks on both UI actions and workflow events.
- No changes are required to the standard DOA configuration, only to the value used for routing.
Dependencies
- Data migration for existing agreements/amendments may be required.
Security, Integrity and Controls
NA
Configuration Requirements
- Custom fields for TCV and Previous TCV must be configured in Icertis.
- Event Custom Task must be configured for the Supersede Event.
- UI customization on the "Next" button for agreement creation/update.
- DOA workflow must reference the TCV field for approval routing.
Language Requirements
NA
Special Requirements
NA
Design Rationale
Functional Requirements
Proposed Technology to Use
Data Source Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Data Validation Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
Master Data
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
| Field Name | Description | Select: | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
Processing Logic
Volumetrics
Performance Considerations
Error Handling
Testing
How to Test
This section outlines the test scenarios, conditions, and expected results to validate the enhancement for Total Contract Value (TCV) calculation and DOA routing.
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
| 1 | Agreement Creation - Create a new agreement with a Contract Value in local currency. Click “Next” or Save. | TCV field is populated with the same value as Contract Value. |
| 2 | Agreement Update - Update the Contract Value of an existing agreement. Click “Next” or Save. | TCV field is updated to reflect the new Contract Value. |
| 3 | Amendment Creation - Create an amendment linked to an existing agreement. Enter Amendment Value. | Amendment is created successfully. |
| 4 | Supersede Event Trigger - Supersede the agreement via amendment. Trigger Event Custom Task. | Previous TCV field is updated with the last known TCV. |
| 5 | TCV Recalculation - After supersede, verify that TCV = Original Contract Value + All Amendment Values. | TCV field reflects the correct cumulative value. |
| 6 | DOA Routing - Submit agreement for approval. | DOA workflow uses updated TCV for routing. Correct approver is selected based on TCV thresholds. |
| 7 | Currency Validation - Create agreement in local currency (e.g., INR, USD). | TCV calculation uses local currency. No conversion to Euro. |
| 8 | Amendment Currency Mismatch - Create amendment with a different currency than parent agreement. | System throws validation error. Amendment cannot proceed. |
| 9 | Audit Log Verification - Perform agreement update and amendment creation. | Audit log captures changes to TCV and Previous TCV. |
| 10 | Error Handling - Leave Contract Value or Amendment Value blank. | System prevents save and displays appropriate error message. |
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Enhancement Implementation
| Enhancement Type | Standard Definition Name | Custom Implementation Name | Design Rationale Reference |
|---|---|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
Appendix
Custom Authorization Group Naming Convention
This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.
ABAP | ZFI | ZMM | ZPS | ZCO | ZSD | ZBC | ZFI | ZCA |
|---|---|---|---|---|---|---|---|---|
| TABLES | ZFIT | ZMMT | ZPST | ZCOT | ZSDT | ZBCT | ZFIT | ZCAT |