SPRX_START SAP Function module - Proxy Geneartion: Entry Screen

SPRX_START is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SPRX_START into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SPRX_START
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SPRX_START - SPRX START

CALL FUNCTION 'SPRX_START' "Proxy Geneartion: Entry Screen
* EXPORTING
*   r3name =                    " prx_r3name    Proxy Generation: Name of an Object in R/3
*   r3obj =                     " prx_r3obj     Proxy Generation: Object Type in R3 (DTEL, TABL,...)
*   category =                  " prx_type      Proxy Generation: Object Type in Enterprise Services Builder
*   name =                      " prx_ifrnam    Proxy Generation: External Name
*   namespace =                 " prx_nspce     Proxy Generation: External Namespace
*   genapp =                    " prxgenappl    Proxy Generation: Generation Source
*   package =                   " devclass      Package
    .  "  SPRX_START

ABAP code example for Function Module SPRX_START

The ABAP code below is a full code listing to execute function module SPRX_START including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_r3name) = 'Check type of data required'.

DATA(ld_r3obj) = 'Check type of data required'.

DATA(ld_category) = 'Check type of data required'.

DATA(ld_name) = 'Check type of data required'.

DATA(ld_namespace) = 'Check type of data required'.

DATA(ld_genapp) = 'Check type of data required'.

DATA(ld_package) = 'Check type of data required'.
.

CALL FUNCTION 'SPRX_START'
* EXPORTING
*   r3name =                     ld_r3name
*   r3obj =                      ld_r3obj
*   category =                   ld_category
*   name =                       ld_name
*   namespace =                  ld_namespace
*   genapp =                     ld_genapp
*   package =                    ld_package
    .  "  SPRX_START

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_r3name
 
 TYPE PRX_R3NAME ,
ld_r3obj
 
 TYPE PRX_R3OBJ ,
ld_category
 
 TYPE PRX_TYPE ,
ld_name
 
 TYPE PRX_IFRNAM ,
ld_namespace
 
 TYPE PRX_NSPCE ,
ld_genapp
 
 TYPE PRXGENAPPL ,
ld_package
 
 TYPE DEVCLASS .


ld_r3name = 'Check type of data required'.
ld_r3obj = 'Check type of data required'.
ld_category = 'Check type of data required'.
ld_name = 'Check type of data required'.
ld_namespace = 'Check type of data required'.
ld_genapp = 'Check type of data required'.
ld_package = 'Check type of data required'.