SAP ARCHIV_GET_PRINTFORMAT Function Module for









ARCHIV_GET_PRINTFORMAT is a standard archiv get printformat SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 archiv get printformat FM, simply by entering the name ARCHIV_GET_PRINTFORMAT into the relevant SAP transaction such as SE37 or SE38.

Function Group: OPTJ
Program Name: SAPLOPTJ
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ARCHIV_GET_PRINTFORMAT 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 'ARCHIV_GET_PRINTFORMAT'"
EXPORTING
APPLICATION = "Name of calling application

IMPORTING
PRINTFORMAT = "Current print format (e.g. OTF, PDF)
.



IMPORTING Parameters details for ARCHIV_GET_PRINTFORMAT

APPLICATION - Name of calling application

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

EXPORTING Parameters details for ARCHIV_GET_PRINTFORMAT

PRINTFORMAT - Current print format (e.g. OTF, PDF)

Data type: TOADD-DOC_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ARCHIV_GET_PRINTFORMAT 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.

DATA:
lv_application  TYPE C, "   
lv_printformat  TYPE TOADD-DOC_TYPE. "   

  CALL FUNCTION 'ARCHIV_GET_PRINTFORMAT'  "
    EXPORTING
         APPLICATION = lv_application
    IMPORTING
         PRINTFORMAT = lv_printformat
. " ARCHIV_GET_PRINTFORMAT




ABAP code using 7.40 inline data declarations to call FM ARCHIV_GET_PRINTFORMAT

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.

 
"SELECT single DOC_TYPE FROM TOADD INTO @DATA(ld_printformat).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!