Business Case & Problem Statement

In many SAP SuccessFactors implementations, HR teams rely on a variety of employee-facing documents — offer letters, confirmation letters, salary certificates, experience letters, and more. Traditionally, generating these documents requires navigating multiple screens: locating the employee profile, accessing the Document Generation module, selecting the appropriate template, and downloading the result. This multi-step process is not only time-consuming but also error-prone, especially when the document context is tied to a specific business record stored in a custom Metadata Framework (MDF) object.

The challenge becomes even more pronounced in scenarios where:

• HR business processes are captured in custom MDF objects (e.g., a probation review record, a training completion record, or a custom agreement tracker).
• The document to be generated depends on the type of record selected in the MDF object (e.g., different letter types mapped via a picklist).
• HR administrators want a single-click experience directly from the MDF object record, without switching contexts or re-entering data.

The Solution

SAP SuccessFactors provides a powerful combination of Document Generation, the Metadata Framework, Picklist Center, and Configuration UI that — when wired together correctly — enables HR teams to generate and download a PDF document directly from a link embedded in a custom MDF object screen. No additional navigation. No re-entry of data. One click.

This blog walks through the complete configuration required to achieve this. It is intended for SAP SuccessFactors consultants and HR system administrators who are comfortable working in Admin Center and the Metadata Framework.

Key Business Benefits

• Reduced Process Time: HR administrators can generate the correct document in a single click directly from the MDF record, eliminating context-switching and manual lookups.
• Dynamic Template Selection: By linking the picklist external code to the Document Template ID, the system automatically selects the right template based on the document type chosen in the MDF record — no hardcoding required.
• Scalability: Adding new document types is as simple as adding a new picklist value and a new template — no changes to the MDF object definition or UI configuration are needed.
• Improved Data Accuracy: Token-based data population pulls live data directly from the system of record, ensuring documents always reflect accurate, up-to-date information without manual intervention.

Solution Architecture Overview

The configuration involves five interdependent components that must be set up in sequence:

• Document Generation Template — the Word-based template with token placeholders that will be merged into the final PDF.
• Picklist with External Codes — a picklist whose external code values match the Document Template IDs, acting as the bridge between user selection and template resolution.
• Custom MDF Object — the business record object with a Picklist field (to select document type) and a String field (to hold the generation link).
• Configuration UI with a Link — the UI screen for the MDF object, enhanced with a dynamic link element that triggers document generation with the correct token values injected into the URL.
• Business Rule — an optional but recommended rule to automate link population upon save, ensuring the link is always in sync with the selected document type.

Let’s walk through each step in detail.

Configuration Steps

Step 1: Create Document Generation Template

• Template Creation Process: Navigate to Admin Center > Document Generation – Manage Document Template and click “Create New”
• Template Configuration Settings: Select “Document Generation Template” as the category and configure template content with placeholders using [[tokenName]] syntax
• Document ID Assignment: Assign a unique Document ID to your template – this will be crucial for the picklist configuration in the next step

Step 2: Configure Picklist with External Code

• Picklist Creation Steps: Go to Admin Center > Picklist Center and create a new picklist for document types
• External Code Configuration Matching Document ID: Set the external code of your picklist values to match exactly with the Document ID from Step 1 – this creates the connection between your MDF object and the document template

Step 3: Create Custom MDF Object with Required Fields

Field 1: Document Type Field

• Document Type Field Configuration: In Configure Object Definitions, create a custom MDF object and add a field for document type
• Picklist Assignment to Document Type Field: Set the data type as “Picklist” and assign the picklist created in Step 2 as the Valid Values Source

Field 2: String Field(Generate Document)

• String Field Creation: Add a second custom field with data type “String” to capture additional information needed for document generation
• Field Properties and Data Type Settings: Configure field length, validation rules, and visibility settings as per business requirements

Step 4: Create UI and Configure Link with Token Mapping

• UI Creation Process: Navigate to Admin Center > Manage Configuration UI and create a new UI screen for your custom MDF object
• Link Addition to UI: Use the “Add Link” functionality in the UI configuration to add a document generation link
• Token Insertion Methodology: Configure the link URL with tokens that will dynamically populate values from your MDF object fields.

Step 5: Create Business Rule with Instance Configuration

Generate Document and Download PDF

• Document Generation Link Activation: After selecting values in your custom MDF object and saving the record, click on the “Generate Document” link

Summary & Final Thoughts

By combining SAP SuccessFactors’ Document Generation module with a custom MDF object, a Picklist with aligned external codes, a Configuration UI link, and an optional Business Rule, you can deliver a seamless one-click document generation experience to your HR team — all without any external integrations.

The key insight in this configuration is the use of the picklist’s external code as the bridge between the user’s document type selection and the Document Template ID. This elegant mapping makes the solution both flexible and scalable — new document types can be supported simply by adding a new picklist entry and a matching template, with zero changes to the object definition or UI.

This pattern can be applied to a wide range of HR use cases: probation confirmation letters, training completion certificates, employment verification letters, custom agreement forms, and more. Once the framework is in place, rolling out additional document types becomes a configuration-only activity.

Have questions or a variation of this use case? Feel free to share in the comments below. Happy configuring!