Do Smart Forms and SAPscript Still Work in S/4HANA?

No, not in one move. Legacy SAPscript and Smart Forms still run on S/4HANA on-premise, but the public cloud edition does not allow them, and SAP steers new form work to Adobe Forms. So the real decision is per form and per output channel, and every form you keep or move needs a documented test. This guide covers what SAP says now, where the dates disagree, and how to scope the work for a conversion or a new implementation.

What SAP says about legacy forms today

The short answer comes from SAP Learning. SAP's course on output management says the legacy technologies still exist and remain supported in S/4HANA, while SAP recommends Adobe Forms through S/4HANA Output Management for new implementations and strategic enhancements. Read that as "keep working forms unless you have a reason to touch them," not as "leave them forever."

The cloud editions are stricter. A SAP Community post on the new output management states that SAPScript, Smart Forms and classic Adobe Forms are not permitted in S/4HANA Public Cloud, because they contain ABAP artifacts that need backend access. Customers cannot view, maintain or transport them there. If your target is Public Cloud, the forms inventory is a hard gate, not a nice-to-have.

For on-premise and Private Edition, the picture is more mixed. A 2024 SAP blog on printing says the existing output frameworks remain usable in those editions, and that there were no plans at the time to deprecate NAST, SAPScript or Smart Forms. That post is dated, so confirm it against the current S/4HANA 2025 release information before you cite it in a steering committee.

Where the dates disagree

The sharpest date issue is not the forms themselves. It is the Java platform under Adobe Document Services (ADS). SAP's maintenance strategy blog for Adobe forms on-premise says the NetWeaver Application Server Java 7.5 that hosts ADS leaves mainstream maintenance at the end of 2027 and extended maintenance at the end of 2030. The same post names SAP HANA Extended Application Services, Advanced Model (XSA) as the successor platform.

The timing of that successor is where sources differ. The SAP blog says SAP planned to deliver the XSA option during the support time frame of S/4HANA 2025. A later SAP topic page and an SAP document both say Q1 2027. Plan around the later date, and check the current SAP maintenance information before you commit budget.

You will also find pages stating that Smart Forms support ends in 2027 or 2030. One lexicon page ties that to the Business Suite end of support and says it is expected "as things stand." I could not find an SAP Note or SAP statement that puts an end-of-support date on Smart Forms itself. Treat those pages as a warning to confirm, not as a deadline.

What changed from ECC

In ECC, most output ran through NAST-based output control, and forms were SAPScript, Smart Forms or Adobe Forms, depending on the application. S/4HANA adds a new output management layer. SAP's output management documentation points to SAP Note 2228611 as the feature overview, and the output parameters are determined through BRF+ rather than only condition records. That means output configuration and testing now touch Business Rule Framework logic as well as the form itself.

Not every application has moved to the new model. A practitioner answer on SAP Community makes the point clearly: Note 2228611 only applies to applications that have adopted S/4HANA output management, and SAP Note 3097507 lists the supported applications. Check that list for each module before you assume the new framework is in play. For SD billing, the simplification list says NAST-based output is no longer available for new billing documents, while migrated billing documents with NAST output can still be processed. That split is a common cause of surprise at cutover.

Step-by-step: scope the forms before you decide

1. InventoryList every SAPScript form (SE71), Smart Form (SMARTFORMS) and Adobe Form (SFP) in the ECC system, with the calling program or function module.
2. Classify by channelSplit each form into print, email, PDF archive, interactive or billing output. Channel drives the test.
3. Check application adoptionFor each module, confirm against SAP Note 3097507 whether it uses the S/4HANA output management framework or still runs NAST.
4. Decide per formKeep as is, rebuild in Adobe Forms, or retire. Record the reason for each choice.
5. Prove ADS worksConfirm the ADS connection and run a test form through it before any form test starts.

Step 1 is where most projects underestimate the work. Forms are called from custom reports, letters and interfaces, not only from standard output. Use the same change-impact discipline you use for custom code. Our guide on running remote ATC checks for S/4HANA custom code covers how to find the custom objects that call them, and the SPDD, SPAU and SPAU_ENH guide explains how to handle modified standard forms during a conversion.

On the rebuild effort, one consultancy's write-up notes that SAP does not provide an automated tool to convert Smart Forms to Adobe Forms. The layouts, data bindings and conditional logic get rebuilt in Adobe LiveCycle Designer. Budget for that as development work, and do not assume a mass export gets you there.

Decision tree: keep, rebuild or retire

1. Is the form used by an application that has adopted S/4HANA output management (per Note 3097507)?Yes → move to the BRF+ and Adobe Forms setup for that application · No → go to the next question
2. Is the target system S/4HANA Public Cloud?Yes → SAPScript and Smart Forms are not permitted; the form must be rebuilt or retired before cutover · No → go to the next question
3. Is the form business-critical and printed or emailed to customers, banks or regulators?Yes → rebuild in Adobe Forms and run a full before-and-after output comparison · No → keep as is, add it to regression, and set a review date
4. Is the form unused in the last 12 months?Yes → retire, after the business owner confirms in writing · No → keep and document the owner

What to test

Test the output, not only the form. A form can render without error and still print the wrong tax line, the wrong bank detail or the wrong language. For each form in scope, build a pack of before-and-after outputs using the same test data and the same driver program.

• Field-level comparison of ECC and S/4HANA output for at least one sample of each document type, including edge cases such as multi-page lines, credit memos and reversed documents.
• Channel test for each route: print queue, email with attachment, PDF archive and any interface that receives the document.
• Output determination test: the right form, the right channel and the right language for each customer or vendor, driven by the BRF+ or NAST settings you configured.
• ADS and connectivity test: a successful run of a test form in each system, not just a green ping.
• Authorization test: users can trigger and view the output they need, and no one else can.
• Regression for changed forms: a repeatable pack you can rerun on every support package or release.

Keep the evidence in the same place as the rest of your test pack. The SAP Output & Forms Test Matrix gives you a starting layout. For regression coverage of the forms that stay, the ECC to S/4HANA migration guide shows where output testing fits into the wider plan, and the N+1 landscape testing guide shows how to schedule these checks across the test systems.

Who signs off

The forms decision needs four signatures. The functional lead for each module confirms the output determination and channel. The business owner of each document signs the output comparison. The basis or ADS owner confirms the platform and connectivity. The test manager confirms that the evidence is complete and that the regression pack covers the forms that stayed. If the forms are customer-facing, add the customer service lead as well, because they are the first people to receive a wrong letter.

If you are still deciding between a system conversion and a new implementation, the brownfield vs greenfield decision tree helps. A greenfield move usually means rebuilding most forms anyway, which changes the cost of this whole exercise. For a deeper course on custom objects, the free Custom Code Migration course covers scoping, and the regression testing course covers how to keep the forms pack alive after go-live.

Frequently asked questions

Do I have to convert Smart Forms to Adobe Forms before an S/4HANA on-premise conversion?

Not as a blanket rule. SAP's learning content says the legacy technologies still exist and are supported in S/4HANA, while Adobe Forms is recommended for new implementations and strategic enhancements. Decide per form, based on channel, application adoption and business criticality.

Are Smart Forms allowed in S/4HANA Public Cloud?

No. SAP's output management material says SAPScript, Smart Forms and classic Adobe Forms are not permitted in the public cloud edition. Any form you need there has to be rebuilt in the supported model or retired before cutover.

What is the SAP Note for output management in S/4HANA?

SAP Note 2228611 is the main feature overview for Output Management in S/4HANA. Note 3097507 lists the applications that support the S/4HANA output control, so check it for each module. Confirm both against the current note version before you rely on them.

Does the ADS platform change affect my S/4HANA on-premise forms?

It can. The Java platform under ADS reaches end of mainstream maintenance at the end of 2027 and end of extended maintenance at the end of 2030. SAP names XSA as the successor, with sources giving different delivery timing, so confirm the current date with SAP before you plan the infrastructure change.

Sources

1. SAP S/4 HANA Output Management and New Form Technologies, SAP Learning, undated course page
2. Advantages of new output management capabilities in SAP S/4HANA, SAP Community blog, 2023
3. Maintenance Strategy Adobe Forms On-Premise, SAP Community blog, 2026
4. SAP Interactive Forms and SAP Forms Service by Adobe, SAP Community topic page, undated
5. SAP Forms by Adobe for SAP HANA extended application services, SAP document, 2025
6. SAP Note 2228611 and 3097507 references in output management blog, SAP Community, 2023
7. Printing with SAP S/4HANA output management, SAP Community blog, 2023
8. Is SAPScript fully supported with S/4HANA Output Management?, SAP Community Q&A, accepted answer
9. Impact on existing smartforms after migration to S/4 on HANA, SAP Community Q&A, accepted answer
10. SAP Smart Forms: background knowledge and features, WSW Software, undated
11. Adobe Forms vs SmartForms in SAP ABAP, ERPVITS, 2025
12. Who is actually converting your Smartforms, 2iresourcing, 2026
13. Adobe Document Services, DSAG ABAP Guideline (German), undated