Show TOC

SAP Document Builder Implementation ConsiderationsLocate this document in the navigation structure

SAP Document Builder is shipped with Customizing that contains detailed configuration information and sample entries. It enables content managers to define content in accordance with their business requirements. Various business add-ins (BAdIs) enhance standard functions.

Customizing includes functional and technical tasks. While functional implementation focuses on content configuration, technical implementation encompasses an array of tasks, such as mapping, form and report design, configuration of an assembly server, and BAdI implementations. Some tasks are performed once during implementation and other tasks require ongoing maintenance. Some key considerations for implementation include the following:

  • Editor and assembly tool

  • Integration with other components

  • Blueprint of the structure and format of document output

  • Business rules to generate documents

  • Form use

You use the following information as guidelines for implementation decisions and as a starting point to gather information for the blueprinting process. SAP Document Builder solutions are not limited to the tools mentioned; you can create your own implementation with other editors or assembly tools.

SAP Document Builder is flexible and enables you to create documents in various formats. The tools used to edit and assemble are based on your requirements. For example, you can generate a PDF, an XML, a WordML, or a DOCX document, or a combination of PDF and Microsoft Word documents, to meet the requirements of your scenario. SAP Document Builder supports WordML and DOCX. WordML is supported for Microsoft Word 2003 and 2007; DOCX is supported for Microsoft Word 2007. DOCX is the preferred format because it does not require third-party ActiveX Control to edit element text while the WordML format does.

Note

The WordML format implementation for PCs with the Microsoft Windows 7 OS is limited. For more information, see SAP Note 1547431 Information published on SAP site.

The following table lists the possible element and output formats and the required tools:

Element Format

Output Format

Third-Party Tool

Microsoft Word + Microsoft Word + Microsoft Word

Microsoft Word

Assembly: None required

Editing: ActiveX Control for WordML only

Adobe Acrobat + Adobe Acrobat + Microsoft Word

Adobe Acrobat

Assembly: Adobe LiveCycle

Editing: ActiveX Control for WordML only

HTML + HTML + Adobe Acrobat

Adobe Acrobat

Assembly: Adobe LiveCycle

Editing: SAP BTF or third-party editor

HTML + HTML + HTML

Adobe Acrobat

Assembly: Apache FOP

Editing: SAP BTF or third-party editor

XML + XML + XML

XML

Assembly: None required

Editing: XML editor

The following table lists general recommendations based on your requirements:

Output Format

Third-Party Tool

Requirement

Document Format

Microsoft Word

Assembly: None required

Editing: ActiveX Control for WordML only

  • Frequent editing

  • Spell checker

Advanced

Adobe Acrobat

Assembly: Adobe LiveCycle

Editing: ActiveX Control for WordML only

  • Embedded PDF forms

  • Frequent editing

  • Spell checker

Advanced

Adobe Acrobat

Assembly: Adobe LiveCycle

Editing: SAP BTF or third-party editor

  • Embedded PDF forms

  • Limited editing

Simple

Adobe Acrobat

Assembly: Apache FOP

Editing: SAP BTF or third-party editor

  • No embedded PDF forms

  • Limited editing

Simple

XML

Assembly: None required

Editing: XML editor

N/A

Simple

Note

You can select other tools.