| 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
The functional design of the Integration Process defines both inbound and outbound interfaces. An integration defines a specific physical interaction that will need to occur between the system and an external application in response to some business event.
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 agreement data is received to CPI (Cloud Platform Integration). Events for Amendment Execution, Renewal and Termination require development within Icertis in order to be initiated and for the data to be received to CPI.
??? How to describe the method by which the data makes its way to Z table
The data received
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 the agreements and change the outline agreements as a result of 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.
Process Flow Diagram
? end to end or just up to the Z table entries
? link to L4s or picture or just steps - link
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 Icertis Contract ID and the relevant data fields from the contract header |
3 | Contract creation upload form is completed | SYRA | The relevant contract creation form is completed via the Syra portal including the Icertis Contract ID |
4 | Upload of the contract creation form | SAP ECC | The relevant background job is executed for the creation of the outline agreement from the content of the form |
5 | Outline agreement is created in the background | SAP ECC | The outline agreement is created in the background with the Icertis Contract ID entered on the header of the outline agreement |
6 | An amendment to a contract in Icertis is executed | Icertis | change scenarios separate |
Update entry for the parent contract in the custom table | SAP ECC | ||
A renewal of a contract is made in Icertis | |||
Assumptions
Dependencies
ERP-151 : Small adjustment based on DOA changes
In order to correctly fill the target value ERP-151 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.
Security, Integrity and Controls
Configuration Requirements
There are no specific configuration requirements for this interface.
Special Requirements
Design Rationale
Data Structure
Source Structure
The following fields will be used to provide the required information for this interface:
| Field | Description |
|---|---|
Target Structure
The following fields will be used to provide the required information for this interface:
| Field | Description |
|---|---|
| put labels name | |
| if a standard field get it's correct label and name and put technical field name in |
Mapping and Calculation
| Source Table | API or Portlet Name | Source Field | Required (Y/N) | Description | Target | API or Portlet Name | Target Field (Label) | Required (Y/N) | Description | Rule Type | Rule Instruction |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ICM Tenant ID | Y | Unique ID that defines purchase contracts within Icertis | Z* | Icertis Tenant ID | Y | middleware rule - filtering, dates formatting | |||||
| CONTRACTTYPENAME | Y | Z* | Contract Type | Y | IN TARGET FIELD put the label for the field from SAP | ||||||
| NAME | Y | Z* | Contract Name | Y | |||||||
| ICMAGREEMENTCODE | N | Z* | Contract ID | N | |||||||
| SYSID | N | Z* | System ID | N | |||||||
| PARENT SYS ID | N | Z* | Parent System ID | N | |||||||
| PARENT AGREEMENT | N | Z* | Parent Contract ID | N | |||||||
| ICMSUPPLIERSAPID | N | Z* | Supplier's Account Number | N | |||||||
| ICMEFFECTIVEDATE | N | Z* | Start of Validity Period | N | |||||||
| ICMEXPIRY | N | Z* | End of Validity Period | N | |||||||
| ICMTARGETVALUE | N | Z* | Target Value for Header Area per Distribution | N | |||||||
| ICMCURRENCY | N | Z* | Currency Key | N | |||||||
| ICMLEGALENTITYCODE | N | Z* | Company Code | N | |||||||
| ICMPURCHASINGGROUP | N | Z* | Purchasing Group | N | |||||||
| ICMPURCHASINGORG | N | Z* | Purchasing Organization | N | |||||||
| ICMCONTRACTOWNER | N | Z* | Contract Owner | N | |||||||
| ICMINCOTERM | N | Z* | Incoterms | N | |||||||
| ICMPAYMENTTERMS | N | Z* | Terms of Payment Key | N |
Processing Logic
Processing within Source
check with Wytse if there is any in Icertis
Processing within Middleware
refer to the mapping sheet
Processing within Target
not applicable
Interface Dependency
Interface Constraints
Delivery Requirements
Delta or Full Load Requirements
Interface Alert & Monitoring
Interface Reporting
Language Requirements
User Interface Requirements
Volumetrics
Performance Consideration
Error Handling
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|---|---|
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|