Create ticket using CRM_ORDER_MAINTAIN

Question

I am creating a service ticket using the above mentined RFC. I want to insert the problem area and actual fault as Level1 (parent) and Level2 (child) within the problem area. For that I am making use of the lt_service_os table and building the subject table within it, on the OBJECTS tab of the ticket.
The problem is both the problem area and fault go into the ticket at parent levels.
I do not want to follow 2 step process of creating the ticket first with parent subject and adding the child subject to it as it takes lot of time.
FORM subject_create  USING    P_GV_HANDLE p_gv_product p_gv_l1 p_gv_l2
                              ibaseid
                     CHANGING
                         P_GT_INPUT_FIELDS type crmt_input_field_tab
                         P_GT_OSSET type crmt_srv_osset_comt.
  DATA:
    ls_subject                TYPE crmt_srv_subject_com,
    ls_object    TYPE  crmt_srv_refobj_com,
    ls_input_field            TYPE crmt_input_field,
    ls_input_field_names      TYPE crmt_input_field_names,
    gc_mode_create            TYPE crmt_mode VALUE 'A',
    gc_object_kind_orderadm_h TYPE crmt_object_kind  VALUE 'A',
    gc_object_name_orderadm_h TYPE crmt_object_name  value 'ORDERADM_H',
    lv_service_h       TYPE  crmc_service_h,
    ls_osset           TYPE  crmt_srv_osset_com2,
    lt_refobj          TYPE  crmt_srv_refobj_comt,
    lt_subject         TYPE  crmt_srv_subject_comt,
    lv_handle          TYPE  crmt_handle,
    lt_service_os      TYPE  crmt_srv_osset_comt,
    lt_input_fields_f TYPE crmt_input_field_tab.
  DATA: BEGIN OF lt_code OCCURS 0.
          INCLUDE STRUCTURE com_code_f4.
  DATA: END OF lt_code.
  REFRESH: lt_subject, lt_refobj.
  CALL FUNCTION 'CRM_ORDER_SERVICE_H_SELECT_CB'
    EXPORTING
      iv_process_type = 'YRMS'
    IMPORTING
      es_service_h    = lv_service_h
    EXCEPTIONS
      entry_not_found = 1
      OTHERS          = 2.
Read subject profile LEVEL 1
  Refresh lt_code.
  CALL FUNCTION 'CRM_SUBJECT_PROF_CODES_PROVIDE'
    EXPORTING
      i_subject_profile = lv_service_h-subject_profile
      I_HIERARCHY_LEVEL = '1'
    TABLES
      e_code_tab        = lt_code
    EXCEPTIONS
      no_valid_entry    = 1
      no_entry          = 2
      OTHERS            = 3.
  read table lt_code with key
  katalogart = 'Y1' codegruppe = p_gv_product code = p_gv_l1.
  clear ls_subject.
  MOVE-CORRESPONDING lt_code TO ls_subject.
  CLEAR ls_subject-ref_guid.
  CLEAR ls_subject-ref_guid_h.
  CLEAR ls_subject-ref_handle_h.
  CALL FUNCTION 'CRM_INTLAY_GET_HANDLE'
    IMPORTING
      ev_handle = ls_subject-ref_handle.
  ls_subject-mode         = gc_mode_create.
  ls_subject-hierarchy_level = 1.
  INSERT ls_subject  INTO TABLE lt_subject.
  lv_handle = ls_subject-ref_handle.
Read subject profile LEVEL 2
  Refresh lt_code.
  CALL FUNCTION 'CRM_SUBJECT_PROF_CODES_PROVIDE'
    EXPORTING
      i_subject_profile = lv_service_h-subject_profile
      I_HIERARCHY_LEVEL = '2'
    TABLES
      e_code_tab        = lt_code
    EXCEPTIONS
      no_valid_entry    = 1
      no_entry          = 2
      OTHERS            = 3.
  read table lt_code with key
  katalogart = 'Y2' codegruppe = p_gv_product code = p_gv_l2.
  clear ls_subject.
  MOVE-CORRESPONDING lt_code TO ls_subject.
  CLEAR ls_subject-ref_guid.
  CLEAR ls_subject-ref_guid_h.
  CLEAR ls_subject-ref_handle_h.
  CALL FUNCTION 'CRM_INTLAY_GET_HANDLE'
    IMPORTING
      ev_handle = ls_subject-ref_handle.
ls_subject-ref_handle = lv_handle + 1.
   ls_subject-ref_handle_h = lv_handle.
  ls_subject-mode         = gc_mode_create.
  ls_subject-hierarchy_level = 2.
  INSERT ls_subject  INTO TABLE lt_subject.
   MOVE p_gv_product to ls_object-product_id .
  CLEAR ls_object-ref_guid.
  ls_object-type_object = 'A'.
  CALL FUNCTION 'CRM_INTLAY_GET_HANDLE'
    IMPORTING
      ev_handle = ls_object-ref_handle.
  ls_object-mode = gc_mode_create.
  INSERT ls_object INTO TABLE lt_refobj .
  IF NOT ibaseid IS INITIAL.
    MOVE:
     p_gv_handle        TO ls_object-ref_handle,
     'B'                TO ls_object-type_object,
     ibaseid            TO ls_object-ib_instance,
     'A'                TO ls_object-mode.
    APPEND ls_object TO lt_refobj.
  ENDIF.
Set Osset for subject and Reference object
  CLEAR ls_osset.
  ls_osset-ref_handle = p_gv_handle.
  ls_osset-subject_profile = lv_service_h-subject_profile.
  ls_osset-profile_type    = 'A'.
  lv_handle = p_gv_handle.
  CALL FUNCTION 'CRM_SERVICE_OS_SET_DATA'
    EXPORTING
      is_srv_osset_com   = ls_osset
      iv_ref_handle      = lv_handle
      iv_ref_kind        = 'A'
      it_srv_refobj_com  = lt_refobj
      it_srv_subject_com = lt_subject
    EXCEPTIONS
      error_occurred     = 1
      invalid_guid       = 2
      no_record_exist    = 3
      OTHERS             = 4.
  CALL FUNCTION 'CRM_SERVICE_OS_PUT_DATA'
    IMPORTING
      et_srv_osset_com = lt_service_os
      et_input_fields  = lt_input_fields_f.
  INSERT LINES OF lt_service_os INTO TABLE p_gt_osset.
  INSERT LINES OF lt_input_fields_f INTO TABLE p_gt_input_fields.
Please suggest how to create parent child relation. The code for creating the subjects in the ticket is pasted below for reference.

Answer 1

Hi Thomas,
The FM CRM_ORDER_MAINTAIN has two changing parameters:CT_ORDERADM_H and CT_ORDERADM_I.You can set the mode in these two changing parameters for header or item.
  ls_orderadm_i-mode = gc_mode-create.
  INSERT ls_orderadm_i INTO TABLE lt_orderadm_i.
and then pass this to the FM:
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
    CHANGING
      ct_orderadm_h   = lt_orderadm_h
      ct_orderadm_i   = lt_orderadm_i
      ct_input_fields = lt_input_fields
    EXCEPTIONS
      OTHERS          = 0.
The possible values for mode are:
BEGIN OF gc_mode,
             create     TYPE   crmt_mode   VALUE   'A',
             change     TYPE   crmt_mode   VALUE   'B',
             display    TYPE   crmt_mode   VALUE   'C',
             delete     TYPE   crmt_mode   VALUE   'D',
           END OF gc_mode.
Hope this helps!
Thanks and Regards,
Rohit
Edited by: rohit raturi on Jul 28, 2008 9:26 AM