POPUP_TO_CONFIRM — Generic confirmation popup function module

POPUP_TO_CONFIRM opens a modal dialog box with a question text and up to two response buttons, optionally accompanied by a separate cancel option triggered by Escape or the window close button. It is used throughout SAP standard code and custom developments to interrupt a program flow and ask for explicit confirmation before something destructive or irreversible happens, such as deleting a document, reversing a posting, or overwriting existing data. It is a synchronous, screen-blocking call: the calling program waits until the user responds. It is treated as a general-purpose utility function module available for use in customer programs, not a private SAP-internal helper, though it only works in a dialog (SAPGUI) context, not in background processing.

Only the parameters that are consistently present across releases are listed here.

There is effectively one exception to worry about, and one non-exception behaviour that causes most of the damage. TEXT_NOT_FOUND is raised when the function module cannot resolve the text elements it needs to build the popup; it is rare in practice and usually points to a text pool or transport inconsistency rather than a data problem. If it is swallowed with no handling, the popup is never shown, ANSWER is never populated by this call, and the program continues holding whatever value ANSWER had before the call - which in many programs is the initial blank value, and code that checks ANSWER against a specific button value rather than explicitly against all three outcomes will silently take the wrong branch. The bigger trap is that cancelling the dialog is not an exception at all: pressing Escape or closing the window returns ANSWER = 'A' with sy-subrc 0, so code that only tests for '1' versus not-'1' treats a user cancellation exactly like pressing the second button.

Populate TITLEBAR and TEXT_QUESTION with meaningful, translated text, set the button labels explicitly rather than relying on defaults if the action is not a plain yes/no decision, and decide up front whether a genuine cancel option is needed via DISPLAY_CANCEL_BUTTON. After the call, check sy-subrc for TEXT_NOT_FOUND first, then branch on ANSWER using an explicit CASE covering '1', '2', and 'A' rather than a single IF/ELSE. Treat any value other than the explicit confirm button as a non-confirm, including blank, so a failed call defaults to safe behaviour rather than proceeding with the dangerous action. Never call this inside background or batch processing; there is no user present to answer it.

POPUP_TO_CONFIRM behaves the same way in S/4HANA as in ECC; it is unaffected by the technical changes of the conversion because it is a pure SAPGUI dynpro utility. It has no released successor function module. In a Fiori or SAPUI5 context it has no equivalent, since screen-blocking modal popups from a synchronous ABAP call do not fit the asynchronous OData/RAP model; UI5 applications implement confirmation dialogs client-side in JavaScript instead. For clean-core custom code intended to run under S/4HANA extensibility guidelines, calling this function module at all is a smell, since it ties logic to classic dynpro presentation rather than to a service layer.

Most incidents involving this function module are logic bugs in the calling program rather than faults in the module itself.

This sits entirely with the ABAP developer who wrote the calling program. Functional consultants only ever see the symptom, typically a user reporting that clicking Cancel deleted the record anyway, or that a background job appears to hang with no error. The fix is always in the calling code's branching logic around ANSWER, not in the function module or in any configuration.

POPUP_TO_CONFIRM is frequently the gate that decides whether a program proceeds to commit a change or abandon it, so it commonly sits immediately before a call to commit or roll back the current update. No database tables are read or written by the function module itself; it only manipulates the presentation layer and returns a character value to the caller.