High- Level Specification

Functional Overview

Icertis Contract Intelligence is the contract management and authoring application for Syensqo's purchase contracts. Purchase orders are created in SAP ECC with reference to purchase contracts (outline agreements). The key information from the legal contract which is relevant for procurement forms the basis of the purchase contract or outline agreement in SAP ECC.  The integration between Icertis and SAP ECC for release 2 is a custom table in SAP ECC to hold key header field content from Icertis. This custom table supports the main objectives:

1. To maintain the relationship between the Icertis Contract ID and the SAP outline agreement number.
2. To report where there are inconsistencies in the data between the two systems.
3. To enable users to easily update the Icertis Contract ID on the SAP outline agreement.

This enhancement is to provide a convenient method for the users to update the SAP outline agreements with their corresponding Icertis Agreement Code numbers.

Scope and Objectives

For one purchase contract in Icertis, there can be multiple outline agreements created in SAP ECC (one per relevant purchasing organization). The Icertis Agreement Code is to be entered on the header of each outline agreement. This can be done during the creation of each one, or via ME32K Change Outline Agreement after creation and one by one. This enhancement allows for all the outline agreements associated to the same Icertis Contract to be updated at the same time. The program will also allow the mass update of the ICM Agreement Codes on multiple outline agreements via the batch processing of a spreadsheet file.

• Provide a correction program that would allow users to easily update the Icertis Agreement Code on one or more associated outline agreements.
  
  
• Provide the ability to update a text element on the outline agreement header for a commentary from the user about the anomaly. A drop down selection of possible values will be available for the user to classify the circumstance/reason for a missing Icertis ID.
  
  
• The text of the selected option will be held in a newly configured header text for the outline agreements.
  
  
• The purpose is to enable the ‘categorized’ outline agreements to be removed from the custom report to assist the users managing cleansing activities.
  
  

For the correction of other key data in ECC which is not aligned with Icertis, the existing upload programs for change outline agreement can be used, or the contract can be changed directly in transaction ME32K.

Assumptions

Dependencies

Security, Integrity and Controls

Configuration Requirements

Language Requirements

Special Requirements

Design Rationale

Functional Requirements

Proposed Technology to Use

Data Source Considerations

Data Validation Considerations

Custom Tables

Master Data

Configuration Table

Selection Screen Enhancement

Processing Logic

Volumetrics

Performance Considerations

Error Handling

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

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

Change log