Error while creating contract type 0002 [Purchase side]

Hiya
While creating a purchase side contract vide tcode wb21 i am getting following error
No basic purchase price relevant to pricing found with schema RM0000
Message no. WV185
Diagnosis
There is no condition record flagged as relevant to pricing in the master conditions defined for the basic purchase price.
Procedure
Check in Customizing (price determination, Purchasing) whether the condition types that are used as gross price or promotion price (these are PB00, PBXX and PA00 in the standard system) are flagged as relevant to pricing. Set this flag if you wish new condition records to be saved as relevant to pricing in future. If you wish to flag existing condition records as "relevant to pricing" in retrospect, use report RWVKP01U.
Kindly help
Regards
Ranjeet

Closing...

Similar Messages

  • Error while creating contract type 0002

    Hiya
    While trying to create purchasing side contract, i am getting an error as below
    No sales prices possible at plant level for distribution chain S001/01
    Message no. WV228
    Diagnosis
    For distribution chain S001/01, in the distribution chain control parameters in Customizing, the "distribution chain pricing level" indicator does not allow plant level as an allowed pricing level below the distribution chain. Plant level must be allowed as a pricing level before you can calculate plant-specific sales prices in sales price calculations.
    System response
    Sales prices cannot be calculated for items containing plants belonging to distribution chain S001/01.
    Procedure
    Make sure you really want to calculate sales prices at plant level. If not, remove the plant(s) concerned.
    If you want to calculate plant-specific sales prices for distribution chain S001/01, change the Customizing settings accordingly.
    Make any necessary Customizing settings if you have the required authorization.
    Contact your system administrator if you cannot make the settingsyourself.
    Any help is appriciated
    Regards

    Hi Vijay
    Thanks for the input, the issue got solved, however i got stuck ahead with another error. it is as belo
    No basic purchase price relevant to pricing found with schema RM0000
    Message no. WV185
    Diagnosis
    There is no condition record flagged as relevant to pricing in the master conditions defined for the basic purchase price.
    Procedure
    Check in Customizing (price determination, Purchasing) whether the condition types that are used as gross price or promotion price (these are PB00, PBXX and PA00 in the standard system) are flagged as relevant to pricing. Set this flag if you wish new condition records to be saved as relevant to pricing in future. If you wish to flag existing condition records as "relevant to pricing" in retrospect, use report RWVKP01U.
    This seems to be from MM side, however if you have any idea please suggest
    Regards
    Ranjeet

  • Getting error while creating condition type in SPRO

    Hi ,
    can somebdy tell me why i am getting the following error while creating condition type in SPRO
    No valid change license available for message /sapcnd/
    and also while rule determination using condition type we are getting the following error.
    system error:system cannot read the structure for table
    reg
    venkat

    Hi Venkat,
    Do you have the error number code!?
    Regards,
    Michel  Bohn

  • Error while creating contract

    Hi Experts,
    I am getting a strange error,while creating quantity contract in VA41 .
    When ever I am trying to save the quantity contract it gives a in completion Log.
    So when I am trying to complete the documents it gives a list of incomplete fields,in those fields I see a field called Net value so when I am clicking on the field its taking me "condition" tab and under that to pricing elements .
    I have assigned pricing procedure to sales org.
    I am not able to understand how to proceed since incomplete doc would not get saved.
    Pls help .

    This is because the cost pricing for EK01 is missing. In t.code V/08, go to pricing procedure. In the pricing procedure, the pricing condition type is ticked as mandatory, hence you see the details in the imcompletion log. For details on cost using EK01, there are plenty of threads in the forum available. Just search, for example Re: Contion Type Line Items:EK01
    Regards,

  • Error While Creating Date type condition query

    Hi All,
    I am getting following error while creating a multiple condition query.
    ERROR:java.lang.IllegalArgumentException: Unexpected field type for D: java.lang.String
    I am pasting the scrap of the code for review below.
    pls note after removing the condition cond6; it works fine, and cond6 is for date type field.
    for(int j=1;j<7;j++){                          
    fd[j] =trd.getFieldDescriptor(arrayHeaderFieldNames[j]);
    BasisFieldType bft1 =  fd[j].getFieldType();
    if (bft1 == BasisFieldType.C) {
      filterOperator[j] = RelationalOperatorType.CONTAINS;       }
    else{
      filterOperator[j] = RelationalOperatorType.EQUALS;
    order[j] =queryFactory.createSortOrder(fd[j],true);
    cond1 =queryFactory.createCondition(fd[1], filterOperator[1], values[0]);
    cond2 =queryFactory.createCondition(fd[2], filterOperator[2], values[1]);
    cond3 =queryFactory.createCondition(fd[3], filterOperator[3], values[2]);
    cond4 =queryFactory.createCondition(fd[4], filterOperator[4], values[3]);
    cond5 =queryFactory.createCondition(fd[5], filterOperator[5], values[4]);
    cond6 =queryFactory.createCondition(fd[6], filterOperator[6], values[5]);
    Condition cond = queryFactory.createCondition(new Condition[]{cond1,cond2,cond3,cond4,cond5,cond6},LogicalOperatorType.AND);
    Please Help!
    Thanks n regards,
    Kapoorchand.

    Hi,
    well that problem is a long time back -. I only have in mind that the date I had to transfer to the quesry was in a "strange" format. Have a lock into the documentation for the date field - your date field is not recognised as a date field from the quesry engine and so this fails - but unfortunately I have no idea at the moment how I fixed it last time - how I converted my date field......
    Sorry, thast I can not give you the real point - but I will have a lock into the old code - hopefully I find it soon.
    Regards,
    Oliver

  • Error while creating contract wrt pr

    hi
    i am creating a pr for cotract, via me51n..selecting outline agr req..then creating pr for a raw material...
    i m releasing this pr in 54n...now i go to 31k...i select wrt pr....now when i give my pr no. i get this error message
    "Requisition doc. type RV not allowed with doc. type"
    i have tried a whole day with different material types...always getting same error msg....
    plz  throw some light on this issue, if u can..
    help appreciated
    regards
    rahul

    SPRO>Materials Management>Purchasing>Contract>Define Document Types
    Here you select your document type and select link to purchase requisation.You can which document typease are assigned.If your entry missed add your PR document type.

  • Error while creating work order from purchase order

    Dear All,
    We are having a subcontracting scenario where we are creating a Work order from PO but getting the below error.
    Error - "No master data assigned to partners-locations-product combination."
    Done all the setting mentioned in the below thread but the error still persist.
    Error in Generating Work order from Purchase Order
    Any suggestions on which master data we need to check?
    Thanks,
    mahesh.

    Hi Mahesh
    In the below transaction
    /SCA/MFGCFG - Work Order Configuration
    Can you maintain Master data Assigment properly
    Valid From
    Valid To
    Active---Checked
    Can you please list what you maintained
    Regards
    Vinod

  • Error while creating data type

    Hi
    I am creating data type for the scenario from File to IDOC
    Namespace urn:xiworkshop:groupxx:legacy is not defined in the software component version NEWPRODUCT , 100 of sap Object Message Type Vendor | urn:xiworkshop:groupxx:legacy references the inactive object Data Type Vendor | urn:xiworkshop:groupxx:legacy
    Please help me

    Hi;
    First activate your namespace and then create the data type.
    Namespace + default datatypes should be activated together.
    Then your data type
    Mudit

  • Error while creating Contracts using BAPI

    Hello,
    I am trying to use BAPI BUS2014 to create new Purchasing Contracts. Now everything works fine, except for some strange cases where Contracts are failing out with a message as:
    Reference document or master record has different language
    I don't understand it why. Language being set in Contracts is defined for those items in MM and it works for others but not for all. I think I am missing some basic point here. Can anyone please suggest?
    Any help is highly appreciated!
    Cheers
    EssKay

    OK - stupid question. I did figure it out myself. Sorry for my impatience. This is my first BAPI program, so a bit too shaky
    Cheers
    EssKay

  • Error While creating Data type from a XSD

    Hi,
    I am trying to import a XSD into my Data type. I have changed the namespace in the XSD to match that of the target namespace. I am getting the following error.
    Global definition Element: http://ls.sbc.com/OMS/ProcessSalesOrderEFE004,   orderRequest in the schema to be edited will be ignored 
    Schema to be edited defines qualified element names (elementFormDefault = 'qualified')
    Could any help me out in this regard. I don't have much knowledge about XML and XSD.
    Regards,
    Ravikanth

    Hi Ravi,
    please check once again your XSD file.
    it should be like this.
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://ls.sbc.com/OMS/ProcessSalesOrderEFE004, " targetNamespace="http://ls.sbc.com/OMS/ProcessSalesOrderEFE004, ">
         <xsd:complexType name="DTO_Data type">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   725b8b10c99e11dc8ff3001cc43a8a68
                   </xsd:appinfo>
    Please check the name of  data type u mentioned in XSD  while imporitng.
    regards
    mahesh..

  • Getting error while creating the variable of Schema Element type

    Hi everybody,
    For creating a variable of schema element type I am doing the following steps...
    Select 'Variables' after right clicking on bpel process. IN this window, go to 'Create VAriable' then select 'Element' type. Now in Type Choose, I expanded the my imported schema files. And selected a element type, then click ok to create this variable... I am getting the message...
    IN ORDER TO SAVE IMPORTED WSDL/SCHEMA FILES, YOU MUST HAVE A PARTNER LINK LOCATED UNDER THE CURRENT PROJECT DIRECTORY.
    What is mean by that.
    I have imported the schema files in project. AFter that I have imported them into the WSDL also. Now why I am getting error while creating the variable. However I can create variable directly in .BPEL file then everything is fine. And it is working also. But what is mean with the above error? Why I am not able to create variable through GUI?
    Thanks.

    Hi,
    I have this same problem this morning, and I was going crazy, until I found this webpage on the internet:
    [http://technology.amis.nl/blog/1803/problem-importing-xml-schema-in-bpel-process|http://technology.amis.nl/blog/1803/problem-importing-xml-schema-in-bpel-process]
    The idea is that the jdeveloper is not very good working with directories with spaces on the directory name. If you move all your work to a directory without spaces, it will work smoothly. At least, it had worked for me.
    Regards,
    Nacho

  • Error while creating "RETURNS" as ERP Sales transaction type

    Description: We are getting error while creating ERP SLO type "Returns-ZRE". Message prompts as "Creation of ERP Transaction failed". We do not get the message for other order types for example "Standard order".
    Please suggest. Please note that this is an ERP sales order in CRM UI not a CR< sales order.
    Thanks
    Shree

    Is this only for a particular order type?
    As stated above this can be to do with user authorisations or the trusted RFC set up. Some things to check are:
    - ST22 dumps in ECC
    - ST01 authorisation trace for the user in ECC
    - Trusted RFC connection set up

  • Error while creating SC: Internal Error - termination type TH_RES_FREE

    Hi I encountered this error while creating a SC. All attributes for this user are maintained and the "check user" transaction does not give any error.
    Amol Mate
    Error when processing your request
    What has happened?
    The URL http://punhjwsapsrm:8000/sap/bc/gui/sap/its/bbpsc02/! was not called due to an error.
    Note
    The following error text was processed in the system SSS : Internal Error
    The error occurred on the application server PUNHJWSAPSRM_SSS_00 and in the work process 1 .
    The termination type was: TH_RES_FREE
    The ABAP call stack was:
    Function: B40B_READ_TABLE of program SAPLBBP_BD_DRIVER_40B
    Function: META_READ_TABLE of program SAPLBBP_BD_META_BAPIS
    Form: LOCATIONS_READ of program SAPLBBP_ATTR_F4
    Function: BBP_ATTR_F4_SLOC_PPOMA of program SAPLBBP_ATTR_F4
    Form: STG_LOC_GET_FOR_LOCATION of program SAPLBBP_SC_APP
    Form: STG_LOC_GET of program SAPLBBP_SC_APP
    Form: LOCATION_STG_LOC_GET of program SAPLBBP_SC_APP
    Form: USER_ATTRIBUTES_GET of program SAPLBBP_SC_APP
    Form: SC_INIT of program SAPLBBP_SC_APP
    Function: BBP_SC_APP_EVENT_DISPATCHER of program SAPLBBP_SC_APP
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SSS in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server PUNHJWSAPSRM_SSS_00 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server PUNHJWSAPSRM_SSS_00 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http-c:100-u:PTEST -l:E-s:SSS-i:PUNHJWSAPSRM_SSS_00 -w:1-d:20051121-t:171904-v: TH_RES_FREE-e:Internal Error
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team

    Hi Amol,
    First of all the sicf transaction is to be used only if you use the internal ITS.
    Now you have to put an external breakpoint in the source code of the ABAP Program or FM you want to debug , one of these in your case :
    Function: B40B_READ_TABLE of program SAPLBBP_BD_DRIVER_40B
    Function: META_READ_TABLE of program SAPLBBP_BD_META_BAPIS
    Form: LOCATIONS_READ of program SAPLBBP_ATTR_F4
    Function: BBP_ATTR_F4_SLOC_PPOMA of program SAPLBBP_ATTR_F4
    Form: STG_LOC_GET_FOR_LOCATION of program SAPLBBP_SC_APP
    Form: STG_LOC_GET of program SAPLBBP_SC_APP
    Form: LOCATION_STG_LOC_GET of program SAPLBBP_SC_APP
    Form: USER_ATTRIBUTES_GET of program SAPLBBP_SC_APP
    Then launch the transaction in IE, once the program reaches a breakpoint, you'll get the ABAP debuger in IE.
    Regards.
    PS: if it doesn't work, put the parameter ~generatedynpro in BBPGLOBAL service to have it applied to all BBP transactions
    Vadim

  • Error while creating the 'LOV' type parameter in Siebel 8.1.1.5

    Hi,
    One of my Customer is facing the below error while creatting the parameter of type 'LOV' in Parameter applet in Siebel 8.1.1.5
    Runtime Error!
    Program: C:\Program Files\Internet Explorer\iexplorer.exe
    This application has requested the Runtime to terminate it in an usual way. Please contact the application’s support team for more information
    Could some please let me know what would be the reason for this issue?
    Thanks in advance for your help.
    Thanks,
    Ravi

    Please close this thread...it appears that the error occurs when the report involves a big set of records. I tried trying to filter only one record and was able to produce the pdf

  • Error while creating an outbound idoc using idoc type delvry02

    hi,
         i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
    ERROR:
                " SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
    MESSAGE NO: AM053
    Help would be appreciated.
    regards
    leo

    The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
    It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
    Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

Maybe you are looking for