How Gilgen Door Systems Creates Complex Quotes From SAP

The manufacturer writes extensive, highly individualized and sometimes very complex quotations. Until now, these were created outside of SAP in MS Word. This was very time-consuming, error-prone, and obviously not integrated in their SAP systems. From now on, the offers will be created using the SAP module SD. SAP partner Teamwork developed a quotation tool that could cover the extensive requirements.

DocBuilder is now used to generate the quotation documents. The standard solution is used by several SAP customers and accesses both SAP and third-party data sources. In the case of Gilgen DS, DocBuilder creates MS Word quotation documents in either DOCX, PDF, or PDF/A file format directly from SAP with the addition of various data sources. MS Word templates which are structured similarly to a serial letter serve as the foundation. However, the fields from SAP or third-party solutions are connected to data sources and are more powerful.

Thanks to this MS Word standard technology, it is possible for the business departments to create and modify forms without any developer knowledge and participation. The dispatch of offers works in a similar way. The customer data from SAP is transferred to MS Outlook, predefined texts are added, and the offer is attached as a PDF file. The entire quotation process at Gilgen DS is now user-friendly, automated, and efficient.

Procedure

First, the prerequisites for complex quotation creation in SAP had to be established. At Gilgen DS, a quotation consists of many individual components, variants, and items, and it must be possible to create them in three languages and in different versions. The main challenges for Teamwork consisted of the user-friendly creation of complex quotations in SAP, the customer requirements for the design of the quotation documents, and the automated dispatch process via e-mail. DocBuilder is fully integrated in the SAP environment as well as in MS Word and uses the best of both worlds.

The quotation process works as follows: first, the quotation data including the positions are entered in the SAP quotation tool by the Gilgen DS customer service center. For this purpose, the quote tool developed by Teamwork based on SAP SD is used. The documents are then generated automatically from SAP with the addition of third-party data sources (e.g. images, technical documents) via TW Solutions DocBuilder using the MS Word templates. The MS Word document can then be customized by the customer service center employees. Once checked and approved, a PDF document is automatically generated. The PDF document is subsequently transferred by TW Solutions DocBuilder to MS Outlook ready for dispatch, including e-mail address, subject, and mail text, and can be sent directly. 

Thanks to the SAP integration, the price calculation from SAP SD can be used. Also very important are the creation and management of different versions and variants of an offer, the processing assignment and tracking functions, and the integration into the existing document management solution. Today, the quote process is very lean and standardized. With DocBuilder, Gilgen DS was able to significantly increase both efficiency in the offer process and quality. 

Flexible solutions

DocBuilder offers flexible form generation from all SAP and many non-SAP systems. These can also be cloud systems such as SuccessFactors, Ariba, Workday, Salesforce or others. Data from a wide variety of systems can be displayed on a form. DocBuilder makes use of the familiar functionality of Microsoft Word's mail merge fields. The solution is intelligent and can implement important objects such as images, if-then queries, tables, barcodes, signatures, text modules, different languages and colloquialisms as standard. Output is in Word, Adobe PDF or in e-mail templates with direct integration into MS Exchange and/or an archive if required.

The overall solution consists of three main components: First, DocBuilder itself - the heart of the solution - is installed as an add-on for SAP Abap on the SAP NetWeaver system. The add-on is delivered in TeamWork's own namespace, which means that no conflicts with existing code can arise.

Using the add-on, the data is retrieved from the SAP or other source systems, prepared and assigned to the document tags. The DocBuilder transfers the prepared data and the template as an XML file to the Doc Renderer via http(s) protocol and receives and saves the finished document. The second component is the DocRenderer, a Java EE servlet. This generates the actual document from the data prepared in the DocBuilder, the recipe and the template and returns this in turn to the DocBuilder as an XML file via http(s). The DocBuilder saves the document in a document archive and/or outputs it as a Word or PDF document. 

The third part is DocModeler. It is also supplied as an add-on for SAP Abap. This enables the department to maintain the Microsoft Word-based templates via a web browser, define text modules and enrich them with additional data. DocModeler also includes a Microsoft Word add-in that displays the tags maintained in SAP in Word and enables them to be inserted as a mail merge field in a simplified manner. The DocBuilder uses the SAP GUI as the user interface for providing the variables in the recipe, Word for creating the templates and any web browser for administering the templates.

TeamWork is currently working on a fourth component that automates the integration of digital signatures via Skribble. This will allow documents to be directly integrated into legally valid digital signature runs and thus also automate the signature processes. 

Requirements

The installation requires an SAP system from release ECC 6.0 EhP 4 with NetWeaver stack from release 7.2 and a Java component (J2EE-compatible server from Java 1.6). DocBuilder has also been used in the S/4 Hana environment by several customers since 2017. The templates are created in Microsoft Word version 2003 or higher; no Word installation is required to generate the documents. Licensing is based on company size, number of SAP production systems and area of use, regardless of the number of users, and the solution is not affected by SAP Indirect Access.

The installation and basic configuration is usually done together with the customer within a few days. For the areas of SAP HCM and SAP RE-FX, a comprehensive recipe with a high standard specification is delivered; for other SAP modules and solutions, the recipe is created customer-specifically. Depending on the area of application and specification, further adjustments may be necessary. 

Conclusion

Currently, a NetWeaver stack is always a prerequisite for installation. TeamWork will also launch a cloud version in the coming months. The target groups for this solution are diverse and can be SAP cloud customers (Business by Design, S/4 Hana Cloud, SuccessFactors, etc.) as well as pure non-SAP customers (Workday, Microsoft, Oracle, etc.).