SAP ALE_CTRACPSINVDOC_PRINT Function Module for BAPI -> IDoc: ALE_CTRACPSINVDOC_PRINT
ALE_CTRACPSINVDOC_PRINT is a standard ale ctracpsinvdoc print SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: ALE_CTRACPSINVDOC_PRINT 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 ale ctracpsinvdoc print FM, simply by entering the name ALE_CTRACPSINVDOC_PRINT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_INV_BOR
Program Name: SAPLFMCA_INV_BOR
Main Program: SAPLFMCA_INV_BOR
Appliation area:
Release date: 10-Oct-2007
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALE_CTRACPSINVDOC_PRINT 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 'ALE_CTRACPSINVDOC_PRINT'"BAPI -> IDoc: ALE_CTRACPSINVDOC_PRINT.
EXPORTING
INVDOCHEADER = "BAPI: Input Structure for Invoicing Document (Header)
* XPRINTSIMULATE = "
* XPRINT = "
* XGETPDF = "
* OBJ_TYPE = 'PS_INVDOC' "
* SERIAL_ID = '0' "
TABLES
* INVDOCPDF = "BAPI: Invoice in PDF Format (128 Bytes per Line)
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for ALE_CTRACPSINVDOC_PRINT
INVDOCHEADER - BAPI: Input Structure for Invoicing Document (Header)
Data type: BAPI_CTRACPSINVDOC_HOptional: No
Call by Reference: No ( called with pass by value option)
XPRINTSIMULATE -
Data type: BAPI_CTRACPSINVDOC_PRNT-X_SIMULATEOptional: Yes
Call by Reference: No ( called with pass by value option)
XPRINT -
Data type: BAPI_CTRACPSINVDOC_PRNT-X_PRINTOptional: Yes
Call by Reference: No ( called with pass by value option)
XGETPDF -
Data type: BAPI_CTRACPSINVDOC_PRNT-X_GETPDFOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJ_TYPE -
Data type: SERIAL-OBJ_TYPEDefault: 'PS_INVDOC'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SERIAL_ID -
Data type: SERIAL-CHNUMDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ALE_CTRACPSINVDOC_PRINT
INVDOCPDF - BAPI: Invoice in PDF Format (128 Bytes per Line)
Data type: BAPI_CTRACPSINVDOC_PDFOptional: Yes
Call by Reference: No ( called with pass by value option)
RECEIVERS -
Data type: BDI_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_DOCUMENTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
APPLICATION_OBJECTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_CREATING_IDOCS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ALE_CTRACPSINVDOC_PRINT 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_invdocpdf | TYPE STANDARD TABLE OF BAPI_CTRACPSINVDOC_PDF, " | |||
| lv_invdocheader | TYPE BAPI_CTRACPSINVDOC_H, " | |||
| lv_error_creating_idocs | TYPE BAPI_CTRACPSINVDOC_H, " | |||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lv_xprintsimulate | TYPE BAPI_CTRACPSINVDOC_PRNT-X_SIMULATE, " | |||
| lv_xprint | TYPE BAPI_CTRACPSINVDOC_PRNT-X_PRINT, " | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_xgetpdf | TYPE BAPI_CTRACPSINVDOC_PRNT-X_GETPDF, " | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_obj_type | TYPE SERIAL-OBJ_TYPE, " 'PS_INVDOC' | |||
| lv_serial_id | TYPE SERIAL-CHNUM. " '0' |
|   CALL FUNCTION 'ALE_CTRACPSINVDOC_PRINT' "BAPI -> IDoc: ALE_CTRACPSINVDOC_PRINT |
| EXPORTING | ||
| INVDOCHEADER | = lv_invdocheader | |
| XPRINTSIMULATE | = lv_xprintsimulate | |
| XPRINT | = lv_xprint | |
| XGETPDF | = lv_xgetpdf | |
| OBJ_TYPE | = lv_obj_type | |
| SERIAL_ID | = lv_serial_id | |
| TABLES | ||
| INVDOCPDF | = lt_invdocpdf | |
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| EXCEPTIONS | ||
| ERROR_CREATING_IDOCS = 1 | ||
| . " ALE_CTRACPSINVDOC_PRINT | ||
ABAP code using 7.40 inline data declarations to call FM ALE_CTRACPSINVDOC_PRINT
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 X_SIMULATE FROM BAPI_CTRACPSINVDOC_PRNT INTO @DATA(ld_xprintsimulate). | ||||
| "SELECT single X_PRINT FROM BAPI_CTRACPSINVDOC_PRNT INTO @DATA(ld_xprint). | ||||
| "SELECT single X_GETPDF FROM BAPI_CTRACPSINVDOC_PRNT INTO @DATA(ld_xgetpdf). | ||||
| "SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type). | ||||
| DATA(ld_obj_type) | = 'PS_INVDOC'. | |||
| "SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id). | ||||
| DATA(ld_serial_id) | = '0'. | |||
Search for further information about these or an SAP related objects