FORMfactor
A report that generates local classes with static methods from an old FORM-based ABAP program, as code to paste in by hand, without support for 740 constructs, TABLES parameters or INCLUDEs.
FORMfactor reads an old program built from FORM routines and produces local classes with static methods from it. It runs as report ZFORMFACTOR and changes nothing in the system by itself: the generated code has to be copy-pasted into the report by hand. Its own limitations list three gaps: the new 740 language constructs, TABLES parameters and INCLUDEs. Installation runs in order — abapGitabapGitA Git client written in ABAP that runs inside the system, so objects are cloned, pulled and pushed without leaving it; with no package manager in ABAP, a cloned repository is how code is distributed.community org, abap, then abapOpenChecksabapOpenChecksAn open-source rule pack for SAP Code Inspector and ABAP Test Cockpit, installed via abapGit and activated as a check variant.independent, abap through abapGit, then FORMfactor — and the maintainer also points to FORMfactor-Eclipse.
Facts
Where it sits
Who is behind it
In the atlas: maintains 13, contributes to 92, wrote 1@larshpmaintainerDomi BiglContributes to this
In the atlas: contributes to 7@bigld1 contributor
Before choosing this
Signals
ActivityQuietNo published releases; repository quiet for 67 months
It publishes no releases, and its repository has been quiet for at least 24 full months. This may be normal for stable software; check whether its current state still fits your use.
What it declares
Every artifact
- Type
- Generator
- Origin
- Independently maintained
As a generator
- Generates
- Code or test data
- Run with
- does not say
- Distributed through
- abapGit
Connections
Naming, structure and language-subset conventions for readable code
Git client written in ABAP that runs inside the system
Open-source rule pack for SAP Code Inspector and ATC
Download
README
quoted from larshp/FORMfactor under MIT, readFORMfactor
Helps refactoring old FORM based programs to local classes with static methods.
Also see https://github.com/larshp/FORMfactor-Eclipse
Limitations
- Does not work with new 740 language constructs
- TABLES parameters not implemented yet
- INCLUDEs not supported
Installation
- Install abapGit
- Install abapOpenChecks using abapGit
- Install FORMfactor
- Run via report ZFORMFACTOR, it will not automatically change anything in the system, code has to be copy-pasted into report manually.

Others providing
Compare all 4 on the Clean code conventions page →- code pal for ABAP — Cloud Editioncode pal for ABAP — Cloud EditionThe same Clean ABAP check set for ABAP Cloud, where the legacy edition cannot run.sap official, abapClean ABAP check set for ABAP Cloud
- code pal for ABAPcode pal for ABAPATC and Code Inspector checks for the parts of Clean ABAP a static analyser can actually check, installed into a system with [abapGit](artifact:abapgit-abapgit) rather than delivered with it.sap official, abapATC and Code Inspector checks for Clean ABAP
- Clean ABAPClean ABAPSAP's open, versioned style guide for ABAP: the answer to how a piece of ABAP should be written, an agreement a team adopts rather than anything to install.sap official, abapOpen, versioned style guide for ABAP
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
abaplint
Contributors
History in the atlas
- First seen.
For your agent
- Ref
artifact:larshp-formfactor- JSON
- /artifacts/larshp-formfactor.json
- MCP
- Connecting an agent