Legacy forms still run, which is why they get left off the plan. An invoice prints, a delivery note reaches the dock, and nobody files a ticket. Then the project reaches cutover week, and a SAPscript layout nobody has opened since 2009 starts failing. This S/4HANA conversion checklist gives your delivery team a practical way to find those forms early, sort them, and fix them before they threaten the go-live date. A strong SAP S/4hana Implementation plan treats output as a deliverable from day one, and this guide shows how.
What Should a Forms Conversion Checklist Cover?
A forms conversion checklist covers six jobs: inventory every form, classify each by business value, pick a target technology, rebuild or convert, test output end to end, and plan cutover. Teams that skip the first job usually pay for it in the last week.
SAPscript is the oldest SAP form technology, built around text-based layout sets and print programs. Smartforms replaced it with a graphical designer. Adobe Forms, built on Adobe LiveCycle Designer, is the current direction for new output in S/4HANA.
Each technology has its own conversion path. Your checklist should treat them separately, because a SAPscript layout and a Smartform fail in different ways. SAPscript usually breaks on print program logic and font handling. Smartforms tend to break on function module names, which change when you transport or regenerate them.
The sections below walk through the checklist in order. You can lift them straight into a project plan, and each one maps to a clear owner, a clear deliverable, and a clear exit test, so progress stays visible to the steering committee.
Step 1: Build a Complete Form Inventory
An inventory lists every form object in your ECC system, along with its print program, output type, and last execution date. Without it, you cannot size the effort or assign owners. Start here, before any design work.
Where to Look for Forms
Forms hide in more places than most teams expect. Check these sources:
- Table TADIR for all SAPscript and Smartform objects in custom namespaces
- Output determination tables for each application area (sales, purchasing, finance, logistics)
- Print program names in NAST and output type configuration
- Custom forms copied from SAP standard and modified years ago
- Forms called by third-party add-ons or interfaces
Do not trust the transport history alone. Some forms never moved through a transport because a developer created them directly in production.
Capture Usage Data
A form that exists is not a form that runs. Pull output history from NAST and spool logs for the last 12 to 24 months. Then flag anything with zero executions.
Dead forms are free wins. Retire them instead of converting them, and your effort drops before the project even starts. In nearly every engagement, the forms inventory reveals two to three times more objects than the team expected, dead forms included.
Record the last execution date next to each object, and note which business unit last used it. A form untouched for two years but owned by a year-end finance process may still be live, so confirm with the owner before you retire anything.
Document Dependencies
Every form depends on something else. A print program may call custom function modules, read Z tables, or pull logos from the document repository. Write these dependencies down now.
When a dependency sits in custom code, it also appears in your custom code analysis for the wider project. Link the two lists so developers do not fix the same object twice.
Step 2: Classify and Prioritize Each Form
Classification means ranking forms by business risk and rebuild effort so the team converts the most important ones first. A simple three-tier model works well and keeps debates short.
Tier one covers forms that touch customers, regulators, or cash: invoices, purchase orders, delivery documents, payment advices, and tax documents. Internal forms with moderate usage, such as goods receipt slips, fall into the second group. Rarely used or duplicate forms make up the third.
For each form, record these fields:
- Business owner who can approve the new layout
- Monthly output volume
- Output channel (print, email, PDF, EDI, fax)
- Languages and country variants
- Special logic such as barcodes, logos, or conditional blocks
The country variant column matters more than it looks. A Canadian bilingual invoice often carries English and French text, GST and HST or QST lines, and province-specific legal wording. Each variant needs its own test case later.
Keep the scoring light. A form with high volume, external recipients, and several variants lands in tier one almost automatically, and a workshop of one hour with the business owners is usually enough to settle the borderline cases.
Step 3: Choose the Target Form Technology
Choosing a target means deciding, form by form, whether to keep the existing technology, convert it, or rebuild in Adobe Forms. Smartforms and SAPscript still run in on-premise S/4HANA, but Adobe Forms is where SAP directs new development.
Use these rules of thumb:
- Keep stable tier-three Smartforms as they are if they pass testing
- Convert SAPscript to Smartforms only when the layout is simple and the budget is tight
- Rebuild tier-one customer documents in Adobe Forms when you want modern layouts, email delivery, or better maintenance
- Retire anything with no usage
How Forms Fit Into Output Management
Output management is the set of functions that decide which document prints, where it goes, and in what format. In ECC, NAST-based output determination drives most of this. S/4HANA keeps NAST for many on-premise scenarios, but SAP pushes newer applications toward its Output Management framework.
S/4HANA Cloud and RISE customers need extra care here. NAST-based output determination is not available in all S/4HANA Cloud scenarios. Evaluate the SAP Output Management framework and the Fiori-based Output Management app early, because they change how you configure output types, receivers, and form templates. A form that converts cleanly can still sit unused if its output determination has no home in the cloud model.
Step 4: Convert or Rebuild the Forms
Conversion work follows the target you chose. Smartforms need regeneration and a check of their function module calls. SAPscript needs print program review. Adobe Forms need a new interface, a new context, and a new layout. For release-specific guidance on obsolete statements and changed objects, consult the SAP S/4HANA 2025 conversion guide before you finalize the work plan.
Work through this sequence for each form:
- Copy the form into the development client
- Run the SAP-delivered checks for custom code against the target release
- Fix print program errors and obsolete statements
- Rebuild or adjust the layout and confirm fonts and logos
- Test with real data from the ECC system
- Record the result and move to the next form
Do not rebuild everything at once. Start with two tier-one forms and use them to set patterns for the team. The first rebuild usually takes three times as long as the tenth, because the team is still learning the templates.
Capture those patterns in a short style guide covering fonts, margins, logo placement, and naming rules. Later rebuilds then follow a template instead of starting from a blank page, and reviewers have a clear standard to check against.
Plan Around Data Model Changes
S/4HANA changes some data models. Business partner replaces separate customer and vendor masters, and material number length can grow. Any form that reads those fields directly may print blanks or truncate values. Check each print program for fields that moved or disappeared.
Step 5: Test Output End to End
Output testing proves that a document looks right, prints to the right device, and reaches the right recipient. It is the step teams shorten first, and it is the one that hurts most when skipped.
A solid SAP Regression Testing plan includes forms as their own test group. Build cases for each form, each language, and each output channel. Then add cases for edge conditions, such as a credit memo with ten line items that spills onto a second page.
Include these checks in every test cycle:
- Page breaks and totals on multi-page documents
- Special characters, including French accents and currency symbols
- Barcode scanning with a real scanner
- Email and PDF delivery to a test mailbox
- Printer routing for each plant and warehouse
Business users should sign off on tier-one forms. Give them a printed copy and the old ECC version side by side. They spot a missing legal line faster than any developer will.
Log every defect against the form and the variant it affects. Patterns show up quickly in that log, such as one font causing repeated truncation across several documents, and fixing the root cause once saves many separate repairs.
Step 6: Plan Cutover for Output
Cutover for forms means making sure every output type, printer, and template works the moment users log in. Add it to the cutover runbook as its own workstream with a named owner.
Most forms issues at go-live trace back to three causes. Printer definitions did not transfer. Output determination records were missed. Adobe Forms services were not configured in the production system. Check all three in a dress rehearsal, not on the weekend of go-live.
For the same reason, keep a short list of fallback options. If a tier-one invoice fails, can finance issue it from a backup template? Decide that before cutover, not during it.
Assign a support contact for each plant during the first week after go-live. Users who cannot print a delivery note will call someone within minutes, and a named contact with the right access can fix a printer mapping before the dock queue builds up.
How Forms Work Fits Your Wider Migration
Forms are one workstream inside a larger programme. Your SAP ECC to S4HANA Migration plan already carries custom code, interfaces, data, and authorizations, and forms touch all four. That overlap is why forms need a named owner who talks to each team.
Your delivery plan should list output as its own deliverable with entry and exit criteria. For Canadian organizations, an SAP S4HANA Implementation Canada project also adds bilingual and tax variants that multiply test cases quickly.
If your team lacks Adobe Forms or ABAP skills, bring in help early. When you look for an SAP implementation partner in Canada, ask for named consultants who have rebuilt invoices and delivery documents in bilingual environments. A partner with SAP Gold Partner Canada status signals tested delivery, but ask for form-specific examples anyway. For background on the target platform, review the SAP S/4HANA product overview.
Frequently Asked Questions
Q. Do SAPscript forms still work in S/4HANA?
A. Yes, SAPscript still runs in on-premise S/4HANA, but SAP no longer develops it. Most teams convert or rebuild tier-one forms to avoid future risk. 2iSolutions helps clients decide which forms justify that effort.
Q. Should we convert Smartforms to Adobe Forms?
A. Not always. Stable Smartforms with low change needs can stay as they are if they pass testing. Rebuild customer-facing documents in Adobe Forms when you need new layouts or better email delivery.
Q. How long does forms conversion take?
A. It depends on the number of live forms and their complexity. A clean inventory is the best way to size the work, because it separates live forms from dead ones.
Q. What about S/4HANA Cloud and RISE?
A. Review the SAP Output Management framework and the Fiori-based Output Management app. NAST-based output determination is not available in all S/4HANA Cloud scenarios, so confirm your scenario before you plan any conversion.
Q. Who should own forms during the project?
A. Name one owner who works with the functional, development, and testing teams. Business owners still approve layouts for their own documents.
Turning the Checklist Into a Delivery Plan
The sequence is simple: inventory every form, classify by risk, choose a target technology, build, test, and cut over. Each step feeds the next, and a gap early in the chain shows up as a failure late in the project.
Starting early is the biggest advantage you have. A forms inventory takes days, while a missed form in cutover week can stop invoicing for an entire business unit. Teams that finish the inventory in the first phase also gain time to retire dead forms and spread rebuild work across sprints.
2iSolutions can run an SAP S/4HANA assessment that includes a full forms inventory, a tiered rebuild plan, and an effort estimate you can take straight to your steering committee.
Register for the December 2 session: Link