Revision as of 10:54, 12 September 2022

ICI for SAP Ariba 

Overview

Icertis Contract Intelligence (ICI) integration with SAP Ariba Contracts

The Icertis Contract Intelligence (ICI) for SAP Ariba Contracts provide organizations an intelligent and flexible contracting platform that is a fully integrated into SAP Ariba Contracts, thereby unlocking the value of the SAP Ariba supplier network through a seamless source-to-contract workflow featuring the best-in-class contract management functionality.

Some key challenges to the organizations are:

• Lack of speed, collaboration among stakeholders: Inefficient processes lead to high turnaround time. Delays in contracting cause a delay in value realization which impacts revenue.
• Lack of insights from contract data leads to limited visibility to enforce performance.
• Security, risk, compliance helps to safeguard brand and intellectual property rights.

The ICI -SAP Ariba Adapter provides the following capabilities to integrate with SAP Ariba.

The diagram above depicts how the end-to-end Source to Contract business flow can be orchestrated leveraging the Icertis Contract Intelligence (ICI) for SAP Ariba Contracts.

• A contract manager can create either a standalone SAP Ariba Contract Workspace (ACW) or corresponding ACW from SAP Ariba Contract Request. A category manager can also create an SAP Ariba Contract Workspace while awarding a sourcing event.
• A contract manager can initiate contract authoring in ICI directly from the SAP Ariba Contract Workspace.
• ICI can automatically assemble the legal language leveraging the predefined template and rules.
• The contract review, approval, and signature can be done in ICI.
• Once the contract is executed in ICI, the metadata and a signed PDF is synchronized with the SAP Ariba Contract Workspace.

ICI for SAP Ariba Solution

• Contract Authoring

Contract Managers can create an SAP Ariba Contract Workspace (ACW), provide minimal information, and initiate authoring in ICI. They can identify whether the agreement will use a third-party paper or their own paper. For third-party papers, ICI’s AI capabilities can be leveraged to extract metadata and clauses for ease of redlining (Editing). For own paper, ICI can easily assemble the legal language based on predefined legal template and rules.

• Repository Contract

The contract manager can easily manage signed PDF contracts by uploading it directly to the ACW and publishing it. The solution will automatically create an executed agreement in ICI, leveraging the ACW attributes and signed PDF.

• Contract Review, Approval, Signature, and Execution

ICI capabilities around contract redlining (such as Microsoft Word Experience, Online Editing), approval, signature can be leveraged to streamline the process with proper governance. Once executed, the metadata along with a signed PDF can is pushed to the ACW.

• Contract Amendment

You can initiate an amendment in ACW and complete the legal authoring for the amendment in ICI. Once the contract amendment is executed in ICI, the changes in the contract are reflected in the ACW.

• Supplier Master Data

 The integration also provides a provision to synch supplier Masterdata from SAP Ariba Contracts to ICI.

Below are synchronizations between ICI and SAP Ariba Contracts. 

• Agreement data synchronization
• Agreement document synchronization
• Agreement team synchronization
• Supplier masterdata synchronization

Benefits

• Accelerate contract turnaround times

Seamless integration with SAP Ariba Contracts enables organizations to easily run contracting processes and quickly author and negotiate contracts closer to their clause positions and operationalize it in SAP Ariba Contracts with the best-in-class technology.

• Realize the full value of every contract

Seamless data integration between ICI and SAP Ariba Contracts ensures negotiated commercial terms are enforced during the procurement and payable processes, helping maximize the value of every contract.

• Effectively manage legal and business risk

Preapproved legal templates, predefined corporate policies, and constant monitoring of contractual obligations and  SLA (Service Level Agreement) enable organizations to effectively manage legal and business risks.

Prerequisites

The ICI SAP Ariba Adapter is supported with ICI version 8.2 and 8.1.2. Ensure that the following prerequisites are met:

•   SAP Ariba contracts  API prerequisites

    o   Use the REST API collection to integrate SAP Ariba Contract Workspaces (ACW), SAP Ariba Documents, and SAP Ariba Team.

    o   The SAP Ariba REST APIs are configured with API rate limit values to make uninterrupted API calls for data syncing. 

•   ICI configuration prerequisites

   o   Creating ICI entities

   o   Mapping attributes for ICI entities (Client App Cross Reference and Client App Entity Mapping) 

   o   Creating filters in the Client App Filter Condition

   o   Defining Date Filter criteria in the Client App Masterdata Sync for field: Effective Date 

   o   Storing SAP Ariba API connection information in the Azure Key Vault   

•   Other prerequisites

   o   Task Service is up and running

   o   Respective events and jobs are enabled

   o   SAP Ariba Contracts allows  ICI Client to consume their APIs 

   o   SAP Ariba Contracts users are provisioned in ICI

   o   SAP Ariba Contracts  IDP integration is configured in ICI

   o   The required SAP Ariba Contracts Masterdata is imported to ICI

Note: To know more about detailed configuration, click here.

Managing Contracts

After integrating ICI with SAP Ariba Contracts, you can perform the following contract authoring activities:

The ICI SAP Ariba Adapter enables you to create and manage the following records:

•      Executed paper agreements

•      Own paper agreements

•      Third party paper agreements

•      Amendments (full and termination)

Working with Contracts

Managing Contracts Created Using Executed Paper

The executed paper contracts refer to the types of contracts that are created offline and uploaded to the system. As a part of the organization’s contract systems these must be stored in a repository.

For example, a contract manager or a contract lead receives an already executed agreement and enters the agreement into the system for keeping records.

The following table explains the possible scenarios while working with contracts created using executed paper.

Creating a Contract Using Executed Paper

1. Create a Contract Workspace in SAP Ariba Contracts in the Draft status.

2. You can view the main agreement in the  CW The signature task is associated with the main agreement document. This signature task can be completed either through the e-signature process or you can upload a signed copy that is created offline.

3. To publish the agreement, perform standard Publish action in SAP Ariba Contracts.

Note: To know more about the standard Ariba Contract Workspace creation process, click here

4. To open the ICI equivalent agreement, click the link in the External ID column (for example: ICMNDA_82).

5. To open SAP Ariba side information,click Details> Ariba Information.

6. To view the owners of the agreement, on the left navigation pane, click Team.

7. To open the Contract details, click Details > General Information.

8. To navigate back to the Ariba Contract Workspace, click Details > Ariba CW Link.

9. The ACW now shows both the ACW ID and the Icertis ID.

Managing Contracts Created Using Own or Third party Paper

You can choose to create an agreement using your own paper or third-party paper:

•   Own paper: Create an agreement by using your own template 

•   Third-Party paper: Create an agreement by using a template provided by the vendor or the provider

The following diagram explains the contract initiation to contract execution process.

Creating a Contract Using Own Paper or Third party Paper

1.   Create a Contract Workspace in SAP Ariba Contracts in the Draft status.

2.   Click Initiate Authoring. The ICI application opens.

3.   On the Contract Type Details page, select the options and click Next.

4.   On the Attributes page, enter the required values and click Next.

5.   (For third party paper only) Upload a contract document and click Next.

6.   (For own paper only) Select or upload a template and click Next.

7.   Click Create and Publish.

8.   Send the contract for required approvals.

9.   Initiate internal and external signatures.

10. Execute the contract in ICI.

11. Once the contract is executed in ICI, you can view the contract details in ACW.

12. Publish the ACW to complete the process.

Managing contracts in unique scenarios

The following table explains the few unique scenarios of SAP Ariba Contract Workspace (ACW), and statuses that reflect in SAP Ariba and ICI. Note that status names are not changed, but only synching SAP Ariba Contract Status to ICI in attribute is changed.

Syncing Contract Line Item Documents (CLID)

A Contract workspace can contain Contract Line items Documents (CLID).

Refer to the tables to see different CLID statuses and corresponding impact in ICI before authoring is initiated and when authoring is already initiated.

• Contract authoring is not initiated

• Contract authoring is already initiated

Working with Amendments  

An amendment is a change made to an executed or signed agreement. In Icertis Contract Intelligence, you can amend an executed agreement whether it is in executed, terminated, or expired state.

For SAP Ariba Contracts, amendment type depends on the reason for amending the main contract.

The following types of amendments are supported in ICI SAP Ariba Contracts integration:

• Amendment ( a full Amendment ) 
• Termination 

Prerequisite

The Ariba Contract Workspace (ACW) was created, and the contract status was published.

Creating an Amendment

1.     Open the SAP Ariba Contract Workspace that you want to amend.

2.    From the Actions menu, click Amend.

3.    Enter the relevant information and the reason for the amendment.

4.    (Optional) Edit the required attributes.

5.    From the Actions menu, click Initiate Authoring. The agreement opens in the ICI application.

6. Enter the details and clickCreate. The amendment record gets created.

Like agreements, a unique amendment ID is created and is synchronized back in ACW. The amendment is created in the Draft status.

7. Publish the ICI amendment.

Note the following important points

• While creating an amendment in ICI, you can select an existing template or can choose a predefined template.
• A new record is created only for the full amendment scenario.
• For all other amendment types, except the full amendment, the Header fields are updated in the parent agreement itself.
• When the signatures are done in ICI[SN3] , the Publish option in the Ariba Contract Workspace is enabled only after the ICI agreement is executed.
• For all the amendment types, except the full Amendment, the publishing is done in ACW. The overall lifecycle and procedure to execute all types of amendments remain the same.
• Each amendment type has a specific set of attributes.
• All amendment types are shown in the same way, with its own SAP Ariba Contracts amendment type name.

• Termination type amendment

The History tab shows the old values and the new values for all changed attributes.

Configuration

SAP Ariba Contracts Side configurations

To know more on SAP Ariba Contracts side configurations, click here.

ICI Side configurations 

To know more on ICI side configurations, click here.

Glossary

Related Topics: Agreement Management