SAP ADS_BUILD_DEVTYPE Function Module for
ADS_BUILD_DEVTYPE is a standard ads build devtype 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 ads build devtype FM, simply by entering the name ADS_BUILD_DEVTYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SPADS
Program Name: SAPLSPADS
Main Program: SAPLSPADS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ADS_BUILD_DEVTYPE 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 'ADS_BUILD_DEVTYPE'".
TABLES
PT022D = "
PTFO03 = "
PTFO04 = "
PTFO06 = "
PTSP06 = "
PTSP06A = "
PTSP0A = "
EXCEPTIONS
MISSING_AUTHORITHY = 1 INVALID_PARAMETER = 2 INVALID_PRINTER_DRIVER = 3 DEVICE_TYPE_LOCKED = 4 DEVICE_TYPE_NOT_MODIFYABLE = 5 ERROR_WHILE_CREATING = 6 FOREIGN_LOCK = 7 SYSTEM_FAILURE = 8 DEVTYPE_ALREADY_THERE = 9
TABLES Parameters details for ADS_BUILD_DEVTYPE
PT022D -
Data type: T022DOptional: No
Call by Reference: Yes
PTFO03 -
Data type: TFO03Optional: No
Call by Reference: Yes
PTFO04 -
Data type: TFO04Optional: No
Call by Reference: Yes
PTFO06 -
Data type: TFO06Optional: No
Call by Reference: Yes
PTSP06 -
Data type: TSP06Optional: No
Call by Reference: Yes
PTSP06A -
Data type: TSP06AOptional: No
Call by Reference: Yes
PTSP0A -
Data type: TSP0AOptional: No
Call by Reference: Yes
EXCEPTIONS details
MISSING_AUTHORITHY -
Data type:Optional: No
Call by Reference: Yes
INVALID_PARAMETER -
Data type:Optional: No
Call by Reference: Yes
INVALID_PRINTER_DRIVER -
Data type:Optional: No
Call by Reference: Yes
DEVICE_TYPE_LOCKED -
Data type:Optional: No
Call by Reference: Yes
DEVICE_TYPE_NOT_MODIFYABLE -
Data type:Optional: No
Call by Reference: Yes
ERROR_WHILE_CREATING -
Data type:Optional: No
Call by Reference: Yes
FOREIGN_LOCK -
Data type:Optional: No
Call by Reference: Yes
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: Yes
DEVTYPE_ALREADY_THERE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ADS_BUILD_DEVTYPE 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_pt022d | TYPE STANDARD TABLE OF T022D, " | |||
| lv_missing_authorithy | TYPE T022D, " | |||
| lt_ptfo03 | TYPE STANDARD TABLE OF TFO03, " | |||
| lv_invalid_parameter | TYPE TFO03, " | |||
| lt_ptfo04 | TYPE STANDARD TABLE OF TFO04, " | |||
| lv_invalid_printer_driver | TYPE TFO04, " | |||
| lt_ptfo06 | TYPE STANDARD TABLE OF TFO06, " | |||
| lv_device_type_locked | TYPE TFO06, " | |||
| lt_ptsp06 | TYPE STANDARD TABLE OF TSP06, " | |||
| lv_device_type_not_modifyable | TYPE TSP06, " | |||
| lt_ptsp06a | TYPE STANDARD TABLE OF TSP06A, " | |||
| lv_error_while_creating | TYPE TSP06A, " | |||
| lt_ptsp0a | TYPE STANDARD TABLE OF TSP0A, " | |||
| lv_foreign_lock | TYPE TSP0A, " | |||
| lv_system_failure | TYPE TSP0A, " | |||
| lv_devtype_already_there | TYPE TSP0A. " |
|   CALL FUNCTION 'ADS_BUILD_DEVTYPE' " |
| TABLES | ||
| PT022D | = lt_pt022d | |
| PTFO03 | = lt_ptfo03 | |
| PTFO04 | = lt_ptfo04 | |
| PTFO06 | = lt_ptfo06 | |
| PTSP06 | = lt_ptsp06 | |
| PTSP06A | = lt_ptsp06a | |
| PTSP0A | = lt_ptsp0a | |
| EXCEPTIONS | ||
| MISSING_AUTHORITHY = 1 | ||
| INVALID_PARAMETER = 2 | ||
| INVALID_PRINTER_DRIVER = 3 | ||
| DEVICE_TYPE_LOCKED = 4 | ||
| DEVICE_TYPE_NOT_MODIFYABLE = 5 | ||
| ERROR_WHILE_CREATING = 6 | ||
| FOREIGN_LOCK = 7 | ||
| SYSTEM_FAILURE = 8 | ||
| DEVTYPE_ALREADY_THERE = 9 | ||
| . " ADS_BUILD_DEVTYPE | ||
ABAP code using 7.40 inline data declarations to call FM ADS_BUILD_DEVTYPE
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