The functional scope is mapped, the code is assessed, and the data migration is planned. Then someone asks what happens to the four hundred output forms. The room goes quiet. Invoices, delivery notes, purchase orders, payslips and customs documents all depend on SmartForms and SAPscript layouts that nobody has looked at in years. A forms workstream belongs in every SAP S/4hana Implementation plan from the first week, with an owner, a start date and clear dependencies.
Why do output forms get missed in S/4HANA project plans?
Output forms get missed because they sit between teams. Functional consultants treat them as technical objects, developers treat them as business documents, and business users only notice them when an invoice prints wrong. Nobody owns them, so nobody plans for them.
The result is predictable. Teams scope custom code, interfaces and data in detail, then discover the forms inventory in the middle of testing. By then the schedule has no room left.
The hidden size of the forms estate
Most mature SAP systems carry far more forms than anyone remembers. Years of acquisitions, regional rules and customer-specific layouts pile up. One company may run five versions of the same invoice for five countries.
Many of those forms are copies of standard programs with small edits. Some print in only one plant. Others have not been used since the last audit. You cannot plan what you have not counted.
Why the old forms will not simply carry over
SAPscript and SmartForms belong to an older output model. Adobe Forms is a layout technology, built on Adobe LiveCycle Designer, that SAP uses for forms in S/4HANA, and it pairs with the newer output management framework. Older forms can run in some cases, but relying on that creates risk. Layouts break, driver programs need changes, and print behaviour shifts.
SAP set the clock itself. SAP News reported in February 2020 that Business Suite 7 mainstream maintenance would end in 2027, with optional extended maintenance to the end of 2030. That date drives every ECC owner, and forms work needs to finish well before it.
What a missed forms plan costs
Consider a distributor that finds its forms late. Testing is already underway, and the team learns that delivery notes, pick lists and customs documents all need rebuilding. Developers get pulled off remediation to fix layouts. Testers wait. The go-live date slides by weeks.
None of this is a technical surprise. It is a planning gap. A forms owner assigned in week one would have caught it.
What does a forms workstream actually include?
A forms workstream is a defined block of project work that inventories, rationalizes, rebuilds, tests and releases every output document in scope. It has its own owner, budget and milestones. It runs next to code remediation and data migration, not after them.
A good workstream breaks into five clear steps.
- Inventory every form, driver program and output type in the source system.
- Rank each form by business use, volume and legal weight.
- Retire duplicates and unused layouts.
- Rebuild the remaining forms in the target technology.
- Test each form with real data and release it with sign-off.
Who should own the work
Pick one person with authority over both the technical and business sides. A senior ABAP lead often fits, as long as a finance or logistics process owner backs them. Without business sign-off, forms sit in review for weeks.
Give that owner a named backup and a weekly checkpoint. Forms slip quietly, and a weekly view catches the slip early.
What the owner needs from other teams
The forms owner depends on others in specific ways. Code remediation tells them which driver programs change. Data teams confirm which fields still exist. Basis teams set up the print and output infrastructure.
If those dependencies live only in someone's head, the plan fails. Write them down and attach dates.
Where does forms work sit beside code remediation, data and testing?
Forms work starts right after the initial code and scope assessment. It overlaps with remediation, data preparation and early testing. It cannot start before the inventory exists, and it must finish before user acceptance testing. This placement gives developers time to rebuild and business users time to approve layouts. Teams can check the SAP S/4HANA Cloud documentation to confirm which output and forms capabilities apply to their release.
Think of the project as four lanes running side by side: code, data, forms and testing. Each lane has its own owner. The forms lane hands finished layouts to testing, and it takes field changes from the data lane.
A sample timeline for the forms lane
Every project differs, but the order of events stays stable. Here is a typical sequence for a mid-sized rollout.
- Weeks 1 to 2: run the inventory and tag every form with an owner.
- Rank forms and agree which ones retire during weeks 3 to 4.
- Weeks 5 to 12: rebuild in waves, starting with legal and customer-facing documents.
- Test with production-like data and fix print issues in weeks 13 to 16.
- Weeks 17 to 18: collect business sign-off and freeze layouts.
Adjust the lengths to your volume. A company with eighty forms needs less time than one with eight hundred. The order, however, should not change.
The link to your migration path
Your chosen route changes the forms effort. A greenfield rollout lets you rebuild from a clean sheet and drop most legacy layouts. A conversion keeps more of the old system, so more forms arrive on the doorstep. Teams planning an SAP ECC to S4HANA Migration should decide the route first, because the forms count follows from it.
How do you decide which forms to keep, rebuild or retire?
Keep, rebuild or retire decisions come from usage data and business value. Pull print volumes from output logs, then rank forms by use, legal weight and customer visibility. Anything unused for a full business cycle is a retirement candidate. The rest get rebuilt in priority order.
This step saves more time than any other. Retiring a hundred dead forms removes a hundred rebuild tasks and a hundred test cases.
Questions to ask for every form
Run each layout through a short set of checks. The answers sort forms into the right bucket fast.
- Did anyone print it in the last twelve months?
- Does a law or contract require it?
- Do customers or suppliers see it?
- Does another form already cover the same need?
- Does it feed an outside system, such as a bank or a carrier?
A form with no yes answers goes to the retirement list. A form with several goes to the front of the rebuild queue.
Handling country and plant variants
Variants cause the most waste. Five country versions of an invoice often differ by a tax line and a logo. Build one template with conditional blocks instead of five separate layouts.
That choice cuts rebuild time and shrinks testing later. It also makes the next change cheaper, since you edit one template, not five.
How should you test and approve output forms before go-live?
Test forms with real data, real printers and real approvers. A form that looks right in preview can still fail on a label printer or a pre-printed stock. Give business users a fixed review window, and treat their sign-off as a gate, not a courtesy.
Forms testing needs a plan of its own. Do not fold it into general integration testing, where a misaligned address block will not get anyone's attention.
What a good forms test covers
A solid test pass checks layout, content, output channel and edge cases. Layout covers fonts, page breaks and logos. Content covers amounts, taxes, languages and currencies. The channel covers print, email, PDF and electronic exchange.
Edge cases catch the real trouble. Test a ten-page order, a zero-value line and a customer with a very long name. Test a credit memo against a returned delivery. These cases break layouts more often than the standard path does.
Getting business approval without delay
Users approve faster when you show them side-by-side samples. Print the old form and the new form on the same page. Highlight every change. Ask for sign-off within five working days.
Set one escalation path for late approvals. Otherwise a single missing signature can hold a whole wave of forms.
What do project leaders and consultants need to line up?
Project leaders need three things: a named forms owner, skilled form developers, and a clear place in the plan. Consultants with Adobe Forms and output management experience are scarce, so booking them early matters. Late hires pay a premium and arrive after the design choices are set.
For IT Directors and CIOs, the practical move is simple. Add forms to the readiness checklist, and ask your delivery partner to show the forms plan in the first steering committee.
Skills that matter on the forms team
A forms developer needs more than layout skill. Look for experience with output management, ABAP driver programs and print setup. A good developer also understands the business document, so they can question an odd field.
- Adobe Forms design and scripting
- ABAP driver program changes
- Output management configuration
- Print and spool setup
- Basic finance or logistics process knowledge
If you are a consultant, this combination is in demand. Few people hold all five, and teams notice when someone does.
Choosing delivery support
Many companies lack spare forms developers during a rollout. External support fills the gap, provided the partner owns the outcome and not just the hours. Ask how they handle inventory, what tools they use, and who signs off. Firms that offer SAP Implementation Services should show a forms method, not just a headcount.
Canadian buyers face an extra layer, because bilingual documents and provincial tax rules add variants. A provider with SAP S4HANA Implementation Canada experience will already know where those variants hide. That knowledge saves weeks in the inventory step.
Putting forms on the plan before they cause delays
Forms stay invisible until they fail, and by then the fix costs weeks. Put them on the plan early, give them an owner, and tie them to the lanes around them. The inventory, the keep-or-retire decision and a dedicated test pass do most of the work.
Teams that treat forms as a first-class workstream finish testing with fewer surprises. Those that treat them as an afterthought spend the last month printing invoices by hand. 2iResourcing helps Canadian teams place SAP developers and consultants with forms and output management experience into S/4HANA programs, so the workstream has skilled people before the first layout is rebuilt.
Frequently Asked Questions
Q. When should the forms workstream start in an S/4HANA project?
A. Start it right after the initial scope and code assessment, ideally in the first few weeks. The inventory comes first, and rebuilding follows once you know which forms survive. Starting later squeezes testing.
Q. Do SmartForms and SAPscript still work in S/4HANA?
A. Some older forms can still run, but relying on them carries risk. Layouts and driver programs often need changes, and print behaviour can shift. Most teams rebuild priority forms in Adobe Forms.
Q. How many forms should we expect to rebuild?
A. Far fewer than the full inventory. A usage review usually reveals many duplicates and unused layouts, which you retire. Country variants can also merge into single templates.
Q. Who should own forms in the project team?
A. One person with authority across technical and business sides, such as a senior ABAP lead backed by a process owner. They need a backup and a weekly checkpoint to keep the work visible.
Q. Can 2iResourcing supply SAP form developers for a rollout?
A. Yes. 2iResourcing places SAP developers and consultants across Canada, including people with Adobe Forms and output management skills. Share your timeline and form count, and the team can match profiles to your waves.
See a forms conversion live on December 2, or get the replay: Link