You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Status

  Approved

Owner
Stakeholders
Jira Request ID

ERP-2343 - Getting issue details... STATUS

Jira Development ID

ERP-2397 - Getting issue details... STATUS

High- Level Specification

ParameterValue
Application SystemSAP ERP (PF2) & SAP ERP (WP2)
Business Process Reference03.04.04.01. Manage Outline Agreements (R2)

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 (ERP-260 Integration Process - Icertis to SAP ECC Contract Data Replication & ERP-261 System Interface - Icertis Contract Data Replication to SAP ECC). This custom table supports the main objectives:

  1. To enable a relationship between the Icertis Agreement Code and the SAP outline agreement number.
  2. To report where there are inconsistencies in the data between the two systems.

This enhancement is to create a program in SAP ECC which makes new entries in the custom table ZMM_ICMCONTRACT for legacy contracts which have been loaded into Icertis Contract Management via their legacy load tool. This method does not generate event messages to CPI in the same way that the execution of a new contract manually does. The program would be a batch input process based on the contents of a spreadsheet to make the table entries.

Once the legacy contract field values are loaded in the table in SAP, all other integration from Icertis is managed via the existing developments referenced above. This includes the execution of amendments, renewals, terminations and tracking field updates.

Scope and Objectives

The purpose of this program is to ensure that all the relevant legacy system contracts which are loaded into Icertis are available in the table in both SAP ECC systems. This ensures that:

  1. Legacy contracts can be selected for assignment on the outline agreement headers (handled by ERP-259 Enhancement for Storage of Icertis ID on OA Header)
  2. Reporting of Icertis contracts in BW and their associations to outline agreements includes the legacy migrated contracts and new ones  ERP-504 - Getting issue details... STATUS

Primarily the purpose of the program is for the load of legacy contracts where currently the expected event messages cannot be triggered to CPI to enable the operation of ERP-260 Integration Process - Icertis to SAP ECC Contract Data Replication & ERP-261 System Interface - Icertis Contract Data Replication to SAP ECC in their current form.

Potentially this program may also provide a backup option to load multiple contract records into the table in the event of a failure in the automated interfaces from Icertis. If an event is not generated, or there is an inability to process the message in CPI (eg. Incorrect tenant id), there is no method in Icertis to resend or to retrigger a new message, nor an ability to update the message in CPI. Manual entry into the table in SAP is the only option. In the case of multiple records, this program may provide a fallback option depending on the circumstances, the volume, the ability to identify and the nature of the failures. 


Process Flow Diagram


Step

Description

Comment











Assumptions

Dependencies

Security, Integrity and Controls


Configuration Requirements

Language Requirements

Special Requirements


Design Rationale

Functional Requirements

Proposed Technology to Use

Data Source Considerations

TableField NameComments/Calculation/Field Manipulation











Data Validation Considerations

TableField NameComments/Calculation/Field Manipulation













Custom Tables

Master Data

FieldDescriptionData Type/LengthValidation rule/ Value Help









Configuration Table

FieldDescriptionData Type/LengthValidation rule/ Value Help








Selection Screen Enhancement

Field NameDescription

Select:

Data Type/LengthDefault Value/ Validation rule/ Value HelpSelection Logic













Processing Logic



Volumetrics


Performance Considerations



Error Handling


Testing

How to Test

Test Conditions and Expected Results

IDConditionExpected Result










Test Considerations/Dependencies


Other Information


Development Details

Package

Package NameParent Package




Enhancement Implementation

Enhancement TypeStandard Definition NameCustom Implementation NameDesign Rationale Reference









Other Development Objects

Appendix

See also


No files shared here yet.

Change log

Version Published Changed By Comment
CURRENT (v. 4) Mar 16, 2026 11:27 ROWLINSON-ext, Kerry
v. 35 Mar 12, 2026 09:00 TORRES-ext, Benedict
v. 34 Mar 12, 2026 08:59 TORRES-ext, Benedict
v. 33 Mar 12, 2026 05:25 ROWLINSON-ext, Kerry
v. 32 Mar 10, 2026 13:33 ROWLINSON-ext, Kerry
v. 31 Mar 10, 2026 12:51 ROWLINSON-ext, Kerry
v. 30 Mar 10, 2026 12:49 ROWLINSON-ext, Kerry
v. 29 Mar 10, 2026 11:47 ROWLINSON-ext, Kerry
v. 28 Mar 10, 2026 11:06 ROWLINSON-ext, Kerry
v. 27 Mar 10, 2026 10:49 ROWLINSON-ext, Kerry

Go to Page History

  • No labels