Introduction
SAP Sourcing/CLM can use either the Microsoft .NET-based WordService or the JAVA-based SAP Sourcing DOCX Generation Service to generate structured contract documents using clause documents, collection variable documents, and contract document templates.
SAP Sourcing DOCX Generation
The Microsoft .NET-based WordService requires setup of an additional Windows server. Due to this overhead and additional TCO, versions of SAP Sourcing 7.0 SP5/9.0 SP11/10.0 or higher now also support the SAP Sourcing DOCX Generation Service, which is WordService based on JAVA technology. The SAP Sourcing DOCX Generation Service does not require an additional Windows server. As this is lower TCO, we recommend switching to the SAP Sourcing DOCX Generation service. For more information on the JAVA-based generation service, see the following link:
The New SAP Sourcing & CLM DOCX Generation service
Microsoft .NET-based Word Service
The Microsoft .NET-based WordService requires setup of an additional Windows server. It uses MS Word on the Windows server to perform operations on the clause documents and generate a structured contract document.
Follow these steps to install the Microsoft .NET-based WordService:
1. Verify that you meet the prerequisites for the installation of .Net WordService. See the checklist of prerequisites:
Prerequisites to configure .Net based contract Generation service
2. Create an “Office Automation User” user account. This user should perform the operations in MS Word on the Windows machine for the generation of contract documents. We recommend not using this user for any other purpose, as that might disrupt the configuration, resulting in the failure of the contract generation service.
Create Office Automation User
3. Install the WordService. For details, see: Install WordService
4. Configure the WordService. For details, including screenshots, see:
Configure IIS for WordService
5. When the installation is complete, check the whether the WordService is working as desired by following these steps: Verify that Contract Generation WordService is working.
6. If the WordService is not working as desired, refer to the troubleshooting techniques here:
General Contract Generation Checklist for CLM Versions 9.x and Below
