TRINT_CHECK_NSP_OBJ_DU_EDIT SAP Function module

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

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

Pattern for FM TRINT_CHECK_NSP_OBJ_DU_EDIT - TRINT CHECK NSP OBJ DU EDIT

CALL FUNCTION 'TRINT_CHECK_NSP_OBJ_DU_EDIT' "
  EXPORTING
*   iv_mode = 'S'               " trpari-flag   General Indicator
    iv_pgmid =                  " tadir-pgmid
    iv_object =                 " tadir-object  Object Type
    iv_obj_name =               " tadir-obj_name  Object Name
    iv_devclass =               " tadir-devclass
*   iv_tdevc_filled = SPACE     " trpari-flag   General Indicator
*   iv_pattern_obj = SPACE      " trnspace-namespace
*   iv_genflag = SPACE          " tadir-genflag  Generation Flag
*   iv_check_editflag = SPACE   " trpari-flag   General Indicator
  IMPORTING
    et_namespaces =             " trnsp_namespaces
    et_dlvunits =               " trdlvunits
* CHANGING
*   cs_tdevc =                  " tdevc
  EXCEPTIONS
    OBJECT_INCONSISTENT = 1     "
    GENFLAG_REQUIRED = 2        "
    MISSING_INPUT = 3           "
    SYSTEM_ERROR = 4            "               System Error
    NO_DU_CHANGEABLE = 5        "
    NO_AUTHORITY_CHANGE_COMPONENT = 6  "
    .  "  TRINT_CHECK_NSP_OBJ_DU_EDIT

ABAP code example for Function Module TRINT_CHECK_NSP_OBJ_DU_EDIT

The ABAP code below is a full code listing to execute function module TRINT_CHECK_NSP_OBJ_DU_EDIT 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_et_namespaces  
 
 TYPE TRNSP_NAMESPACES
,
ld_et_dlvunits  
 
 TYPE TRDLVUNITS
.


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


DATA(ld_iv_mode) = some text here
 

SELECT single PGMID 
  FROM TADIR 
  INTO @DATA(ld_iv_pgmid).

 

SELECT single OBJECT 
  FROM TADIR 
  INTO @DATA(ld_iv_object).

 

SELECT single OBJ_NAME 
  FROM TADIR 
  INTO @DATA(ld_iv_obj_name).

 

SELECT single DEVCLASS 
  FROM TADIR 
  INTO @DATA(ld_iv_devclass).



DATA(ld_iv_tdevc_filled) = some text here
 

SELECT single NAMESPACE 
  FROM TRNSPACE 
  INTO @DATA(ld_iv_pattern_obj).

 

SELECT single GENFLAG 
  FROM TADIR 
  INTO @DATA(ld_iv_genflag).



DATA(ld_iv_check_editflag) = some text here
.

CALL FUNCTION 'TRINT_CHECK_NSP_OBJ_DU_EDIT'
  EXPORTING
*   iv_mode =                    ld_iv_mode
    iv_pgmid =                   ld_iv_pgmid
    iv_object =                  ld_iv_object
    iv_obj_name =                ld_iv_obj_name
    iv_devclass =                ld_iv_devclass
*   iv_tdevc_filled =            ld_iv_tdevc_filled
*   iv_pattern_obj =             ld_iv_pattern_obj
*   iv_genflag =                 ld_iv_genflag
*   iv_check_editflag =          ld_iv_check_editflag
  IMPORTING
    et_namespaces =              ld_et_namespaces
    et_dlvunits =                ld_et_dlvunits
* CHANGING
*   cs_tdevc =                   ld_cs_tdevc
  EXCEPTIONS
    OBJECT_INCONSISTENT =        1
    GENFLAG_REQUIRED =           2
    MISSING_INPUT =              3
    SYSTEM_ERROR =               4
    NO_DU_CHANGEABLE =           5
    NO_AUTHORITY_CHANGE_COMPONENT =    6
    .  "  TRINT_CHECK_NSP_OBJ_DU_EDIT

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
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "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_cs_tdevc
 
 TYPE TDEVC ,
ld_et_namespaces
 
 TYPE TRNSP_NAMESPACES ,
ld_iv_mode
 
 TYPE TRPARI-FLAG ,
ld_et_dlvunits
 
 TYPE TRDLVUNITS ,
ld_iv_pgmid
 
 TYPE TADIR-PGMID ,
ld_iv_object
 
 TYPE TADIR-OBJECT ,
ld_iv_obj_name
 
 TYPE TADIR-OBJ_NAME ,
ld_iv_devclass
 
 TYPE TADIR-DEVCLASS ,
ld_iv_tdevc_filled
 
 TYPE TRPARI-FLAG ,
ld_iv_pattern_obj
 
 TYPE TRNSPACE-NAMESPACE ,
ld_iv_genflag
 
 TYPE TADIR-GENFLAG ,
ld_iv_check_editflag
 
 TYPE TRPARI-FLAG .


ld_cs_tdevc = 'Check type of data required'.

ld_iv_mode = some text here

SELECT single PGMID 
  FROM TADIR 
  INTO ld_iv_pgmid.


SELECT single OBJECT 
  FROM TADIR 
  INTO ld_iv_object.


SELECT single OBJ_NAME 
  FROM TADIR 
  INTO ld_iv_obj_name.


SELECT single DEVCLASS 
  FROM TADIR 
  INTO ld_iv_devclass.


ld_iv_tdevc_filled = some text here

SELECT single NAMESPACE 
  FROM TRNSPACE 
  INTO ld_iv_pattern_obj.


SELECT single GENFLAG 
  FROM TADIR 
  INTO ld_iv_genflag.


ld_iv_check_editflag = some text here