| Status | Approved |
|---|---|
| Owner | ROWLINSON-ext, Kerry |
| Stakeholders | |
| Jira Request ID | ERP-228 - Getting issue details... STATUS |
| Jira Development ID | ERP-260 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System (Source) | Icertis Contract Intelligence |
| Application System ( Target) | SAP ERP (PF2) & SAP ERP (WP2) |
| Business Process Reference | 03.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 S/4 HANA 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 S/4 HANA. For release 4, the integration between Icertis and S/4 HANA will be more complete and automated. However, for release 2 the option for a 'light' integration was decided due to the limitations of the two SAP ECC systems and in particular the substantial existing custom logic which needed to remain unaffected by any changes.
The 'light' integration consists of three main parts:
- Maintaining the relationship between the Icertis Contract ID and the SAP outline agreement number.
- The ability to report where there are inconsistencies in the data between the two systems.
- The ability for users to update the Icertis Contract ID on the SAP outline agreement.
When an agreement in Icertis is executed, an event in Icertis is initiated and the stream event payload is received to CPI (Cloud Platform Integration). CPI then uses key fields from that payload to make a call to Icertis to retrieve the complete contract record payload from Icertis. An additional call is made for some agreement types to find associations to a master agreement. A subset of the total fields provided are then mapped to fields in a custom table in both SAP ECC systems (PF2 and WP2) where the data is stored.
Events for Amendment Execution, Renewal and Termination require development within Icertis in order to be initiated and for a custom event job to send the default payload to CPI.
Scope and Objectives
The objective of the interface for release 2 is to provide a functional relationship between the Icertis Contract and the SAP outline agreement to enable consistency of the data to be reported and therefore maintained. The business users will manually create and change the outline agreements as a result of contract executions, amendments, renewals and contract terminations.
The entry and update of the contract data in the custom table enables:
- Validation that the correct Icertis Contract ID is entered on the outline agreement.
- Reporting any key header data from the outline agreement which is not aligned with the corresponding data in Icertis.
- Enables identification of orphan outline agreements which do not have an Icertis Contract ID assigned.
- Enables a complete reporting view of all the Icertis types of purchase contracts, their hierarchical structure along with their association to the SAP outline agreement (if relevant for assignment).
Without this integration there is no place where the hierarchical structure of Icertis Master Agreements & associated Sub Agreements, Standalone Agreements, and Non-Disclosure Agreements can be viewed with their association to the outline agreements in SAP ECC. It provides a mechanism to ensure the purchase contract content common to both systems remains aligned despite the reliance on manual entry by business users in SAP.
The linking of the documents in this way acts as a starting point for data enrichment for release 4, allowing the identification of outline agreements which do not have a legal purchase contract. The data will be the foundation for the conversion of open outline agreements in release 4.
Process Flow Diagram
Step | Description | System | Comment |
|---|---|---|---|
1 | A purchase contract is executed in Icertis | Icertis | A legal purchase contract is executed in Icertis |
2 | New entry in custom table for the Icertis Contract | SAP ECC | Integration automatically creates the Icertis Contract record in custom table in both SAP ECC systems (WP2 & PF2) with the Tenant ID, Agreement Type, System ID, Icertis Agreement Code and the relevant data fields from the contract header. |
3 | An amendment to a contract in Icertis is executed | Icertis | An amendment for an existing contract is executed in Icertis. |
4 | Change entry in custom table for the parent contract of the amendment | SAP ECC | The existing entry in the table for the parent agreement of the amendment is located and the relevant fields in the table are overwritten with the values provided in the amendment. |
5 | A renewal of an existing contract in Icertis is made. | Icertis | An existing purchase contract in Icertis is renewed which updates the overall value and the validity end date. |
6 | The entry in the custom table for the contract is updated. | SAP ECC | The existing entry in the table for the purchase contract is updated to reflect the changes to the overall value and the validity end date. |
7 | An existing purchase contract in Icertis subject to automatic renewal is renewed. | Icertis | An existing purchase contract in Icertis is renewed automatically when the renewal date comes due which updates the validity end date. |
8 | The entry in the custom table for the contract is updated. | SAP ECC | The existing entry in the table for the purchase contract is updated to reflect the changes to the validity end date. |
9 | An existing purchase contract in Icertis is terminated. | Icertis | An existing purchase contract in Icertis is terminated which updates the validity end date and the status in Icertis. |
10 | The entry in the custom table for the contract is updated. | SAP ECC | The existing entry in the table for the purchase contract is updated to reflect the changes to the validity end date. |
11 |
Assumptions
There are no specific assumptions identified.
Dependencies
The following two enhancement requests in Icertis are required to fully support the integration of the purchase contracts to the custom table in SAP ECC.
ERP-203 : Icertis: Total Contract Value Calculation with Multiple Amendments
In order to correctly fill the target value ERP-203 enhancement is being made in Icertis to consolidate the total value of the amendments. In addition to ensure the currency of the contract is passed to SAP, the logic is being adjusted so that it uses the local agreed currency instead of defaulting to EURO.
This is required in order for the target value field for the contract in the custom table to be tested in all scenarios.
ERP-508: Enhancement for Icertis Event Streams
Configure a custom event job to send the default payload (equal to the stream event payload) to SAP CPI from Icertis. This enhancement will support the following event types:
Amendment Executed
Renewal
Termination
This development in Icertis is required in order for integration to be tested for event types other than Agreement Execution.
Security, Integrity and Controls
There are no specific security, integrity or controls required for the processing of the interface.
Configuration Requirements
There are no specific configuration requirements for this interface.
Special Requirements
As the interface is one-way from Icertis to SAP ECC there are no special requirements, security or authentication considerations to take into account. Other custom tables in SAP ECC do not have any authorization controls apart from transaction code. This custom table does not require a transaction as it is not subject to manual maintenance.
Design Rationale
The diagram below shows the data flow between Icertis Contract Management and SAP ECC.
The process is that events in Icertis transmit a record to CPI with ContractTypeName, SYSID and ActionName. With that information CPI makes two calls to Icertis to retrieve the agreement data and any associating instances (which exist between Sub Agreements and their Master Agreements).
CPI makes the necessary translations and ABAP logic then takes the field information from CPI to populate into the same custom table in each of the SAP ECC systems.
The availability of the key Icertis purchase contract information within the SAP ECC systems then makes it possible to report outline agreements associated to Icertis contracts and to compare key data objects.
Below is an example of the out-of-the-box payload sent from Icertis to CPI on the events:
Below is an example of the type of file received for the call to Icertis to retrieve the agreement information using the Contract Type Name and the System ID. The returned fields shown are just an example and are dependent on the configuration of the metadata in Icertis for Syensqo.
Data Structure
Source Structure
The following fields from Icertis are required for the content of the custom table in SAP, or to support the interface process.
| Field | Field Label | Description | Length/Format |
|---|---|---|---|
| ICM Tenant ID | Tenant ID | **Confirm with Dhiraj format and length and how we define - specific client for purchasing contracts; Dhiraj to check with Wytse; and whether it belongs in the source structure here Wytse: For identifying the tenant, we can use either the CNAME or the URL. Regarding the initial trigger from Icertis, I believe there’s a field highlighted in the payload that helps with this, but I’ll double-check and get back to you to confirm.*** | TBA |
| ActionName | n/a | The ActionName is provided in the payload from the events which are sent to CPI. The content denotes whether the event is a creation, a renewal, a termination or an amendment. Termination of a contract "Terminated" Renewal of a contract "Renewed" Amendment executing "AmendmentExecuted" Agreement creation "Executed" | n/a |
| CONTRACTTYPENAME | Icertis Agreement Type | Possible values are: (supporting agreement is the NDA; no amendments possible for Baseline Agreements) Termination Agreements - we will receive notification to CPI of 'Terminated' for the original contract (Master/Sub etc.); call for the original contract will have termination date for the original contract. CONTRACTTYPENAME not in metadata (only as a column)** | 224 CHAR |
| NAME | Agreement Name | Still to be determined how the NAME field is going to be used but it is expected to be descriptive and therefore a useful addition to the report to help users identify what the contract is for (eg. where there are multiple for a supplier and our report will have no line items for context. Formatting rules and length outstanding; not in metadata sheet | 1000 CHAR |
| ICMAGREEMENTCODE | Agreement Code | The naming convention for Icertis Agreements is defined; characters describe the type and the fact it is amendment may be in the structure of the code. Amit to provide the complete updated list of numbering so we can determine the maximum field length required to display on the screen** | 224 CHAR |
| SYSID | System ID | Along with CONTRACTTYPENAME, SYSID is the key with which CPI makes the call to Icertis to retrieve the complete header contract field details. This is important to have from Icertis in addition to the agreement code - used in backend table mapping in Icertis and is important to keep the relationship to the agreement code. Note: in the calls to Icertis, the field is labelled {agreementId} double check with Wytse that tech field name is agreementId*** | 36 CHAR |
| PARENTSYSID | Parent System ID | An amendment in Icertis is assigned a new ICMAGREEMENTCODE and a new SYSID. But the original agreement code that the amendment is for is in the PARENT CONTRACT field, and the original system id is in the PARENT SYS ID field. Not in the metadata to confirm*** | 36 CHAR |
| PARENTCONTRACT | Parent Contract | An amendment in Icertis is assigned a new ICMAGREEMENTCODE and a new SYSID. But the original agreement code that the amendment is for is in the PARENT CONTRACT field, and the original system id is in the PARENT SYS ID field. So the format of the Parent Contract field will be the format of the original agreement code field: Not in the metadata to confirm field | 224 CHAR |
| ICMSUPPLIERSAPID | Supplier's Account Number | The supplier numbers will be the same as the ECC supplier numbers. NDA's may not necessarily have a supplier id as it is possible to define an NDA for a bidder supplier only. **Multi-party contracts are under discussion which could mean two suppliers on one contract; relationship between is unclear and would not be possible to represent this on a single outline agreement unless there was a partner function defined in SAP. | 224 CHAR |
| ICMEFFECTIVEDATE | Effective Date | Start date of the agreement "YYYY-MM-DDTHH:MM:SS" | DATE |
| ICMEXPIRY | Expiry | End date of the agreement "YYYY-MM-DDTHH:MM:SS" | DATE |
| ICMTOTALCONTRACTVALUE | Target Value for Header Area per Distribution | It needs to be the total value of the contract (in ECC it is target value at header level) | INT(15 including 2 decimals) |
| ICMCURRENCY | Currency Key | Confirmed the currency codes in Icertis are aligned to SAP codes | 5 CHAR |
| ICMLEGALENTITYCODE | Syensqo Legal Entity Code | Organizational data - company code, purchasing group, purchasing org are being aligned in Icertis to ECC - it is the 4 char code for company code which matches SAP | 1000 CHAR |
ICMPURCHASEGROUPCODE | Purchasing Group | Organizational data - company code, purchasing group, purchasing org are being aligned in Icertis to ECC - it is the 3 char code for purchasing group which matches SAP | 1000 CHAR |
| ICMPURCHASINGORGCODE | Purchasing Org | Organizational data - company code, purchasing group, purchasing org are being aligned in Icertis to ECC- it is the 4 char code for purchasing organization which matches SAP. Script attribute, not visible to the user as they select based on the description. Single value only for each agreement. | 1000 CHAR |
| ICMREGION | Region | Icertis has values for each region which will be useful for the consolidation report to enable filtering of the Icertis Z table records by region. Possible values are: Check on this with Amit - can hold multiple values for a contract - we only have one field, not required? TBA | 4 CHAR |
| ICMPRIMARYOWNERNAME | Contract Owner | Use for filtering in the report on Z table so owners can find their own to work on First name, last name and email id in one field | 224 CHAR |
| ICMINCOTERMCODE | Incoterms | Incoterms are being aligned to correspond between Icertis and ECC Check technical name - meta data has ICMINCOTERMS | 224 CHAR |
| ICMPAYMENTTERMSCODE | Payment Terms | Payment terms are being aligned to correspond between Icertis and ECC This is the 4 char code that matches to SAP's codes in ECC Check technical name - metadata has ICMPAYMENTTERMS | 224 CHAR |
| ICMTERMINATIONDATE | Termination Date | When a termination message is received, the expiry date field remains same in ICertis but the termination date will have to become the expiry date Check technical name: ICMTerminationNoticedate TBA - confirm with Amit | DATE |
Target Structure
The following fields will be used to provide the required information for this interface.
Note: Although some of the Icertis fields correspond directly to fields in SAP, it is not possible to use these fields for validation due to the two separate SAP ECC systems. The intention is to have the same content filled in the custom table in both systems, regardless of whether the company code, purchasing organization, supplier etc. are defined in that system. All fields therefore have to be text-based fields.
Field labels are to correspond with the Icertis field labels.
Apart from the fields Icertis Agreement Type and System ID which are defined to be the key for the table and will therefore be (i) available for all events (ii) considered mandatory, all other fields are optional entry in the custom table.
Parent System ID and Parent Contract are not relevant to store in the custom table. The situation where these fields are filled from Icertis is when the Agreement Type is an amendment. These will only be used in the middleware to determine which entry in the custom table requires updating.
Icertis Amendments will not be stored in the custom table. Amendment events received will make the call to Icertis to obtain the amendment contract data, but the update of the table entries will the values retrieved will be made for the Parent Contract and Parent System ID.
The key of the table will be Tenant ID, Icertis Agreement Type and System ID and Agreement Code which will form a unique record. The two fields used for the calls to Icertis, are Agreement Type and System ID which form a unique record in Icertis.
Note: For clarity, the field System ID is not a 'system identifier', it is a unique 36 char code which is held in Icertis as a unique code for a contract id. This is not the contract id which the users see, but it is the code that represents the contract and it will need to be stored in SAP ECC.
| Field | Field Label | Description | Length/Format |
|---|---|---|---|
| Z* | Tenant ID | Tenant ID to identify the Icertis system the record has come from | TBA |
| Z* | Icertis Agreement Type | Possible values are: ICMMasterAgreement ICMSupportingAgreement ICMSubAgreement ICMStandaloneAgreement ICMBaselineAgreement ICMMasterAgreementAmendment ICMSupportingAgreementAmendment ICMSubAgreementAmendment ICMStandaloneAgreementAmendment (supporting agreement is the NDA; no amendments possible for Baseline Agreements) | 224 CHAR |
| Z* | Agreement Code | The agreement code is the contract number in Icertis and is preceded by the agreement type. Example: ICMMasterAgreement_nnnnnnnnnn This value from Icertis will be stored on the header of the outline agreement in SAP ECC. | 224 CHAR |
| Z* | System ID | Along with CONTRACTTYPENAME, SYSID is the key with which CPI makes the call to Icertis to retrieve the complete header contract field details. Example: 1343f2e0-9386-4fa7-aa5b-22abba04d35a (36 chars) | 36 CHAR |
| Z* | Name | Description given to the contract (useful for reporting) | 1000 CHAR |
| Z* | Associating Entity Agreement Type | This is the Icertis Agreement Type of the associated agreement (for example ICMMasterAgreement if the record is a ICMSubAgreement; or | 224 CHAR |
| Z* | Associating Entity Agreement Code | 224 CHAR | |
| Z* | Associating Entity System ID | 36 CHAR | |
| Z* | Supplier's Account Number | The supplier numbers will be the same as the ECC supplier numbers. NDA's may not necessarily have a supplier id as it is possible to define an NDA for a bidder supplier only. Cannot be validated as the supplier records do not exist in both SAP systems. | 224 CHAR |
| Z* | Start of Validity Period | YYYYMMDD | DATE |
| Z* | End of Validity Period | YYYYMMDD | DATE |
| Z* | Target Value for Header Area per Distribution | It needs to be the total value of the contract (in ECC it is target value at header level) In the case of amendments, it needs to be the updated overall total Renewals may also update the overall value. ERP-203 Icertis: Total Contract Value calculation with multiple amendments to enable ECC Integration | INT(15 including 2 decimals) |
| Z* | Currency Key | Confirmed the currency codes in Icertis are aligned to SAP codes | 5 CHAR |
| Z* | Company Code | Organizational data - company code, purchasing group, purchasing org are being aligned in Icertis to ECC - it is the 4 char code for company code which matches SAP | 1000 CHAR |
| Z* | Purchasing Group | Organizational data - company code, purchasing group, purchasing org are being aligned in Icertis to ECC - it is the 3 char code for purchasing group which matches SAP | 1000 CHAR |
| Z* | Purchasing Org | Organizational data - company code, purchasing group, purchasing org are being aligned in Icertis to ECC- it is the 4 char code for purchasing organization which matches SAP | 1000 CHAR |
| Z* | Region | Icertis has values for each region which will be useful for the consolidation report to enable filtering of the Icertis Z table records by region. Possible values are: WW, EMEA, APAC, AMS (world-wide, Europe, Asia Pacific, Americas) | 4 CHAR |
| Z* | Contract Owner | Use for filtering in the report on Z table so owners can find their own to work on First name, last name and email id in one field | 224 CHAR |
| Z* | Incoterms | Incoterms are being aligned to correspond between Icertis and ECC This field in Icertis is the 3 char code for the terms | 224 CHAR |
| Z* | Payment Terms | Payment terms are being aligned to correspond between Icertis and ECC This is the 4 char code that matches to SAP's codes in ECC | 224 CHAR |
| Z* | Termination Date | When a termination message is received, the expiry date field remains same in ICertis but the termination date will have to become the expiry date | DATE |
Mapping and Calculation
Note: For all field values from Icertis, remove any blank spaces from the beginning and end of the value and the remaining content is to go into the target field. Icertis has many text-based fields ranging from 224 to 1000 chars which are able to be input by users. We cannot control that the contents will fit into a fixed length field on the target system.
Field lengths for the custom fields in SAP ECC will have to correspond to the length of the fields in Icertis.
Important: The ActionName field in the initial event received to CPI is the key controlling information which determines whether a new line item in the custom table is required, or an existing line is to be updated. The values in this field are:
"Terminated" (update existing entry)
"Renewed" (update existing entry)
"AmendmentExecuted" (update existing entry, but for the Parent Contract and Parent System ID)
"Executed" (create a new entry)
The payload of the agreement data from Icertis is expected to have many more fields than what are relevant to store in the custom table in SAP ECC. CPI will filter out the fields which are not required to be stored in SAP.
| Source Table | API or Portlet Name | Source Field | Required (Y/N) | Description | Target | API or Portlet Name | Target Field | Required (Y/N) | Description (Label in SAP) | Rule Type | Rule Instruction |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Z* | Y | Tenant ID | To be defined what the value is and how it is identified | ||||||||
N/A | CONTRACTTYPENAME | Y | Contract Type Name | Z* | CONTRACTTYPENAME | Y | Contract Type Name | If ActionName is 'Executed', then a new entry is made in the Z table for CONTRACTYPENAME and SYSID If ActionName is 'Renewed' or 'Terminated', then the existing entry is updated for the CONTRACTTYPENAME and SYSID If the ActionName is 'AmendmentExecuted' then the existing entry for PARENT CONTRACT and PARENT SYS ID is updated. | |||
| N/A | SYSID | Y | System ID | Z* | SYSID | Y | System ID | If ActionName is 'Executed', then a new entry is made in the Z table for CONTRACTYPENAME and SYSID If ActionName is 'Renewed' or 'Terminated', then the existing entry is updated for the CONTRACTTYPENAME and SYSID If the ActionName is 'AmendmentExecuted' then the existing entry for PARENT CONTRACT and PARENT SYS ID is updated. | |||
| N/A | NAME | N | Description | Z* | NAME | N | Description | Direct Mapping | |||
| N/A | ICMAGREEMENTCODE | Y | ICM Agreement Code | Z* | ICMAGREEMENTCODE | Y | ICM Agreement Code | Direct Mapping | |||
| N/A | N/A | N | Z* | **TBA - Association | Associating Entity Name | ** TBA - The association of sub agreement to a master agreement - exact content to be advised | |||||
| N/A | PARENT SYS ID | N | Parent System ID | Used for amendments to determine which existing record in the Z table is to be updated. Field is not stored in the Z-table. | |||||||
| N/A | PARENT CONTRACT | N | Parent Contract | Used for amendments to determine which existing record in the Z table is to be updated. Field is not stored in the Z-table. | |||||||
| N/A | ICMSUPPLIERSAPID | N | Supplier Number | Z* | ICMSUPPLIERSAPID | N | Supplier Number | Direct Mapping | |||
| N/A | ICMEFFECTIVEDATE | N | Effective from date | Z* | ICMEFFECTIVEDATE | N | Effective from date | Format received is YYYY-MM-DDTHH:MM:SS Remove the HH:MM:SS and 'dashes' to store in the Z table as YYYYMMDD | |||
| N/A | ICMEXPIRY | N | Expiry date | Z* | ICMEXPIRY | N | Expiry date | Format received is YYYY-MM-DDTHH:MM:SS If ActionName is 'Executed', 'Renewed' or 'Amendment Executed', direct mapping. If ActionName 'Terminated', fill with the value from ICMTERMINATIONDATE. The format of the contents also need to be updated to remove the time and dashes to store in the Z table as YYYYMMDD | |||
| N/A | ICMTOTALCONTRACTVALUE | N | Target Value | Z* | ICMTOTALCONTRACTVALUE | N | Target Value | Direct Mapping | |||
| N/A | ICMCURRENCY | N | Currency Key | Z* | ICMCURRENCY | N | Currency Key | Direct Mapping | |||
| N/A | ICMLEGALENTITYCODE | N | Legal Entity Code | Z* | ICMLEGALENTITYCODE | N | Legal Entity Code | Direct Mapping | |||
| N/A | ICMPURCHASEGROUPCODE | N | Purchasing Group | Z* | ICMPURCHASEGROUPCODE | N | Purchasing Group | Direct Mapping | |||
| N/A | ICMPURCHASEORGCODE | N | Purchasing Organization | Z* | ICMPURCHASEORGCODE | N | Purchasing Organization | Direct Mapping | |||
| N/A | ICMREGION | N | Region | Z* | ICMREGION | N | Region | Direct Mapping | |||
| N/A | ICMPRIMARYOWNERNAME | N | Primary Contract Owner | Z* | ICMPRIMARYOWNERNAME | N | Primary Contract Owner | Direct Mapping | |||
| N/A | ICMINCOTERMCODE | N | Incoterms | Z* | ICMINCOTERMCODE | N | Incoterms | Direct Mapping | |||
| N/A | ICMPAYMENTTERMSCODE | N | Terms of Payment | Z* | ICMPAYMENTTERMSCODE | N | Terms of Payment | Direct Mapping | |||
| N/A | ICMTERMINATIONDATE | N | Termination Date | Z* | Used for the determination of the expiry date, not stored directly in the Z table. In the case of a termination, the expiry date is not updated in Icertis, but this termination date is held separately. | ||||||
Processing Logic
Processing within Source
There is no processing requirement to be carried out in the Source System Icertis.
Processing within Middleware
All processing within CPI is defined in the mapping sheet.
Processing within Target
There is no processing to be carried out within the target system.
Interface Dependency
There are no dependent interfaces identified which require processing prior to this interface.
Interface Constraints
There are no constraints identified.
Delivery Requirements
The delivery requirements are expected to be as close to real time as possible, allowing just for processing.
The triggering events from Icertis are received to CPI and is a push of the event information. There is then a pull of the contract information from Icertis by CPI based on the event data provided in the initial payload.
Delta or Full Load Requirements
CPI will filter out any additional fields provided in the payloads from Icertis and keep only those required to be stored in SAP or used by the ABAP logic.
Interface Alert & Monitoring
The following will be monitored:
- API endpoints are available.
- Failures on inbound processing and outbound side need to be handled . Please check the Error Handling section.
- Messages are processed in reasonable time to ensure that the custom table record in SAP ECC is available for the business user when they go to create the outline agreement. This is expected to be within the hour immediately after the execution of a new contract.
Interface Reporting
There are no specific reporting requirements identified to support this interface.
Language Requirements
There are no specific language requirements. The contract content from Icertis is predominantly text based and will therefore be shown in the language it which it was entered in Icertis.
User Interface Requirements
There are no requirements for any user interface associated with this interface. The only interaction with users will be via the consolidation report being delivered via Business Warehouse.
Volumetrics
BAU - up to 10,000 contracts
Performance Consideration
<100 new/changes per day
Error Handling
Error Handling:
- SAP Cloud ALM (CALM) will be used to capture integration execution errors.
- To correct the error, the Administrator must ensure that the data inconsistency is resolved in the concerned system.
- Refer to the link below to troubleshoot Error Messages Returned by the Event Management API.
Testing
How to Test
Dhiraj & Kapila - these will have to be initiated in Icertis?
Dependency on the metadata having been configured in Icertis?
Z-table entries can be reset manually in order to reuse payloads from Icertis
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|---|---|
| Execution | ||
| 1 | Execute Master Agreement | Execution event received in CPI Successful call to Icertis for agreement details Successful retrieval of agreement details Creation of new entry in custom table with field values as defined. |
| 2 | Execute Sub Agreement (single) | Execution event received in CPI Successful call to Icertis for agreement details Successful call to Icertis for association details Successful retrieval of agreement details Successful retrieval of association details Creation of new entry in custom table with field values as defined. Check association of Sub Agreement to the relevant Master Agreement is correct |
| 3 | Execute Stand Alone Agreement | Execution event received in CPI Successful call to Icertis for agreement details Successful retrieval of agreement details Creation of new entry in custom table with field values as defined. |
| 4 | Execute Supporting Agreement (NDA) | Execution event received in CPI Successful call to Icertis for agreement details Successful retrieval of agreement details Creation of new entry in custom table with field values as defined. |
| 5 | Execute Baseline Agreement | Execution event received in CPI Successful call to Icertis for agreement details Successful retrieval of agreement details Creation of new entry in custom table with field values as defined. |
| 6 | Execute Sub Agreement (multiple for the one Master Agreement) | Execution event received in CPI Successful call to Icertis for agreement details Successful retrieval of agreement details Creation of new entries in custom table with field values as defined. Check association of Sub Agreements to the relevant Master Agreement is correct |
| 7 | Renewal | |
| 8 | Agreement with auto renewal is renewed when the renewal date is reached | Renewal event received in CPI Successful call to Icertis for agreement details Successful retrieval of agreement details Update of existing record in custom table with expiry updated to the renewal date. |
| 9 | Agreement without auto renewal is renewed | Renewal event received in CPI Successful call to Icertis for agreement details Successful retrieval of agreement details Update of existing record in custom table with expiry updated to the renewal date. |
| 10 | Termination | |
| 11 | Existing active Agreement is terminated with notice (method 1) | Renewal event received in CPI Successful call to Icertis for agreement details Successful retrieval of agreement details Update of existing record in custom table with expiry updated to the termination date. |
| 12 | Existing active Agreement is terminated without notice (method 2) | Renewal event received in CPI Successful call to Icertis for agreement details Successful retrieval of agreement details Update of existing record in custom table with expiry updated to the termination date. |
| 13 | Amendment Executed | |
| 14 | ||
| 15 | ||
| 16 | ||
| 17 | ||
| 18 | ||
| 19 | ||
| 20 | ||
| 21 | ||
| 22 | ||
| 23 | ||
| 24 | ||
| 25 | ||
| 26 | ||
| 27 | ||
| 28 | ||
| 29 | ||
| 30 | ||
| 31 | ||
| 32 | ||
| 33 |
Test Considerations/Dependencies
ERP-203 Icertis: Total Contract Value calculation with multiple amendments to enable ECC Integration needs to be completed in order for the target value to reflect the total of all amendments and the original contract target value.
ERP-508 Enhancement for Icertis event streams need to be completed in order for the events for renewals, terminations, amendments to be generated from Icertis and send the initial payload to CPI.
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|