'/%3E%3C/svg%3E){kind=small}
THREE COMMON STARTING POINTS
When Is the Right Time to Move to Adobe Forms?
Form migration does not necessarily have to coincide with an SAP® system migration. In practice, there are three common scenarios, each with different objectives and project planning requirements.
01
Modernising an Established Forms Landscape
An SAP® system has been in use for many years. SAPscript or Smart Forms solutions that have evolved over time have become increasingly difficult to change. New company codes, sales organisations, countries and languages add further complexity.
Our Approach: Analyse existing processes and variants, eliminate unnecessary special-case logic and establish a systematic, maintainable Adobe Forms architecture — even without a simultaneous S/4HANA migration.
02
Introducing Adobe Forms During the S/4HANA Migration
The migration to SAP® S/4HANA is used as an opportunity to modernise existing forms technologies and output processes at the same time. This allows new requirements for data retrieval, interfaces and output management to be addressed together.
Our Approach: Coordinate form migration closely with the S/4HANA project, clarify technical dependencies early and integrate the necessary tests into the overall project plan.
03
Migrating Forms Before the S/4HANA Project
The move to S/4HANA is planned but has not yet started. Existing SAPscript or Smart Forms are deliberately migrated to Adobe Forms in the current system ahead of time.
Our Approach: Bring forward a substantial and often time-consuming work package to reduce the workload during the later S/4HANA project. We ensure that the solution is suitable for the planned target architecture while allowing for necessary adjustments and testing after the system migration.
The most suitable approach depends on the existing forms landscape, the target S/4HANA system, the output management concept and the project schedule.
WHY MODERNISE?
When Legacy Forms Become a Risk
01
Complex Legacy Logic
Conditions accumulated over many years make changes difficult and can cause unexpected side effects.
02
New Requirements
Additional company codes, languages, layout variants and output channels increase the need for changes.
03
Technology Modernisation
PDF-based forms and modern output processes require a carefully planned target architecture.
MIGRATION, NOT A 1:1 COPY
The Real Challenge Lies in the Form Logic
Migration involves more than recreating the appearance of a SAPscript or Smart Forms layout. Much of the real work lies in print programs, text determination, pricing, output control, country-specific requirements and custom enhancements.
That is why we do not recommend an unexamined 1:1 conversion. We analyse the actual business processes and determine which logic should be retained, simplified or standardised. Learn more about this approach in How We Work.
Our Goal: Rather than transferring old complexity to new technology, we create a stable, transparent forms architecture.
Typical Areas to Review
- Output triggers and output control
- Printing, email, archiving and PDF requirements
- Company codes, sales organisations and languages
- Texts, logos, conditions and pricing
- Form variants and special cases
- ABAP data retrieval and interfaces
TECHNICAL OVERVIEW
SAPscript, Smart Forms and Adobe Forms
SAPscript
An older SAP® forms technology. Migration generally requires a new form implementation and analysis of the existing logic.
Smart Forms
Existing form logic and print programs must be reviewed. Technical conversion tools cannot replace a functional and technical redesign.
Adobe Forms
PDF-based forms with separate interfaces, context and layout. Data retrieval, output control and Adobe Document Services (ADS) prerequisites are part of the overall solution.
Note: Implementation depends on the SAP® release, deployment model and available forms/output technology. Traditional ABAP and Adobe Forms approaches cannot be transferred unchanged to every Public Cloud environment.
OUR PROJECT APPROACH
Four Phases to a Modern Forms Landscape
1
Analysis & Inventory
Inventory of forms, print programs, output types and variants. Interviews with key users and creation of a test-case matrix.
2
Strategy & Architecture
Define the target forms, data models, reusable components and future output processes.
3
Development & Migration
Adobe Forms layouts, interfaces and ABAP data retrieval ; implement the solution using existing solidforms templates and solidFormKit where appropriate.
4
Testing & Go-Live
Functional regression testing across countries, languages, document types and output channels. Production rollout followed by stabilisation.
WHAT MATTERS
Identifying Common Pitfalls Early
Hidden Logic in Legacy Forms and Print Programs
Nested conditions, custom routines, special texts and years of enhancements are often poorly documented. We therefore examine source code alongside real output examples.
Multiple Variants, Company Codes and Languages
Combining every variant into a single form without analysis can make maintenance more difficult. We seek the right balance between reuse and manageable complexity.
Differences in Pricing and Text Determination
Especially for SD forms, print indicators, conditions, subtotals and text determination must be coordinated with the business departments.
Output Channels and Technical Prerequisites
PDF output, email, printers, archiving and Adobe Document Services must work within the relevant system and output framework. We also explicitly assess PDF/A requirements.
Testing Effort and a Reliable Go-Live
We define representative test cases for different documents, countries, languages and special scenarios so that changes can be tested reliably.
FROM OUR PROJECT EXPERIENCE
Case Study: Migrating Sales Forms to Adobe Forms
At a company in the wood industry, SAPscript sales forms had become unstable after years of enhancements. A further rollout to a French company code prompted a fundamental modernisation of the forms landscape.
Initial Situation
- Numerous special cases accumulated over time
- High risk of errors when making changes
- New Requirements durch internationale Rollouts
Implementation
- Logic analysis and documented test cases
- Revision of pricing print indicators
- Adobe-Forms-Templates und solidFormKit
- Customer-specific adjustments and testing
Outcome: More standardised, reliable sales forms and a stronger foundation for future rollouts.
VALUE FOR YOUR PROJECT
Why Migrate with solidforms?
Forms and ABAP Expertise
We consider form layouts, data retrieval and printing processes as a whole.
Proven Templates
Existing form templates can simplify development when they match the requirements.
solidFormKit
Suitable texts, labels and settings can be maintained centrally and systematically.
SAP® FORM MIGRATION
Planning to Move to Adobe Forms?
We analyse your existing forms landscape, assess effort and risks, and develop a practical migration strategy with you. In our consulting workshops , we work together to define the next steps.