FTR_STAV_OBJECT_CREATE SAP Function module - Generate Status Object

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

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

Pattern for FM FTR_STAV_OBJECT_CREATE - FTR STAV OBJECT CREATE

CALL FUNCTION 'FTR_STAV_OBJECT_CREATE' "Generate Status Object
  EXPORTING
    obtyp =                     " jsto-obtyp    Object Type
*   stsma = SPACE               " jsto-stsma    Status Profile
*   chgkz = SPACE               "               Kennzeichen Änderungsbelegfortschreibung Objekt
*   objnr = SPACE               " jsto-objnr    Object Number
  IMPORTING
    e_objnr =                   " jsto-objnr    Object Number
  EXCEPTIONS
    OBTYP_INVALID = 1           "               Invalid Object Type
    STATUS_OBJECT_ALREADY_EXISTS = 2  "         Status Object Already Exists
    STSMA_INVALID = 3           "               Invalid status profile
    STSMA_OBTYP_INVALID = 4     "               Status Profile Not Created for Object Type
    .  "  FTR_STAV_OBJECT_CREATE

ABAP code example for Function Module FTR_STAV_OBJECT_CREATE

The ABAP code below is a full code listing to execute function module FTR_STAV_OBJECT_CREATE 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_e_objnr  
 
 TYPE JSTO-OBJNR
.

 

SELECT single OBTYP 
  FROM JSTO 
  INTO @DATA(ld_obtyp).

 

SELECT single STSMA 
  FROM JSTO 
  INTO @DATA(ld_stsma).


DATA(ld_chgkz) = 'some text here'.
 

SELECT single OBJNR 
  FROM JSTO 
  INTO @DATA(ld_objnr).

.

CALL FUNCTION 'FTR_STAV_OBJECT_CREATE'
  EXPORTING
    obtyp =                      ld_obtyp
*   stsma =                      ld_stsma
*   chgkz =                      ld_chgkz
*   objnr =                      ld_objnr
  IMPORTING
    e_objnr =                    ld_e_objnr
  EXCEPTIONS
    OBTYP_INVALID =              1
    STATUS_OBJECT_ALREADY_EXISTS =    2
    STSMA_INVALID =              3
    STSMA_OBTYP_INVALID =        4
    .  "  FTR_STAV_OBJECT_CREATE

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
ELSEIF SY-SUBRC EQ 4. "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_e_objnr
 
 TYPE JSTO-OBJNR ,
ld_obtyp
 
 TYPE JSTO-OBTYP ,
ld_stsma
 
 TYPE JSTO-STSMA ,
ld_chgkz
 
 TYPE STRING ,
ld_objnr
 
 TYPE JSTO-OBJNR .



SELECT single OBTYP 
  FROM JSTO 
  INTO ld_obtyp.


SELECT single STSMA 
  FROM JSTO 
  INTO ld_stsma.

ld_chgkz = 'some text here'.

SELECT single OBJNR 
  FROM JSTO 
  INTO ld_objnr.