SAP /AIN/PUB_DEVCOM_DEVCTR_PRINT Function Module for Construct and send a Print message to device controller
/AIN/PUB_DEVCOM_DEVCTR_PRINT is a standard /ain/pub devcom devctr 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 Construct and send a Print message to device controller 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 /ain/pub devcom devctr print FM, simply by entering the name /AIN/PUB_DEVCOM_DEVCTR_PRINT into the relevant SAP transaction such as SE37 or SE38.
Function Group: /AIN/PUB_DEVCOM
Program Name: /AIN/SAPLPUB_DEVCOM
Main Program: /AIN/SAPLPUB_DEVCOM
Appliation area:
Release date: 10-May-2006
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /AIN/PUB_DEVCOM_DEVCTR_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 '/AIN/PUB_DEVCOM_DEVCTR_PRINT'"Construct and send a Print message to device controller.
EXPORTING
IV_DEVGRP_INTID = "Device Group Internal ID
* IV_TAG_UPDATE = '' "Update Tag (Yes / No)
TABLES
IT_USER_DATA = "User Memory Data
IT_LBL_QTY = "Label format and quantity of tags to be printed
* ET_RETURN = "Table with BAPI Return Information
EXCEPTIONS
TECHNICAL_LEVEL_ERROR = 1 TECHNICAL_LEVEL_ERROR_COMM = 2 BUSINESS_LEVEL_ERROR_INPUT = 3
IMPORTING Parameters details for /AIN/PUB_DEVCOM_DEVCTR_PRINT
IV_DEVGRP_INTID - Device Group Internal ID
Data type: /AIN/PUB_DEVGRP_INTIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_TAG_UPDATE - Update Tag (Yes / No)
Data type: /AIN/PUB_DEVCOM_TAG_UPDATEDefault: ''
Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for /AIN/PUB_DEVCOM_DEVCTR_PRINT
IT_USER_DATA - User Memory Data
Data type: /AIN/PUB_ID_UDATA_TABOptional: No
Call by Reference: Yes
IT_LBL_QTY - Label format and quantity of tags to be printed
Data type: /AIN/PUB_DEVCOM_PRN_LBLQTY_TABOptional: No
Call by Reference: Yes
ET_RETURN - Table with BAPI Return Information
Data type: BAPIRETTABOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
TECHNICAL_LEVEL_ERROR -
Data type:Optional: No
Call by Reference: Yes
TECHNICAL_LEVEL_ERROR_COMM - Communication failure to device controller
Data type:Optional: No
Call by Reference: Yes
BUSINESS_LEVEL_ERROR_INPUT - Nothing to write to tag / label
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for /AIN/PUB_DEVCOM_DEVCTR_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_it_user_data | TYPE STANDARD TABLE OF /AIN/PUB_ID_UDATA_TAB, " | |||
| lv_iv_devgrp_intid | TYPE /AIN/PUB_DEVGRP_INTID, " | |||
| lv_technical_level_error | TYPE /AIN/PUB_DEVGRP_INTID, " | |||
| lt_it_lbl_qty | TYPE STANDARD TABLE OF /AIN/PUB_DEVCOM_PRN_LBLQTY_TAB, " | |||
| lv_iv_tag_update | TYPE /AIN/PUB_DEVCOM_TAG_UPDATE, " '' | |||
| lv_technical_level_error_comm | TYPE /AIN/PUB_DEVCOM_TAG_UPDATE, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
| lv_business_level_error_input | TYPE BAPIRETTAB. " |
|   CALL FUNCTION '/AIN/PUB_DEVCOM_DEVCTR_PRINT' "Construct and send a Print message to device controller |
| EXPORTING | ||
| IV_DEVGRP_INTID | = lv_iv_devgrp_intid | |
| IV_TAG_UPDATE | = lv_iv_tag_update | |
| TABLES | ||
| IT_USER_DATA | = lt_it_user_data | |
| IT_LBL_QTY | = lt_it_lbl_qty | |
| ET_RETURN | = lt_et_return | |
| EXCEPTIONS | ||
| TECHNICAL_LEVEL_ERROR = 1 | ||
| TECHNICAL_LEVEL_ERROR_COMM = 2 | ||
| BUSINESS_LEVEL_ERROR_INPUT = 3 | ||
| . " /AIN/PUB_DEVCOM_DEVCTR_PRINT | ||
ABAP code using 7.40 inline data declarations to call FM /AIN/PUB_DEVCOM_DEVCTR_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.| DATA(ld_iv_tag_update) | = ''. | |||
Search for further information about these or an SAP related objects