SAPSCRIPT_ORDER_CHECK SAP Function module - Styles and Forms: Is There Already a Transport / Correction?

SAPSCRIPT_ORDER_CHECK 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 SAPSCRIPT_ORDER_CHECK into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM SAPSCRIPT_ORDER_CHECK - SAPSCRIPT ORDER CHECK

CALL FUNCTION 'SAPSCRIPT_ORDER_CHECK' "Styles and Forms: Is There Already a Transport / Correction?
  EXPORTING
    objecttype =                " c
*   form =                      " itcta-tdform  Form Name
*   style =                     " itcda-tdstyle  Style Name
  IMPORTING
    order =                     " e071k-trkorr
    value_tadir =               " tadir
  EXCEPTIONS
    INVALID_INPUT = 1           "
    OBJECT_LOCKED = 2           "
    OBJECT_NOT_AVAILABLE = 3    "
    .  "  SAPSCRIPT_ORDER_CHECK

ABAP code example for Function Module SAPSCRIPT_ORDER_CHECK

The ABAP code below is a full code listing to execute function module SAPSCRIPT_ORDER_CHECK 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_order  
 
 TYPE E071K-TRKORR
,
ld_value_tadir  
 
 TYPE TADIR
.


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


DATA(ld_form) = some text here


DATA(ld_style) = some text here
.

CALL FUNCTION 'SAPSCRIPT_ORDER_CHECK'
  EXPORTING
    objecttype =                 ld_objecttype
*   form =                       ld_form
*   style =                      ld_style
  IMPORTING
    order =                      ld_order
    value_tadir =                ld_value_tadir
  EXCEPTIONS
    INVALID_INPUT =              1
    OBJECT_LOCKED =              2
    OBJECT_NOT_AVAILABLE =       3
    .  "  SAPSCRIPT_ORDER_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
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_order
 
 TYPE E071K-TRKORR ,
ld_objecttype
 
 TYPE C ,
ld_value_tadir
 
 TYPE TADIR ,
ld_form
 
 TYPE ITCTA-TDFORM ,
ld_style
 
 TYPE ITCDA-TDSTYLE .


ld_objecttype = 'Check type of data required'.

ld_form = some text here

ld_style = some text here