Error while creating a pricing condition record.

Hi
I am trying to use the Material Group 1 (MVGR1) field from the field catalog to create a pricing condition table(9 series). I was able to create the table with MVGR1 as one of the columns but when I try to maintain condition records in the table, System gives me the following error. I have maintained certain values in the config for material group1. there is neither F4 values for the field Material group nor I can type in config values of MVGR1 in that field. I am getting this error. Any help on how to get past this issue will be highly appreciated.
Thanks
Object Material group 1 not provided with characteristic AS. (Note other fields!)
Message no. VK432
Diagnosis
The value entered in a field is not permitted.
System response
The system issues an error message.
Procedure
Check the entry and make the necessary corrections. Note any relationships between the individual fields. Entries in other fields may also be incorrect.
Example: There are two fields for maintaining the country and region. These fields are linked. The country chosen would be permitted if it were by itself. So would the region. But the region may not be in the the country chosen. In this case, an error message is issued. The country should then be corrected, not the region!
Edited by: Suraj Ramakrishnan on Dec 24, 2009 2:45 AM

Message no. VK432
Check note 750841
thanks
G. Lakshmipathi

Similar Messages

  • 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 in BDOC while uploading the pricing condition record to ECC from CRM

    Hi all,
    I have created a condition record for ECC pricing condition type (I have maintained all settings required for maintaining ECC condition type in CRM 7.0) in CRM 7.0. But theis condition record is not uploaded to ECC. I have checked BDOC, it is showing with error status for BDOC type "CND_M_SUP". The errors are as below.
    1. sBDoc CNBCCPSAP005 does not contain structure CDBD_CONDREF
    Message no. CND_MAST064
    2. sBDoc CNBCCPSAP005 does not contain structure CDBD_CONDREF
    Message no. CND_MAST064
    3. Service that caused the error: CND_MAST_INT_DEEP_MB_TO_SBDOC
    Message no. SMO8047Diagnosis
    A service caused/ reported an error.
    Can some one help me in fixing this issue  please.
    Thanks in advance,
    JM
    Edited by: JM on Sep 7, 2010 4:46 PM

    Hi,
    sBDOCs are not used in ECC to CRM or CRM to ECC data replication scenario. You can either ignore the error or disable mobile bridge.
    Regards
    Prasenjit

  • Error while mainitain the pricing ( condition type - j3ap )

    Hi,
      While i am creating the pricing for an AFS material in T code mek1 ( condition type is j3ap ) i am getting the following error ::
    Information  857    Report RV13F002 generated.
    Information  711    No Screens are generated.
    Information  857    Report  RV13F003 generated.
    Information  711    No screens are generated
    Errors        806     Report RV13F004 has a syntax error
    Information  711    No screens are generated.
    What is these error?? what setting should i change to correct it ,.
    Regards
    Rakesh

    you can refer to
    http://www.triggergroup.org/blog/archives/585

  • Error while creating pivot table in recording macro

    im getting error " Run time error 1004: unable to get the pivottables property of the worksheet class
    below is the code
    Sub Macro16()
    ' Macro16 Macro
    ' Keyboard Shortcut: Ctrl+t
        ActiveWorkbook.PivotCaches.Create(SourceType:=xlDatabase, SourceData:= _
            "Premium Data!R1C1:R25000C11", Version:=xlPivotTableVersion14). _
            CreatePivotTable TableDestination:="", TableName:= _
            "PivotTable14", DefaultVersion:=xlPivotTableVersion14
        Sheets("Premium Pivot").Select
        Cells(2, 2).Select
        With ActiveSheet.PivotTables("PivotTable14").PivotFields("RM")
            .Orientation = xlRowField
            .Position = 1
        End With
        ActiveSheet.PivotTables("PivotTable14").AddDataField ActiveSheet.PivotTables( _
            "PivotTable14").PivotFields("KL"), "Sum of KL", xlSum
    End Sub

    You have TableDestination:="" which means you are not specifying a destination and therefore a new sheet gets created and it becomes the active sheet. You are selecting Sheets("Premium Pivot") which will not
    have the pivot table and the remainder of the code references the ActiveSheet.
    Either delete the line Sheets("Premium Pivot").Select or set the table destination like the following.
    TableDestination:="'Premium Pivot'!R3C1"      (Note the single quotes around the sheet name that contains a space. Edit the range on the destination to suit your requirements.)
    Regards, OssieMac

  • Error while creating absence record in PA30 using 2001 infotype

    Hi all,
    iam getting an error while creating absence record for infotype 2001for LOP(unpaid)
    error : No quota available for att./abs. 6000 for pers. no. 61000052 between 31.12.2009 and 31.12.2009
    i have did
    Create a absence type LOP
    Determine Entry Screens and Time Constraint Classes
    Define Counting Rules
    Assign Counting Rules to Absence Types
    Payroll: India>>Absences>Describe Absence Valuation Rules 01 Unpaid Leave
    Group Absences for Absence Valuation>>Absence valuation rule>>F4 country grouping 40>> assign 01Unpaid Leave
    please solve this

    Actually I don't know how your system is configured.
    However, the error you're receiving seems you have assigned the absence type to a quota type.
    Please go to your counting rule and check whether Deduction rule - absence quotas - within entitlement field is filled.
    If yes, get the deduction rule value and go to
    SPRO Time man- Time data rec - Absences - Absence Cat - Abs counting - rules for counting (new) - deduction rules for abs quotas and check the quota type in here.
    If there is a quota assignment in place, before creating an IT2001 you need to create a IT2006 for that specific time period.
    Or, you need to delete the quota assignment via two config steps mentioned above.
    Regards,
    Dilek

  • 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

  • ESS: Error while creating Family/Dependents record from portal

    Hi All,
    I'm getting a critical error while creating family members and dependents record from portal.
    CRITICAL ERROR
    "Type conflict in the ASSIGN statement in the program CL_HRPA_CONVERT_0021_US=======CP        ., error key: RFC_ERROR_SYSTEM_FAILURE"
    I checked the short dump in R/3 Side and searched for OSS note and didnt find any. I raised an OSS message.
    If any had've already comeacross this, pls let me know.
    System Details
    EP 6.0 SP15
    ESS Business Package BPERP4ESS0_0
    ESS Support Package  ESS10P_2-10002965, PCUIGP010P_1-20000568
    Thanks
    Karthik

    Hello Karthik:
    I'm getting the same error:
    "critical error while creating family members and dependents record from portal.
    Type conflict in the ASSIGN statement in the program CL_HRPA_CONVERT_0021_US=======CP ., error key: RFC_ERROR_SYSTEM_FAILURE"
    Maybe you can help me solving this problem.
    I appreciate your help.
    Thanks in advance.

  • Is there a  BAPI to create IS-Oil (formula) MM Pricing condition records

    Hi,
    Is there a standard BAPI to create IS-Oil (formula) MM Pricing condition records, which would include the maintaining of the formula?
    Regards
    Kasi

    no BAPI exists

  • BAPI  to create IS-Oil (formula) MM Pricing condition records

    Hi,
    Is there a standard BAPI  to create IS-Oil (formula) MM Pricing condition records, which would include the maintaining of the formula?
    Regards
    Kasi

    no BAPI exists

  • 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,

  • Pricing condition records should not be picked up

    Hi,
    I have configured a scenario for Supplementary Invoice for which I created a new sales order type. The requirement is such that this order type should not pick the pricing condition records that have been created in VK11. Please suggest how can this be configured.
    Do I have to use any Userexits, if so which one?
    Regards,
    Abhishek

    As mentioned by you, you have created a new Sales Order Type, you can create a new document pricing procedure, based on which you can determine a new pricing procedure.
    To configure new Document Pricing Procedure:
    IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Define Document Pricing Procedure. (Maintain the new Document Pricing Procedure in new Sales Order Type)
    Maintain a new Pricing Procedure, maintaining the Condition Types as manual. Maintain the determination of Pricing Procedure appropriately.
    Pricing Procedure Determination:
    In SD, Pricing Procedure is determined (T.Code: OVKK) based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
    Pricing Procedure Configuration:
    In SD, the steps to configure Pricing procedure are as under:
    Step 1:
    Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
    Step 2:
    Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
    Step 3:
    Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
    Step 4:
    a. Pricing Procedure (T.Code: V/08):  It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
    b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
    5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
    Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
    Regards,
    Rajesh Banka

  • Creating new pricing condition type in srm ecs

    Hi Guru's
    I see that there is an option to select the Source system " local" , "other system, eg: R/3" while creating a new condition type in SRM. can you please let me know what is the importance of this? can we determine price in srm using backend pricing conditions? can we invoke the backend pricing procedure from srm and populate the price in SRM PO?
    any helpful info would be appreciated
    regards
    deepu

    Hi Nitin,
    Appreciate your response. Can you please let me know how major development is it? if you can provide highlights that would be helpful. I do understand that we can customize the pricing procedure in SRM. Can you please share if you have any documentation regarding creating new condition types, access sequences, condition records in SRM similar to ECC? it would be appreciated if you can send it to pradeepwsu(gmail) id.
    Thanks in advance
    Deepu

  • Getting ORA-20001: Address_Cannot_be_Primary error while creating US Global

    Dear All,
    I am getting ORA-20001: Address_Cannot_be_Primary error while creating address record of address type US global.
    While analyzing the PYUPIP trace, I found the following piece of the code is causing issue:
    File : /* $Header: peusaddlh.pkb 120.0.12010000.2 2010/05/08 09:10:25 lbodired noship $ */
    Package : APPS.PER_US_ADD_LEG_HOOK.CREATE_US_ADDRESS
    Code check :
    IF (p_style <> 'US'
    AND P_PRIMARY_FLAG = 'Y'
    AND csr_emp_assign%FOUND) THEN
    close csr_emp_assign;
    hr_utility.set_message (800, 'Address_Cannot_be_Primary');
    hr_utility.raise_error;
    END IF;
    It seems that while applying this check the case of the US Global address style is not taken care.
    It has struck the address conversion, as all the records of my client has the address style US Global.
    Please suggest how it will effect if for the time being I do following code changes in the seeded package(I know it is not recommened, but can not wait for the patch).
    1. Comment the whole check
    2. Replace the above code with the follwoing code :
    IF (p_style not in ('US','US_GLB')
    AND P_PRIMARY_FLAG = 'Y'
    AND csr_emp_assign%FOUND) THEN
    close csr_emp_assign;
    hr_utility.set_message (800, 'Address_Cannot_be_Primary');
    hr_utility.raise_error;
    END IF;
    Looking for the prompt reply.
    regards
    Devender Yadav

    Dear All,
    Oracle has supplied the patch 9902020 for the fix of the issue.
    Now the payroll install check condition is also added in the check.
    Code in the check is now like this :
    IF (p_style <> 'US'
    AND P_PRIMARY_FLAG = 'Y'
    AND csr_emp_assign%FOUND
    AND hr_general.chk_product_installed('801') = 'TRUE') THEN
    close csr_emp_assign;
    hr_utility.set_message (800, 'Address_Cannot_be_Primary');
    hr_utility.raise_error;
    END IF;
    As my client has not installed the payroll, so the fix will work for us.
    Thanks to all of you for your replies.
    Regards
    Devender Yadav

  • Error while creating table

    Hi,
    I am getting an error while creating a table,
    create table cs_temp_xml_data as select rowid RW_ID, value(d).getClobVal() xml_value FROM cs_tmp_wcl_xml_data p,table(xmlsequence(extract(p.xml_data,'/records/record'))) d ;
    Here cs_tmp_wcl_xml_data contains a data of 600 mb in oracle directory
    ORA-04030: out of process memory when trying to allocate 4000 bytes (qmxlu subheap,qmemNextBuf:alloc)
    Can anyone help me out regarding this error?

    check out metalink doc: 543239.996
    also bug 3436395.

Maybe you are looking for