6 Replies Latest reply: May 17, 2012 8:19 AM by vijay khandare RSS

Crm Opportunity : Header data - subject profile does not exist

Nageshwar Nagula
Currently Being Moderated

Could some one help on this attached error.

  • Re: Crm Opportunity : Header data - subject profile does not exist
    vijay khandare
    Currently Being Moderated

    Dear Not Active Contributor

     

    If you have created opportunity using upload program ,you might enter wrong value for subject Profie.

    another think ,if you have created opportunity direcly, issue might be with Subject Profile Customization.

    you could have deleted any values.please check.

    also attach screen shot of status and reason field.

     

    Regard ,

    vijay

  • Re: Crm Opportunity : Header data - subject profile does not exist
    Nithish PP
    Currently Being Moderated

    Hi Avinash,

     

    In SPRO go to Customer Relationship Management->Transactions->Settings for Investigations->Codes and Catalogs->Define Subject Profile

     

    Here you need to define subject profile and assign it to specific transaction types . Check here whether particular subject profile has been defined and assigned.

     

    Regards,

    Nithish

    • Re: Crm Opportunity : Header data - subject profile does not exist
      Satish P
      Currently Being Moderated

      Hello Friends,

       

      We are also facing the same issue.

       

      We have uploaded cutover opportunities using a program.

       

      Many Opportunities have either missing status or reason for status therefore we have developed another program to update the missing status as well reason.

       

      To our surprise status as well reason does get updated but error message : Header Data - subject profile does not exist remains intact.

       

      Nithish : can you please elaborate the use of Settings for Investigations in SPRO.

       

      Thanks,

      Satish

      • Re: Crm Opportunity : Header data - subject profile does not exist
        Nithish PP
        Currently Being Moderated

        HI Satish,

         

        In SPRO check the path Customer Relationship Management->Basic Functions->Catalogs, Codes and Profiles. You can define your custom reasons and codes and use in any of the business transactions.

         

        Here first you need to define Define Catalogs, then define Define Code Groups and Codes for Catalogs next Define Code Group Profiles and finally Define Subject Profiles.

         

        Assign this subject profiles to particular transaction types using Assign Status Profile and Subject Profile to Business Transaction Type . Then you can enter the reason code.

         

        Regards,

        Nithish

  • Re: Crm Opportunity : Header data - subject profile does not exist
    Nageshwar Nagula
    Currently Being Moderated

    Hello Friends,

     

    Actually we are using a custom upload program to upload the Opportunites. When there is a missing status and reason is uploaded this error occurs.

     

    This error remains after correcting the status and reason for that Opportunites and get uploaded, but on the screen it is shows corrected status and reason for that Opportunites.

     

    Regards

    Avinash N

    • Re: Crm Opportunity : Header data - subject profile does not exist
      vijay khandare
      Currently Being Moderated

      Please correct program,upload program might assign wrong values in fields.

       

       

      check following code might help you,

       

      {

       

       


      *subject
      **********************************************************************

        wa_subject-ref_handle = '1'.
        wa_subject-katalogart = 'O1'.


            wa_subject-codegruppe = 'ZOPTCLD1'.

       

        MOVE wa_oppt_upd-statusreason TO wa_subject-code.
      *      wa_subject-code = lw_code.
        wa_subject-mode = 'A'.


        APPEND wa_subject TO it_subject.

       

        CALL FUNCTION 'CRM_GUID_CREATE'
          IMPORTING
            ev_guid = lw_service_guid.""LS_OSSET-GUID.

            wa_osset-subject_profile = 'ZOPTSP001'.
            READ TABLE wa_crmt_srv_osset_wrk-osset INTO wa_temp_osset WITH KEY subject_profile = 'ZOPTSP001'.


      *  lw_service_guid = wa_temp_osset-guid.

        CLEAR wa_osset.
        wa_osset-ref_handle = '0000000000'.
        wa_osset-ref_guid = lw_service_guid.


        wa_osset-profile_type = 'H'.
        wa_osset-subject = it_subject.

        APPEND wa_osset TO it_osset.

        wa_service_os-ref_guid = lv_guid_ref.
        wa_service_os-ref_kind = 'A'.
        wa_service_os-osset = it_osset.

        APPEND wa_service_os TO it_service_os.


        CLEAR wa_field_names.
        REFRESH it_field_names.
        wa_field_names-fieldname = 'CODE'.
        APPEND wa_field_names TO it_field_names.

        wa_field_names-fieldname = 'CODEGRUPPE'.
        APPEND wa_field_names TO it_field_names.

        wa_field_names-fieldname = 'DEFECTCLASS'.
        APPEND wa_field_names TO it_field_names.

        wa_field_names-fieldname = 'DEFQUANTITY'.
        APPEND wa_field_names TO it_field_names.

        wa_field_names-fieldname = 'KATALOGART'.
        APPEND wa_field_names TO it_field_names.

        wa_field_names-fieldname = 'LISTCODE'.
        APPEND wa_field_names TO it_field_names.

        wa_field_names-fieldname = 'QUALITY'.
        APPEND wa_field_names TO it_field_names.

       

        CLEAR wa_input_fields.
        wa_input_fields-ref_handle = '0000000000'.
        wa_input_fields-ref_guid = lv_guid_ref.
        wa_input_fields-ref_kind = 'A'.
        wa_input_fields-objectname = 'SERVICE_OS'.
        wa_input_fields-field_names = it_field_names.

        APPEND wa_input_fields TO it_input_fields.


      **********************************************************************

      }

       

       

      regard ,

      vijay.

Actions