SE78 — SE78 SAPscript Forms Graphics Management

SE78 is the maintenance transaction for graphics used in form output: company logos on letterheads, signature bitmaps, background images referenced from a SAPscript window or a Smart Forms graphic node. A graphic is imported once from a local file (BMP or TIFF), stored under an object type (monochrome BMON, color BCOL, or printer-specific TIFF) and a name, then referenced by that name from the form definition rather than embedded directly. The structural fact that explains most confusion: the graphic is a standalone repository object stored per client, independent of the form that references it. The form only holds a pointer. This means a form can transport cleanly while the logo it prints stays behind, or a logo can be replaced centrally and every form referencing it changes at once without touching the form itself.

SE78 gets used whenever a form needs a static image: onboarding a new company logo for invoice or delivery note printouts, replacing a letterhead after a rebrand, adding a scanned signature to an output correspondence type, or troubleshooting why a printed document shows a blank rectangle where the logo should be. It sits upstream of SE71 and SE80's Smart Forms editor, both of which only reference graphic names created here. It is not the tool for Adobe Forms working with modern XFA/interactive layouts using embedded images in the form template itself, nor for Fiori-based output where images are typically handled through different attachment or branding mechanisms. Reach for SE78 specifically when the graphic lives in the SAPscript/Smart Forms bitmap repository and the symptom is missing, wrong, or garbled printed images.

Open SE16 on the SAPscript bitmap directory table and filter by object type and graphic name to confirm the object exists in the system being checked, then compare the same filter across dev, QA and production to see whether the entry is missing or has a different last-changed timestamp in one of them. If the logo prints wrong in only one system, the entry exists everywhere but the binary content or format differs; the directory row's format and size fields are the fastest signal that the wrong variant was imported.

SE78 itself is unchanged on S/4HANA and remains the transaction for SAPscript and Smart Forms graphics; there is no dedicated Fiori app replacing it. What has shifted is emphasis: new output-management scenarios on S/4HANA increasingly favor Adobe Forms and, further out, form templates with embedded or externally managed branding, reducing new dependence on SE78 without removing existing SAPscript and Smart Forms output that still relies on it.

This is ABAP development or forms-development territory, not a functional configuration task, because it touches the form layout repository directly. A clean handover from functional to development includes the exact printed document showing the defect, the output type and form name involved, the graphic name expected, and confirmation of which system tier the issue reproduces in.

Read SE71 next to see how a SAPscript form actually references a graphic by name and object type inside a window. SE16 is the fastest way to prove or disprove that a graphic entry exists and matches across landscape tiers. SE09 and SE01 matter once the diagnosis lands on a transport gap, since moving a graphic between systems is a transport organizer action, not a form-editor one.