Transaction CLM1 not allowed for notification type QL

Hello guys,
one of our user try to open the transaction CLM1/CLM2/CLM3 he getting error message Transaction CLM1 not allowed for notification type QL
please any one give solution for this issue.
find the error screen shot for your reference.
Thanks
Surya

Hello Surya,
Have you done Basic configuration for Claims processing in SAP Project System.
SPRO > Project System > Claim > Notification - Claim > Notification creation
Also check config for Settings for Claims.
Refer sap help for more details
SAP Library - Claim Management
Regards
Tushar

Similar Messages

  • Transaction QM03 not allowed for notification type MQ

    HI Dears,
         The following error is appearing when i want to view my notification created through defects
    Transaction QM03 not allowed for notification type MQ
         How to rectify it ?
    Alagesan

    Hi,
    Check IQS3 transaction also....
    Cheers,
    Tushar

  • Set type COMM_PR_UNIT is not allowed for product type

    Hello all, I am working in SRM 7.0 and when I try to replicate service master (DNL_CUST_SRVMAS) I have this error:
    Set type COMM_PR_UNIT is not allowed for product type
    What can I do? I think that is an ABAP problem
    Thanks in advance
    Rosa Rodríguez

    Rosa,
    This note is something different and nothing to do with the issue. Can you share how did you resolve the DNL_CUST_SRVMAS issue? We are also getting same error.
    Thanks,
    Jagadish

  • Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'

    Hi All,
    I created the wsdl for mobile and I tried to send a SOAP request from Altova XMLSpy. However when I geive the wsdl in 'wsdl file location' I receive the following.
    File http://127.0.0.1:8080/B1iXcellerator/exec/dummy/com.sap.b1i.vplatform.scenarios.setup/vPac.sap.B1Mobile/001sap0003_sap.B1Mobile.wsdl is not valid.
    Invalid XML schema: 'Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'.'
      Error location: wsdl:definitions / wsdl:types / xs:schema / xs:element / @type
    Any Idea?
    Vangelis

    Hi,
      it seems that Altove did not cope with defaultNs prefix that is used for marking default namespace.
       just look up in your <xs:schema > tag what namespace prefix is used for your namespace - you shall find there something like this
    <xs:schema xmlns:ns0="your.namespace.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
    and replace prefix defaultNs with prefix of your namespace (in example above it would be ns0)
    There might be several usages of defalutNs iside of WSDL (at least in my case were two) so replace it everywhere using same approach
    Best regards, Artem

  • Status profile not allowed for object type

    hi
    i had created a status profile (for having 2 statuses before production order release) and assigned in the order type.
    but while creating the production order i receive the following error.
    Message no - CO622
    status profile not allowed for object type
    please provide your inputs
    regards
    Ramesh

    Ramesh,
    once you cerate a Status profile in BS02 and add status to the same. in the tollbar you will see OBJECT TYPE push button, select teh obejcts like PP/PM order header / operation /comepeoent and PRT ect where that staus can be applied.
    Then assign the statsu profile to order type.

  • Method SAP_WAPI_WORKITEM_COMPLETE not allowed for type F

    Hi Gurus
    I have created a webdynpro abap application in which these steps
    1. Application triggers the workflow and workitem got created through FM1.
    2. Workitem loads up webdynpro abap application from portal or outlook by changing settings in SWFVISU transaction.
    3. Application completes the workflow by calling FM2.
    Here FM1 is SAP_WAPI_START_WORKFLOW which returns the workitem id. When I am giving the same workitem id in function module SAP_WAPI_WORKITEM_COMPLETE , it is giving me error that Method SAP_WAPI_WORKITEM_COMPLETE not allowed for type F
    My workflow has only one activity step which is mapped with class CL_PT_REQ_WF_ATTRIBS and method DUMMY. I have checked the synchronous method.
    Please let me know how can I correct it.
    With regards
    Manu Sharma

    Hi
    You need to give the workitem id of the dialog task which has been configured in SWFVISU. You will get this workitem id via application parameter in your Webdynpro method.
    Wokflow will be completed, if all the steps has been executed
    Vinoth
    Edited by: S Vinoth on Oct 27, 2010 10:08 AM

  • Create PO condtion FRA1 "One-time vendor not allowed for this transaction"

    Hi all,
    When create Freight conditon for po item, if i choose a one-time vendor , it gives me an error  "One-time vendor not allowed for this transaction" .
    Why it happened? How to config system let one-time vendor be the conditon's vendor ?
    Thanks .

    dear wayne,
    what is your account group for the vendor if OTA (one time account ) is ticked for that account, the system will not allow you to give the condition type FRA1.
    Please correct me if I m wrong and revert back if any doubt.
    Njoy
    Ashish

  • ABAP Dictionary type FLTP is not allowed for screen element

    Hi Experts
    I tried to open VBFA in se16 and i got the message in the status bar like this , what does it mean. please explain.
    "ABAP Dictionary type FLTP is not allowed for screen element"

    Hi,
        This is from help
    ABAP Dictionary type FLTP is not allowed for screen element
    Message no. 37048
    <b>Diagnosis</b>
    The format of the ABAP Dictionary field is only for use within the ABAP
    program and cannot be used in the Screen Painter.
    <b>Procedure</b>
    The field cannot be used in screens. If you want to output the
    information in the field or assign a value to the field from the screen,
    you must use an intermediate field with an appropriate format.
    <b>Reward points</b>
    Regards

  • The operation is not allowed for result set type FORWARD_ONLY

    Hi,
    I am trying to use scroll insensitive resultset in following manner-
    Statement stmt = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
    ResultSet rs = stmt.executeQuery("some sql here");
    rs.last();
    but the rs.last() throws this exception-
    com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: The operation is not allowed for result set type FORWARD_ONLY.
         at com.sap.dbtech.jdbc.ResultSetSapDB.assertNotForwardOnly(ResultSetSapDB.java:2725)
         at com.sap.dbtech.jdbc.ResultSetSapDB.last(ResultSetSapDB.java:557)
    Database version: Kernel    7.5.0    Build 019-121-082-363
    Driver Version: MaxDB JDBC Driver, MySQL MaxDB, 7.6.0    Build 030-000-005-567
    This used to work with 7.5 version driver. Why this is failing with 7.6 driver, any clues?
    Thanks,
    Vinod

    Hi Vinod,
    due to performance improvement when using forward only cursor we changed the default for the resultset type from TYPE_SCROLL_SENSITIVE to TYPE_FORWARD_ONLY starting with JDBC driver version 7.6. So I guess the exception comes from a statement where you didn't set the resultset type while creating it. Please check if all of the statements that you want to be scrollable have set the correct resultset type.
    Regards,
    Marco

  • Rebate-Manual payment is not allowed for this agreement type

    Hi,
    While processing the Rebates, after the Sales cycle till Billing document, when i i try to process the partial settlement it is givin a message as "Manual payment is not allowed for this agreement type"
    could you please suggest.
    Regards
    AS

    Hi AS
    If you want to do manual payment then in VB)2 select the Agreement type and then in that agreement type check wheather Manual rebate order type has been assigned or not and Manual payment has been checked or not . If they are not maintained and Checked  then maintain the rebate document type and check the box Manual accruals and then you can do Manual Payment for that agreement
    Regards
    Srinath

  • Cross Company MIRO Transaction - BSEG-TXGRP Not Valued for Account Type "S"

    I am working with the ABAP group to create tax reports for audits and sales tax charged by vendor.  I am basically wanting a line item report of all purchases along with any tax applied to each line.  Therefore, I am, for the most part, using tables BKPF, BSEG, and BSET.  For our US transactions, we have one company paying the invoice on behalf of all other US companies.  Essentially, every transaction is a cross-company transaction.  The problem is I am having a hard time tying BSEG to BSET by line item.  For FB60 transactions, I can tie BSEG-TXGRP to BSET-TXGRP; however, for MIRO transactions, BSEG-TXGRP is not valued for Account Type "S" (GL Accounts).  Any ideas?  I could not find a note to capture this issue.  There was a note, but it was with regard to Account Types "D" and "K" I believe, vendor and customer accounts.
    Any help would be greatly appreciated.
    Thanks,
    Deanna

    So,
    Did you ever resolve this.  I have the EXACT problem right now.   Inter-co. MIRO documents only getting TAXGRP popuplated for Original Co. Document (not cross-co. document).
    Thanks,
    - Tim

  • Activity type E not allowed for equipment entered

    Dear Sir , We are using ETM . Following error is coming while creating  performace based document .
    Activity type E not allowed for equipment entered
    Regards
    Anil

    Give 1 for both type and give it a try.
    for target=actual which is type 5 pls check the link below
    http://help.sap.com/saphelp_46c/helpdata/EN/66/bc6faa43c211d182b30000e829fbfe/content.htm

  • ESS Business Package Error: Period type not allowed for profile ESS

    Hi,
    We are trying to configure the business package for Employee Self Service on Enterprise Portal 6.0. We followed this SDN contribution <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eb036a-0a01-0010-25a3-b2224432640a">ESS doc guide</a>
    So far we have successfully deployed the business packages and followed all the configurations that were pointed out in the doc guide. Unfortunately when we try to access the Employee Self-Service portal pages (Overview, Employee Search, etc), we encounter this error:
    Critical Error:
    Period type not allowed for profile ESS, error key: RFC_ERROR_SYSTEM_FAILURE
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException:      Period type not allowed for profile ESS, error key: RFC_ERROR_SYSTEM_FAILURE
    Any ideas on how to fix this issue?
    Regards,
    Jojo

    Hi Jojo,
    Have you solved the problem? If yes can you please help me even I am facing the same error.
    this is very help full to me .
    Thanks and Regards,
    Shilpi.

  • Error in RFx : Item type 'Service' not allowed for this Item

    hi , experts,
      We use SRM7.0 in Standalone scenario .
      i get an error when i transfer SC to RFx :     Line 0001: Item type 'Service' not allowed for this Item .
    if someone kindly tell me how to correct this Error.
      another question is ,in the Standalone scenario , can we create Service Master with multiple level(hierarchy) use Tcode 'COMMPR01 ' ?
       reagrds
               claud

    Hi Claud,
    SRM does not support hierarchy in service for operational documents like PO, contract, confirmation and invoice in SRM 7. It does support hierarchy in service only for RFx doucments. You need to activate the hierarchy template for SRM for that.
    Thanks and regards,
    Ranjan

  • Error : Wage Type is not allowed for personnel SG grouping for WT 3

    Hi All,
    When i am trying to create wage type Degree allowance i am getting error like below.
    WT xxxx is not allowed for personnel SG grouping for WT 3 (from 01.09.2006 to
    31.12.9999)
         Message no. PG 074
    Diagnosis
         In the "Personnel Subgroup Grouping for Primary Wage Types" view
         (V_001P_K), the employee is assigned to personnel SG for primary wage
         types 3. However, this grouping is not valid for wage type xxxx in the
         period from 01.09.2006 to 31.12.9999.
    Please let me know where i needs to check.
    Thanks.

    try to change the start date and try like 01.01.1990 like this
    juss chk and update

Maybe you are looking for