Is it possible to integrate the Code Inspector in Transport Management

[Former Member]

Hi,

Is it possible to integrate the Code Inspector in the Transport Management.

The idea is, that on a release of a request the code inspector starts automatically and if there are error the release is not possible.

Greeting

Marcus Schug

[former_member192895]

You can write 'event' for it..

[Former Member]

Can you tell me how I could write the event?

[former_member192895]

In your case, no need to write any event because whenever you release any request and if it is syntactically incorrect it won't allow you to transport.So, I don't think that you have to worry about integration of code inspector with Transport management.It automatically take care of this.

[Former Member]

The syntactically correctness is one side, but I also want to check some other things like coding convenions with the code inspector.

[Former Member]

Hi

It's like the Code Inspector Check is already included in the Trasnport mangament.

Normally you will do the following checks before transporting any objects right.

For inactive objects, for consistency, object checks , where the your required CIC performed

It's what upto my knowledge. if you have any doubts other than this..

Please come forward.

Regards,

GP

Rewards point if useful

[Former Member]

There are some BAdIs beeing triggered by CTS, perhaps one of these might be helpful:

CTS_CURRENT_PROJECT 
CTS_EXPORT_FEEDBACK 
CTS_IMPORT_FEEDBACK 
CTS_INT_REQUEST_CHCK
CTS_REQUEST_CHECK   
CTS_TASKDOC_TEMPLATE

[Former Member]

In the BaDi CTS_REQUEST_CHECK I could use the method IF_EX_CTS_REQUEST_CHECK~CHECK_BEFORE_RELEASE

I tried the following

  DATA ls_request_header TYPE trwbo_request_header.
  DATA lt_objects TYPE tr_objects.
  DATA lt_mainobjects TYPE scit_objs.
  ls_request_header-trkorr = trkorr.
  CALL FUNCTION 'TR_GET_OBJECTS_OF_REQ_AN_TASKS'
    EXPORTING
      is_request_header            = ls_request_header
*     IV_CONDENSE_OBJECTLIST       = ' '
   IMPORTING
     et_objects                   = lt_objects
*     ET_KEYS                      =
   EXCEPTIONS
     invalid_input                = 1
     OTHERS                       = 2
            .
  IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  ENDIF.

  ycl_check=>map_limu_to_r3tr(
    EXPORTING
      p_trobjects   = lt_objects
    IMPORTING
      p_mainobjects = lt_mainobjects
         ).

  DATA lv_ok TYPE  sychar01.
  DATA lo_result TYPE REF TO  cl_ci_check_result.
  DATA lo_inspection TYPE REF TO cl_ci_inspection.
  TRY.
      cl_ci_check=>object_list(
        EXPORTING
*    p_variant_user          =
          p_variant               = 'Y_DEVELOMENT'
          p_objects               = lt_mainobjects
*    p_insp_user             =
*    p_insp_name             =
*    p_objs_user             =
*    p_objs_name             =
*    p_text                  =
*    p_execute_parallel      =
*    p_ignore_pseudocomments =
        IMPORTING
          p_ok                    = lv_ok
          p_result                = lo_result
             ).

      lo_inspection = lo_result->get_inspection( ).

    CATCH cx_ci_invalid_variant .
    CATCH cx_ci_invalid_objectset .
    CATCH cx_ci_check_error .
  ENDTRY.

But how can I get the messages from the Code Inspection

[former_member226999]

In the transport management screen of SE10, go to menu UTILITIES->settings and select the check box for "Check objects when released". This would enable code checking at the time of release and also scream with all errors.

Hope this helps. Please reward points if answered.

[Former Member]

Thank, but this is only individual.

[former_member186444]

Hi Marcus,

can you (or anyone else) tell me if there is an answer to this as we wuld like to do the same thing - ie, on release of a transport, automatically run the Code Inspector and get the results back.

thanks,

Malcolm.

[Former Member]

Hi:

Are there any answer related to get result of class CL_CI_CHECK?

[OttoGold]

Hello gentlemen,

does that mean that this question was never answered? Or somebody could jump in even so late and share one?

Thanks Otto

[former_member182670]

1. You have to enable object check on release.

It can be set globally (In SE03>Administration>Global Customizing) or for users individually in SE09 settings

2. If you want to customize the inspection which is triggered during release then table SCICHKV_ALTER has to be maintained. See note 1465965

[OttoGold]

Hi, thanks for the hint.

I activated it, but now cannot see any result. Can you give one more hint where can I then see the result of the check?

I expected a message in SE10, but got none. I would also like to be stopped from releasing the transport if there are any errors during the SCI check.

Thanks again,

Otto

[former_member182670]

In case no errors were found the system will proceed with release otherwise you should get a popup with error information.

See also [http://help.sap.com/saphelp_erp60_sp/helpdata/EN/57/38e22b4eb711d182bf0000e829fbfe/frameset.htm|http://help.sap.com/saphelp_erp60_sp/helpdata/EN/57/38e22b4eb711d182bf0000e829fbfe/frameset.htm]

[Former Member]

This message was moderated.