High- Level Specification

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.

Insert the flowchart and fill in the steps

Assumptions

• Contract values and amendment contract value are maintained in Euro. The Total Contract Value will be done in Local currency
• 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 Contract Value in Euro and Amendment Value in Euro

Language Requirements

NA

Special Requirements

NA

Design Rationale

Functional Requirements

• Automated TCV Calculation:

  • On agreement creation or update, TCV is set to the contract value.
  • On amendment creation, the amendment value is added to the parent agreement’s TCV.
  • On supersede event, TCV is recalculated as the sum of the original contract value and all amendments.

• UI and Workflow Integration:

  • TCV field is updated on “Next” or “Save” actions in the UI.
  • DOA workflow references the TCV field for approval routing.

• Validation:

  • Contract and amendment values must be in the same currency.
  • System prevents saving if required values are blank or currencies mismatch.

• Audit and Logging:

  • All changes to TCV and Previous TCV are logged for audit purposes.

• Error Handling:

  • User is notified if values are missing or currencies do not match.

Proposed Technology to Use

Typically, an enhancement will be based on an existing SAP BADI / user exit. If this is the case, please provide the proposed details of the BADI / user exit.

Data Source Considerations

Not Applicable

Data Validation Considerations

Not Applicable

Custom Tables

Not Applicable

Master Data

Not Applicable

Configuration Table

Selection Screen Enhancement

Not Applicable

Processing Logic

• Agreement Creation/Update

  • When a user creates or updates an agreement, the system captures the Contract Value (in Euro or local currency).
  • On clicking “Next” or “Save,” the system copies the Contract Value to the TCV field.
  • If the agreement is being updated, the TCV field is overwritten with the new Contract Value.

• Amendment Creation

  • When a user creates an amendment, the system requires the Amendment Value and ensures the currency matches the parent agreement.
  • If the currency does not match, the system throws a validation error and prevents the amendment from being saved.

• Supersede Event (Amendment Activation)

  • When an amendment is activated (supersede event), a custom event task is triggered.
  • The system retrieves the parent agreement’s TCV and all related amendment values.
  • The system calculates the new TCV as:
    $$\text{TCV}=\text{Original Contract Value}+\sum (\text{All Amendment Values})$$
  • The Previous TCV field is updated with the last known TCV before recalculation.
  • The TCV field is updated with the new cumulative value.

• DOA Workflow Routing

  • When the agreement (with or without amendments) is submitted for approval, the DOA workflow references the updated TCV field.
  • The workflow determines the correct approver based on the latest TCV and the configured approval thresholds.

• Validation and Error Handling

  • The system validates that all required fields (Contract Value, Amendment Value) are populated.
  • If any required value is missing or currencies do not match, the system prevents saving and displays an appropriate error message.
  • All changes to TCV and Previous TCV are logged in the audit trail for traceability.

• Audit Logging

  • Every update to TCV and Previous TCV, as well as amendment creation and supersede events, are recorded in the audit log for compliance and review.

Volumetrics

Not Applicable

Performance Considerations

Not Applicable

Error Handling

Not Applicable

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

Test Considerations/Dependencies

Not Applicable

Other Information

Not Applicable

Development Details

Package

Enhancement Implementation

Other Development Objects

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.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log