SAP TURKEY_BOE_PRINT_NEW Function Module for
TURKEY_BOE_PRINT_NEW is a standard turkey boe print new 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 turkey boe print new FM, simply by entering the name TURKEY_BOE_PRINT_NEW into the relevant SAP transaction such as SE37 or SE38.
Function Group: IDTR
Program Name: SAPLIDTR
Main Program: SAPLIDTR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TURKEY_BOE_PRINT_NEW 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 'TURKEY_BOE_PRINT_NEW'".
TABLES
T_BKPF = "Accounting Document Header
T_BSEG = "Accounting Document Segment
T_BSED = "Bill of Exchange Fields Document Segment
TABLES Parameters details for TURKEY_BOE_PRINT_NEW
T_BKPF - Accounting Document Header
Data type: BKPFOptional: No
Call by Reference: Yes
T_BSEG - Accounting Document Segment
Data type: BSEGOptional: No
Call by Reference: Yes
T_BSED - Bill of Exchange Fields Document Segment
Data type: BSEDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for TURKEY_BOE_PRINT_NEW 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: | ||||
| lt_t_bkpf | TYPE STANDARD TABLE OF BKPF, " | |||
| lt_t_bseg | TYPE STANDARD TABLE OF BSEG, " | |||
| lt_t_bsed | TYPE STANDARD TABLE OF BSED. " |
|   CALL FUNCTION 'TURKEY_BOE_PRINT_NEW' " |
| TABLES | ||
| T_BKPF | = lt_t_bkpf | |
| T_BSEG | = lt_t_bseg | |
| T_BSED | = lt_t_bsed | |
| . " TURKEY_BOE_PRINT_NEW | ||
ABAP code using 7.40 inline data declarations to call FM TURKEY_BOE_PRINT_NEW
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