SAP IF_CREATE_XML_PRINT_ONCE Function Module for Mass printing in single form output

Search SAP Function Modules

IF_CREATE_XML_PRINT_ONCE is a standard if create xml print once SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Mass printing in single form output processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for if create xml print once FM, simply by entering the name IF_CREATE_XML_PRINT_ONCE into the relevant SAP transaction such as SE37 or SE38.

Function Group: CAF_EU_GP_IF
Program Name: SAPLCAF_EU_GP_IF
Main Program: SAPLCAF_EU_GP_IF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function IF_CREATE_XML_PRINT_ONCE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'IF_CREATE_XML_PRINT_ONCE'"Mass printing in single form output
  EXPORTING
   IV_SINGLE_FORMS_DATA =  "Holds the data for single form

 IMPORTING
   EV_OUTPUT_XML =  "
   EV_PHYSICAL_TEMPLATE_ID =  "GUID in 'CHAR' Format in Uppercase

EXCEPTIONS
   ENGINE_EXCEPTION = 1    INVOCATION_EXCEPTION = 2 

.

IMPORTING Parameters details for IF_CREATE_XML_PRINT_ONCE

IV_SINGLE_FORMS_DATA - Holds the data for single form

Data type: EUP_IF_FORM_DATA
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for IF_CREATE_XML_PRINT_ONCE

EV_OUTPUT_XML -

Data type: XSTRING
Optional: No
Call by Reference: No ( called with pass by value option)

EV_PHYSICAL_TEMPLATE_ID - GUID in 'CHAR' Format in Uppercase

Data type: GUID_32
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ENGINE_EXCEPTION -

Data type:
Optional: No
Call by Reference: Yes

INVOCATION_EXCEPTION -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IF_CREATE_XML_PRINT_ONCE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM IF_CREATE_XML_PRINT_ONCE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects