SAP JIT_CALL_PRINT_PDF Function Module for NOTRANSL: Adobe output for jit_call_print form
JIT_CALL_PRINT_PDF is a standard jit call print pdf SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Adobe output for jit_call_print form 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 jit call print pdf FM, simply by entering the name JIT_CALL_PRINT_PDF into the relevant SAP transaction such as SE37 or SE38.
Function Group: JITOUT07
Program Name: SAPLJITOUT07
Main Program: SAPLJITOUT07
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JIT_CALL_PRINT_PDF 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 'JIT_CALL_PRINT_PDF'"NOTRANSL: Adobe output for jit_call_print form.
EXPORTING
SCREEN_IV = "Transmission Medium of Message
NAST_IS = "Message Status
TNAPR_IS = "
EXCEPTIONS
ERROR_MESSAGE_RECEIVED = 1
IMPORTING Parameters details for JIT_CALL_PRINT_PDF
SCREEN_IV - Transmission Medium of Message
Data type: NAST-NACHAOptional: No
Call by Reference: Yes
NAST_IS - Message Status
Data type: NASTOptional: No
Call by Reference: Yes
TNAPR_IS -
Data type: TNAPROptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_MESSAGE_RECEIVED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for JIT_CALL_PRINT_PDF 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_screen_iv | TYPE NAST-NACHA, " | |||
| lv_error_message_received | TYPE NAST, " | |||
| lv_nast_is | TYPE NAST, " | |||
| lv_tnapr_is | TYPE TNAPR. " |
|   CALL FUNCTION 'JIT_CALL_PRINT_PDF' "NOTRANSL: Adobe output for jit_call_print form |
| EXPORTING | ||
| SCREEN_IV | = lv_screen_iv | |
| NAST_IS | = lv_nast_is | |
| TNAPR_IS | = lv_tnapr_is | |
| EXCEPTIONS | ||
| ERROR_MESSAGE_RECEIVED = 1 | ||
| . " JIT_CALL_PRINT_PDF | ||
ABAP code using 7.40 inline data declarations to call FM JIT_CALL_PRINT_PDF
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 NACHA FROM NAST INTO @DATA(ld_screen_iv). | ||||
Search for further information about these or an SAP related objects