cancel
Showing results for 
Search instead for 
Did you mean: 

Ariba vs ESO - for contract Management

Former Member
0 Kudos

Hi,

currently we have 2 systems - Ariba and ESO. We are deciding on to which system should we keep for our contract management and migrate the one that is not suitable out to the one that is best. Anyone who has experience with both system for contract management? What is your recommendation?

Regards,

Lisa

Accepted Solutions (1)

Accepted Solutions (1)

tridip_chakraborthy
Contributor
0 Kudos

Hi Lisa

This is a very tricky question.

Trust me, I have worked on both these solutions and both stand best of breed for contract management since they have Both Operational and legal contracts

However, if you are an SAP shop, its much preferred to go with SAP ESO since there is a standard integration solution that comes as a Consulting solution with the latest available ESO version 5.1 and will be available as a delivered solution as a part of the standard offerign with ESO 6.0 release

Hope this clarifies

Regards

Tridip

Former Member
0 Kudos

Hi Tridip,

Thanks. Have you ever done immigration of Ariba contract to ESO before. Does it requires great effort and is it possible?

Regards

Lisa

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi james,

Is there any similar template/method to upload legacy RFx documents.

Thanks in advance,

Sai.

james_wojnicki
Employee
Employee
0 Kudos

Hi Lisa,

SAP CLM does have a contract migration tool. Once set up it is relatively easy to utilize.

What you do is use a CSV Import file to create Master Agreements as containers for the Contract Documents (This is the meta data associated with the contract: Vendor/ Customer, Owner, Validity Dates etc.) Then you use the Contract/ Attachment Importer to import the Contract Documents (.doc or .pdf or other format) into the system. Then you use a automated report to generate a conversion file that converts the attachments to contract documents associated with the appropriate Master Agreement. Of course this can be done a number of ways but this is the basic process. Sounds a little complicated but once you get the hang of it it is relatively simple. Most time consuming part is getting the .doc or .pdf files.

If you need more information on Ariba Contracts vs. SAP CLM have your SAP sales person contact me by email they will find me in their Global Address List.

Regards,

James

Former Member
0 Kudos

Hi James,

Does the contract importer work the same way for Master Agreements and Agreements. For ex: If we want the attachment to be made to the agreements in some cases and in MA in other cases - would maintaining the mapping in the doc mapping file be sufficient?

Thanks & Regards,

Srivatsan

Former Member
0 Kudos

Hi James,

Indeed the method is bit complex. Is there any step by step manual to follow with the same.

Regards,

Tripti

tridip_chakraborthy
Contributor
0 Kudos

Hi All,

In one of our past projects on Contract Migration from legacy system to SAP Sourcing was quite complex

However, this is what we did

1) Analyzed all the fields that are coming in from the Legacy Contract Management system

2) Created a one-on one mapping table that maps the fields from the legacy system to the SAP Sourcing Contract Importer

3) Created extensions and Collections for all the fields that are non-standard Client specific and buffered them into the Contracts Import workbook

4) Uploaded the Contracts workbook.

However at step 4, an additional step is required, if there is a one to many upload and referencing to attachments to contracts, you need to open an OSS message with SAP and their COnsulting Solution team would help in creating the attachment and Contracts importer JAR file, this JAR file is based on the version of SAP Sourcing and the patch level.

This is not 100% accurate, but it is definitely better than going into each contract individually and uploading attachments.

Business situation

If the Activity is as complex such as migrating from a legacy system that has over 1000 contracts and these 1000 contracts have 500+ sub agreements and there is many to one relationship between contracts and the relevant attachments associated with the Contract Metadata, its worth going in for the SAP Consulting solution

Regards

Tridip

Former Member
0 Kudos

Yes we did it and it do require decent amount to manual work cleaning up the data extracted from Ariba before importing to ESO.

Good Luck