SE71 — SAPscript Form Painter

SE71 is the editor for SAPscript layout sets (forms). A form defines pages, the windows placed on those pages, and the paragraph and character formats applied inside them, and is used to render printed business documents - invoices, delivery notes, purchase orders, dunning letters. The structural fact that explains most confusion: a form is really two linked objects under one name. The layout structure (pages, windows, format definitions) is largely language-independent, while the actual text sitting inside a window is stored per language as a separate text object. Editing the German version of a window's content does nothing to the English version, and vice versa, even though both live under the same form name in SE71. Most 'I fixed it and it still prints wrong' tickets trace back to this split.

SE71 is reached for when a classic print output - a document driven by SAPscript rather than Smart Forms or Adobe Forms - shows a wrong label, missing field, misaligned box, or blank window on the printed layout. Output determination (via the NAST-driven condition record on the business document) points to a form name and a print program; SE71 is where the form side of that pair is inspected and changed. It is not reached for when the form is a Smart Form or Adobe Form - those use different editors entirely, and SE71 will simply not open them. It also is not the place to fix wrong data on the printout if the data was never passed by the print program; that fix belongs on the ABAP side, not in the layout.

Query STXH filtered on object type FORM, form name, and language, and compare the active-flag and change-timestamp fields against what SE71 displays for that same form and language - a saved-but-inactive version explains why nothing changed on print. Read STXL for the matching key to see the actual stored window content rather than trusting the editor screen alone. Separately, pull the NAST entries for the failing document by output type and date to confirm which form name and print program were resolved at runtime, since a mismatch there means the wrong form was never the one printed at all.

SAPscript and SE71 continue to work on S/4HANA for forms that have not been migrated; SAP's direction for new form development is Adobe Forms, maintained through different transactions, not SE71. There is no Fiori app equivalent to SE71 and no functional change to the transaction itself on S/4HANA. It remains a legacy-maintenance tool, used specifically when an existing SAPscript-based output has not yet been converted.

Functional consultants identify what is wrong on the printed output and which document, output type and language reproduce it. ABAP or development owns the SAPscript layout edit and the print program logic behind it. A clean handover states the form name, language, output type, the NAST record for the failing document, and a screenshot or printout showing exactly what field or layout is wrong.

SE78 is worth knowing alongside SE71 since logos and graphics embedded in a SAPscript form are stored and managed there rather than inside the form painter itself. SE09 or SE10 matter whenever a form change needs to move between systems, since the form is transported as its own object separate from the print program. SE16 is the practical companion for confirming the STXH and STXL state directly rather than trusting what SE71 displays. SE80 is the entry point for tracing which ABAP print program actually calls the form and what data it passes in.