SAP RSPO_VALID_DEVICE Function Module for









RSPO_VALID_DEVICE is a standard rspo valid device 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 rspo valid device FM, simply by entering the name RSPO_VALID_DEVICE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SPOC
Program Name: SAPLSPOC
Main Program: SAPLSPOC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RSPO_VALID_DEVICE 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 'RSPO_VALID_DEVICE'"
EXPORTING
LNAME = "Spool: Long device names
* CLIENT = SY-MANDT "Client

EXCEPTIONS
INVALID = 1
.



IMPORTING Parameters details for RSPO_VALID_DEVICE

LNAME - Spool: Long device names

Data type: TSP03D-NAME
Optional: No
Call by Reference: Yes

CLIENT - Client

Data type: T000-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

INVALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSPO_VALID_DEVICE 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_lname  TYPE TSP03D-NAME, "   
lv_invalid  TYPE TSP03D, "   
lv_client  TYPE T000-MANDT. "   SY-MANDT

  CALL FUNCTION 'RSPO_VALID_DEVICE'  "
    EXPORTING
         LNAME = lv_lname
         CLIENT = lv_client
    EXCEPTIONS
        INVALID = 1
. " RSPO_VALID_DEVICE




ABAP code using 7.40 inline data declarations to call FM RSPO_VALID_DEVICE

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 NAME FROM TSP03D INTO @DATA(ld_lname).
 
 
"SELECT single MANDT FROM T000 INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!