ICIHelp8.2 - User contributions [en]

Patch Release Notes

2023-12-11T06:53:34Z

WikiSysop:

= Patch Release Notes =

<span style="font-size:larger;">The following patches are released for ICI 8.2: </span>

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_6.pdf|8.2 Patch 6]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_5.pdf|8.2 Patch 5]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_4.pdf|8.2 Patch 4]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_3.pdf|8.2 Patch 3]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_2.pdf|8.2 Patch 2]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_1.pdf|8.2 Patch 1]]</span> 

File:ICI Release Notes 8.2 Patch 6.pdf

2023-12-11T06:52:58Z

WikiSysop:

File:ICI Release Notes 8.2 Patch 5.pdf

2023-06-30T13:17:23Z

WikiSysop: WikiSysop uploaded a new version of File:ICI Release Notes 8.2 Patch 5.pdf

Patch Release Notes

2023-06-30T10:32:21Z

WikiSysop:

= Patch Release Notes =

<span style="font-size:larger;">The following patches are released for ICI 8.2: </span>

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_5.pdf|8.2 Patch 5]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_4.pdf|8.2 Patch 4]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_3.pdf|8.2 Patch 3]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_2.pdf|8.2 Patch 2]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_1.pdf|8.2 Patch 1]]</span> 

File:ICI Release Notes 8.2 Patch 5.pdf

2023-06-30T10:31:40Z

WikiSysop:

Patch Release Notes

2023-04-17T04:11:49Z

WikiSysop:

= Patch Release Notes =

<span style="font-size:larger;">The following patches are released for ICI 8.2: </span>

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_4.pdf|8.2 Patch 4]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_3.pdf|8.2 Patch 3]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_2.pdf|8.2 Patch 2]]</span> 

<span style="font-size:larger;">[[Media:ICI_Release_Notes_8.2_Patch_1.pdf|8.2 Patch 1]]</span> 

File:ICI Release Notes 8.2 Patch 4.pdf

2023-04-17T04:10:02Z

WikiSysop:

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2023-03-21T08:10:49Z

WikiSysop:

 

 

 

 

 

 

= ICI for SAP CPQ and SAP S/4HANA (Sell side) Adapter Replication, Integration, and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI). To know more, see [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=ICI_for_SAP_CPQ ICI for SAP CPQ and SAP S/4HANA (Sell side) Adapter]

'''Note''': If you are using ICI version 8.3 or later, to access the latest information for ICI for SAP CPQ and SAP S/4HANA (Sell side) Adapter, click the help icon from the product UI.

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/> To know more, see [https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549/236d552f22654f759b5533b2d22ecbb3.html?q=Direct%20output#data-replication-using-soa-with-data-replication-framework-(drf) Data Replication Using SOA With Data Replication Framework (DRF)].

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*ICI Platform

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

=== View Prepackaged iFlows using SAP Cloud Integration (CI) ===

#Access the SAP Cloud Integration Web UI.<br/> It should be in the following format: [ http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''''.''
#To view all the artifacts of the package, click '''Artifacts.'''

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example,  '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, choose '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the integration package copied in the Configure and Deploy the iFlow using SAP Cloud Integration section.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2023-03-21T08:09:57Z

WikiSysop:

 

 

 

= ICI for SAP CPQ and SAP S/4HANA (Sell side) Adapter Replication, Integration, and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI). To know more, see [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=ICI_for_SAP_CPQ ICI for SAP CPQ and SAP S/4HANA (Sell side) Adapter]

'''Note''': If you are using ICI version 8.3 or later, to access the latest information for ICI for SAP CPQ and SAP S/4HANA (Sell side) Adapter, click the help icon from the product UI.

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/> To know more, see [https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549/236d552f22654f759b5533b2d22ecbb3.html?q=Direct%20output#data-replication-using-soa-with-data-replication-framework-(drf) Data Replication Using SOA With Data Replication Framework (DRF)].

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*ICI Platform

 

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

 

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

 

 

=== View Prepackaged iFlows using SAP Cloud Integration (CI) ===

#Access the SAP Cloud Integration Web UI.<br/> It should be in the following format: [ http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''''.''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example,  '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, choose '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the integration package copied in the Configure and Deploy the iFlow using SAP Cloud Integration section.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2023-03-21T08:09:42Z

WikiSysop:

 

 

 

= ICI for SAP CPQ and SAP S/4HANA (Sell side) Adapter Replication, Integration, and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI). To know more, see [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=ICI_for_SAP_CPQ ICI for SAP CPQ and SAP S/4HANA (Sell side) Adapter]

'''Note''': If you are using ICI version 8.3 or later, to access the latest information for ICI for SAP CPQ and SAP S/4HANA (Sell side) Adapter, click the help icon from the product UI.

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/> To know more, see [https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549/236d552f22654f759b5533b2d22ecbb3.html?q=Direct%20output#data-replication-using-soa-with-data-replication-framework-(drf) Data Replication Using SOA With Data Replication Framework (DRF)].

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*ICI Platform

==   ==

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

 

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

 

 

=== View Prepackaged iFlows using SAP Cloud Integration (CI) ===

#Access the SAP Cloud Integration Web UI.<br/> It should be in the following format: [ http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''''.''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example,  '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, choose '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the integration package copied in the Configure and Deploy the iFlow using SAP Cloud Integration section.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

File:ICI for SAP CPQ and S4HANA Lead to Cash Adapter Integration Guide.pdf

2023-03-06T11:13:03Z

WikiSysop: WikiSysop uploaded a new version of File:ICI for SAP CPQ and S4HANA Lead to Cash Adapter Integration Guide.pdf

MediaWiki:SidebarTree

2023-02-02T07:13:23Z

WikiSysop:

{{#tree:
*[[Home]]
*[[Agreements]]
**[[Working with Agreements]]
**[[Amendments]]
*[[Requests]]
*[[Associations]]
*[[Compliances]]
*[[Templates]]
**[[Create a Template_in ICI Word Add-in]]
**[[Approve/Reject a Template]]
**[[Bilingual Templates]]
*[[Clauses]]
*[[Configure]]
**[[Contract Type]]
**[[Attribute]]
**[[Rule]]
**[[Masterdata]]
**[[Alias Master]]
**[[Cascade Team]]
**[[Promote Configurations]]
**[[System Configurations]]
**[[SSO Configurations]]
**[[E-sign Configuration]]
*[[Reports]]
**[[Agreement Details Page Reports]]
**[[Legal and Compliance]]
**[[Admin Reports]]
**[[Workflow Reports]]
**[[Power BI Integration with ICI]]
**[[Obligation Management Reports]]
**[[Sourcing Reports]]
*[[Advanced Analytics]]
**[[Power BI]]
*[[Bulk Actions]]
*[[Admin]]
**[[Managing Organization]]
**[[Managing Users]]
**[[Managing User Groups]]
**[[Managing Security Groups]]
**[[Application Settings]]
**[[Notification Settings]]
**[[Currencies]]
**[[Reasons]]
**[[Legacy Upload]]
**[[Admin Task]]
**[[Dashboard Configuration]]
**[[Action Button Configuration]]
**[[Configuring MS Teams with ICI]]
*[[Self-Serve Tools]]
*[[Icertis Business Apps]]
**[[ICI Sourcing App]]
**[[ICI Obligation Management]]
**[[ICI Risk Management]]
**[[ICI Proposal Management]]
**[[ICI Supplier Relationship Management]]
**[[ICI Rebates and Promotions App]]
*[[AI Apps]]
**[[Managing US Federal Contracts using ICI]]
**[[Contract Digitalization]]
**[[Discover AI]]
**[[Negotiate AI]]
**[[Obligation AI]]
**[[Visualize AI]]
*[[ICI Add-ins]]
**[[Icertis Experience for Word]]
**[[Outlook Add-in]]
**[[Collaboration experience with Microsoft Teams]]
*[[Integrations]]
**[[ICI for SAP Ariba Strategic Sourcing]]
**[[ICI for SAP CPQ]]
**[[ICI for SAP Fieldglass]]
**[[Salesforce]]
**[[Microsoft Dynamics CRM]]
**[[Icertis Experience for Workday]]
**[[System for Cross Domain Identity Management]]
**[[Using Adobe Sign]]
**[[Using DocuSign]]
**[[Using Namirial eSignAnywhere]]
**[[Generic Integration Framework to Support SFTP Interface]]
**[[Generic Integration Framework to Support ASB Interface]]
*[[API Capabilities]]
*[[ICI Mobile App]]
*[[ICI BOT]]
*[[Release Notes]]
*[[Patch Release Notes]]
}}

Patch Release Notes

2023-02-02T07:08:47Z

WikiSysop: Created page with " = Patch Release Notes = <span style="font-size:larger;">The following patches are released for ICI 8.2: </span> <span style="font-size:larger;">Media:ICI_Release_Not..."

File:ICI Release Notes 8.2 Patch 1.pdf

2023-02-02T07:05:22Z

WikiSysop:

File:ICI Release Notes 8.2 Patch 2.pdf

2023-02-02T07:05:01Z

WikiSysop:

File:ICI Release Notes 8.2 Patch 3.pdf

2023-02-02T07:04:38Z

WikiSysop:

ICI for SAP CPQ

2023-02-02T06:13:16Z

WikiSysop:

 

= ICI for SAP CPQ with S/4HANA (Sell side) Adapter =

== Overview ==

The ICI for SAP CPQ with SAP S/4HANA (Sell side) Adapter supports the quote-to-cash flow with a two-way integration between ICI and SAP CPQ. The adapter provides a personalized sales experience that helps accelerate the selling process. Preconfigured products and pricing models from SAP CPQ enable the sales organization to easily assemble a quote and improve operational efficiency. Preapproved legal templates and preconfigured workflows in ICI enable contract managers to quickly assemble and effectively negotiate contracts and thus reduce the contract time and risk.

SAP CPQ provides a rich customer experience by empowering sales teams and partners to easily offer complex product configurations, optimized pricing, and great-looking proposals.

[[File:ICI-CPQ functional diagram.PNG|upright|ICI-CPQ functional diagram.PNG]]

The Lead-to-Cash process starts with generating leads, capturing the prospect, creating an opportunity, and assigning the appropriate stage. A preapproved NDA can be shared with the customer for signature, leveraging digital signature applications such as AdobeSign or DocuSign. After the quote is reviewed with the client and approved internally, a contract can be created automatically in ICI. Relevant data from customer accounts and quotes are utilized to create the contract. To know more, see [https://help.sap.com/docs/SAP_CX/fe1b9a180649472eb58843ec01732ed9/03559e96735249e7bd37929f1f387b85.html Lead-to-cash Process].

In large enterprise functional landscape, SAP S/4HANA acts as a single source of truth for Business Partner and Product master data. Sell-side systems sync customer information and orderable product information from SAP S/4HANA. End-to-end integrated journeys for Lead-to-Cash from SAP CPQ to ICI to S/4HANA require Business Partner and Product data to be synced from SAP S/4HANA to SAP CPQ and ICI. Master data sync is one of the prerequisites for accurate and consistent data availability across the systems to ensure smooth functional flows and user journeys. To know more, [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration click here].

The following image shows the functional flow of the adapter.

[[File:ICI CPQImg1.PNG|700px|ICI CPQImg1.PNG]]

 

 

'''Note:''' The ICI for SAP CPQ with SAP S/4HANA (Sell side) Adapter is supported with ICI version 8.2 onwards.

 

 

 

== Benefits ==

*Reduce the lead-to-cash cycle time<br/> Seamlessly integrate customer and pricing data from SAP CPQ into ICI to quickly and accurately create contracts that reference the agreed pricing terms, promotions, incentives, and rebates when building contracts.
*Easily discover, monitor, and mitigate contract risk<br/> Discover risks caused by deviations from normal business practices to proactively identify and monitor business risk to reduce the impact on operational, financial, and reputational risk, contributing significantly to the company's bottom line.
*Collaborate on contracts seamlessly among all parties<br/> Reduce rework and improve customer satisfaction with accurate redlining, versioning, and approval workflows, reducing risk exposure for your company. Enable secure communication with suppliers, customers, and partners.
*Gain deeper insights into sales and contracts<br/> Manage agreements across multiple departments to gain deeper insights and align supplier and customer terms with AI-supported search, digitization, and negotiation.
*Reduce errors by ensuring data consistency<br/> Consistent data across systems ensure accuracy, which in turn reduces rework and improves customer satisfaction.
*Reduced time for data sync<br/> Seamlessly sync data from SAP S/4HANA into ICI quickly with real-time sync or at the desired frequency by setting periodic incremental sync.
*Extensibility offered with a solution<br/> As per implementation requirements, master data attributes can be added in ICI and mapping can be established to sync up the master data from SAP S/4HANA.

== Creating Contracts from Quotes ==

After integrating ICI with SAP CPQ, you can create contracts from quotes created in SAP CPQ. Once the contract is executed in ICI, you can either place the order for the related quote manually or configure auto-ordering for it.

 

 

=== Prerequisites ===

*Ensure that Customer (Business Partner) Master data present in ICI are in sync with Customer Master.
*Ensure that Product Master data present in ICI are in sync with Product Master.

For end-to-end integration having S/4HANA for Orders, Master Data Integration is available to sync the Customer (Business Partner) and Product Master data from S/4HANA to ICI.<br/> To know how to configure master data integration from SAP S/4HANA to ICI, [[ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration|click here]].

To complete the Quote to Order process, you need to perform the following steps:

#Create contract
#Execute contract
#Place Order

 

=== Create Contract ===

#Create a quote and add products.<br/> To know how to create a quote, see [https://help.sap.com/docs/SAP_CPQ/551616e85ad64739835aa69241222f53/12df2dee87b046ba8e585571cab4d231.html Quote Creation].
#Enter the '''Opportunity, Quote Name''', '''Effective Date''', '''Contract Term (Months)''', and '''Sold-to Party''' (Customer).<br/> Note that the '''Contract Link''' and '''Contract Number''' fields are read-only and don't contain any values.
#Once the commercials of the quote are finalized, change the status to '''Ready for Contracting'''.<br/> ICI checks for quotes in '''Ready for Contracting''' status and picks them for contract creation through seamless integration.<br/> When the quote is picked for contracting, the status changes to '''Contract Created'''.<br/> On the '''Additional Info''' tab, the contract link and contract number are now available.

 

=== Execute Contract ===

#Use the contact link on the '''Additional Info''' tab and navigate to the contract in ICI.<br/> The contract is in '''Draft''' status.
#Click on the '''Details''' tab in the left pane to see that the attribute values from the quote have been populated.
#Click the '''Associations''' tab in the left pane to see the line items from the quote and their details.<br/> To know how to create an association, see [https://iciwikiapac.icertis.com/ICIHelp8.1/index.php?title=Associations#Creating_associations_on_create.2Fedit_wizard_of_agreement Creating Associations.]
#To preview the contract, click '''Download''' > '''Assemble Contract''' and click the two-pane icon.<br/> This allows for a side-by-side comparison between the assembled contract and the details in the '''Default Agreement Dashboard'''. Attributes populated in the contract are highlighted.
#Send the contract for review and approval. <br/> To know more about the approval process in ICI, see [https://iciwikiapac.icertis.com/ICIHelp8.1/index.php?title=Send_the_Contract_Type_for_Approval Send the contract type for approval. ]
#Once the contract is approved, initiate external and internal signatures.<br/> Post signatures, the contract status is '''Executed'''.

 

=== Place Order ===

Place order action leverages SAP CPQ and SAP S/4HANA integration to send quote details to SAP S/4HANA for order placement.

From SAP S/4HANA, Solution Quote ID is updated back on SAP CPQ Quote as Sales Order ID.

*To place the order, on the '''Quotation''' tab, click the ellipsis icon > '''Place Order'''.

The Place Order action can be automated if auto-ordering is configured for the integration in ICI. The system invokes the '''Place Order''' action as soon as the contract is executed.

Place order action changes quote status to '''Order Confirmation Pending'''.

The quote status is displayed as follows:

*On successful order, the quote status gets updated to '''Order Placed''' through SAP CPQ – SAP S/4HANA integration.
*On order failure, the quote status gets updated to '''Order Failed''' through SAP CPQ – SAP S/4HANA integration.

 

== Configuration ==

For detailed information about the required configuration, reach out to your Icertis point of contact (POC).

ICI for SAP CPQ

2023-02-02T06:05:40Z

WikiSysop:

ICI for SAP CPQ

2023-02-02T06:00:07Z

WikiSysop:

ICI for SAP CPQ

2023-02-02T05:58:26Z

WikiSysop:

ICI for SAP CPQ

2023-02-01T11:23:10Z

WikiSysop:

ICI for SAP CPQ

2023-01-30T11:26:21Z

WikiSysop:

 

 

 

= ICI for SAP CPQ with S/4HANA (Sell side) Adapter =

== Overview ==

The ICI for SAP CPQ with SAP S/4HANA (Sell side) Adapter supports the quote-to-cash flow with a two-way integration between ICI and SAP CPQ. The adapter provides a personalized sales experience that helps accelerate the selling process. Preconfigured products and pricing models from SAP CPQ enable the sales organization to easily assemble a quote and improve operational efficiency. Preapproved legal templates and preconfigured workflows in ICI enable contract managers to quickly assemble and effectively negotiate contracts and thus reduce the contract time and risk.

SAP CPQ provides a rich customer experience by empowering sales teams and partners to easily offer complex product configurations, optimized pricing, and great-looking proposals.

[[File:ICI-CPQ functional diagram.PNG|upright|ICI-CPQ functional diagram.PNG]]

The Lead-to-Cash process starts with generating leads, capturing the prospect, creating an opportunity, and assigning the appropriate stage. A preapproved NDA can be shared with the customer for signature, leveraging digital signature applications such as AdobeSign or DocuSign. After the quote is reviewed with the client and approved internally, a contract can be created automatically in ICI. Relevant data from customer accounts and quotes are utilized to create the contract. To know more, see [https://help.sap.com/docs/SAP_CX/fe1b9a180649472eb58843ec01732ed9/03559e96735249e7bd37929f1f387b85.html Lead-to-cash Process].

In large enterprise functional landscape, SAP S/4HANA acts as a single source of truth for Business Partner and Product master data. Sell-side systems sync customer information and orderable product information from SAP S/4HANA. End-to-end integrated journeys for Lead-to-Cash from SAP CPQ to ICI to S/4HANA require Business Partner and Product data to be synced from SAP S/4HANA to SAP CPQ and ICI. Master data sync is one of the prerequisites for accurate and consistent data availability across the systems to ensure smooth functional flows and user journeys. To know more, [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration click here].

The following image shows the functional flow of the adapter.

[[File:ICI CPQImg1.PNG|700px|ICI CPQImg1.PNG]]

 

 

'''Note:''' The ICI for SAP CPQ with SAP S/4HANA (Sell side) Adapter is supported with ICI version 8.2 onwards.

 

 

== Benefits ==

*Reduce the lead-to-cash cycle time<br/> Seamlessly integrate customer and pricing data from SAP CPQ into ICI to quickly and accurately create contracts that reference the agreed pricing terms, promotions, incentives, and rebates when building contracts.
*Easily discover, monitor, and mitigate contract risk<br/> Discover risks caused by deviations from normal business practices to proactively identify and monitor business risk to reduce the impact on operational, financial, and reputational risk, contributing significantly to the company's bottom line.
*Collaborate on contracts seamlessly among all parties<br/> Reduce rework and improve customer satisfaction with accurate redlining, versioning, and approval workflows, reducing risk exposure for your company. Enable secure communication with suppliers, customers, and partners.
*Gain deeper insights into sales and contracts<br/> Manage agreements across multiple departments to gain deeper insights and align supplier and customer terms with AI-supported search, digitization, and negotiation.
*Reduce errors by ensuring data consistency<br/> Consistent data across systems ensure accuracy, which in turn reduces rework and improves customer satisfaction.
*Reduced time for data sync<br/> Seamlessly sync data from SAP S/4HANA into ICI quickly with real-time sync or at the desired frequency by setting periodic incremental sync.
*Extensibility offered with a solution<br/> As per implementation requirements, master data attributes can be added in ICI and mapping can be established to sync up the master data from SAP S/4HANA.

== Creating Contracts from Quotes ==

After integrating ICI with SAP CPQ, you can create contracts from quotes created in SAP CPQ. Once the contract is executed in ICI, you can either place the order for the related quote manually or configure auto-ordering for it.

 

=== Prerequisites ===

*Ensure that Customer (Business Partner) Master data present in ICI are in sync with Customer Master.
*Ensure that Product Master data present in ICI are in sync with Product Master.

For end-to-end integration having S/4HANA for Orders, Master Data Integration is available to sync the Customer (Business Partner) and Product Master data from S/4HANA to ICI.<br/> To know how to configure master data integration from SAP S/4HANA to ICI, [[ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration|click here]].

To complete the Quote to Order process, you need to perform the following steps:

#Create contract
#Execute contract
#Place Order

 

=== Create Contract ===

#Create a quote and add products.<br/> To know how to create a quote, see [https://help.sap.com/docs/SAP_CPQ/551616e85ad64739835aa69241222f53/12df2dee87b046ba8e585571cab4d231.html Quote Creation].
#Enter the '''Opportunity, Quote Name''', '''Effective Date''', '''Contract Term (Months)''', and '''Sold-to Party''' (Customer).<br/> Note that the '''Contract Link''' and '''Contract Number''' fields are read-only and don't contain any values.
#Once the commercials of the quote are finalized, change the status to '''Ready for Contracting'''.<br/> ICI checks for quotes in '''Ready for Contracting''' status and picks them for contract creation through seamless integration.<br/> When the quote is picked for contracting, the status changes to '''Contract Created'''.<br/> On the '''Additional Info''' tab, the contract link and contract number are now available.

 

=== Execute Contract ===

#Use the contact link on the '''Additional Info''' tab and navigate to the contract in ICI.<br/> The contract is in '''Draft''' status.
#Click on the '''Details''' tab in the left pane to see that the attribute values from the quote have been populated.
#Click the '''Associations''' tab in the left pane to see the line items from the quote and their details.<br/> To know how to create an association, see [https://iciwikiapac.icertis.com/ICIHelp8.1/index.php?title=Associations#Creating_associations_on_create.2Fedit_wizard_of_agreement Creating Associations.]
#To preview the contract, click '''Download''' > '''Assemble Contract''' and click the two-pane icon.<br/> This allows for a side-by-side comparison between the assembled contract and the details in the '''Default Agreement Dashboard'''. Attributes populated in the contract are highlighted.
#Send the contract for review and approval. <br/> To know more about the approval process in ICI, see [https://iciwikiapac.icertis.com/ICIHelp8.1/index.php?title=Send_the_Contract_Type_for_Approval Send the contract type for approval. ]
#Once the contract is approved, initiate external and internal signatures.<br/> Post signatures, the contract status is '''Executed'''.

 

=== Place Order ===

Place order action leverages SAP CPQ and SAP S/4HANA integration to send quote details to SAP S/4HANA for order placement.

From SAP S/4HANA, Solution Quote ID is updated back on SAP CPQ Quote as Sales Order ID.

*To place the order, on the '''Quotation''' tab, click the ellipsis icon > '''Place Order'''.

The Place Order action can be automated if auto-ordering is configured for the integration in ICI. The system invokes the '''Place Order''' action as soon as the contract is executed.

Place order action changes quote status to '''Order Confirmation Pending'''.

The quote status is displayed as follows:

*On successful order, the quote status gets updated to '''Order Placed''' through SAP CPQ – SAP S/4HANA integration.
*On order failure, the quote status gets updated to '''Order Failed''' through SAP CPQ – SAP S/4HANA integration.

 

== Configuration ==

For detailed information about the required configuration, click [[Media:ICI_SAP_CPQ_Adapter_Configuration_Guide.pdf|here]].

ICI for SAP CPQ

2023-01-19T14:14:13Z

WikiSysop:

 

 

 

= ICI for SAP CPQ with S/4HANA (Sell side) Adapter =

== Overview ==

The ICI for SAP CPQ with SAP S/4HANA (Sell side) Adapter supports the quote-to-cash flow with a two-way integration between ICI and SAP CPQ. The adapter provides a personalized sales experience that helps accelerate the selling process. Preconfigured products and pricing models from SAP CPQ enable the sales organization to easily assemble a quote and improve operational efficiency. Preapproved legal templates and preconfigured workflows in ICI enable contract managers to quickly assemble and effectively negotiate contracts and thus reduce the contract time and risk.

SAP CPQ provides a rich customer experience by empowering sales teams and partners to easily offer complex product configurations, optimized pricing, and great-looking proposals.

[[File:ICI-CPQ functional diagram.PNG|upright|ICI-CPQ functional diagram.PNG]]

The Lead-to-Cash process starts with generating leads, capturing the prospect, creating an opportunity, and assigning the appropriate stage. A preapproved NDA can be shared with the customer for signature, leveraging digital signature applications such as AdobeSign or DocuSign. After the quote is reviewed with the client and approved internally, a contract can be created automatically in ICI. Relevant data from customer accounts and quotes are utilized to create the contract. To know more, see [https://help.sap.com/docs/SAP_CX/fe1b9a180649472eb58843ec01732ed9/03559e96735249e7bd37929f1f387b85.html Lead-to-cash Process].

In large enterprise functional landscape, SAP S/4HANA acts as a single source of truth for Business Partner and Product master data. Sell-side systems sync customer information and orderable product information from SAP S/4HANA. End-to-end integrated journeys for Lead-to-Cash from SAP CPQ to ICI to S/4HANA require Business Partner and Product data to be synced from SAP S/4HANA to SAP CPQ and ICI. Master data sync is one of the prerequisites for accurate and consistent data availability across the systems to ensure smooth functional flows and user journeys. To know more, [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration click here].

The following image shows the functional flow of the adapter.

[[File:ICI CPQImg1.PNG|700px|ICI CPQImg1.PNG]]

 

 

'''Note:''' The ICI for SAP CPQ with SAP S/4HANA (Sell side) Adapter is supported with ICI version 8.2 onwards.

 

 

== Benefits ==

*Reduce the lead-to-cash cycle time<br/> Seamlessly integrate customer and pricing data from SAP CPQ into ICI to quickly and accurately create contracts that reference the agreed pricing terms, promotions, incentives, and rebates when building contracts.
*Easily discover, monitor, and mitigate contract risk<br/> Discover risks caused by deviations from normal business practices to proactively identify and monitor business risk to reduce the impact on operational, financial, and reputational risk, contributing significantly to the company's bottom line.
*Collaborate on contracts seamlessly among all parties<br/> Reduce rework and improve customer satisfaction with accurate redlining, versioning, and approval workflows, reducing risk exposure for your company. Enable secure communication with suppliers, customers, and partners.
*Gain deeper insights into sales and contracts<br/> Manage agreements across multiple departments to gain deeper insights and align supplier and customer terms with AI-supported search, digitization, and negotiation.
*Reduce errors by ensuring data consistency<br/> Consistent data across systems ensure accuracy, which in turn reduces rework and improves customer satisfaction.
*Reduced time for data sync<br/> Seamlessly sync data from SAP S/4HANA into ICI quickly with real-time sync or at the desired frequency by setting periodic incremental sync.
*Extensibility offered with a solution<br/> As per implementation requirements, master data attributes can be added in ICI and mapping can be established to sync up the master data from SAP S/4HANA.

== Creating Contracts from Quotes ==

After integrating ICI with SAP CPQ, you can create contracts from quotes created in SAP CPQ. Once the contract is executed in ICI, you can either place the order for the related quote manually or configure auto-ordering for it.

 

=== Prerequisites ===

*Ensure that Customer (Business Partner) Master data present in ICI are in sync with Customer Master
*Ensure that Product Master data present in ICI are in sync with Product Master

For end-to-end integration having S/4HANA for Orders, Master Data Integration is available to sync the Customer (Business Partner) and Product Master data from S/4HANA to ICI.<br/> To know how to configure master data integration from SAP S/4HANA to ICI, [[ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration|click here]].

To complete the Quote to Order process, you need to perform the following steps:

#Create contract
#Execute contract
#Place Order

 

=== Create Contract ===

#Create a quote and add products.<br/> To know how to create a quote, see [https://help.sap.com/docs/SAP_CPQ/551616e85ad64739835aa69241222f53/12df2dee87b046ba8e585571cab4d231.html Quote Creation].
#Enter the '''Opportunity, Quote Name''', '''Effective Date''', '''Contract Term (Months)''', and '''Sold-to Party''' (Customer).<br/> Note that the '''Contract Link''' and '''Contract Number''' fields are read-only and don't contain any values.
#Once the commercials of the quote are finalized, change the status to '''Ready for Contracting'''.<br/> ICI checks for quotes in '''Ready for Contracting''' status and picks them for contract creation through seamless integration.<br/> When the quote is picked for contracting, the status changes to '''Contract Created'''.<br/> On the '''Additional Info''' tab, the contract link and contract number are now available.

 

=== Execute Contract ===

#Use the contact link on the '''Additional Info''' tab and navigate to the contract in ICI.<br/> The contract is in '''Draft''' status.
#Click on the '''Details''' tab in the left pane to see that the attribute values from the quote have been populated.
#Click the '''Associations''' tab in the left pane to see the line items from the quote and their details.<br/> To know how to create an association, see [https://iciwikiapac.icertis.com/ICIHelp8.1/index.php?title=Associations#Creating_associations_on_create.2Fedit_wizard_of_agreement Creating Associations.]
#To preview the contract, click '''Download''' > '''Assemble Contract''' and click the two-pane icon.<br/> This allows for a side-by-side comparison between the assembled contract and the details in the '''Default Agreement Dashboard'''. Attributes populated in the contract are highlighted.
#Send the contract for review and approval. <br/> To know more about the approval process in ICI, see [https://iciwikiapac.icertis.com/ICIHelp8.1/index.php?title=Send_the_Contract_Type_for_Approval Send the contract type for approval. ]
#Once the contract is approved, initiate external and internal signatures.<br/> Post signatures, the contract status is '''Executed'''.

 

=== Place Order ===

Place order action leverages SAP CPQ and SAP S/4HANA integration to send quote details to SAP S/4HANA for order placement.

From SAP S/4HANA, Solution Quote ID is updated back on SAP CPQ Quote as Sales Order ID.

*To place the order, on the '''Quotation''' tab, click the ellipsis icon > '''Place Order'''.

The Place Order action can be automated if auto-ordering is configured for the integration in ICI. The system invokes the '''Place Order''' action as soon as the contract is executed.

Place order action changes quote status to '''Order Confirmation Pending'''.

The quote status is displayed as follows:

*On successful order, the quote status gets updated to '''Order Placed''' through SAP CPQ – SAP S/4HANA integration.
*On order failure, the quote status gets updated to '''Order Failed''' through SAP CPQ – SAP S/4HANA integration.

 

== Configuration ==

For detailed information about the required configuration, click [[Media:ICI_SAP_CPQ_Adapter_Configuration_Guide.pdf|here]].

ICI for SAP CPQ

2023-01-19T13:51:59Z

WikiSysop:

 

 

 

= ICI for SAP CPQ with S/4HANA (Sell side) Adapter =

== Overview ==

The ICI for SAP CPQ with SAP S/4HANA (Sell side) Adapter supports the quote-to-cash flow with a two-way integration between ICI and SAP CPQ. The adapter provides a personalized sales experience that helps accelerate the selling process. Preconfigured products and pricing models from SAP CPQ enable the sales organization to easily assemble a quote and improve operational efficiency. Preapproved legal templates and preconfigured workflows in ICI enable contract managers to quickly assemble and effectively negotiate contracts and thus reduce the contract time and risk.

SAP CPQ provides a rich customer experience by empowering sales teams and partners to easily offer complex product configurations, optimized pricing, and great-looking proposals.

[[File:ICI-CPQ functional diagram.PNG|upright|ICI-CPQ functional diagram.PNG]]

The Lead-to-Cash process starts with generating leads, capturing the prospect, creating an opportunity, and assigning the appropriate stage. A preapproved NDA can be shared with the customer for signature, leveraging digital signature applications such as AdobeSign or DocuSign. After the quote is reviewed with the client and approved internally, a contract can be created automatically in ICI. Relevant data from customer accounts and quotes are utilized to create the contract. To know more, see [https://help.sap.com/docs/SAP_CX/fe1b9a180649472eb58843ec01732ed9/03559e96735249e7bd37929f1f387b85.html Lead-to-cash Process].

In large enterprise functional landscape, SAP S/4HANA acts as a single source of truth for Business Partner and Product master data. Sell-side systems sync customer information and orderable product information from SAP S/4HANA. End-to-end integrated journeys for Lead-to-Cash from SAP CPQ to ICI to S/4HANA require Business Partner and Product data to be synced from SAP S/4HANA to SAP CPQ and ICI. Master data sync is one of the prerequisites for accurate and consistent data availability across the systems to ensure smooth functional flows and user journeys. To know more, [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration click here].

The following image shows the functional flow of the adapter.

[[File:ICI CPQImg1.PNG|700px|ICI CPQImg1.PNG]]

 

 

'''Note:''' The ICI for SAP CPQ with SAP S/4HANA (Sell side) Adapter is supported with ICI version 8.2 onwards.

 

 

== Benefits ==

*Reduce the lead-to-cash cycle time<br/> Seamlessly integrate customer and pricing data from SAP CPQ into ICI to quickly and accurately create contracts that reference the agreed pricing terms, promotions, incentives, and rebates when building contracts.
*Easily discover, monitor, and mitigate contract risk<br/> Discover risks caused by deviations from normal business practices to proactively identify and monitor business risk to reduce the impact on operational, financial, and reputational risk, contributing significantly to the company's bottom line.
*Collaborate on contracts seamlessly among all parties<br/> Reduce rework and improve customer satisfaction with accurate redlining, versioning, and approval workflows, reducing risk exposure for your company. Enable secure communication with suppliers, customers, and partners.
*Gain deeper insights into sales and contracts<br/> Manage agreements across multiple departments to gain deeper insights and align supplier and customer terms with AI-supported search, digitization, and negotiation.
*Reduce errors by ensuring data consistency<br/> Consistent data across systems ensure accuracy, which in turn reduces rework and improves customer satisfaction.
*Reduced time for data sync<br/> Seamlessly sync data from SAP S/4HANA into ICI quickly with real-time sync or at the desired frequency by setting periodic incremental sync.
*Extensibility offered with a solution<br/> As per implementation requirements, master data attributes can be added in ICI and mapping can be established to sync up the master data from SAP S/4HANA.

== Creating Contracts from Quotes ==

After integrating ICI with SAP CPQ, you can create contracts from quotes created in SAP CPQ. Once the contract is executed in ICI, you can either place the order for the related quote manually or configure auto-ordering for it.

 

=== Prerequisites ===

*Ensure that Customer (Business Partner) Master data present in ICI are in sync with Customer Master
*Ensure that Product Master data present in ICI are in sync with Product Master

For end-to-end integration having S/4HANA for Orders, Master Data Integration is available to sync the Customer (Business Partner) and Product Master data from S/4HANA to ICI.<br/> To know how to configure master data integration from SAP S/4HANA to ICI, [[ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration|click here]].

To complete the Quote to Order process, you need to perform the following steps:

#Create contract
#Execute contract
#Place Order

 

=== Create Contract ===

#Create a quote and add products.<br/> To know how to create a quote, see [https://help.sap.com/docs/SAP_CPQ/551616e85ad64739835aa69241222f53/12df2dee87b046ba8e585571cab4d231.html Quote Creation].
#Enter the '''Opportunity, Quote Name''', '''Effective Date''', '''Contract Term (Months)''', and '''Sold-to Party''' (Customer).<br/> Note that the '''Contract Link''' and '''Contract Number''' fields are read-only and don't contain any values.
#Once the commercials of the quote are finalized, change the status to '''Ready for Contracting'''.<br/> ICI checks for quotes in '''Ready for Contracting''' status and picks them for contract creation through seamless integration.<br/> When the quote is picked for contracting, the status changes to '''Contract Created'''.<br/> On the '''Additional Info''' tab, the contract link and contract number are now available.

 

=== Execute Contract ===

#Use the contact link on the '''Additional Info''' tab and navigate to the contract in ICI.<br/> The contract is in '''Draft''' status.
#Click on the '''Details''' tab in the left pane to see that the attribute values from the quote have been populated.
#Click the '''Associations''' tab in the left pane to see the line items from the quote and their details.<br/> To know how to create an association, see [https://iciwikiapac.icertis.com/ICIHelp8.1/index.php?title=Associations#Creating_associations_on_create.2Fedit_wizard_of_agreement Creating Associations.]
#To preview the contract, click '''Download''' > '''Assemble Contract''' and click the two-pane icon.<br/> This allows for a side-by-side comparison between the assembled contract and the details in the '''Default Agreement Dashboard'''. Attributes populated in the contract are highlighted.
#Send the contract for review and approval. <br/> To know more about the approval process in ICI, see [https://iciwikiapac.icertis.com/ICIHelp8.1/index.php?title=Send_the_Contract_Type_for_Approval Send the contract type for approval. ]
#Once the contract is approved, initiate external and internal signatures.<br/> Post signatures, the contract status is '''Executed'''.

 

=== Place Order ===

Place order action leverages SAP CPQ and SAP S/4HANA integration to send quote details to SAP S/4HANA for order placement.

From SAP S/4HANA, Solution Quote ID is updated back on SAP CPQ Quote as Sales Order ID.

*To place the order, on the '''Quotation''' tab, click the ellipsis icon > '''Place Order'''.

The Place Order action can be automated if auto-ordering is configured for the integration in ICI. The system invokes the '''Place Order''' action as soon as the contract is executed.

Place order action changes quote status to '''Order Confirmation Pending'''.

The quote status is displayed as follows:

*On successful order, the quote status gets updated to '''Order Placed''' through SAP CPQ – SAP S/4HANA integration.
*On order failure, the quote status gets updated to '''Order Failed''' through SAP CPQ – SAP S/4HANA integration.

 

== Configuration ==

For detailed information about the required configuration, click [[Media:ICI_SAP_CPQ_Adapter_Configuration_Guide.pdf|here]].

ICI for SAP CPQ

2023-01-06T18:01:15Z

WikiSysop:

 

 

 

= ICI for SAP CPQ and S/4HANA Lead to Cash Adapter =

== Overview ==

The ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter supports the quote-to-cash flow with a two-way integration between ICI and SAP CPQ. The adapter provides a personalized sales experience that helps accelerate the selling process. Preconfigured products and pricing models from SAP CPQ enable the sales organization to easily assemble a quote and improve operational efficiency. Preapproved legal templates and preconfigured workflows in ICI enable contract managers to quickly assemble and effectively negotiate contracts and thus reduce the contract time and risk.

SAP CPQ provides a rich customer experience by empowering sales teams and partners to easily offer complex product configurations, optimized pricing, and great-looking proposals.

[[File:ICI-CPQ functional diagram.PNG|upright]]

The Lead-to-Cash process starts with generating leads, capturing the prospect, creating an opportunity, and assigning the appropriate stage. A preapproved NDA can be shared with the customer for signature, leveraging digital signature applications such as AdobeSign or DocuSign. Once the quote is reviewed with the client and approved internally, a contract can be created automatically in ICI. Relevant data from customer accounts and quotes are utilized to create the contract.

In large enterprise functional landscape, SAP S/4HANA acts as a single source of truth for Business Partner and Product master data. Sell-side systems sync customer information and orderable product information from SAP S/4HANA. End-to-end integrated journeys for Lead-to-Cash from SAP CPQ to ICI to S/4HANA require Business Partner and Product data to be synced from SAP S/4HANA to SAP CPQ and ICI. Master data sync is one of the prerequisites for accurate and consistent data availability across the systems to ensure smooth functional flows and user journeys. To know more, [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration click here].

The following image shows the functional flow of the adapter.

[[File:ICI for SAP CPQ flowchart.png|upright|ICI for SAP CPQ flowchart.png]]

'''Note:''' The ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter is supported with ICI version 8.2 onwards.

 

== Benefits ==

*Reduce the lead-to-cash cycle time<br/> Seamlessly integrate customer and pricing data from SAP CPQ into ICI to quickly and accurately create contracts that reference the agreed pricing terms, promotions, incentives, and rebates when building contracts.
*Easily discover, monitor & mitigate contract risk<br/> Discover risks caused by deviations from normal business practices to proactively identify and monitor business risk to reduce the impact on operational, financial, and reputational risk, contributing significantly to the company's bottom line.
*Collaborate on contracts seamlessly among all parties<br/> Reduce rework and improve customer satisfaction with accurate redlining, versioning, and approval workflows, reducing risk exposure for your company. Enable secure communication with suppliers, customers, and partners.
*Gain deeper insights into sales and contracts<br/> Manage agreements across multiple departments to gain deeper insights and align supplier and customer terms with AI-supported search, digitization, and negotiation.
*Reduce errors by ensuring data consistency<br/> Consistent data across systems ensure accuracy, which in turn reduces rework and improves customer satisfaction.
*Reduced time for data sync<br/> Seamlessly sync data from SAP S/4HANA into ICI quickly with real-time sync or at the desired frequency by setting periodic incremental sync.
*Extensibility offered with a solution<br/> As per implementation requirements, master data attributes can be added in ICI and mapping can be established to sync up the master data from SAP S/4HANA.

== Prerequisites ==

=== SAP CPQ Side ===

ICI for SAP CPQ and S/4HANA Lead to Cash Adapter integrates with SAP CPQ by leveraging SAP CPQ Quote 2.0 REST APIs. Before calling SAP CPQ REST endpoints, the below-mentioned prerequisites must be satisfied:

*An SAP CPQ Quote 2.0 tenant with its URL is shared with the ICI team.
*Create an integration user account in SAP CPQ and add the user to the '''Sales''' user group. This user will be used to authenticate all the REST API calls.
*SAP CPQ configuration is completed as mentioned in the ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter configuration guide.
*SAP CPQ allows ICI Client to consume their APIs.

 

=== ICI Configuration Side ===

*Create ICI entities  
*Map attributes for ICI entities (Client App Cross Reference and Client App Entity Mapping)  
*Create filters in the Client App Filter Condition  
*Store SAP CPQ API connection information in the Azure Key Vault    
*Import the required SAP CPQ contracts master data to ICI 
*Provision SAP CPQ contracts users in ICI 
*Configure the ICI environment with master data contract types for the following entities and required attributes.
**Customer
**Product<br/> Customer and Product master data is either synced through master data integration or is set up in ICI.

== Creating Contracts from Quotes ==

After integrating ICI with SAP CPQ, you can create contracts for quotes created in SAP CPQ. Once the contract is executed in ICI, you can either place the order for the related quote manually or configure auto-ordering for it.

=== Prerequisites ===

*Ensure that Customer (Business Partner) Master data present in ICI are in sync with Customer Master.
*Ensure that Product Master data present in ICI are in sync with Product Master.

For end-to-end integration having S/4HANA for Orders, Master Data Integration is available to sync the Customer (Business Partner) and Product Master data from S/4HANA to ICI.<br/> To know how to configure master data integration from SAP S/4HANA to ICI, [[ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration|click here]].

To complete the Quote to Order process, you need to perform the following steps:

#Create contract
#Execute contract
#Place Order

=== Create Contract ===

#Create a quote and add products.<br/> To know how to create a quote, see [https://help.sap.com/docs/SAP_CPQ/551616e85ad64739835aa69241222f53/12df2dee87b046ba8e585571cab4d231.html Quote Creation].
#Enter the '''Opportunity, Quote Name''', '''Effective Date''', '''Contract Term (Months)''', and '''Sold-to Party''' (Customer).<br/> Note that the '''Contract Link''' and '''Contract Number''' fields are empty.
#Once the commercials of the quote are finalized, change the status to '''Ready for Contracting'''.<br/> When the quote is picked for contracting, the status changes to '''Contract Created'''.<br/> On the '''Additional Info''' tab, the contract link and contract number are now available.

 

=== Execute Contract ===

#Use the contact link on the '''Additional Info''' tab and navigate to the contract in ICI.<br/> The contract is in '''Draft''' status.
#Click on the '''Details''' tab in the left pane to see that the attribute values from the quote have been populated.
#Click the '''Associations''' tab in the left pane to see the line items from the quote and their details.
#To preview the contract, click '''Download''' > '''Assemble Contract''' and click the two-pane icon.<br/> This allows for a side-by-side comparison between the assembled contract and the details in the '''Default Agreement Dashboard'''. Attributes populated in the contract are highlighted.
#Send the contract for review and approval.
#Once the contract is approved, initiate external and internal signatures.<br/> Post signatures, the contract status is '''Executed'''.

=== Place Order ===

#To place the order, on the '''Quotation''' tab, click the ellipsis icon > '''Place Order'''.<br/> This can be automated if auto-ordering is configured for the integration in ICI. The system invokes the '''Place Order''' action as soon as the contract is executed.
#Place order action changes quote status to '''Order Confirmation Pending'''.
#Place order action leverages SAP CPQ and SAP S/4HANA integration to send quote details to SAP S/4HANA for order placement.
#From SAP S/4HANA, Solution Quote ID is updated back on SAP CPQ Quote as Sales Order ID.
#On successful order, the quote status gets updated to '''Order Placed''' through SAP CPQ – SAP S/4HANA integration.
#On order failure, the quote status gets updated to '''Order Failed''' through SAP CPQ – SAP S/4HANA integration.

 

== Configuration ==

For detailed information about the required configuration, click [[Media:ICI_SAP_CPQ_Adapter_Configuration_Guide.pdf|here]].

File:ICI-CPQ functional diagram.PNG

2023-01-06T18:00:09Z

WikiSysop:

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2023-01-06T07:52:02Z

WikiSysop:

 

 

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication, Integration, and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI). To know more, see [[ICI_for_SAP_CPQ|ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter]].

'''Note''': If you are using ICI version 8.3 or later, to access the latest information for ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter, click the help icon from the product UI.

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/> To know more, see [https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549/236d552f22654f759b5533b2d22ecbb3.html?q=Direct%20output#data-replication-using-soa-with-data-replication-framework-(drf) Data Replication Using SOA With Data Replication Framework (DRF)].

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

 

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

 

 

=== View Prepackaged iFlows using SAP Cloud Integration (CI) ===

#Access the SAP Cloud Integration Web UI.<br/> It should be in the following format: [ http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''''.''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example,  '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, choose '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the integration package copied in the Configure and Deploy the iFlow using SAP Cloud Integration section.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP Ariba Strategic Sourcing

2023-01-05T19:55:30Z

WikiSysop:

= ICI for SAP Ariba Strategic Sourcing =

== Overview ==

'''Icertis Contract Intelligence (ICI) integration with SAP Ariba Contracts'''

The Icertis Contract Intelligence (ICI) for SAP Ariba Contracts integration provides organizations an intelligent and flexible contracting platform leveraging 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 the revenue. 
*Lack of insights from contract data leads to limited visibility to enforce performance. 
*Security, risk, and compliance helps to safeguard the brand and intellectual property rights. 

The ICI for SAP Ariba adapter provides the following capabilities.<br/>  
<div class="image-green-border">[[File:Sa1.png|upright]]</div>
 

The diagram above depicts how the end-to-end source to contract business flow can be orchestrated leveraging the ICI for SAP Ariba Contracts integration.  

*A contract manager can create a standalone SAP Ariba Contract Workspace (ACW) or a corresponding ACW from SAP Ariba Contract Request. 
*A contract manager can also create an SAP Ariba Contract Workspace while awarding a sourcing event. 
*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 ACW, provide minimal information, and initiate authoring in ICI. You can leverage ICI’s AI capabilities to extract metadata and clauses for ease of redlining. ICI assembles the legal language based on predefined legal template and rules.

*'''Repository Contract'''

A contract manager can easily manage signed PDF contracts by uploading it directly to the ACW and publishing it. The solution automatically creates an executed agreement in ICI.

*'''Contract Review, Approval, Signature, and Execution'''

ICI capabilities around contract redlining (such as Microsoft Word Experience, online editing), approval, signature can streamline the process with proper governance. Once executed, the metadata along with a signed PDF can is synced back in 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 ACW. 

*'''Supplier Master Data'''

 You can also synch supplier master data from SAP Ariba Contracts to ICI.

*'''Auto-link sub-agreement to a Master Agreement'''

You can create a sub-agreement in ACW for an existing master agreement that is interfaced with ICI. The system creates a corresponding child agreement in ICI and auto-links it to its parent agreement.

The following data is synchronized between ICI and SAP Ariba Contracts.  

*Agreement data  
*Agreement document data 
*Agreement team data 
*Supplier master data

 

== 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.<br/>  
*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.<br/>  
*Effectively manage legal and business risk: preapproved legal templates, predefined corporate policies, and constant monitoring of contractual obligations and SLAs (Service Level Agreement) enable organizations to effectively manage legal and business risks.

== Prerequisites ==

The ICI SAP Ariba Adapter is supported with ICI versions 8.2.1, 8.2.0, 8.1.4, 8.1.3, and 8.1.2.  Ensure that the following prerequisites are met:

*SAP Ariba Contracts prerequisites 
**Use the REST API collection to integrate SAP Ariba Contract Workspaces (ACW), SAP Ariba Documents, and SAP Ariba Team. 
**The SAP Ariba REST APIs are configured with API rate limit values to make uninterrupted API calls for data syncing.  
**Task Service is up and running  
**Required events and jobs are enabled  
**SAP Ariba Contracts allows ICI Client to consume their APIs  

'''Note:''' To know more about the SAP Ariba prerequisites, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/a1709b3b0a824b018577e0add8d1b27a.html here].  

*ICI configuration prerequisites 
**Creating ICI entities  
**Mapping attributes for ICI entities (Client App Cross Reference and Client App Entity Mapping)  
**Creating filters in the Client App Filter Condition  
**Defining Date Filter criteria in the Client App Master data Sync for field: Effective Date  
**Storing SAP Ariba API connection information in the Azure Key Vault    
**The required SAP Ariba Contracts master data is imported to ICI – ICI side 
**SAP Ariba Contracts users are provisioned in ICI 
**SAP Ariba Contracts IDP integration is configured in ICI 

'''Note:''' Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the '''ICI for SAP Ariba''' adapter.

= 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.

[[File:Sa14.PNG|upright]]

 

=== Creating a Contract Using Executed Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=9 edit]] ===

1. Create a Contract Workspace in SAP Ariba Contracts in the '''Draft''' status.
<div class="image-green-border">[[File:Sa2.png|upright]]</div>
2. 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.
<div class="image-green-border">[[File:Sa15.png|upright]]</div>
3. To publish the agreement, click '''Actions '''> '''Publish '''in ACW.
<div class="image-green-border">[[File:Sa3.png|upright]]</div>
'''Note''': To know more about the standard Ariba Contract Workspace creation process, click [https://help.sap.com/docs/ARIBA_SOURCING/fa6038501b9b4b548e7a7628356e33ca/7cd9712c71ea1014a8d3d6cf4fe940c0.html here].

4. To open the ICI equivalent agreement, click the link in the '''External ID''' column (for example: ICMNDA_82).
<div class="image-green-border">[[File:Sa4.png|upright]]</div>
5. To view the SAP Ariba information in ICI, click '''''Details '''''> '''A''riba Information.'''''
<div class="image-green-border">[[File:Sa5.png|upright]]</div>
6. To view the owners of the agreement, on the left navigation pane, click '''Team'''.
<div class="image-green-border">[[File:Sa6.png|upright]]</div>
 

7. To view the contract details, click '''Details''' > '''General Information'''.
<div class="image-green-border">[[File:Sa16.png|upright]]</div>
 

8. To navigate back to the ACW, click '''Details''' > '''Ariba CW Link'''.
<div class="image-green-border">[[File:Sa7.png|upright]]</div>
9. The ACW now shows both the '''ACW ID''' and the '''Icertis ID'''.
<div class="image-green-border">[[File:Sa8.png|upright]]</div>

=== Managing Contracts Created Using Own or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=10 edit]] ===

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 by the supplier

The following diagram explains the contract initiation to contract execution process.
<div class="image-green-border">[[File:Flowchart 1v2.png|upright]]</div>
 

=== Creating a Contract Using Own Paper or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=11 edit]] ===

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.

After the contract is executed in ICI, the ACW is published automatically.

=== Managing contracts in unique scenarios[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=12 edit]] ===

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.

[[File:SAP Ariba Contract not initiated.png|upright]]

 

=== 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

[[File:CLID 1.PNG|upright]]

 

*Contract authoring is already initiated

[[File:CLID 2.PNG|upright]]

 

== Working with Amendments[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=14 edit]] ==

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

SAP Ariba supports five amendment types, please find the details below along with respective impact in ICI:

*Amendment: This amendment type allows to change any part of the Contract. In this case, an amendment agreement will be generated at ICI side and interfaced back to SAP Ariba.
*Renewal: This amendment type allows to change effective, expiration dates along with many other attributes of the contract. It’s recommended to use ‘Amendment’ option for all such changes
*Termination: This amendment type is used to close a contract before its expiration date. In this case the contract will be terminated at Ariba side and Ariba contract status will be stored in an ICI attribute.
*Administrative: This amendment type is used for change in non-contract fields like Name, Description etc. In this case the main agreement will be updated at Ariba and ICI side.
*Price Update: This amendment type allows to change existing items along with many other attributes. It’s recommended to use ‘Amendment’ option for all such changes.

 

'''Prerequisite'''

The ACW must be created, and the contract should be 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.
<div class="image-green-border">[[File:Sa11.png|upright|Sa11.png]]</div>
6. Enter the details and click '''Create'''. The amendment record is created.
<div class="image-green-border">[[File:Sa12.png|upright|Sa12.png]]</div>
Like agreements, a unique amendment ID is created and is synched back in ACW. The amendment is created in the '''Draft''' status.

Once the amendment is executed in ICI, the amendment is auto-published in ACW.

'''Note the following important points'''

*An ICI amendment record is created against the amendment of  a Ariba Contract workspace (ACW) · 
*An ICI amendment records goes through the same process of an agreement.
*The History tab shows the old values and the new values for all changed attributes.

== Configuration[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=15 edit]] ==

=== SAP Ariba Contracts Side configurations ===

To know more on SAP Ariba Contracts side configurations, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/79e20b26eabc4af0a486acd8818877d5.html here].

=== ICI Side configurations  ===

Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the ICI for SAP Ariba adapter.

== Glossary ==

 

{| align="left" border="1" cellpadding="1" cellspacing="1" style="width: 650px;"
|-
! scope="col" | ICI Terminology
! scope="col" | SAP Ariba Contract Terminology
! scope="col" | Description
|-
| Agreement
| Ariba Contract Workspace (ACW)
| A legally binding contract, where all information and supporting documents are recorded.
|-
| Own Paper
| NA
| A type of paper used while creating an agreement. Own paper indicates using the organization's template to create an agreement.
|-
| Third-party paper
| NA
| A type of paper used while creating an agreement. Third-party paper indicates using an external or third-party template to create an agreement.
|-
| Executed paper
| NA
| Indicates an agreement that is created offline and uploaded to the system. The signature action for this type of agreement can be performed offline or in the system.
|}

 

 

 

 

 

 

 

 

 

 

'''Related Topics''': [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Working_with_Agreements Agreement Management]

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-15T09:56:09Z

WikiSysop:

 

 

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication, Integration, and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI). To know more, see [[ICI_for_SAP_CPQ|ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter]].

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/> To know more, see [https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549/236d552f22654f759b5533b2d22ecbb3.html?q=Direct%20output#data-replication-using-soa-with-data-replication-framework-(drf) Data Replication Using SOA With Data Replication Framework (DRF)].

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

 

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

 

 

=== View Prepackaged iFlows using SAP Cloud Integration (CI) ===

#Access the SAP Cloud Integration Web UI.<br/> It should be in the following format: [ http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''''.''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example,  '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, choose '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the integration package copied in the Configure and Deploy the iFlow using SAP Cloud Integration section.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-15T09:51:54Z

WikiSysop:

 

 

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI). To know more, see [[ICI_for_SAP_CPQ|ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter]].

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/> To know more, see [https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549/236d552f22654f759b5533b2d22ecbb3.html?q=Direct%20output#data-replication-using-soa-with-data-replication-framework-(drf) Data Replication Using SOA With Data Replication Framework (DRF)].

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

 

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

 

=== View Prepackaged iFlows using SAP Cloud Integration (CI) ===

#Access the SAP Cloud Integration Web UI.<br/> It should be in the following format: [ http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''''.''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example,  '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, choose '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the integration package copied in the Configure and Deploy the iFlow using SAP Cloud Integration section.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-15T09:51:33Z

WikiSysop:

 

 

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI). To know more, see [[ICI_for_SAP_CPQ|ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter]].

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/> To know more, see [https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549/236d552f22654f759b5533b2d22ecbb3.html?q=Direct%20output#data-replication-using-soa-with-data-replication-framework-(drf) Data Replication Using SOA With Data Replication Framework (DRF)].

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

 

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

 

=== View Prepackaged iFlows using SAP Cloud Integration (CI) ===

#Access the SAP Cloud Integration Web UI.<br/> It should be in the following format: [ http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash''''''.''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example,  '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, choose '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the integration package copied in the Configure and Deploy the iFlow using SAP Cloud Integration section.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-15T09:39:28Z

WikiSysop:

 

 

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI). To know more, see [[ICI_for_SAP_CPQ|ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter]].

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/> To know more, see [https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549/236d552f22654f759b5533b2d22ecbb3.html?q=Direct%20output#data-replication-using-soa-with-data-replication-framework-(drf) Data Replication Using SOA With Data Replication Framework (DRF)].

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

 

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

 

=== View Prepackaged iFlows using SAP Cloud Integration (CI) ===

#Access the SAP Cloud Integration Web UI.<br/> It should be in the following format: [ http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash''''''.'''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example,  '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, choose '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the integration package copied in the Configure and Deploy the iFlow using SAP Cloud Integration section.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ

2022-12-15T08:29:43Z

WikiSysop:

 

 

= ICI for SAP CPQ and S/4HANA Lead to Cash Adapter =

== Overview ==

The ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter supports the quote-to-cash flow with a two-way integration between ICI and SAP CPQ. The adapter provides a personalized sales experience that helps accelerate the selling process. Preconfigured products and pricing models from SAP CPQ enable the sales organization to easily assemble a quote and improve operational efficiency. Preapproved legal templates and preconfigured workflows in ICI enable contract managers to quickly assemble and effectively negotiate contracts and thus reduce the contract time and risk.

SAP CPQ provides a rich customer experience by empowering sales teams and partners to easily offer complex product configurations, optimized pricing, and great-looking proposals.

[[File:Integration process.png|RTENOTITLE]]

The Lead-to-Cash process starts with generating leads, capturing the prospect, creating an opportunity, and assigning the appropriate stage. A preapproved NDA can be shared with the customer for signature, leveraging digital signature applications such as AdobeSign or DocuSign. Once the quote is reviewed with the client and approved internally, a contract can be created automatically in ICI. Relevant data from customer accounts and quotes are utilized to create the contract.

In large enterprise functional landscape, SAP S/4HANA acts as a single source of truth for Business Partner and Product master data. Sell-side systems sync customer information and orderable product information from SAP S/4HANA. End-to-end integrated journeys for Lead-to-Cash from SAP CPQ to ICI to S/4HANA require Business Partner and Product data to be synced from SAP S/4HANA to SAP CPQ and ICI. Master data sync is one of the prerequisites for accurate and consistent data availability across the systems to ensure smooth functional flows and user journeys. To know more, [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration click here].

The following image shows the functional flow of the adapter.

[[File:ICI for SAP CPQ flowchart.png|upright|ICI for SAP CPQ flowchart.png]]

'''Note:''' The ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter is supported with ICI version 8.2 onwards.

 

== Benefits ==

*Reduce the lead-to-cash cycle time<br/> Seamlessly integrate customer and pricing data from SAP CPQ into ICI to quickly and accurately create contracts that reference the agreed pricing terms, promotions, incentives, and rebates when building contracts.
*Easily discover, monitor & mitigate contract risk<br/> Discover risks caused by deviations from normal business practices to proactively identify and monitor business risk to reduce the impact on operational, financial, and reputational risk, contributing significantly to the company's bottom line.
*Collaborate on contracts seamlessly among all parties<br/> Reduce rework and improve customer satisfaction with accurate redlining, versioning, and approval workflows, reducing risk exposure for your company. Enable secure communication with suppliers, customers, and partners.
*Gain deeper insights into sales and contracts<br/> Manage agreements across multiple departments to gain deeper insights and align supplier and customer terms with AI-supported search, digitization, and negotiation.
*Reduce errors by ensuring data consistency<br/> Consistent data across systems ensure accuracy, which in turn reduces rework and improves customer satisfaction.
*Reduced time for data sync<br/> Seamlessly sync data from SAP S/4HANA into ICI quickly with real-time sync or at the desired frequency by setting periodic incremental sync.
*Extensibility offered with a solution<br/> As per implementation requirements, master data attributes can be added in ICI and mapping can be established to sync up the master data from SAP S/4HANA.

== Prerequisites ==

=== SAP CPQ Side ===

ICI for SAP CPQ and S/4HANA Lead to Cash Adapter integrates with SAP CPQ by leveraging SAP CPQ Quote 2.0 REST APIs. Before calling SAP CPQ REST endpoints, the below-mentioned prerequisites must be satisfied:

*An SAP CPQ Quote 2.0 tenant with its URL is shared with the ICI team.
*Create an integration user account in SAP CPQ and add the user to the '''Sales''' user group. This user will be used to authenticate all the REST API calls.
*SAP CPQ configuration is completed as mentioned in the ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter configuration guide.
*SAP CPQ allows ICI Client to consume their APIs.

 

=== ICI Configuration Side ===

*Create ICI entities  
*Map attributes for ICI entities (Client App Cross Reference and Client App Entity Mapping)  
*Create filters in the Client App Filter Condition  
*Store SAP CPQ API connection information in the Azure Key Vault    
*Import the required SAP CPQ contracts master data to ICI 
*Provision SAP CPQ contracts users in ICI 
*Configure the ICI environment with master data contract types for the following entities and required attributes.
**Customer
**Product<br/> Customer and Product master data is either synced through master data integration or is set up in ICI.

== Creating Contracts from Quotes ==

After integrating ICI with SAP CPQ, you can create contracts for quotes created in SAP CPQ. Once the contract is executed in ICI, you can either place the order for the related quote manually or configure auto-ordering for it.

=== Prerequisites ===

*Ensure that Customer (Business Partner) Master data present in ICI are in sync with Customer Master.
*Ensure that Product Master data present in ICI are in sync with Product Master.

For end-to-end integration having S/4HANA for Orders, Master Data Integration is available to sync the Customer (Business Partner) and Product Master data from S/4HANA to ICI.<br/> To know how to configure master data integration from SAP S/4HANA to ICI, [[ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration|click here]].

To complete the Quote to Order process, you need to perform the following steps:

#Create contract
#Execute contract
#Place Order

=== Create Contract ===

#Create a quote and add products.<br/> To know how to create a quote, see [https://help.sap.com/docs/SAP_CPQ/551616e85ad64739835aa69241222f53/12df2dee87b046ba8e585571cab4d231.html Quote Creation].
#Enter the '''Opportunity, Quote Name''', '''Effective Date''', '''Contract Term (Months)''', and '''Sold-to Party''' (Customer).<br/> Note that the '''Contract Link''' and '''Contract Number''' fields are empty.
#Once the commercials of the quote are finalized, change the status to '''Ready for Contracting'''.<br/> When the quote is picked for contracting, the status changes to '''Contract Created'''.<br/> On the '''Additional Info''' tab, the contract link and contract number are now available.

 

=== Execute Contract ===

#Use the contact link on the '''Additional Info''' tab and navigate to the contract in ICI.<br/> The contract is in '''Draft''' status.
#Click on the '''Details''' tab in the left pane to see that the attribute values from the quote have been populated.
#Click the '''Associations''' tab in the left pane to see the line items from the quote and their details.
#To preview the contract, click '''Download''' > '''Assemble Contract''' and click the two-pane icon.<br/> This allows for a side-by-side comparison between the assembled contract and the details in the '''Default Agreement Dashboard'''. Attributes populated in the contract are highlighted.
#Send the contract for review and approval.
#Once the contract is approved, initiate external and internal signatures.<br/> Post signatures, the contract status is '''Executed'''.

=== Place Order ===

#To place the order, on the '''Quotation''' tab, click the ellipsis icon > '''Place Order'''.<br/> This can be automated if auto-ordering is configured for the integration in ICI. The system invokes the '''Place Order''' action as soon as the contract is executed.
#Place order action changes quote status to '''Order Confirmation Pending'''.
#Place order action leverages SAP CPQ and SAP S/4HANA integration to send quote details to SAP S/4HANA for order placement.
#From SAP S/4HANA, Solution Quote ID is updated back on SAP CPQ Quote as Sales Order ID.
#On successful order, the quote status gets updated to '''Order Placed''' through SAP CPQ – SAP S/4HANA integration.
#On order failure, the quote status gets updated to '''Order Failed''' through SAP CPQ – SAP S/4HANA integration.

 

== Configuration ==

For detailed information about the required configuration, click [[Media:ICI_SAP_CPQ_Adapter_Configuration_Guide.pdf|here]].

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-15T07:33:13Z

WikiSysop:

 

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI). To know more, see [[ICI_for_SAP_CPQ|ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter]].

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/> To know more, see 

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

 

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

 

=== View Prepackaged iFlows using SAP Cloud Integration (CI) ===

#Access the SAP Cloud Integration Web UI.<br/> It should be in the following format: [ http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash''''''.'''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example,  '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, choose '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the integration package copied in the Configure and Deploy the iFlow using SAP Cloud Integration section.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-15T07:30:10Z

WikiSysop:

 

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI).

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/> To know more, see 

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

 

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

 

=== View Prepackaged iFlows using SAP Cloud Integration (CI) ===

#Access the SAP Cloud Integration Web UI.<br/> It should be in the following format: [ http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash''''''.'''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example,  '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, choose '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the integration package copied in the Configure and Deploy the iFlow using SAP Cloud Integration section.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-15T07:28:18Z

WikiSysop:

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI).

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/> To know more, see 

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries
*
To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

 

=== View Prepackaged iFlows using SAP Cloud Integration (CI) ===

#Access the SAP Cloud Integration Web UI.<br/> It should be in the following format: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash''''''.'''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example,  '''Icertis Contract Intelligence Integration with SAP CPQ and S/4HANA Lead to Cash'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, choose '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the integration package copied in the Configure and Deploy the iFlow using SAP Cloud Integration section.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the '''Actions''' symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ

2022-12-15T06:55:44Z

WikiSysop:

 

 

= ICI for SAP CPQ and S/4HANA Lead to Cash Adapter =

== Overview ==

The ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter supports the quote-to-cash flow with a two-way integration between ICI and SAP CPQ. The adapter provides a personalized sales experience that helps accelerate the selling process. Preconfigured products and pricing models from SAP CPQ enable the sales organization to easily assemble a quote and improve operational efficiency. Preapproved legal templates and preconfigured workflows in ICI enable contract managers to quickly assemble and effectively negotiate contracts and thus reduce the contract time and risk.

SAP CPQ provides a rich customer experience by empowering sales teams and partners to easily offer complex product configurations, optimized pricing, and great-looking proposals.

[[File:Integration process.png|RTENOTITLE]]

The Lead-to-Cash process starts with generating leads, capturing the prospect, creating an opportunity, and assigning the appropriate stage. A preapproved NDA can be shared with the customer for signature, leveraging digital signature applications such as AdobeSign or DocuSign. Once the quote is reviewed with the client and approved internally, a contract can be created automatically in ICI. Relevant data from customer accounts and quotes are utilized to create the contract.

The following image shows the functional flow of the adapter.

[[File:ICI for SAP CPQ flowchart.png|upright|ICI for SAP CPQ flowchart.png]]

'''Note:''' The ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter is supported with ICI version 8.2 onwards.

 

== Benefits ==

*Reduce the lead-to-cash cycle time<br/> Seamlessly integrate customer and pricing data from SAP CPQ into ICI to quickly and accurately create contracts that reference the agreed pricing terms, promotions, incentives, and rebates when building contracts.
*Easily discover, monitor & mitigate contract risk<br/> Discover risks caused by deviations from normal business practices to proactively identify and monitor business risk to reduce the impact on operational, financial, and reputational risk, contributing significantly to the company's bottom line.
*Collaborate on contracts seamlessly among all parties<br/> Reduce rework and improve customer satisfaction with accurate redlining, versioning, and approval workflows, reducing risk exposure for your company. Enable secure communication with suppliers, customers, and partners.
*Gain deeper insights into sales and contracts<br/> Manage agreements across multiple departments to gain deeper insights and align supplier and customer terms with AI-supported search, digitization, and negotiation.
*Reduce errors by ensuring data consistency<br/> Consistent data across systems ensure accuracy, which in turn reduces rework and improves customer satisfaction.
*Reduced time for data sync<br/> Seamlessly sync data from SAP S/4HANA into ICI quickly with real-time sync or at the desired frequency by setting periodic incremental sync.
*Extensibility offered with a solution<br/> As per implementation requirements, master data attributes can be added in ICI and mapping can be established to sync up the master data from SAP S/4HANA.

== Prerequisites ==

=== SAP CPQ Side ===

ICI for SAP CPQ and S/4HANA Lead to Cash Adapter integrates with SAP CPQ by leveraging SAP CPQ Quote 2.0 REST APIs. Before calling SAP CPQ REST endpoints, the below-mentioned prerequisites must be satisfied:

*An SAP CPQ Quote 2.0 tenant with its URL is shared with the ICI team.
*Create an integration user account in SAP CPQ and add the user to the '''Sales''' user group. This user will be used to authenticate all the REST API calls.
*SAP CPQ configuration is completed as mentioned in the ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter configuration guide.
*SAP CPQ allows ICI Client to consume their APIs.

 

=== ICI Configuration Side ===

*Create ICI entities  
*Map attributes for ICI entities (Client App Cross Reference and Client App Entity Mapping)  
*Create filters in the Client App Filter Condition  
*Store SAP CPQ API connection information in the Azure Key Vault    
*Import the required SAP CPQ contracts master data to ICI 
*Provision SAP CPQ contracts users in ICI 
*Configure the ICI environment with master data contract types for the following entities and required attributes.
**Customer
**Product<br/> Customer and Product master data is either synced through master data integration or is set up in ICI.

== Creating Contracts from Quotes ==

After integrating ICI with SAP CPQ, you can create contracts for quotes created in SAP CPQ. Once the contract is executed in ICI, you can either place the order for the related quote manually or configure auto-ordering for it.

=== Prerequisites ===

*Ensure that Customer (Business Partner) Master data present in ICI are in sync with Customer Master.
*Ensure that Product Master data present in ICI are in sync with Product Master.

For end-to-end integration having S/4HANA for Orders, Master Data Integration is available to sync the Customer (Business Partner) and Product Master data from S/4HANA to ICI.<br/> To know how to configure master data integration from SAP S/4HANA to ICI, [[ICI_for_SAP_CPQ_and_S4/HANA_Lead_to_Cash_Adapter_Replication_Integration_and_Configuration|click here]].

To complete the Quote to Order process, you need to perform the following steps:

#Create contract
#Execute contract
#Place Order

=== Create Contract ===

#Create a quote and add products.<br/> To know how to create a quote, see [https://help.sap.com/docs/SAP_CPQ/551616e85ad64739835aa69241222f53/12df2dee87b046ba8e585571cab4d231.html Quote Creation].
#Enter the '''Opportunity, Quote Name''', '''Effective Date''', '''Contract Term (Months)''', and '''Sold-to Party''' (Customer).<br/> Note that the '''Contract Link''' and '''Contract Number''' fields are empty.
#Once the commercials of the quote are finalized, change the status to '''Ready for Contracting'''.<br/> When the quote is picked for contracting, the status changes to '''Contract Created'''.<br/> On the '''Additional Info''' tab, the contract link and contract number are now available.

 

=== Execute Contract ===

#Use the contact link on the '''Additional Info''' tab and navigate to the contract in ICI.<br/> The contract is in '''Draft''' status.
#Click on the '''Details''' tab in the left pane to see that the attribute values from the quote have been populated.
#Click the '''Associations''' tab in the left pane to see the line items from the quote and their details.
#To preview the contract, click '''Download''' > '''Assemble Contract''' and click the two-pane icon.<br/> This allows for a side-by-side comparison between the assembled contract and the details in the '''Default Agreement Dashboard'''. Attributes populated in the contract are highlighted.
#Send the contract for review and approval.
#Once the contract is approved, initiate external and internal signatures.<br/> Post signatures, the contract status is '''Executed'''.

=== Place Order ===

#To place the order, on the '''Quotation''' tab, click the ellipsis icon > '''Place Order'''.<br/> This can be automated if auto-ordering is configured for the integration in ICI. The system invokes the '''Place Order''' action as soon as the contract is executed.
#Place order action changes quote status to '''Order Confirmation Pending'''.
#Place order action leverages SAP CPQ and SAP S/4HANA integration to send quote details to SAP S/4HANA for order placement.
#From SAP S/4HANA, Solution Quote ID is updated back on SAP CPQ Quote as Sales Order ID.
#On successful order, the quote status gets updated to '''Order Placed''' through SAP CPQ – SAP S/4HANA integration.
#On order failure, the quote status gets updated to '''Order Failed''' through SAP CPQ – SAP S/4HANA integration.

 

== Configuration ==

For detailed information about the required configuration, click [[Media:ICI_SAP_CPQ_Adapter_Configuration_Guide.pdf|here]].

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-15T06:37:02Z

WikiSysop:

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI).

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/>  

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*SAP CPQ
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

*Contact the Network Security team to prepare the network environment across different systems and set its security aspects.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

== Configuration in SAP CPQ ==

*Complete the configuration steps from the SAP CPQ side.
*Synchronize S/4HANA Business Partners and Products with SAP CPQ.

 

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*Create contract types for holding all master data information.

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

=== View Prepackaged iFlows using SAP Cloud Integration ===

#Access the SAP CI (Cloud Integration) Web UI from the provisioning e-mail.<br/> It should be in the following format: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows delivered by SAP.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''SAP S/4HANA - ICI - Masterdata Integration - L2C.'''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example, '''SAP S/4HANA - ICI - Masterdata Integration - L2C'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, click '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the copied integration package.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the Actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-14T17:34:17Z

WikiSysop:

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI).

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/>  

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*SAP CPQ
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

*Contact the Network Security team to prepare the network environment across different systems and set its security aspects.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure the Masterdata contract type, see [[Masterdata|Masterdata]].

== Configuration in SAP CPQ ==

*Complete the configuration steps from the SAP CPQ side.
*Synchronize S/4HANA Business Partners and Products with SAP CPQ.

 

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*Create contract types for holding all master data information.

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

=== View Prepackaged iFlows using SAP Cloud Integration ===

#Access the SAP CI (Cloud Integration) web UI from the provisioning e-mail.<br/> It should be in the following format: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows delivered by SAP.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''SAP S/4HANA - ICI - Masterdata Integration - L2C.'''
#To view all the artifacts of the package, click '''Artifacts.'''

 

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example, '''SAP S/4HANA - ICI - Masterdata Integration - L2C'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, click '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the copied integration package.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the Actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-14T17:33:04Z

WikiSysop:

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI).

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/>  

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*SAP CPQ
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

*Contact the Network Security team to prepare the network environment across different systems and set its security aspects.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure Masterdata contract type, see [[Masterdata]].

== Configuration in SAP CPQ ==

*Complete the configuration steps from the SAP CPQ side.
*Synchronize S/4HANA Business Partners and Products with SAP CPQ.

 

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*Create contract types for holding all master data information.

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

=== View Prepackaged iFlows using SAP Cloud Integration ===

#Access the SAP CI (Cloud Integration) web UI from the provisioning e-mail.<br/> It should be in the following format: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows delivered by SAP.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''SAP S/4HANA - ICI - Masterdata Integration - L2C.'''
#To view all the artifacts of the package, click '''Artifacts.'''

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example, '''SAP S/4HANA - ICI - Masterdata Integration - L2C'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, in the top right corner, click '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package or overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the copied integration package.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the Actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from'''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-14T17:31:49Z

WikiSysop:

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI).

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/>  

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*SAP CPQ
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

*Contact the Network Security team to prepare the network environment across different systems and set its security aspects.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure Masterdata contract type, see [[Masterdata]].

== Configuration in SAP CPQ ==

*Complete the configuration steps from the SAP CPQ side.
*Synchronize S/4HANA Business Partners and Products with SAP CPQ.

 

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*Create contract types for holding all master data information.

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

=== View Prepackaged iFlows using SAP Cloud Integration ===

#Access the SAP CI (Cloud Integration) web UI from the provisioning e-mail.<br/> It should be in the following format: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows delivered by SAP.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''SAP S/4HANA - ICI - Masterdata Integration - L2C.'''
#To view all the artifacts of the package, click '''Artifacts.'''

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example, '''SAP S/4HANA - ICI - Masterdata Integration - L2C'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, on top right corner, click '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package, or to overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select the '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from '''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the copied integration package.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the Actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from'''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-14T17:30:39Z

WikiSysop:

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the master data integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using SAP Cloud Integration.

This master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI).

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)<br/>  

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*SAP CPQ
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA with ICI.

*Contact the Network Security team to prepare the network environment across different systems and set its security aspects.
*ICI environment should be configured with Masterdata contract type for the following entities:
**Customer
**Product
**Countries

To know how to configure Masterdata contract type, see [[Masterdata]].

== Configuration in SAP CPQ ==

*Complete the configuration steps from the SAP CPQ side.
*Synchronize S/4HANA Business Partners and Products with SAP CPQ.

 

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*Create contract types for holding all master data information.

== Configuration in SAP Cloud Integration ==

To use the iFlow (Integration Flow), you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving systems. To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/368c481cd6954bdfa5d0435479fd4eaf/e5724cd84b854719973afe0356ea128b.html Getting Started with Integration Flow Development].

=== View Prepackaged iFlows using SAP Cloud Integration ===

#Access the SAP CI (Cloud Integration) web UI from the provisioning e-mail.<br/> It should be in the following format: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, view all prepackaged integration flows delivered by SAP.<br/> To know more, see [https://help.sap.com/docs/CLOUD_INTEGRATION/987273656c2f47d2aca4e0bfce26c594/bd2ed3ef889b4638b1bbf66608e47bef.html?q=Discover Working with Prepackaged Integration Content].
#Choose the package '''SAP S/4HANA - ICI - Masterdata Integration - L2C.'''
#To view all the artifacts of the package, click '''Artifacts.'''

=== Configure and Deploy the iFlow using SAP Cloud Integration ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example, '''SAP S/4HANA - ICI - Masterdata Integration - L2C'''.
#To view all the iFlows related to this integration package, choose '''Artifacts'''.
#To copy the package to the design area, on top right corner, click '''Copy'''.<br/> '''Note''': If the integration package is being created for the first time, you see the '''Integration Package Created''' message. If not, you see a dialog box asking you to either create a new copy of the package, or to overwrite the existing integration package content. Choose '''Overwrite'''.
#In the left navigation bar, select the '''Design''' mode.<br/> The package is now visible in the design area and can be configured.

=== Replicate Business Partners from SAP S/4HANA to ICI ===

#Select the integration package copied in the previous procedure.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#From the left navigation bar, choose '''Monitor'''
#Choose '''All '''from'''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

=== Replicate Products from SAP S/4HANA to ICI ===

#Select the copied integration package.
#To view the list of iFlows, choose the '''Artifacts''' tab of the package.
#Choose the Actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#After completing the configuration, choose '''Save'''.
#After completion of the configuration, choose '''Deploy'''.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#After all the above configurations are done, choose '''Deploy'''.
#From the left navigation bar, choose '''Monitor'''.
#Next, choose '''All '''from'''Manage Integration Content'''.
#Verify if the deployment was successful.<br/> The status should be '''Started''', and an endpoint URL is displayed.

Self-Serve Tools

2022-12-14T14:30:54Z

WikiSysop:

= Self-Serve Tools =

Self-Serve tools include tools and features of ICI that can be used out-of-the-box by authorized users. Besides serving ICI users with specific feature and performance goals, being self-sufficient is the primary goal of these tools. These tools are user-friendly and time-saving, enabling users to perform tasks by themselves instead of reaching out to Icertis Solutions Engineering, Database or Support teams based on the requirement. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.

The ICI Self-Serve tools include:

*Search Sync Tool
*Translations Editor Tool
*Configurations Key Editor Tool
*Promote to Production (P2P) Tool
*Import Solution Tool
<div class="image-caption"> </div> <div class="image-caption">'''<span style="color:#008000;">Prerequisites</span>'''</div>
*The ICI application, version 7.11 and above
*The user must have valid credentials to access ICI and the ''User Administration'' tile.

== Search Sync Tool ==

The Search Sync tool gets data from Icertis Search for a given instance’s Sys Id and synchronizes it if required. Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if sync is required. This tool can be accessed by the Administrator from the Admin Task on the "Admin" tile.

If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as an input CSV file or as a comma-separated. Either comma-separated Sys Ids can be entered or a CSV file can be uploaded.

This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.

'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with Sys ID.

Refer to Search Sync Tool on the [[Admin_Task|Admin Task]] page for more details.
<div class="image-caption"><span style="color:#008000;">'''''Icertis Search Sync'''''</span></div>
Users can now get data from Icertis search for a given instance’s ''SysId'' so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message “Could not fetch value for provided SysId”.
<div class="note-box">'''Note''': Data can be fetched from only one instance at a time.</div> <div class="image-green-border"> </div>
== Translations Editor Tool ==

The ICI platform is available in different languages and different languages label text are available for localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.

Hence, a self-service Translations Editor tool has been introduced that contains all strings that are localized. The Translations Editor tool supports adding localized values in different languages for Reason Codes as well.

Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.

Using this tool, users can now:

*Search for a specific string using the search bar and update the Resource Key value for Language and Locale.
*Update multiple language strings by selecting and saving the Resource Key value.
*Download and upload the localization key values using Microsoft Excel.
*View the modified values in the ICI instance immediately.

To use the Translations Editor Tool:

Refer to Translation Editor in [[Admin_Task|Admin Task]] page for more details

 

 

== Configuration Key Editor Tool ==

The Configuration Key Editor tool facilitates a logged-in user (who has access to Azure subscription) to search and update configuration keys, as and when required. It has been introduced for easier instance management and improved productivity, thus reducing the dependency on the Engineering and DevOps teams.

It includes:

*The Config Editor
*The Redis Flush

The "Config Editor" is a self-service tool that allows teams to edit instance configurations without having to connect to the instance machines. Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by the Operations team, and the tool would not be available for the production environment.

The "Redis Flush" is a self-service tool that allows Administrators to flush the cache or look up a particular key for its value of Delete a Key. The tool can also be used to perform "Role Restart" on the instances to which the user has access.
<div class="note-box">'''Note:'''  The user must have access privileges to an Environment CName in Config Editor.</div> <div class="image-green-border"> </div> <div class="image-green-border">To use the Configuration Key Editor Tool:<br/> 1. Login to the ICI Tools portal (icmtools.icertis.com) with your ICI credentials.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:Self Serve Tool 8.2.png|720px|Self Serve Tool 8.2]]</div> <div class="image-green-border"> </div> <div class="image-green-border">2. '''Click '''the "Config Editor" tab on the "Home" page.</div> <div class="image-green-border"> </div> <div class="image-green-border">3. '''Select '''the environment from the Environment'' ''"CName" that you need to access for configuration. All the instances that have you have access to will be displayed. </div>
4. '''Click "'''Submit"'' ''after selecting the environment. The configuration JSON files for the selected environment are displayed for all available features, security details, database connections, and so on related to the selected instance.
<div class="image-green-border">[[File:Self Serve Tool 8.4.png|720px|Self Serve Tool 8.4]]</div>
5. '''Select''' a Config Key from the list to change its value as required. For example, the Config Key AgreementAutoRenewReminderNotificationPeriod has the reminder period set at 3 days may be changed to 2 days.
<div class="image-green-border">[[File:Self Serve Tool 8.5.png|720px|Self Serve Tool 8.5]]</div>
6. '''Click "'''Save and Role Restart" to save the new value of 2 days. The specific JSON file for the respective CName will be reset (i.e. perform a role restart). This means that the configuration is reset in the Icertis search and the server is restarted so that the new value is reflected on the instance.

7. '''Click''' "Download" to download the entire file so that you can edit it offline and then upload it directly to the instance.

 

 

 

== Promote Configurations (P2P) Tool ==

The Promote to Production (P2P) process of the ICI platform helps to move ICI Configuration from source (Config/UAT) environment to target environment, thus reducing the manual efforts to do so. P2P process enables to selectively move ICI configuration. The Promote Configuration Tool or P2P is designed to accomplish just that.

The tool already supported contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The Icertis search sync is also supported by the tool.

With the 7.15 release, to provide a seamless P2P experience, enhancements have been made in ICI to support the following additional entities :

*Organizations (Orgs), Organization Groups (Org Groups)
*Users, User Groups, Security Groups
*Role Action Mapping
*Currencies
*Reasons
*SLA Matrix
*Notification Category
*Default Search Columns
*Application Settings
*Global/Admin Saved Searches
<div class="note-box">'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.</div>
Here is an overview of the P2P process:
<div class="image-green-border">[[File:P2P 1.png|720px|P2P 1]]</div>
 

 

=== <span style="color:#008000;">''Accessing P2P Tool''</span> ===

To access the P2P tool: 

'''Click '''"Configure"'' '''>'''''"P2P''' '''Configuration"'' ''tile or menu on the top navigation. The "Promote Configuration" page opens.
<div class="image-green-border">[[File:8.0-P2P-Menu-Purple.png|420px|8.0-P2P-Menu-Purple.png]]</div>
The Promote Configurations''displays the current status of P2P requests and their status.''

'''Note: '''Users cannot edit a request that is in the ''Completed'' state.
<div class="image-green-border"> </div>
=== <span style="color:#008000;">''Creating a P2P Request''</span> ===

To create a P2P Request:

1. '''Click'''  "Configure" ''> ''"Promote Configurations"''> ''"Create Request". The "Create Request" page opens.
<div class="image-green-border">[[File:8.0-P2P-1tab-Purple.PNG|920px|8.0-P2P-1tab-Purple.PNG]]</div>
2. '''Enter''' a "Request Name". 

3. '''Select''' a "Target" from the drop-down. 

4. '''Select''' the "P2P Request Start Date Time".

5. '''Select '''the time to trigger an email to the recipient from the "Intimation Email minutes before P2P Starts" drop-down list. For example, ''15 Min''.

6. '''Enter''' the intimation recipient Email Id in the "Notification Email – Intimation"'' ''field.

7. '''Enter''' the notification recipient Email Id in the "Notification Email – Success"'' ''field.

8. '''Enter''' the notification recipient email Id in the "Notification Email– Failure"'' ''field.

9. '''Enter''' the notification recipient email Id in the "Notification Email'' – ''Cancel" field.

10. '''Click''' "Next"''. ''The "Contract Type" tab opens.
<div class="note-box">'''Note: '''As stated in the disclaimer, while promoting configuration, the target environment will be down during contract type publish. This tool must be used responsibly under the project team’s approvals to avoid inconsistency and downtime.</div>
11. '''Select''' the "Contract Type"'' ''from the "Available Contract Types". 
<div class="image-green-border">[[File:8.0-P2P-2tab-Purple.png|920px|8.0-P2P-2tab-Purple.png]]</div>
12. '''Click '''the right arrow to move the selected contract type to the'' ''"Selected Contract Types".
<div class="image-green-border">13. '''Click''' "Next". The "Templates and Clauses" tab opens.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-P2P-3tab-Purple.png|920px|8.0-P2P-3tab-Purple.png]]</div>
14. '''Select''' a template from the "Available Templates" columns. 

15. '''Click '''the arrow key to move the selected template to the "Selected Templates" column.
<div class="image-green-border">16. '''Select''' a clause from the'' ''"Available Clauses" columns.</div>
17. '''Click '''the arrow key to move the selected clause to the "Selected Clauses" column.
<div class="image-green-border">18. '''Click '''"Next"''. ''The "Rules" tab opens.</div> <div class="image-green-border">[[File:8.0-P2P-4tab-Purple.png|420px|8.0-P2P-4tab-Purple.png]]</div> <div class="image-green-border"> </div> <div class="image-green-border">19. '''Select''' the "Contract Type" from the drop-down.</div>
20. '''Select''' the Rules that appear.

21. '''Click '''"Next". The "Notifications" tab opens.
<div class="image-green-border">[[File:8.0-P2P-5tab-Purple.png|920px|8.0-P2P-5tab-Purple.png]]</div>
22. '''Select '''the notifications from the grid.

24. '''Click''' "Next". The "Master Data & Core Seed Data" tab opens.
<div class="note-box">'''''Note''''': Users can use the ''P2P tool Master Data'' tab for the faster transition of Master Data to production than the Bulk utility tool option.</div> <div class="image-green-border"> </div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-P2P-6tab-Purple.png|820px|8.0-P2P-6tab-Purple.png]]</div>
25. '''Click '''the arrow key to move the selected rule to the "Selected Master Data" column.

26. '''Select '''the seed data from the "Available Core Seed Data column". 

27. '''Click '''the arrow key to move the selected master data to the "Selected Core Seed Data"'' ''column.
<div class="image-green-border">28. '''Click "'''Next"''. ''The "Users & User groups" tab opens.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-P2P-7tab-Purple.png|920px|8.0-P2P-7tab-Purple.png]]</div>
31. '''Select''' the users on the "Select Users" pane. 

32. '''Click '''"Selected Users" from the top right of the pane to view the list of users that have been selected.
<div class="image-green-border">[[File:8.0-P2P-7.2tab-Purple.png|920px|8.0-P2P-7.2tab-Purple.png]]</div>
33. '''Click '''"Filter Users" to view the list of users by an attribute or click "Add Another Attribute"'' ''to filter users by additional attributes. For example, Email ID, Phone Number. 
<div class="image-green-border">34. '''Click '''the trash icon''' '''to remove an added user attribute.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-P2P-7.1tab-Purple.png|920px|8.0-P2P-7.1tab-Purple.png]]</div>
35. '''Click''''' ''"Next" if any or no user or user group is selected. The "Security Groups" tab opens.
<div class="image-green-border">[[File:8.0-P2P-8tab-Purple.png|920px|8.0-P2P-8tab-Purple.png]]</div>
36. '''Select '''the security group from the "Available Security Groups" columns.

37. '''Click '''the arrow key to move the selected security group to the "Selected Security Groups" column.

38. '''Select '''the KPI from the "Available KPI’s" columns.

39. '''Click '''the arrow key to move the selected KPI to the "Selected SaveSearchKPIs" column. 
<div class="image-green-border">40. '''Click''' "Next". The'' ''"Verify" tab opens.</div>
41. '''Verify''' details of the contract types, attributes, templates, clauses, ruleset information, notification templates, transactional master data, core seed data, user and user groups, save search KPI, and security groups that you have selected. You can expand all categories by Expand/Collapse ALL icon at the top right or can expand the individual category or tab information with arrows provided in the far right of each category.
<div class="image-green-border">[[File:8.0-P2P-9tab-Purple.png|920px|8.0-P2P-9tab-Purple.png]]</div>
42. '''Click '''"Create". The confirmation window opens indicating that downtime is required for this request.
<div class="image-green-border"> </div> <div class="note-box">'''''Note''''': The P2P tool verifies all the information entered by the user before creating a P2P request.</div>
43. '''Click '''"Yes" if you wish to proceed. The success message opens indicating that the P2P request created successfully.

The P2P request status changes to "ADDED".

On completion of the P2P request, the status changes to "Completed".
<div class="note-box">'''Note''': Users cannot edit a request that is in ''Completed'' state.</div> <div class="image-green-border"> </div> <div class="image-green-border">The Status column on Promote Configurations index page displays the InProgress percentage (calculated on the basis of weightage provided to each step). Once the task is complete, the status changes to Completed.</div> <div class="image-green-border"><br/> To view error details:</div> <div class="image-green-border">1. '''Navigate '''to Promote Configuration page from "Configure" > "Promote Configurations" > "Promote Configurations". The Promote Configuration index page listing all Requests created appears.</div> <div class="image-green-border"><br/> 2. '''Click '''the three dots in the "View" column on the far right.  </div> <div class="image-green-border">[[File:8.0-P2P-Index-Page-Purple.png|920px|8.0-P2P-Index-Page-Purple.png]]</div> <div class="image-green-border"> </div> <div class="image-green-border">The drawer displaying the “Request Error Details” and “Manual Work Pending” tabs are displayed.</div> <div class="image-green-border"> </div> <div class="image-green-border"> </div> <div class="image-green-border">During validation, all errors that are auto-fixable will be fixed, and the result will be displayed.</div> <div class="image-green-border"> </div> <div class="image-green-border">In case of any persisting errors, the details are displayed in the “Request Error Details” tab.</div>
*Request Error Details: This tab contains multiple columns providing more information about the P2P Request. 
**Warning: Displays if an error or warning is encountered when creating the P2P request.
**Validation Area: Displays the specific area where the validation error occurred.
**Error Message: Displays the error message for the P2P request including entity name and SysId.
**Error Description: Displays the detailed description of the error that has occurred when creating the P2P request. 
**Environments: Displays the environments where P2P request creation is not working as expected. For example, Source, Target. 
**Auto-Fix: Indicates if the error encountered when creating the P2P request can be fixed automatically. 
**Manual Step Actions: Displays the list of actions that users need to perform manually to fix the errors when creating the P2P Request. 
<div class="image-green-border">[[File:8.0-P2P-Index-Page-Error-Purple.png|920px|8.0-P2P-Index-Page-Error-Purple.png]]</div>
*Manual Work Pending: Displays the actions that must be taken manually after P2P request is completed. 
**Action: Displays the list of actions users must perform to fix the errors encountered when the P2P request is completed. For example, “Publish Required”, “Cache flush required” and so on. 
**The following details are displayed for an action where applicable. For example, if the action “Es Sync required” action is displayed, then the corresponding details are displayed in the three columns:
***Entity Name
***Entity Value
***SysId
<div class="note-box">'''Note''': <br/> Users can apply the fix automatically by clicking “Apply Fix”. This removes all the existing validation errors and ensures that the errors which are marked as auto fix get fixed automatically. <br/> This button appears only if at least one of the errors can be auto fixed, that is, at least one error displays the value “Yes” in the Auto Fix column. </div> <div class="image-green-border"> </div> <div class="image-green-border">'''To Resume P2P Request:'''</div> <div class="image-green-border"> </div> <div class="image-green-border">'''Click '''the View Details eye icon for the P2P request which you want to resume.</div> <div class="image-green-border"> </div> <div class="image-green-border">The “View Request” page is displayed.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-P2P-View-Request-Purple.png|920px|8.0-P2P-View-Request-Purple.png]]</div> <div class="image-green-border"><br/> If there are any errors encountered when creating the P2P Request, users can resume the P2P Request creation from the step where it failed by clicking “Resume” which will appear at that time.</div> <div class="image-green-border">You can edit with "Edit" or "Validate".</div>
== Import Solution Tool ==

ICI features an out-of-the-box solution for configuring ICI entities from the outset - the Import Solution tool. While saving valuable time and complexities associated with the initial configuration process, this tool provides a self-service, automated utility, and alleviates human intervention or any manual processing.

Using the Import Solution tool, ICI users can:

*Import configurations –
**From a source ICI instance to a target ICI Instance.
**Between multiple versions of ICI.
<div class="note-box">'''Note:'''</div> <div class="note-box">- On a target instance with no pre-existing configuration data.</div> <div class="note-box">- Support will be provided for up to 2 releases preceding the target ICI version. </div>
*These entities can be imported with this tool:
**Contract Types
**Templates
**Clauses
**Rules
**Notifications
**Masterdata Instances
**Seeded Masterdata entity instances
**Users & User Groups

 

=== Prerequisites for Import Solution to be implemented ===

==== Source instance setup ====

1.  Register and publish preconfigured import solutions, therefore availing source instances for utilization.<br/> 2.  Set up records for below seeded Masterdata contract types:

[[File:Import1.PNG|720px|Import1.PNG]]

3.  This configuration key can be used for the Source to communicate with the Import Solution engine – “Core.Tools.P2P.P2PDBConnectionString”. The value for this key should be the DB connection string of the Import Solution engine.
<div class="note-box">'''Note:''' For releases before 8.1, please reach out to the database team.</div>
==== Target instance setup ====

*This configuration key can be used for the Target to communicate with the Import Solution engine – “Core.Tools.ImportSolution.Configuration”. The value for this key should be the DB connection string of the Import Solution engine.
*“Manage” permissions will be required in the Security Groups for – “Admin Task” and “Promote Configuration”.

==== Source and Target mapping ====

The Source and Target instances need to be mapped in the Import Solution engine database. To do this, please reach out to the database team.

 

=== Using the Import Solution tool ===

To access the Import Solution tool and create an import configuration request:

1.  Click the “Admin” tile > “Admin Task”.<br/> 2.  Click “Import Solution”. The “Import Solution” page opens.
<div class="image-green-border">[[File:Import2.png|280px|Import2.png]]</div>
3.  Click “Create” on the Import Solution tool page. The “Create Import Configuration Request” page opens.
<div class="image-green-border">[[File:Import3.png|720px|Import3.png]]</div>
4.  Fill all required fields and click “Next”.
<div class="image-green-border">[[File:Import4.png|720px|Import4.png]]</div>
5.  Select and fill all necessary information across all the relevant tabs.

6.  Verify all information within the “Verify” tab.
<div class="image-green-border">[[File:Import5.png|720px|Import5.png]]</div>
7.  Click “Create”. The request to import the specified configuration will be created, and a confirmation message is displayed on the “Import Solution Request Progress” drawer.
<div class="image-green-border">[[File:Import6.png|720px|Import6.png]]</div>
 

 

 

'''Related Topics: '''[[Agreements|Agreement Management]] | [[Associations|Association Management]] | [[Compliances|Compliance Management]] | [[Templates|Template Management]] | [[Clauses|Clause Management]] | [[Configure|Configuration]] | [[Reports|Reports]] | [[Localizing_ICI|Localizing ICI]] |

Self-Serve Tools

2022-12-12T09:46:34Z

WikiSysop:

= Self-Serve Tools =

Self-Serve tools include tools and features of ICI that can be used out-of-the-box by authorized users. Besides serving ICI users with specific feature and performance goals, being self-sufficient is the primary goal of these tools. These tools are user-friendly and time-saving, enabling users to perform tasks by themselves instead of reaching out to Icertis Solutions Engineering, Database or Support teams based on the requirement. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.

The ICI Self-Serve tools include:

*Search Sync Tool
*Translations Editor Tool
*Improved ICI Health Check Tool
*Configurations Key Editor Tool
*Promote to Production (P2P) Tool
*Import Solution Tool
<div class="image-caption"> </div> <div class="image-caption">'''<span style="color:#008000;">Prerequisites</span>'''</div>
*The ICI application, version 7.11 and above
*The user must have valid credentials to access ICI and the ''User Administration'' tile.

== Search Sync Tool ==

The Search Sync tool gets data from Icertis Search for a given instance’s Sys Id and synchronizes it if required. Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if sync is required. This tool can be accessed by the Administrator from the Admin Task on the "Admin" tile.

If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as an input CSV file or as a comma-separated. Either comma-separated Sys Ids can be entered or a CSV file can be uploaded.

This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.

'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with Sys ID.

Refer to Search Sync Tool on the [[Admin_Task|Admin Task]] page for more details.
<div class="image-caption"><span style="color:#008000;">'''''Icertis Search Sync'''''</span></div>
Users can now get data from Icertis search for a given instance’s ''SysId'' so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message “Could not fetch value for provided SysId”.
<div class="note-box">'''Note''': Data can be fetched from only one instance at a time.</div> <div class="image-green-border"> </div>
== Translations Editor Tool ==

The ICI platform is available in different languages and different languages label text are available for localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.

Hence, a self-service Translations Editor tool has been introduced that contains all strings that are localized. The Translations Editor tool supports adding localized values in different languages for Reason Codes as well.

Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.

Using this tool, users can now:

*Search for a specific string using the search bar and update the Resource Key value for Language and Locale.
*Update multiple language strings by selecting and saving the Resource Key value.
*Download and upload the localization key values using Microsoft Excel.
*View the modified values in the ICI instance immediately.

To use the Translations Editor Tool:

Refer to Translation Editor in [[Admin_Task|Admin Task]] page for more details

 

 

== Configuration Key Editor Tool ==

The Configuration Key Editor tool facilitates a logged-in user (who has access to Azure subscription) to search and update configuration keys, as and when required. It has been introduced for easier instance management and improved productivity, thus reducing the dependency on the Engineering and DevOps teams.

It includes:

*The Config Editor
*The Redis Flush

The "Config Editor" is a self-service tool that allows teams to edit instance configurations without having to connect to the instance machines. Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by the Operations team, and the tool would not be available for the production environment.

The "Redis Flush" is a self-service tool that allows Administrators to flush the cache or look up a particular key for its value of Delete a Key. The tool can also be used to perform "Role Restart" on the instances to which the user has access.
<div class="note-box">'''Note:'''  The user must have access privileges to an Environment CName in Config Editor.</div> <div class="image-green-border"> </div> <div class="image-green-border">To use the Configuration Key Editor Tool:<br/> 1. Login to the ICI Tools portal (icmtools.icertis.com) with your ICI credentials.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:Self Serve Tool 8.2.png|720px|Self Serve Tool 8.2]]</div> <div class="image-green-border"> </div> <div class="image-green-border">2. '''Click '''the "Config Editor" tab on the "Home" page.</div> <div class="image-green-border"> </div> <div class="image-green-border">3. '''Select '''the environment from the Environment'' ''"CName" that you need to access for configuration. All the instances that have you have access to will be displayed. </div>
4. '''Click "'''Submit"'' ''after selecting the environment. The configuration JSON files for the selected environment are displayed for all available features, security details, database connections, and so on related to the selected instance.
<div class="image-green-border">[[File:Self Serve Tool 8.4.png|720px|Self Serve Tool 8.4]]</div>
5. '''Select''' a Config Key from the list to change its value as required. For example, the Config Key AgreementAutoRenewReminderNotificationPeriod has the reminder period set at 3 days may be changed to 2 days.
<div class="image-green-border">[[File:Self Serve Tool 8.5.png|720px|Self Serve Tool 8.5]]</div>
6. '''Click "'''Save and Role Restart" to save the new value of 2 days. The specific JSON file for the respective CName will be reset (i.e. perform a role restart). This means that the configuration is reset in the Icertis search and the server is restarted so that the new value is reflected on the instance.

7. '''Click''' "Download" to download the entire file so that you can edit it offline and then upload it directly to the instance.

 

 

 

== Promote Configurations (P2P) Tool ==

The Promote to Production (P2P) process of the ICI platform helps to move ICI Configuration from source (Config/UAT) environment to target environment, thus reducing the manual efforts to do so. P2P process enables to selectively move ICI configuration. The Promote Configuration Tool or P2P is designed to accomplish just that.

The tool already supported contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The Icertis search sync is also supported by the tool.

With the 7.15 release, to provide a seamless P2P experience, enhancements have been made in ICI to support the following additional entities :

*Organizations (Orgs), Organization Groups (Org Groups)
*Users, User Groups, Security Groups
*Role Action Mapping
*Currencies
*Reasons
*SLA Matrix
*Notification Category
*Default Search Columns
*Application Settings
*Global/Admin Saved Searches
<div class="note-box">'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.</div>
Here is an overview of the P2P process:
<div class="image-green-border">[[File:P2P 1.png|720px|P2P 1]]</div>
 

 

=== <span style="color:#008000;">''Accessing P2P Tool''</span> ===

To access the P2P tool: 

'''Click '''"Configure"'' '''>'''''"P2P''' '''Configuration"'' ''tile or menu on the top navigation. The "Promote Configuration" page opens.
<div class="image-green-border">[[File:8.0-P2P-Menu-Purple.png|420px|8.0-P2P-Menu-Purple.png]]</div>
The Promote Configurations''displays the current status of P2P requests and their status.''

'''Note: '''Users cannot edit a request that is in the ''Completed'' state.
<div class="image-green-border"> </div>
=== <span style="color:#008000;">''Creating a P2P Request''</span> ===

To create a P2P Request:

1. '''Click'''  "Configure" ''> ''"Promote Configurations"''> ''"Create Request". The "Create Request" page opens.
<div class="image-green-border">[[File:8.0-P2P-1tab-Purple.PNG|920px|8.0-P2P-1tab-Purple.PNG]]</div>
2. '''Enter''' a "Request Name". 

3. '''Select''' a "Target" from the drop-down. 

4. '''Select''' the "P2P Request Start Date Time".

5. '''Select '''the time to trigger an email to the recipient from the "Intimation Email minutes before P2P Starts" drop-down list. For example, ''15 Min''.

6. '''Enter''' the intimation recipient Email Id in the "Notification Email – Intimation"'' ''field.

7. '''Enter''' the notification recipient Email Id in the "Notification Email – Success"'' ''field.

8. '''Enter''' the notification recipient email Id in the "Notification Email– Failure"'' ''field.

9. '''Enter''' the notification recipient email Id in the "Notification Email'' – ''Cancel" field.

10. '''Click''' "Next"''. ''The "Contract Type" tab opens.
<div class="note-box">'''Note: '''As stated in the disclaimer, while promoting configuration, the target environment will be down during contract type publish. This tool must be used responsibly under the project team’s approvals to avoid inconsistency and downtime.</div>
11. '''Select''' the "Contract Type"'' ''from the "Available Contract Types". 
<div class="image-green-border">[[File:8.0-P2P-2tab-Purple.png|920px|8.0-P2P-2tab-Purple.png]]</div>
12. '''Click '''the right arrow to move the selected contract type to the'' ''"Selected Contract Types".
<div class="image-green-border">13. '''Click''' "Next". The "Templates and Clauses" tab opens.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-P2P-3tab-Purple.png|920px|8.0-P2P-3tab-Purple.png]]</div>
14. '''Select''' a template from the "Available Templates" columns. 

15. '''Click '''the arrow key to move the selected template to the "Selected Templates" column.
<div class="image-green-border">16. '''Select''' a clause from the'' ''"Available Clauses" columns.</div>
17. '''Click '''the arrow key to move the selected clause to the "Selected Clauses" column.
<div class="image-green-border">18. '''Click '''"Next"''. ''The "Rules" tab opens.</div> <div class="image-green-border">[[File:8.0-P2P-4tab-Purple.png|420px|8.0-P2P-4tab-Purple.png]]</div> <div class="image-green-border"> </div> <div class="image-green-border">19. '''Select''' the "Contract Type" from the drop-down.</div>
20. '''Select''' the Rules that appear.

21. '''Click '''"Next". The "Notifications" tab opens.
<div class="image-green-border">[[File:8.0-P2P-5tab-Purple.png|920px|8.0-P2P-5tab-Purple.png]]</div>
22. '''Select '''the notifications from the grid.

24. '''Click''' "Next". The "Master Data & Core Seed Data" tab opens.
<div class="note-box">'''''Note''''': Users can use the ''P2P tool Master Data'' tab for the faster transition of Master Data to production than the Bulk utility tool option.</div> <div class="image-green-border"> </div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-P2P-6tab-Purple.png|820px|8.0-P2P-6tab-Purple.png]]</div>
25. '''Click '''the arrow key to move the selected rule to the "Selected Master Data" column.

26. '''Select '''the seed data from the "Available Core Seed Data column". 

27. '''Click '''the arrow key to move the selected master data to the "Selected Core Seed Data"'' ''column.
<div class="image-green-border">28. '''Click "'''Next"''. ''The "Users & User groups" tab opens.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-P2P-7tab-Purple.png|920px|8.0-P2P-7tab-Purple.png]]</div>
31. '''Select''' the users on the "Select Users" pane. 

32. '''Click '''"Selected Users" from the top right of the pane to view the list of users that have been selected.
<div class="image-green-border">[[File:8.0-P2P-7.2tab-Purple.png|920px|8.0-P2P-7.2tab-Purple.png]]</div>
33. '''Click '''"Filter Users" to view the list of users by an attribute or click "Add Another Attribute"'' ''to filter users by additional attributes. For example, Email ID, Phone Number. 
<div class="image-green-border">34. '''Click '''the trash icon''' '''to remove an added user attribute.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-P2P-7.1tab-Purple.png|920px|8.0-P2P-7.1tab-Purple.png]]</div>
35. '''Click''''' ''"Next" if any or no user or user group is selected. The "Security Groups" tab opens.
<div class="image-green-border">[[File:8.0-P2P-8tab-Purple.png|920px|8.0-P2P-8tab-Purple.png]]</div>
36. '''Select '''the security group from the "Available Security Groups" columns.

37. '''Click '''the arrow key to move the selected security group to the "Selected Security Groups" column.

38. '''Select '''the KPI from the "Available KPI’s" columns.

39. '''Click '''the arrow key to move the selected KPI to the "Selected SaveSearchKPIs" column. 
<div class="image-green-border">40. '''Click''' "Next". The'' ''"Verify" tab opens.</div>
41. '''Verify''' details of the contract types, attributes, templates, clauses, ruleset information, notification templates, transactional master data, core seed data, user and user groups, save search KPI, and security groups that you have selected. You can expand all categories by Expand/Collapse ALL icon at the top right or can expand the individual category or tab information with arrows provided in the far right of each category.
<div class="image-green-border">[[File:8.0-P2P-9tab-Purple.png|920px|8.0-P2P-9tab-Purple.png]]</div>
42. '''Click '''"Create". The confirmation window opens indicating that downtime is required for this request.
<div class="image-green-border"> </div> <div class="note-box">'''''Note''''': The P2P tool verifies all the information entered by the user before creating a P2P request.</div>
43. '''Click '''"Yes" if you wish to proceed. The success message opens indicating that the P2P request created successfully.

The P2P request status changes to "ADDED".

On completion of the P2P request, the status changes to "Completed".
<div class="note-box">'''Note''': Users cannot edit a request that is in ''Completed'' state.</div> <div class="image-green-border"> </div> <div class="image-green-border">The Status column on Promote Configurations index page displays the InProgress percentage (calculated on the basis of weightage provided to each step). Once the task is complete, the status changes to Completed.</div> <div class="image-green-border"><br/> To view error details:</div> <div class="image-green-border">1. '''Navigate '''to Promote Configuration page from "Configure" > "Promote Configurations" > "Promote Configurations". The Promote Configuration index page listing all Requests created appears.</div> <div class="image-green-border"><br/> 2. '''Click '''the three dots in the "View" column on the far right.  </div> <div class="image-green-border">[[File:8.0-P2P-Index-Page-Purple.png|920px|8.0-P2P-Index-Page-Purple.png]]</div> <div class="image-green-border"> </div> <div class="image-green-border">The drawer displaying the “Request Error Details” and “Manual Work Pending” tabs are displayed.</div> <div class="image-green-border"> </div> <div class="image-green-border"> </div> <div class="image-green-border">During validation, all errors that are auto-fixable will be fixed, and the result will be displayed.</div> <div class="image-green-border"> </div> <div class="image-green-border">In case of any persisting errors, the details are displayed in the “Request Error Details” tab.</div>
*Request Error Details: This tab contains multiple columns providing more information about the P2P Request. 
**Warning: Displays if an error or warning is encountered when creating the P2P request.
**Validation Area: Displays the specific area where the validation error occurred.
**Error Message: Displays the error message for the P2P request including entity name and SysId.
**Error Description: Displays the detailed description of the error that has occurred when creating the P2P request. 
**Environments: Displays the environments where P2P request creation is not working as expected. For example, Source, Target. 
**Auto-Fix: Indicates if the error encountered when creating the P2P request can be fixed automatically. 
**Manual Step Actions: Displays the list of actions that users need to perform manually to fix the errors when creating the P2P Request. 
<div class="image-green-border">[[File:8.0-P2P-Index-Page-Error-Purple.png|920px|8.0-P2P-Index-Page-Error-Purple.png]]</div>
*Manual Work Pending: Displays the actions that must be taken manually after P2P request is completed. 
**Action: Displays the list of actions users must perform to fix the errors encountered when the P2P request is completed. For example, “Publish Required”, “Cache flush required” and so on. 
**The following details are displayed for an action where applicable. For example, if the action “Es Sync required” action is displayed, then the corresponding details are displayed in the three columns:
***Entity Name
***Entity Value
***SysId
<div class="note-box">'''Note''': <br/> Users can apply the fix automatically by clicking “Apply Fix”. This removes all the existing validation errors and ensures that the errors which are marked as auto fix get fixed automatically. <br/> This button appears only if at least one of the errors can be auto fixed, that is, at least one error displays the value “Yes” in the Auto Fix column. </div> <div class="image-green-border"> </div> <div class="image-green-border">'''To Resume P2P Request:'''</div> <div class="image-green-border"> </div> <div class="image-green-border">'''Click '''the View Details eye icon for the P2P request which you want to resume.</div> <div class="image-green-border"> </div> <div class="image-green-border">The “View Request” page is displayed.</div> <div class="image-green-border"> </div> <div class="image-green-border">[[File:8.0-P2P-View-Request-Purple.png|920px|8.0-P2P-View-Request-Purple.png]]</div> <div class="image-green-border"><br/> If there are any errors encountered when creating the P2P Request, users can resume the P2P Request creation from the step where it failed by clicking “Resume” which will appear at that time.</div> <div class="image-green-border">You can edit with "Edit" or "Validate".</div>
== Import Solution Tool ==

ICI features an out-of-the-box solution for configuring ICI entities from the outset - the Import Solution tool. While saving valuable time and complexities associated with the initial configuration process, this tool provides a self-service, automated utility, and alleviates human intervention or any manual processing.

Using the Import Solution tool, ICI users can:

*Import configurations –
**From a source ICI instance to a target ICI Instance.
**Between multiple versions of ICI.
<div class="note-box">'''Note:'''</div> <div class="note-box">- On a target instance with no pre-existing configuration data.</div> <div class="note-box">- Support will be provided for up to 2 releases preceding the target ICI version. </div>
*These entities can be imported with this tool:
**Contract Types
**Templates
**Clauses
**Rules
**Notifications
**Masterdata Instances
**Seeded Masterdata entity instances
**Users & User Groups

 

=== Prerequisites for Import Solution to be implemented ===

==== Source instance setup ====

1.  Register and publish preconfigured import solutions, therefore availing source instances for utilization.<br/> 2.  Set up records for below seeded Masterdata contract types:

[[File:Import1.PNG|720px|Import1.PNG]]

3.  This configuration key can be used for the Source to communicate with the Import Solution engine – “Core.Tools.P2P.P2PDBConnectionString”. The value for this key should be the DB connection string of the Import Solution engine.
<div class="note-box">'''Note:''' For releases before 8.1, please reach out to the database team.</div>
==== Target instance setup ====

*This configuration key can be used for the Target to communicate with the Import Solution engine – “Core.Tools.ImportSolution.Configuration”. The value for this key should be the DB connection string of the Import Solution engine.
*“Manage” permissions will be required in the Security Groups for – “Admin Task” and “Promote Configuration”.

==== Source and Target mapping ====

The Source and Target instances need to be mapped in the Import Solution engine database. To do this, please reach out to the database team.

 

=== Using the Import Solution tool ===

To access the Import Solution tool and create an import configuration request:

1.  Click the “Admin” tile > “Admin Task”.<br/> 2.  Click “Import Solution”. The “Import Solution” page opens.
<div class="image-green-border">[[File:Import2.png|280px|Import2.png]]</div>
3.  Click “Create” on the Import Solution tool page. The “Create Import Configuration Request” page opens.
<div class="image-green-border">[[File:Import3.png|720px|Import3.png]]</div>
4.  Fill all required fields and click “Next”.
<div class="image-green-border">[[File:Import4.png|720px|Import4.png]]</div>
5.  Select and fill all necessary information across all the relevant tabs.

6.  Verify all information within the “Verify” tab.
<div class="image-green-border">[[File:Import5.png|720px|Import5.png]]</div>
7.  Click “Create”. The request to import the specified configuration will be created, and a confirmation message is displayed on the “Import Solution Request Progress” drawer.
<div class="image-green-border">[[File:Import6.png|720px|Import6.png]]</div>
 

 

 

'''Related Topics: '''[[Agreements|Agreement Management]] | [[Associations|Association Management]] | [[Compliances|Compliance Management]] | [[Templates|Template Management]] | [[Clauses|Clause Management]] | [[Configure|Configuration]] | [[Reports|Reports]] | [[Localizing_ICI|Localizing ICI]] |

ICI for SAP CPQ and S4/HANA Lead to Cash Adapter Replication Integration and Configuration

2022-12-06T13:37:47Z

WikiSysop:

 

= ICI for SAP CPQ and SAP S/4HANA Lead to Cash Adapter Replication Integration and Configuration =

This topic describes the steps to configure the Master data Integration between Icertis Contract Intelligence (ICI) platform and SAP S/4HANA using the SAP Cloud Integration.

This Master data integration use case is a part of the larger Lead-to-Cash (L2C) scenario involving SAP CPQ, SAP S/4HANA, and Icertis Contract Intelligence (ICI).

SAP S/4HANA is the master for Business Partner (Customer) and Product data. The data should be synced (create, update) to SAP CPQ and ICI.

Master data sync should be set up for the below scenarios:

*Event-Based (Create, Update, Delete) Realtime Sync
*Scheduled Batch Sync (Incremental Updates for date-time range)

== System Requirements ==

The system requirements for a successful configuration:

*SAP S/4HANA
*SAP Cloud Integration
*SAP CPQ
*ICI Platform

== Prerequisites ==

Following are some general prerequisites that need to be fulfilled to integrate SAP S/4HANA and SAP CPQ with ICI.

*Contact the Network Security team to prepare the network environment across different systems and set its security aspects.
*Quote 2.0 should be enabled in the SAP CPQ tenant.
*ICI environment should be configured with the master data contract type for the following entities:
**Customer
**Product
**Countries

== Configuration in SAP CPQ ==

*Complete the configuration steps from the SAP CPQ side.
*Synchronize S/4HANA Business Partners and Products with SAP CPQ.

== Configuration in ICI ==

*Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration.
*Contact ICI Admin to configure the infrastructure level changes in ICI.
*Create contract types for holding all master data information.

== SAP Cloud Integration Configuration ==

To use the iFlow, you must copy and configure it in your local environment. As a part of this configuration, the iFlow is adapted to the integration environment by providing system details of the sending and receiving system.

=== Viewing Prepackaged iFlows using the SAP Cloud Integration Web ===

#Access the SAP CI (Cloud Integration) Web UI from the provisioning e-mail. It should be in the format: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, you should be able to view all prepackaged integration flows delivered by SAP.
#Choose the package '''SAP S/4HANA - ICI - Masterdata Integration - L2C.'''
#All the artifacts of this package will be displayed when the '''Artifacts''' tab is selected.

=== Configuring and Deploying the iFlow using the SAP Cloud Integration Web UI ===

#Connect to the tenant management node of the SAP Cloud Integration system with the URL: [http:// http://]<tenant management node URL>/itspaces.
#On the '''Discover''' tab, select the package, for example, '''SAP S/4HANA - ICI - Masterdata Integration - L2C'''.
#Choose '''Artifacts '''to view all the iFlows related to this integration package.
#Choose '''Copy '''on the top right corner to copy it to the design area.<br/> '''Note''': If the Integration package is being created for the first time, you will see the ‘Integration Package Created’ message. If not, you will see the dialog box asking to either create a new copy of the package or to Overwrite the existing integration package content. Choose Overwrite.
#Select the '''Design''' mode in the left navigation bar.<br/> The package is now visible in the design area and can be configured.

=== Configuration of the Replicate Business Partners from SAP S/4HANA to ICI iFlow ===

#Select the copied Integration Package.
#Choose the '''Artifacts''' tab of the package to view the list of iFlows.
#Choose the actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI '''iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (in this case, SAP S/4HANA) and the receiver system (in this case, ICI) and additional information.
#Choose '''Save '''after completing the configuration.<br/> Choose '''Deploy '''after completing the complete configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:312px;" |
'''Field Name'''

| style="width:312px;" |
'''Value'''

|-
| style="width:312px;" |
Sender

| style="width:312px;" |
S/4HANA

|-
| style="width:312px;" |
Adapter Type

| style="width:312px;" |
SOAP

|-
| style="width:312px;" |
Authorization

| style="width:312px;" |
User Role

|-
| style="width:312px;" |
Address

| style="width:312px;" |
iFlow Endpoint (e.g.: BusinessPartnerReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:132px;" |
'''Field Name'''

| style="width:492px;" |
'''Value'''

|-
| style="width:132px;" |
Receiver

| style="width:492px;" |
ICI

|-
| style="width:132px;" |
Adapter Type

| style="width:492px;" |
HTTP

|-
| style="width:132px;" |
Parameter_1

| style="width:492px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#Choose '''Monitor''' from the left navigation bar.
#Next, choose '''All from Manage Integration Content'''.
#Check if the deployment was successful. The status should be started, and an endpoint URL is displayed.

=== Configuring the Replicate Products from SAP S/4HANA to ICI iFlow ===

#Select the copied integration package.
#Choose the '''Artifacts''' tab of the package to view the list of iFlows.
#Choose the Actions symbol beside the '''Replicate Business Partners from SAP S/4HANA to ICI''' iFlow.
#Choose '''Configure'''.<br/> The configuration is explained in the following topics. Configuration of the sender system (In this case, SAP S/4 HANA) and the receiver system (In this case, ICI) and additional information.
#Choose '''Save''' after completing the configuration.
#Choose '''Deploy''' after completion of the complete configuration.

'''Sender Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 116px;" |
'''Field Name'''

| style="width: 508px;" |
'''Value'''

|-
| style="width: 116px;" |
Sender

| style="width: 508px;" |
S/4HANA

|-
| style="width: 116px;" |
Adapter Type

| style="width: 508px;" |
SOAP

|-
| style="width: 116px;" |
Authorization

| style="width: 508px;" |
User Role

|-
| style="width: 116px;" |
Address

| style="width: 508px;" |
iFlow Endpoint<br/> (for example, ProductReplication)

|}

'''Receiver Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
! style="width: 106px;" |
Field Name

! style="width: 518px;" |
Value

|-
| style="width: 106px;" |
Receiver

| style="width: 518px;" |
ICI

|-
| style="width: 106px;" |
Adapter Type

| style="width: 518px;" |
HTTP

|-
| style="width: 106px;" |
Parameter_1

| style="width: 518px;" |
<<ICI Business API URL>> (Get it from ICI Admin)

|}

'''More Tab'''

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width:126px;" |
'''Field Name'''

| style="width:498px;" |
'''Value'''

|-
| style="width:126px;" |
Logging

| style="width:498px;" |
True or False

|-
| style="width:126px;" |
ICIAuthToken

| style="width:498px;" |
<<ICI Authentication token>> (Get it from ICI Admin)

|}

'''Deployment'''

#Choose '''Deploy''' after all the above configurations are done.
#Choose '''Monitor''' from the left navigation bar.
#Next, choose '''All from Manage Integration Content'''.
#Check if the deployment was successful. The status should be started, and an endpoint URL is displayed.

ICI for SAP Ariba Strategic Sourcing

2022-12-02T07:28:37Z

WikiSysop:

= ICI for SAP Ariba Strategic Sourcing =

== Overview ==

'''Icertis Contract Intelligence (ICI) integration with SAP Ariba Contracts'''

The Icertis Contract Intelligence (ICI) for SAP Ariba Contracts integration provides organizations an intelligent and flexible contracting platform leveraging 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 the revenue. 
*Lack of insights from contract data leads to limited visibility to enforce performance. 
*Security, risk, and compliance helps to safeguard the brand and intellectual property rights. 

The ICI for SAP Ariba adapter provides the following capabilities.<br/>  
<div class="image-green-border">[[File:Sa1.png|upright]]</div>
 

The diagram above depicts how the end-to-end source to contract business flow can be orchestrated leveraging the ICI for SAP Ariba Contracts integration.  

*A contract manager can create a standalone SAP Ariba Contract Workspace (ACW) or a corresponding ACW from SAP Ariba Contract Request. 
*A contract manager can also create an SAP Ariba Contract Workspace while awarding a sourcing event. 
*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 ACW, provide minimal information, and initiate authoring in ICI. You can leverage ICI’s AI capabilities to extract metadata and clauses for ease of redlining. ICI assembles the legal language based on predefined legal template and rules.

*'''Repository Contract'''

A contract manager can easily manage signed PDF contracts by uploading it directly to the ACW and publishing it. The solution automatically creates an executed agreement in ICI.

*'''Contract Review, Approval, Signature, and Execution'''

ICI capabilities around contract redlining (such as Microsoft Word Experience, online editing), approval, signature can streamline the process with proper governance. Once executed, the metadata along with a signed PDF can is synced back in 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 ACW. 

*'''Supplier Master Data'''

 You can also synch supplier master data from SAP Ariba Contracts to ICI.

*'''Auto-link sub-agreement to a Master Agreement'''

You can create a sub-agreement in ACW for an existing master agreement that is interfaced with ICI. The system creates a corresponding child agreement in ICI and auto-links it to its parent agreement.

The following data is synchronized between ICI and SAP Ariba Contracts.  

*Agreement data  
*Agreement document data 
*Agreement team data 
*Supplier master data

 

== 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.<br/>  
*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.<br/>  
*Effectively manage legal and business risk: preapproved legal templates, predefined corporate policies, and constant monitoring of contractual obligations and SLAs (Service Level Agreement) enable organizations to effectively manage legal and business risks.

== Prerequisites ==

The ICI SAP Ariba Adapter is supported with ICI versions 8.2.1, 8.2.0, 8.1.4, 8.1.3, and 8.1.2.  Ensure that the following prerequisites are met:

*SAP Ariba Contracts prerequisites 
**Use the REST API collection to integrate SAP Ariba Contract Workspaces (ACW), SAP Ariba Documents, and SAP Ariba Team. 
**The SAP Ariba REST APIs are configured with API rate limit values to make uninterrupted API calls for data syncing.  
**Task Service is up and running  
**Required events and jobs are enabled  
**SAP Ariba Contracts allows ICI Client to consume their APIs  

'''Note:''' To know more about the SAP Ariba prerequisites, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/a1709b3b0a824b018577e0add8d1b27a.html here].  

*ICI configuration prerequisites 
**Creating ICI entities  
**Mapping attributes for ICI entities (Client App Cross Reference and Client App Entity Mapping)  
**Creating filters in the Client App Filter Condition  
**Defining Date Filter criteria in the Client App Master data Sync for field: Effective Date  
**Storing SAP Ariba API connection information in the Azure Key Vault    
**The required SAP Ariba Contracts master data is imported to ICI – ICI side 
**SAP Ariba Contracts users are provisioned in ICI 
**SAP Ariba Contracts IDP integration is configured in ICI 

'''Note:''' Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the '''ICI for SAP Ariba''' adapter.

= 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.

[[File:Sa14.PNG|upright]]

 

=== Creating a Contract Using Executed Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=9 edit]] ===

1. Create a Contract Workspace in SAP Ariba Contracts in the '''Draft''' status.
<div class="image-green-border">[[File:Sa2.png|upright]]</div>
2. 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.
<div class="image-green-border">[[File:Sa15.png|upright]]</div>
3. To publish the agreement, click '''Actions '''> '''Publish '''in ACW.
<div class="image-green-border">[[File:Sa3.png|upright]]</div>
'''Note''': To know more about the standard Ariba Contract Workspace creation process, click [https://help.sap.com/docs/ARIBA_SOURCING/fa6038501b9b4b548e7a7628356e33ca/7cd9712c71ea1014a8d3d6cf4fe940c0.html here].

4. To open the ICI equivalent agreement, click the link in the '''External ID''' column (for example: ICMNDA_82).
<div class="image-green-border">[[File:Sa4.png|upright]]</div>
5. To view the SAP Ariba information in ICI, click '''''Details '''''> '''A''riba Information.'''''
<div class="image-green-border">[[File:Sa5.png|upright]]</div>
6. To view the owners of the agreement, on the left navigation pane, click '''Team'''.
<div class="image-green-border">[[File:Sa6.png|upright]]</div>
 

7. To view the contract details, click '''Details''' > '''General Information'''.
<div class="image-green-border">[[File:Sa16.png|upright]]</div>
 

8. To navigate back to the ACW, click '''Details''' > '''Ariba CW Link'''.
<div class="image-green-border">[[File:Sa7.png|upright]]</div>
9. The ACW now shows both the '''ACW ID''' and the '''Icertis ID'''.
<div class="image-green-border">[[File:Sa8.png|upright]]</div>

=== Managing Contracts Created Using Own or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=10 edit]] ===

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 by the supplier

The following diagram explains the contract initiation to contract execution process.
<div class="image-green-border">[[File:Flowchart 1v2.png|upright]]</div>
 

=== Creating a Contract Using Own Paper or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=11 edit]] ===

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.

After the contract is executed in ICI, the ACW is published automatically.

=== Managing contracts in unique scenarios[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=12 edit]] ===

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.

[[File:SAP Ariba Contract not initiated.png|upright]]

 

=== 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

[[File:CLID 1.PNG|upright]]

 

*Contract authoring is already initiated

[[File:CLID 2.PNG|upright]]

 

== Working with Amendments[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=14 edit]] ==

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

SAP Ariba supports five amendment types, please find the details below along with respective impact in ICI:

*Amendment: This amendment type allows to change any part of the Contract. In this case, an amendment agreement will be generated at ICI side and interfaced back to SAP Ariba.
*Renewal: This amendment type allows to change effective, expiration dates along with many other attributes of the contract. It’s recommended to use ‘Amendment’ option for all such changes
*Termination: This amendment type is used to close a contract before its expiration date. In this case the contract will be terminated at Ariba side and Ariba contract status will be stored in an ICI attribute.
*Administrative: This amendment type is used for change in non-contract fields like Name, Description etc. In this case the main agreement will be updated at Ariba and ICI side.
*Price Update: This amendment type allows to change existing items along with many other attributes. It’s recommended to use ‘Amendment’ option for all such changes.

 

'''Prerequisite'''

The ACW must be created, and the contract should be 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.
<div class="image-green-border">[[File:Sa11.png|upright]]</div>
6. Enter the details and click'''Create'''. The amendment record is created.
<div class="image-green-border">[[File:Sa12.png|upright]]</div>
Like agreements, a unique amendment ID is created and is synched back in ACW. The amendment is created in the '''Draft''' status.

Once the amendment is executed in ICI, the amendment is auto-published in ACW.

'''Note the following important points'''

*An ICI amendment record is created against the amendment of  a Ariba Contract workspace (ACW) · 
*An ICI amendment records goes through the same process of an agreement.
*The History tab shows the old values and the new values for all changed attributes.

== Configuration[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=15 edit]] ==

=== SAP Ariba Contracts Side configurations ===

To know more on SAP Ariba Contracts side configurations, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/79e20b26eabc4af0a486acd8818877d5.html here].

=== ICI Side configurations  ===

Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the ICI for SAP Ariba adapter.

== Glossary ==

 

{| align="left" border="1" cellpadding="1" cellspacing="1" style="width: 650px;"
|-
! scope="col" | ICI Terminology
! scope="col" | SAP Ariba Contract Terminology
! scope="col" | Description
|-
| Agreement
| Ariba Contract Workspace (ACW)
| A legally binding contract, where all information and supporting documents are recorded.
|-
| Own Paper
| NA
| A type of paper used while creating an agreement. Own paper indicates using the organization's template to create an agreement.
|-
| Third-party paper
| NA
| A type of paper used while creating an agreement. Third-party paper indicates using an external or third-party template to create an agreement.
|-
| Executed paper
| NA
| Indicates an agreement that is created offline and uploaded to the system. The signature action for this type of agreement can be performed offline or in the system.
|}

 

 

 

 

 

 

 

 

 

 

'''Related Topics''': [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Working_with_Agreements Agreement Management]

ICI for SAP Ariba Strategic Sourcing

2022-12-02T07:27:31Z

WikiSysop:

= ICI for SAP Ariba Strategic Sourcing =

== Overview ==

'''Icertis Contract Intelligence (ICI) integration with SAP Ariba Contracts'''

The Icertis Contract Intelligence (ICI) for SAP Ariba Contracts integration provides organizations an intelligent and flexible contracting platform leveraging 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 the revenue. 
*Lack of insights from contract data leads to limited visibility to enforce performance. 
*Security, risk, and compliance helps to safeguard the brand and intellectual property rights. 

The ICI for SAP Ariba adapter provides the following capabilities.<br/>  
<div class="image-green-border">[[File:Sa1.png|upright]]</div>
 

The diagram above depicts how the end-to-end source to contract business flow can be orchestrated leveraging the ICI for SAP Ariba Contracts integration.  

*A contract manager can create a standalone SAP Ariba Contract Workspace (ACW) or a corresponding ACW from SAP Ariba Contract Request. 
*A contract manager can also create an SAP Ariba Contract Workspace while awarding a sourcing event. 
*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 ACW, provide minimal information, and initiate authoring in ICI. You can leverage ICI’s AI capabilities to extract metadata and clauses for ease of redlining. ICI assembles the legal language based on predefined legal template and rules.

*'''Repository Contract'''

A contract manager can easily manage signed PDF contracts by uploading it directly to the ACW and publishing it. The solution automatically creates an executed agreement in ICI.

*'''Contract Review, Approval, Signature, and Execution'''

ICI capabilities around contract redlining (such as Microsoft Word Experience, online editing), approval, signature can streamline the process with proper governance. Once executed, the metadata along with a signed PDF can is synced back in 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 ACW. 

*'''Supplier Master Data'''

 You can also synch supplier master data from SAP Ariba Contracts to ICI.

*'''Auto-link sub-agreement to a Master Agreement'''

You can create a sub-agreement in ACW for an existing master agreement that is interfaced with ICI. The system creates a corresponding child agreement in ICI and auto-links it to its parent agreement.

The following data is synchronized between ICI and SAP Ariba Contracts.  

*Agreement data  
*Agreement document data 
*Agreement team data 
*Supplier master data

 

== 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.<br/>  
*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.<br/>  
*Effectively manage legal and business risk: preapproved legal templates, predefined corporate policies, and constant monitoring of contractual obligations and SLAs (Service Level Agreement) enable organizations to effectively manage legal and business risks.

== Prerequisites ==

The ICI SAP Ariba Adapter is supported with ICI versions 8.2.1, 8.2.0, 8.1.4, 8.1.3, and 8.1.2.  Ensure that the following prerequisites are met:

*SAP Ariba Contracts prerequisites 
**Use the REST API collection to integrate SAP Ariba Contract Workspaces (ACW), SAP Ariba Documents, and SAP Ariba Team. 
**The SAP Ariba REST APIs are configured with API rate limit values to make uninterrupted API calls for data syncing.  
**Task Service is up and running  
**Required events and jobs are enabled  
**SAP Ariba Contracts allows ICI Client to consume their APIs  

'''Note:''' To know more about the SAP Ariba prerequisites, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/a1709b3b0a824b018577e0add8d1b27a.html here].  

*ICI configuration prerequisites 
**Creating ICI entities  
**Mapping attributes for ICI entities (Client App Cross Reference and Client App Entity Mapping)  
**Creating filters in the Client App Filter Condition  
**Defining Date Filter criteria in the Client App Master data Sync for field: Effective Date  
**Storing SAP Ariba API connection information in the Azure Key Vault    
**The required SAP Ariba Contracts master data is imported to ICI – ICI side 
**SAP Ariba Contracts users are provisioned in ICI 
**SAP Ariba Contracts IDP integration is configured in ICI 

'''Note:''' Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the '''ICI for SAP Ariba''' adapter.

= 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.

[[File:Sa14.PNG|upright]]

 

=== Creating a Contract Using Executed Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=9 edit]] ===

1. Create a Contract Workspace in SAP Ariba Contracts in the '''Draft''' status.
<div class="image-green-border">[[File:Sa2.png|upright]]</div>
2. 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.
<div class="image-green-border">[[File:Sa15.png|upright]]</div>
3. To publish the agreement, click '''Actions '''> '''Publish '''in ACW.
<div class="image-green-border">[[File:Sa3.png|upright]]</div>
'''Note''': To know more about the standard Ariba Contract Workspace creation process, click [https://help.sap.com/docs/ARIBA_SOURCING/fa6038501b9b4b548e7a7628356e33ca/7cd9712c71ea1014a8d3d6cf4fe940c0.html here].

4. To open the ICI equivalent agreement, click the link in the '''External ID''' column (for example: ICMNDA_82).
<div class="image-green-border">[[File:Sa4.png|upright]]</div>
5. To view the SAP Ariba information in ICI, click '''''Details '''''> '''A''riba Information.'''''
<div class="image-green-border">[[File:Sa5.png|upright]]</div>
6. To view the owners of the agreement, on the left navigation pane, click '''Team'''.
<div class="image-green-border">[[File:Sa6.png|upright]]</div>
 

7. To view the contract details, click '''Details''' > '''General Information'''.
<div class="image-green-border">[[File:Sa16.png|upright]]</div>
 

8. To navigate back to the ACW, click '''Details''' > '''Ariba CW Link'''.
<div class="image-green-border">[[File:Sa7.png|upright]]</div>
9. The ACW now shows both the '''ACW ID''' and the '''Icertis ID'''.
<div class="image-green-border">[[File:Sa8.png|upright]]</div>

=== Managing Contracts Created Using Own or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=10 edit]] ===

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 by the supplier

The following diagram explains the contract initiation to contract execution process.
<div class="image-green-border">[[File:Flowchart 1v2.png|upright]]</div>
 

=== Creating a Contract Using Own Paper or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=11 edit]] ===

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.

After the contract is executed in ICI, the ACW is published automatically.

=== Managing contracts in unique scenarios[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=12 edit]] ===

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.

[[File:SAP Ariba Contract not initiated.png|upright]]

 

=== 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

[[File:CLID 1.PNG|upright]]

 

*Contract authoring is already initiated

[[File:CLID 2.PNG|upright]]

 

== Working with Amendments[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=14 edit]] ==

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

SAP Ariba supports five amendment types, please find the details below along with respective impact in ICI:

*Amendment: This amendment type allows to change any part of the Contract. In this case, an amendment agreement will be generated at ICI side and interfaced back to SAP Ariba.
*Renewal: This amendment type allows to change effective, expiration dates along with many other attributes of the contract. It’s recommended to use ‘Amendment’ option for all such changes
*Termination: This amendment type is used to close a contract before its expiration date. In this case the contract will be terminated at Ariba side and Ariba contract status will be stored in an ICI attribute.
*Administrative: This amendment type is used for change in non-contract fields like Name, Description etc. In this case the main agreement will be updated at Ariba and ICI side.
*Price Update: This amendment type allows to change existing items along with many other attributes. It’s recommended to use ‘Amendment’ option for all such changes.

 

'''Prerequisite'''

The ACW must be created, and the contract should be 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.
<div class="image-green-border">[[File:Sa11.png|upright]]</div>
6. Enter the details and click'''Create'''. The amendment record is created.
<div class="image-green-border">[[File:Sa12.png|upright]]</div>
Like agreements, a unique amendment ID is created and is synched back in ACW. The amendment is created in the '''Draft''' status.

Once the amendment is executed in ICI, the amendment is auto-published in ACW.

'''Note the following important points'''

*An ICI amendment record is created against the amendment of  a Ariba Contract workspace (ACW) · 
*An ICI amendment records goes through the same process of an agreement.
*The History tab shows the old values and the new values for all changed attributes.

== Configuration[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=15 edit]] ==

=== SAP Ariba Contracts Side configurations ===

To know more on SAP Ariba Contracts side configurations, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/79e20b26eabc4af0a486acd8818877d5.html here].

=== ICI Side configurations  ===

Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the ICI for SAP Ariba adapter.

== Glossary ==

 

{| align="left" border="1" cellpadding="1" cellspacing="1" style="width: 650px;"
|-
! scope="col" | ICI Terminology
! scope="col" | SAP Ariba Contract term
! scope="col" | Description
|-
| Agreement
| Ariba Contract Workspace (ACW)
| A legally binding contract, where all information and supporting documents are recorded.
|-
| Own Paper
| NA
| A type of paper used while creating an agreement. Own paper indicates using the organization's template to create an agreement.
|-
| Third-party paper
| NA
| A type of paper used while creating an agreement. Third-party paper indicates using an external or third-party template to create an agreement.
|-
| Executed paper
| NA
| Indicates an agreement that is created offline and uploaded to the system. The signature action for this type of agreement can be performed offline or in the system.
|}

 

 

 

 

 

 

 

 

 

 

'''Related Topics''': [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Working_with_Agreements Agreement Management]

ICI for SAP Ariba Strategic Sourcing

2022-12-02T07:27:08Z

WikiSysop:

= ICI for SAP Ariba Strategic Sourcing =

== Overview ==

'''Icertis Contract Intelligence (ICI) integration with SAP Ariba Contracts'''

The Icertis Contract Intelligence (ICI) for SAP Ariba Contracts integration provides organizations an intelligent and flexible contracting platform leveraging 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 the revenue. 
*Lack of insights from contract data leads to limited visibility to enforce performance. 
*Security, risk, and compliance helps to safeguard the brand and intellectual property rights. 

The ICI for SAP Ariba adapter provides the following capabilities.<br/>  
<div class="image-green-border">[[File:Sa1.png|upright]]</div>
 

The diagram above depicts how the end-to-end source to contract business flow can be orchestrated leveraging the ICI for SAP Ariba Contracts integration.  

*A contract manager can create a standalone SAP Ariba Contract Workspace (ACW) or a corresponding ACW from SAP Ariba Contract Request. 
*A contract manager can also create an SAP Ariba Contract Workspace while awarding a sourcing event. 
*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 ACW, provide minimal information, and initiate authoring in ICI. You can leverage ICI’s AI capabilities to extract metadata and clauses for ease of redlining. ICI assembles the legal language based on predefined legal template and rules.

*'''Repository Contract'''

A contract manager can easily manage signed PDF contracts by uploading it directly to the ACW and publishing it. The solution automatically creates an executed agreement in ICI.

*'''Contract Review, Approval, Signature, and Execution'''

ICI capabilities around contract redlining (such as Microsoft Word Experience, online editing), approval, signature can streamline the process with proper governance. Once executed, the metadata along with a signed PDF can is synced back in 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 ACW. 

*'''Supplier Master Data'''

 You can also synch supplier master data from SAP Ariba Contracts to ICI.

*'''Auto-link sub-agreement to a Master Agreement'''

You can create a sub-agreement in ACW for an existing master agreement that is interfaced with ICI. The system creates a corresponding child agreement in ICI and auto-links it to its parent agreement.

The following data is synchronized between ICI and SAP Ariba Contracts.  

*Agreement data  
*Agreement document data 
*Agreement team data 
*Supplier master data

 

== 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.<br/>  
*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.<br/>  
*Effectively manage legal and business risk: preapproved legal templates, predefined corporate policies, and constant monitoring of contractual obligations and SLAs (Service Level Agreement) enable organizations to effectively manage legal and business risks.

== Prerequisites ==

The ICI SAP Ariba Adapter is supported with ICI versions 8.2.1, 8.2.0, 8.1.4, 8.1.3, and 8.1.2.  Ensure that the following prerequisites are met:

*SAP Ariba Contracts prerequisites 
**Use the REST API collection to integrate SAP Ariba Contract Workspaces (ACW), SAP Ariba Documents, and SAP Ariba Team. 
**The SAP Ariba REST APIs are configured with API rate limit values to make uninterrupted API calls for data syncing.  
**Task Service is up and running  
**Required events and jobs are enabled  
**SAP Ariba Contracts allows ICI Client to consume their APIs  

'''Note:''' To know more about the SAP Ariba prerequisites, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/a1709b3b0a824b018577e0add8d1b27a.html here].  

*ICI configuration prerequisites 
**Creating ICI entities  
**Mapping attributes for ICI entities (Client App Cross Reference and Client App Entity Mapping)  
**Creating filters in the Client App Filter Condition  
**Defining Date Filter criteria in the Client App Master data Sync for field: Effective Date  
**Storing SAP Ariba API connection information in the Azure Key Vault    
**The required SAP Ariba Contracts master data is imported to ICI – ICI side 
**SAP Ariba Contracts users are provisioned in ICI 
**SAP Ariba Contracts IDP integration is configured in ICI 

'''Note:''' Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the '''ICI for SAP Ariba''' adapter.

= 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.

[[File:Sa14.PNG|upright]]

 

=== Creating a Contract Using Executed Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=9 edit]] ===

1. Create a Contract Workspace in SAP Ariba Contracts in the '''Draft''' status.
<div class="image-green-border">[[File:Sa2.png|upright]]</div>
2. 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.
<div class="image-green-border">[[File:Sa15.png|upright]]</div>
3. To publish the agreement, click '''Actions '''> '''Publish '''in ACW.
<div class="image-green-border">[[File:Sa3.png|upright]]</div>
'''Note''': To know more about the standard Ariba Contract Workspace creation process, click [https://help.sap.com/docs/ARIBA_SOURCING/fa6038501b9b4b548e7a7628356e33ca/7cd9712c71ea1014a8d3d6cf4fe940c0.html here].

4. To open the ICI equivalent agreement, click the link in the '''External ID''' column (for example: ICMNDA_82).
<div class="image-green-border">[[File:Sa4.png|upright]]</div>
5. To view the SAP Ariba information in ICI, click '''''Details '''''> '''A''riba Information.'''''
<div class="image-green-border">[[File:Sa5.png|upright]]</div>
6. To view the owners of the agreement, on the left navigation pane, click '''Team'''.
<div class="image-green-border">[[File:Sa6.png|upright]]</div>
 

7. To view the contract details, click '''Details''' > '''General Information'''.
<div class="image-green-border">[[File:Sa16.png|upright]]</div>
 

8. To navigate back to the ACW, click '''Details''' > '''Ariba CW Link'''.
<div class="image-green-border">[[File:Sa7.png|upright]]</div>
9. The ACW now shows both the '''ACW ID''' and the '''Icertis ID'''.
<div class="image-green-border">[[File:Sa8.png|upright]]</div>

=== Managing Contracts Created Using Own or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=10 edit]] ===

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 by the supplier

The following diagram explains the contract initiation to contract execution process.
<div class="image-green-border">[[File:Flowchart 1v2.png|upright]]</div>
 

=== Creating a Contract Using Own Paper or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=11 edit]] ===

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.

After the contract is executed in ICI, the ACW is published automatically.

=== Managing contracts in unique scenarios[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=12 edit]] ===

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.

[[File:SAP Ariba Contract not initiated.png|upright]]

 

=== 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

[[File:CLID 1.PNG|upright]]

 

*Contract authoring is already initiated

[[File:CLID 2.PNG|upright]]

 

== Working with Amendments[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=14 edit]] ==

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

SAP Ariba supports five amendment types, please find the details below along with respective impact in ICI:

*Amendment: This amendment type allows to change any part of the Contract. In this case, an amendment agreement will be generated at ICI side and interfaced back to SAP Ariba.
*Renewal: This amendment type allows to change effective, expiration dates along with many other attributes of the contract. It’s recommended to use ‘Amendment’ option for all such changes
*Termination: This amendment type is used to close a contract before its expiration date. In this case the contract will be terminated at Ariba side and Ariba contract status will be stored in an ICI attribute.
*Administrative: This amendment type is used for change in non-contract fields like Name, Description etc. In this case the main agreement will be updated at Ariba and ICI side.
*Price Update: This amendment type allows to change existing items along with many other attributes. It’s recommended to use ‘Amendment’ option for all such changes.

 

'''Prerequisite'''

The ACW must be created, and the contract should be 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.
<div class="image-green-border">[[File:Sa11.png|upright]]</div>
6. Enter the details and click'''Create'''. The amendment record is created.
<div class="image-green-border">[[File:Sa12.png|upright]]</div>
Like agreements, a unique amendment ID is created and is synched back in ACW. The amendment is created in the '''Draft''' status.

Once the amendment is executed in ICI, the amendment is auto-published in ACW.

'''Note the following important points'''

*An ICI amendment record is created against the amendment of  a Ariba Contract workspace (ACW) · 
*An ICI amendment records goes through the same process of an agreement.
*The History tab shows the old values and the new values for all changed attributes.

== Configuration[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=15 edit]] ==

=== SAP Ariba Contracts Side configurations ===

To know more on SAP Ariba Contracts side configurations, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/79e20b26eabc4af0a486acd8818877d5.html here].

=== ICI Side configurations  ===

Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the ICI for SAP Ariba adapter.

== Glossary ==

 

{| align="left" border="1" cellpadding="1" cellspacing="1" style="width: 650px;"
|-
! scope="col" | ICI Terminology
! scope="col" | SAP Ariba Contract term
! scope="col" | Description
|-
| Agreement
| Ariba Contract Workspace (ACW)
| A legally binding contract, where all information and supporting documents are recorded.
|-
| Own Paper
| NA
| A type of paper used while creating an agreement. Own paper indicates using the organization's template to create an agreement.
|-
| Third-party paper
| NA
| A type of paper used while creating an agreement. Third-party paper indicates using an external or third-party template to create an agreement.
|-
| Executed paper
| NA
| Indicates an agreement that is created offline and uploaded to the system. The signature action for this type of agreement can be performed offline or in the system.
|}

 

 

 

 

 

 

 

 

 

 

'''Related Topics''': [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Working_with_Agreements Agreement Management]

ICI for SAP Ariba Strategic Sourcing

2022-12-02T07:26:51Z

WikiSysop:

= ICI for SAP Ariba Strategic Sourcing =

== Overview ==

'''Icertis Contract Intelligence (ICI) integration with SAP Ariba Contracts'''

The Icertis Contract Intelligence (ICI) for SAP Ariba Contracts integration provides organizations an intelligent and flexible contracting platform leveraging 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 the revenue. 
*Lack of insights from contract data leads to limited visibility to enforce performance. 
*Security, risk, and compliance helps to safeguard the brand and intellectual property rights. 

The ICI for SAP Ariba adapter provides the following capabilities.<br/>  
<div class="image-green-border">[[File:Sa1.png|upright]]</div>
 

The diagram above depicts how the end-to-end source to contract business flow can be orchestrated leveraging the ICI for SAP Ariba Contracts integration.  

*A contract manager can create a standalone SAP Ariba Contract Workspace (ACW) or a corresponding ACW from SAP Ariba Contract Request. 
*A contract manager can also create an SAP Ariba Contract Workspace while awarding a sourcing event. 
*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 ACW, provide minimal information, and initiate authoring in ICI. You can leverage ICI’s AI capabilities to extract metadata and clauses for ease of redlining. ICI assembles the legal language based on predefined legal template and rules.

*'''Repository Contract'''

A contract manager can easily manage signed PDF contracts by uploading it directly to the ACW and publishing it. The solution automatically creates an executed agreement in ICI.

*'''Contract Review, Approval, Signature, and Execution'''

ICI capabilities around contract redlining (such as Microsoft Word Experience, online editing), approval, signature can streamline the process with proper governance. Once executed, the metadata along with a signed PDF can is synced back in 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 ACW. 

*'''Supplier Master Data'''

 You can also synch supplier master data from SAP Ariba Contracts to ICI.

*'''Auto-link sub-agreement to a Master Agreement'''

You can create a sub-agreement in ACW for an existing master agreement that is interfaced with ICI. The system creates a corresponding child agreement in ICI and auto-links it to its parent agreement.

The following data is synchronized between ICI and SAP Ariba Contracts.  

*Agreement data  
*Agreement document data 
*Agreement team data 
*Supplier master data

 

== 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.<br/>  
*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.<br/>  
*Effectively manage legal and business risk: preapproved legal templates, predefined corporate policies, and constant monitoring of contractual obligations and SLAs (Service Level Agreement) enable organizations to effectively manage legal and business risks.

== Prerequisites ==

The ICI SAP Ariba Adapter is supported with ICI versions 8.2.1, 8.2.0, 8.1.4, 8.1.3, and 8.1.2.  Ensure that the following prerequisites are met:

*SAP Ariba Contracts prerequisites 
**Use the REST API collection to integrate SAP Ariba Contract Workspaces (ACW), SAP Ariba Documents, and SAP Ariba Team. 
**The SAP Ariba REST APIs are configured with API rate limit values to make uninterrupted API calls for data syncing.  
**Task Service is up and running  
**Required events and jobs are enabled  
**SAP Ariba Contracts allows ICI Client to consume their APIs  

'''Note:''' To know more about the SAP Ariba prerequisites, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/a1709b3b0a824b018577e0add8d1b27a.html here].  

*ICI configuration prerequisites 
**Creating ICI entities  
**Mapping attributes for ICI entities (Client App Cross Reference and Client App Entity Mapping)  
**Creating filters in the Client App Filter Condition  
**Defining Date Filter criteria in the Client App Master data Sync for field: Effective Date  
**Storing SAP Ariba API connection information in the Azure Key Vault    
**The required SAP Ariba Contracts master data is imported to ICI – ICI side 
**SAP Ariba Contracts users are provisioned in ICI 
**SAP Ariba Contracts IDP integration is configured in ICI 

'''Note:''' Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the '''ICI for SAP Ariba''' adapter.

= 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.

[[File:Sa14.PNG|upright]]

 

=== Creating a Contract Using Executed Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=9 edit]] ===

1. Create a Contract Workspace in SAP Ariba Contracts in the '''Draft''' status.
<div class="image-green-border">[[File:Sa2.png|upright]]</div>
2. 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.
<div class="image-green-border">[[File:Sa15.png|upright]]</div>
3. To publish the agreement, click '''Actions '''> '''Publish '''in ACW.
<div class="image-green-border">[[File:Sa3.png|upright]]</div>
'''Note''': To know more about the standard Ariba Contract Workspace creation process, click [https://help.sap.com/docs/ARIBA_SOURCING/fa6038501b9b4b548e7a7628356e33ca/7cd9712c71ea1014a8d3d6cf4fe940c0.html here].

4. To open the ICI equivalent agreement, click the link in the '''External ID''' column (for example: ICMNDA_82).
<div class="image-green-border">[[File:Sa4.png|upright]]</div>
5. To view the SAP Ariba information in ICI, click '''''Details '''''> '''A''riba Information.'''''
<div class="image-green-border">[[File:Sa5.png|upright]]</div>
6. To view the owners of the agreement, on the left navigation pane, click '''Team'''.
<div class="image-green-border">[[File:Sa6.png|upright]]</div>
 

7. To view the contract details, click '''Details''' > '''General Information'''.
<div class="image-green-border">[[File:Sa16.png|upright]]</div>
 

8. To navigate back to the ACW, click '''Details''' > '''Ariba CW Link'''.
<div class="image-green-border">[[File:Sa7.png|upright]]</div>
9. The ACW now shows both the '''ACW ID''' and the '''Icertis ID'''.
<div class="image-green-border">[[File:Sa8.png|upright]]</div>

=== Managing Contracts Created Using Own or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=10 edit]] ===

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 by the supplier

The following diagram explains the contract initiation to contract execution process.
<div class="image-green-border">[[File:Flowchart 1v2.png|upright]]</div>
 

=== Creating a Contract Using Own Paper or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=11 edit]] ===

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.

After the contract is executed in ICI, the ACW is published automatically.

=== Managing contracts in unique scenarios[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=12 edit]] ===

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.

[[File:SAP Ariba Contract not initiated.png|upright]]

 

=== 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

[[File:CLID 1.PNG|upright]]

 

*Contract authoring is already initiated

[[File:CLID 2.PNG|upright]]

 

== Working with Amendments[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=14 edit]] ==

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

SAP Ariba supports five amendment types, please find the details below along with respective impact in ICI:

*Amendment: This amendment type allows to change any part of the Contract. In this case, an amendment agreement will be generated at ICI side and interfaced back to SAP Ariba.
*Renewal: This amendment type allows to change effective, expiration dates along with many other attributes of the contract. It’s recommended to use ‘Amendment’ option for all such changes
*Termination: This amendment type is used to close a contract before its expiration date. In this case the contract will be terminated at Ariba side and Ariba contract status will be stored in an ICI attribute.
*Administrative: This amendment type is used for change in non-contract fields like Name, Description etc. In this case the main agreement will be updated at Ariba and ICI side.
*Price Update: This amendment type allows to change existing items along with many other attributes. It’s recommended to use ‘Amendment’ option for all such changes.

 

'''Prerequisite'''

The ACW must be created, and the contract should be 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.
<div class="image-green-border">[[File:Sa11.png|upright]]</div>
6. Enter the details and click'''Create'''. The amendment record is created.
<div class="image-green-border">[[File:Sa12.png|upright]]</div>
Like agreements, a unique amendment ID is created and is synched back in ACW. The amendment is created in the '''Draft''' status.

Once the amendment is executed in ICI, the amendment is auto-published in ACW.

'''Note the following important points'''

*An ICI amendment record is created against the amendment of  a Ariba Contract workspace (ACW) · 
*An ICI amendment records goes through the same process of an agreement.
*The History tab shows the old values and the new values for all changed attributes.

== Configuration[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=15 edit]] ==

=== SAP Ariba Contracts Side configurations ===

To know more on SAP Ariba Contracts side configurations, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/79e20b26eabc4af0a486acd8818877d5.html here].

=== ICI Side configurations  ===

Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the ICI for SAP Ariba adapter.

== Glossary ==

 

{| align="left" border="1" cellpadding="1" cellspacing="1" style="width: 650px;"
|-
! scope="col" | ICI Terminology
! scope="col" | SAP Ariba Contract term
! scope="col" | Description
|-
| Agreement
| Ariba Contract Workspace (ACW)
| A legally binding contract, where all information and supporting documents are recorded.
|-
| Own Paper
| NA
| A type of paper used while creating an agreement. Own paper indicates using the organization's template to create an agreement.
|-
| Third-party paper
| NA
| A type of paper used while creating an agreement. Third-party paper indicates using an external or third-party template to create an agreement.
|-
| Executed paper
| NA
| Indicates an agreement that is created offline and uploaded to the system. The signature action for this type of agreement can be performed offline or in the system.
|}

 

 

 

 

 

 

 

 

 

 

 

 

'''Related Topics''': [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Working_with_Agreements Agreement Management]

ICI for SAP Ariba Strategic Sourcing

2022-12-02T07:26:30Z

WikiSysop:

= ICI for SAP Ariba Strategic Sourcing =

== Overview ==

'''Icertis Contract Intelligence (ICI) integration with SAP Ariba Contracts'''

The Icertis Contract Intelligence (ICI) for SAP Ariba Contracts integration provides organizations an intelligent and flexible contracting platform leveraging 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 the revenue. 
*Lack of insights from contract data leads to limited visibility to enforce performance. 
*Security, risk, and compliance helps to safeguard the brand and intellectual property rights. 

The ICI for SAP Ariba adapter provides the following capabilities.<br/>  
<div class="image-green-border">[[File:Sa1.png|upright]]</div>
 

The diagram above depicts how the end-to-end source to contract business flow can be orchestrated leveraging the ICI for SAP Ariba Contracts integration.  

*A contract manager can create a standalone SAP Ariba Contract Workspace (ACW) or a corresponding ACW from SAP Ariba Contract Request. 
*A contract manager can also create an SAP Ariba Contract Workspace while awarding a sourcing event. 
*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 ACW, provide minimal information, and initiate authoring in ICI. You can leverage ICI’s AI capabilities to extract metadata and clauses for ease of redlining. ICI assembles the legal language based on predefined legal template and rules.

*'''Repository Contract'''

A contract manager can easily manage signed PDF contracts by uploading it directly to the ACW and publishing it. The solution automatically creates an executed agreement in ICI.

*'''Contract Review, Approval, Signature, and Execution'''

ICI capabilities around contract redlining (such as Microsoft Word Experience, online editing), approval, signature can streamline the process with proper governance. Once executed, the metadata along with a signed PDF can is synced back in 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 ACW. 

*'''Supplier Master Data'''

 You can also synch supplier master data from SAP Ariba Contracts to ICI.

*'''Auto-link sub-agreement to a Master Agreement'''

You can create a sub-agreement in ACW for an existing master agreement that is interfaced with ICI. The system creates a corresponding child agreement in ICI and auto-links it to its parent agreement.

The following data is synchronized between ICI and SAP Ariba Contracts.  

*Agreement data  
*Agreement document data 
*Agreement team data 
*Supplier master data

 

== 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.<br/>  
*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.<br/>  
*Effectively manage legal and business risk: preapproved legal templates, predefined corporate policies, and constant monitoring of contractual obligations and SLAs (Service Level Agreement) enable organizations to effectively manage legal and business risks.

== Prerequisites ==

The ICI SAP Ariba Adapter is supported with ICI versions 8.2.1, 8.2.0, 8.1.4, 8.1.3, and 8.1.2.  Ensure that the following prerequisites are met:

*SAP Ariba Contracts prerequisites 
**Use the REST API collection to integrate SAP Ariba Contract Workspaces (ACW), SAP Ariba Documents, and SAP Ariba Team. 
**The SAP Ariba REST APIs are configured with API rate limit values to make uninterrupted API calls for data syncing.  
**Task Service is up and running  
**Required events and jobs are enabled  
**SAP Ariba Contracts allows ICI Client to consume their APIs  

'''Note:''' To know more about the SAP Ariba prerequisites, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/a1709b3b0a824b018577e0add8d1b27a.html here].  

*ICI configuration prerequisites 
**Creating ICI entities  
**Mapping attributes for ICI entities (Client App Cross Reference and Client App Entity Mapping)  
**Creating filters in the Client App Filter Condition  
**Defining Date Filter criteria in the Client App Master data Sync for field: Effective Date  
**Storing SAP Ariba API connection information in the Azure Key Vault    
**The required SAP Ariba Contracts master data is imported to ICI – ICI side 
**SAP Ariba Contracts users are provisioned in ICI 
**SAP Ariba Contracts IDP integration is configured in ICI 

'''Note:''' Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the '''ICI for SAP Ariba''' adapter.

= 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.

[[File:Sa14.PNG|upright]]

 

=== Creating a Contract Using Executed Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=9 edit]] ===

1. Create a Contract Workspace in SAP Ariba Contracts in the '''Draft''' status.
<div class="image-green-border">[[File:Sa2.png|upright]]</div>
2. 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.
<div class="image-green-border">[[File:Sa15.png|upright]]</div>
3. To publish the agreement, click '''Actions '''> '''Publish '''in ACW.
<div class="image-green-border">[[File:Sa3.png|upright]]</div>
'''Note''': To know more about the standard Ariba Contract Workspace creation process, click [https://help.sap.com/docs/ARIBA_SOURCING/fa6038501b9b4b548e7a7628356e33ca/7cd9712c71ea1014a8d3d6cf4fe940c0.html here].

4. To open the ICI equivalent agreement, click the link in the '''External ID''' column (for example: ICMNDA_82).
<div class="image-green-border">[[File:Sa4.png|upright]]</div>
5. To view the SAP Ariba information in ICI, click '''''Details '''''> '''A''riba Information.'''''
<div class="image-green-border">[[File:Sa5.png|upright]]</div>
6. To view the owners of the agreement, on the left navigation pane, click '''Team'''.
<div class="image-green-border">[[File:Sa6.png|upright]]</div>
 

7. To view the contract details, click '''Details''' > '''General Information'''.
<div class="image-green-border">[[File:Sa16.png|upright]]</div>
 

8. To navigate back to the ACW, click '''Details''' > '''Ariba CW Link'''.
<div class="image-green-border">[[File:Sa7.png|upright]]</div>
9. The ACW now shows both the '''ACW ID''' and the '''Icertis ID'''.
<div class="image-green-border">[[File:Sa8.png|upright]]</div>

=== Managing Contracts Created Using Own or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=10 edit]] ===

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 by the supplier

The following diagram explains the contract initiation to contract execution process.
<div class="image-green-border">[[File:Flowchart 1v2.png|upright]]</div>
 

=== Creating a Contract Using Own Paper or Third party Paper[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=11 edit]] ===

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.

After the contract is executed in ICI, the ACW is published automatically.

=== Managing contracts in unique scenarios[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=12 edit]] ===

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.

[[File:SAP Ariba Contract not initiated.png|upright]]

 

=== 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

[[File:CLID 1.PNG|upright]]

 

*Contract authoring is already initiated

[[File:CLID 2.PNG|upright]]

 

== Working with Amendments[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=14 edit]] ==

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

SAP Ariba supports five amendment types, please find the details below along with respective impact in ICI:

*Amendment: This amendment type allows to change any part of the Contract. In this case, an amendment agreement will be generated at ICI side and interfaced back to SAP Ariba.
*Renewal: This amendment type allows to change effective, expiration dates along with many other attributes of the contract. It’s recommended to use ‘Amendment’ option for all such changes
*Termination: This amendment type is used to close a contract before its expiration date. In this case the contract will be terminated at Ariba side and Ariba contract status will be stored in an ICI attribute.
*Administrative: This amendment type is used for change in non-contract fields like Name, Description etc. In this case the main agreement will be updated at Ariba and ICI side.
*Price Update: This amendment type allows to change existing items along with many other attributes. It’s recommended to use ‘Amendment’ option for all such changes.

 

'''Prerequisite'''

The ACW must be created, and the contract should be 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.
<div class="image-green-border">[[File:Sa11.png|upright]]</div>
6. Enter the details and click'''Create'''. The amendment record is created.
<div class="image-green-border">[[File:Sa12.png|upright]]</div>
Like agreements, a unique amendment ID is created and is synched back in ACW. The amendment is created in the '''Draft''' status.

Once the amendment is executed in ICI, the amendment is auto-published in ACW.

'''Note the following important points'''

*An ICI amendment record is created against the amendment of  a Ariba Contract workspace (ACW) · 
*An ICI amendment records goes through the same process of an agreement.
*The History tab shows the old values and the new values for all changed attributes.

== Configuration[[https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Ici_for_SAP_Ariba&action=edit&section=15 edit]] ==

=== SAP Ariba Contracts Side configurations ===

To know more on SAP Ariba Contracts side configurations, click [https://help.sap.com/docs/ARIBA_SOURCING/9e0dca5bce1347ceb72ccae76a15c2c9/79e20b26eabc4af0a486acd8818877d5.html here].

=== ICI Side configurations  ===

Contact your Icertis Contract Intelligence (ICI) implementation team to complete the configuration of the ICI for SAP Ariba adapter.

== Glossary ==

 

{| align="left" border="1" cellpadding="1" cellspacing="1" style="width: 650px;"
|-
! scope="col" | ICI Terminology
! scope="col" | SAP Ariba Contract term
! scope="col" | Description
|-
| Agreement
| Ariba Contract Workspace (ACW)
| A legally binding contract, where all information and supporting documents are recorded.
|-
| Own Paper
| NA
| A type of paper used while creating an agreement. Own paper indicates using the organization's template to create an agreement.
|-
| Third-party paper
| NA
| A type of paper used while creating an agreement. Third-party paper indicates using an external or third-party template to create an agreement.
|-
| Executed paper
| NA
| Indicates an agreement that is created offline and uploaded to the system. The signature action for this type of agreement can be performed offline or in the system.
|}

 

 

 

 

 

 

 

 

 

 

 

 

 

 

'''Related Topics''': [https://iciwikiapac.icertis.com/ICIHelp8.2/index.php?title=Working_with_Agreements Agreement Management]