VPRS condition requirement 604

Hi,
When I create sales order, cost (VPRS) is not coming. It is saying that requirement 604 not fullfilled. Where do I check to see whether it is calculating cost based on item category or not?
Fully rewarded.
Thanks

Hi Mike,
Looking at the error it seems that you have assigned routine 604 (which must be custome made) to condition type in pricing procedure you are using.
There must be certain checks defined in the routine which are failing because of reasons which you need to analyse.
Simply put breakpoint in routine and debugg.You will get the answer,
Reward points if useful
Regards,
Amrish Puorhit

Similar Messages

  • VPRS condition

    Hi All,
    Could someone please explain me ,why "VPRS condition is missing" comes up , inspite of standard price and moving/average price having maintained in the material master.
    Thank you .

    Hi swetha
    Check the following data
    1) VPRS condition type should be statistical  and in item category details VOV7 , check relevant for statistics
    2) In V/06 , in VPRS details check the field  Condition category . G FOR COSTING.
    3)  In pricing procedure maintain subtotal B and requirement 4 ( Cost )
    Regards
    Srinath

  • No Value in VPRS Condition type

    Dear Experts
    While preparing a sales order , i am getting zero value against the cond type VPRS.It was working fine until recently this problem has started coming.In the Conditions details , it shows Incative-Inactive via formula of incorrect.
    the accounting view in the material master is also maintained.
    Your immediate comments for the same are required.

    Ensure that "Moving avarage price" or the "Standard price" is maintained in the Material master data in "Accounting 1".
    Specify the "Price control" in the MATERIAL MASTER as "V" if you want that system should take the "Moving avarage price" or specify "S" if you want that "Standard price " to be taken.
    In the Pricing procedure(V/08), Subtotal should be "B" and Requirement should be "4" for the VPRS condition type.
    Activate, the "Determine cost" check box in the Item category for Sales (VOV7).
    In the condition type VPRS, ensure that it has "Condition category" G.

  • VPRS condition type not getting computed while retro billing.

    Dear All,
    I have an issue while generation of Reto billing using the T.Code : VFRB.While running VFRB the values are getting computed correctly and the supplimentary debit / credit note gets created.
    But the values for the condition type VPRS is not getting computed and getting transfered to CO-PA.
    On pricing analysis agaist VPRS i am getting the message (Condition ignored (requirement 004 not fulfilled)).
    The Item category used is TAN and the Determine cost Indicator is marked.Also while doing a sales invoice the VPRS condition type is getting computed and the value is posted in CO - PA.
    What would be the reason for the error .Could some one suggest a solution .Kindlye help.
    Regards,
    K.Vivek

    Hello vivek,
    this is usually caused by userexit. Please check  userexit_pricing_prepare_tkomp userexit_number_range using in rv60afzz.
    Best regards,
    Ivano.

  • VPRS condition to use, but not to display to user

    Hi,
    We have a requirement to use VPRS condition type in billing documents. However, the values in this condition should not be visible to the users.
    Please suggest, if this is possible and how.

    Hi
    Check OSS note 105621
    http://www.sapfans.com/forums/viewtopic.php?t=80256
    Regards
    Edited by: Dublin on Dec 24, 2009 12:42 PM

  • VPRS condition not floating in to sales order...

    Good evening every body...
    My query is VPRS condition not floating in to sales order...
    Please give your valuable inputs
    I checked Pricing procedure analysis
    giving error requirement 004 not fulfilled
    Note:
    I checked determine cost in Item category (TAN)
    VPRS condition in my pricing procedure
    I maintained Standard price in Accounting1 tab of MMR
    Valuation class I maintained in MMR
    VPRS condition type I maintain condition category-"G"
    Anything I missed out???
    Regards,
    Krishna

    In my view, the information provided by you is not sufficient to provide you an exact solution.
    As based on & differs business scenario to business scenario you are following.
    Like whether it is BOM, MTO/MTS, Free Goods, batches, third party sales, Order-related billing or Delivery-related billing:...
    Business Process
    Source of costing
    - Order-related billing
    Valuation price of the material master
    - Delivery-related billing
    Goods issue
    Further there are various way to carry out costing at Sales order, like
    - Product costing
    - Unit costing
    So, you can check whether EK01/EK02 or any other cost related is executing prior/take preference to VPRS in your pricing
    Also. kindly check your entries for Account Determination for valuation area(T001K) by using TCode OMWD.
    If everything is fine, then test run a Sales cycle till Billing, so as to see whether at billing VPRS is reflecting or not.
    If in case you need further assistance, do let us know.
    Regards
    JP

  • VPRS condition type in Third party sales

    Hi
    We have the following scenario for 3rd party sales:
    1. SO is created which generates a PR
    2. PO is created.  Example below
    Base price - 100
    Freight - 10
    Insurance - 10
    3. GR is done with below a/c entry
    COGS Dr 120
    Clearing Cr 120
    4. IR is done (Regular a/c entry)
    4. Billing - At the time of billing, i expect that system should pass 120 to VPRS value field in COPA (100+10+10 from PO), however, it is only passing 100 (Base price from PO).  Any adivse how to fix this
    Thanks in advance
    Shiv

    Hi,
    Also, go through the below customized settings for cost + other value to be updated in the VPRs
    condition type.
    In Pricing, you may want to compare the prices with costs or even implement contribution margin accounting.
    To do this, you can use the condition type VPRS as the cost price.
    The condition type VPRS goes into the valuation segment in the material master and determines from this the standard price or average price.
    Settings in Customizing
    The condition type VPRS is labeled as a statistical condition in the pricing procedure.
    Using the condition category G, the condition type VPRS goes into the valuation segment of the material master and determines from here the standard or average price.
    The condition category S always accesses the standard price whereas condition category T always accesses the average price.
    The profit margin is determined using the calculation formula 11 assigned in the pricing procedure. In this calculation formula the cost price is subtracted from the subtotal of net value 2.
    Regards
    Srinivas Salpala

  • HT201359 The new (09/19/13) Apple terms and conditions require one to click the AGREE button in order to update the apps;  however, there is no such button to click on.  Therefore I cannot update the apps on my iPhone.  Any ideas?

    The new (09/19/13) Apple terms and conditions require one to click the AGREE button in order to update the apps;  however, there is no such button to click on.  Therefore I cannot update the apps on my iPhone.  Any ideas?

    I was having the same problem, I had to go into iTunes on my laptop and agree to the terms there, and now i can download apps on my iPhone.

  • Rebate:condition requirement 24 not fulfilled

    Dear Sirs
    I am processing billing doc but rebate condition type is not activated at f2 billing type.
    I have maintained rebate condition type in pricing procedure.
    When i go through "Analysis" tab in sales order item condition level I found that there is message regarding rebate condition type was
    "condition requirement 24 not fulfilled" . I have gone through thread dated 2 feb 2011 raised by sapuser. I refer the same but not very much clear regarding the solution.
    solution suggested " when debuging it was found that pricing type changed from X to xx in copy control"
    now my queries are :
    1)  In which screen pricing type has to changed for copy control
    2)  What could be possible errors might come in case condition requirement not fulfilled in pricing procedure with reference to rebates  because there are about 5 types of rebates and all are having same requirement in pricing procedure
    Kindly help
    Regards
    KAPIL MORE

    Dear Ivano Sir
    Firstly extremely sorry to close these query so late and also thanks for giving me yours valuable time but henceforth i will see that i should give response to your feedback .
    Actually i have solve this query by debugging and understood.
    Could u please if possible kindly give me some inputs regarding user-exits.
    Regards
    KAPIL MORE

  • VPRS condition type not to display

    Hi all
    I have condition type VPRS in my pricing procedure but my client wants it should not be display to the all user while creating sale order. Is there any way.
    Kindly replay urgently.
    Vinod

    Hi Vinod,
    Specific condition types can be hidden on pricing screens; we did the same for VPRS condition type.
    In include LV69AFZZ there is a user exit - USEREXIT_FIELD_MODIFICATION; here you need to add code as follows. 
    if <whatever conditions in which you want to hide it>
    CASE SCREEN-NAME.
    WHEN 'KOMV-KBETR'.
    IF KOMV-KSCHL = 'VPRS'.
    SCREEN-ACTIVE = 0.
    ENDIF.
    WHEN 'KOMV-KWERT'.
    IF KOMV-KSCHL = 'VPRS'.
    SCREEN-ACTIVE = 0.
    ENDIF.
    WHEN 'KOMV-KWERT_K'.
    IF KOMV-KSCHL = 'VPRS'.
    SCREEN-ACTIVE = 0.
    ENDIF.
    ENDCASE.
    ENDIF (for conditions in which the field has to be hidden)
    However we found that this happened only at item level; header still showed the condition type. Smart users can proportionately allocate the header condition amount to arrive upon the item level values. But you may investigate along these lins to determine if it is possible at header too.
    Please reward with points if useful.
    Cheers,
    KC
    SAP SD

  • VPRS Condition is missing in invoice for bacth determine line item

    Hi Gurus,
    I have an Concern, My user has created Sales order with three line items.
    He did delivery and Invoice individually for each line item.
    For 2 line items he entered batch manually and did invoice there we didn't find any issue.
    For third line item he did auto batch determination there for that item VPRS condition is missing in invoice.
    I have checked the note ( 70038 ) and I have applied the note also, But still I am facing same problem.
    Please provide me solution if any modification need to be done,
    Thanks and Regards
    Subbu

    Hi Subbu
    As VPRS condition type is coming for the first 2 line items and not for 3rd line item , so kindly check the Material Master Record->Accounting tab.What is the difference between the 3rd material and another 1st and 2nd materials.Also check in the Analysis what it is showing for the third line item billing document
    Regards
    Srinath

  • Not able to create conditional required fields at Tcode CJ20N Proj Systems

    Hello experts,
    I have a requirement to create a few custom fields under custom enhancement tab in CJ20N transaction, and depending on a particular value for one of the fields, another set of fields need to be set to required. (If FIELD1 = 'Y', FIELD2 & FIELD3 should be set to required)
    My approaches..
    1. Assign a screen group to FIELD2 and FIELD3. If FIELD1 = 'Y' then LOOP AT SCREEN, and set screen-required = 1 for that specific screen group.
    Problem with this approach is that, if I select FIELD1 = 'Y' (hit space or enter -> sy-ucomm = TOGGLE), the fields are successfully set to required. However, now if at this point I go and change value for FIELD1 = 'X' (hit space or enter), FIELD2 and FIELD3 still remain set to required, and keep requesting value.
    2. Do not set any fields to required. Instead set it to an information message in PAI, informing user that this field requires a value when FIELD1 = 'Y' on TOGGLE and SAVE.
    Problem with this approach is that even though during TOGGLE event user is provided with an informational message, if the user directly decides to SAVE (no change for TOGGLE event), in this case the same message is displayed, and the project screen itself is closed. I do not think it would be ideal for the user to see the entire project close on SAVE everytime they miss a conditionally required field.
    I am just not sure at this point how to handle this at SAVE so that I can still have the same control as I would when TOGGLE event is triggered.
    Experts please help if you have come across such a situation!!! Your insight would be greatly appreciated!
    Edited by: akkinair on Dec 16, 2011 1:25 AM

    Please find below the response.
    1. Assign a screen group to FIELD2 and FIELD3. If FIELD1 = 'Y' then LOOP AT SCREEN, and set screen-required = 1 for that specific screen group.
    Problem with this approach is that, if I select FIELD1 = 'Y' (hit space or enter -> sy-ucomm = TOGGLE), the fields are successfully set to required. However, now if at this point I go and change value for FIELD1 = 'X' (hit space or enter), FIELD2 and FIELD3 still remain set to required, and keep requesting value.
    --> When FIELD1 chnage used module with additon CHAIN-REQUEST and check its value if it is to be set to optional by using loop at screen and set screen-required =0.*_
    2. Do not set any fields to required. Instead set it to an information message in PAI, informing user that this field requires a value when FIELD1 = 'Y' on TOGGLE and SAVE.
    Problem with this approach is that even though during TOGGLE event user is provided with an informational message, if the user directly decides to SAVE (no change for TOGGLE event), in this case the same message is displayed, and the project screen itself is closed. I do not think it would be ideal for the user to see the entire project close on SAVE everytime they miss a conditionally required field.
    --> Can you please clarify it.
    Thanks
    Nabehet

  • VPRS condition in export pricing procedure

    Hi All,
    I have done the configuration for export sale scenario. I created a complete cycle from sales to Billing and documents are getting created.
    As there was no VPRS condition in standard pricing procedure for exports (JINEXPO), i have not included in my Pricing procedure. Pl note no "CIN" is introduced in our project.
    My doubt is why "VPRS" is not included in the std pricing proced, and how cost will be captured in the export sale?
    Regards
    Anand.M

    Hi,
    please reff this link.
    http://sapsdforum.com/2007/10/23/pricing-in-sd-in-great-detail

  • VPRS Condition amount varies in third party scenario.

    Hi,
    We all know that COST (VPRS condition value) in Invoice is fetched from MIRO in case of Third party sales scenario.
    When we have 2 quantity in PO for a particular item, I have completed the MIRO(Vendor Invoicing) & VF01 (Customer Invoicing) for 1 quantity. Then the cost was reflecting in the document.
    When I have created a new MIRO for the second quantity and cancelled the MIRO, system is updating the VPRS amount in already saved customer invoice to the extent of tax amount in the cancelled MIRO.
    For Example:
    PO Quantity - 2 for the material 'MAT12'
    1st MIRO - Amount - 816000(incl of tax 16000)
    Customer Invoice '123'- Cost (VPRS): 816000 (Initially shown)
    2nd MIRO - Amount 816000(Incl of tax 16000)
    And Cancelled this MIRO.
    After cancelling, Customer Invoice '123' - Cost(VPRS) is 832000 (Got updated to the extent of tax amount in the cancelled MIRO).
    CAN ANYONE PLS EXPLAIN WHY THIS UPDATION IN THE COST.
    THANKS.
    Guru

    Good Morning,
    For complete details on the behaviour of VPRS, please refer to the OSS Note 547570 (I have copied the relevant information below):
    FAQ: VPRS in pricing
    1.  How is the cost determined in pricing?
        In the order, the cost is generally taken from the valuation segment
        of the material master. In the billing document, however, it may
        have other sources. Depending on the business transaction, the costs
        can be taken from the goods issue of the billed delivery or, in the
        case of a third-party order processing or individual purchase order,
        from the respective purchase order, the goods receipt or the invoice
        verification in purchasing. As an example, only the goods issue will
        be mentioned here. However, the descriptions also apply to costs
        from purchase orders, goods receipts or invoice verifications. For
        details, refer to Notes 372760 and 547590. These costs are entered
        externally in pricing and included in the value of the VPRS
        condition. The amount is obtained by calculating back amount = value
        / quantity.
    4. How can I recognize how the cost was determined?
        Go to the detail display of the VPRS condition. If the condition
        control (KSTEU) is set to 'H', the cost was taken from the goods
        issue. If it set to 'A', it was redetermined from the valuation
        segment of the material master, in case of 'D' or 'E' it was copied
        from the preceding document.
    7. Why is my VPRS not zero although my goods issue had value zero?
        For technical reasons, it is not possible within pricing to
        differentiate whether a goods issue with value zero exists or
        whether no goods issue exists. For this reason, in both cases the
        costs are determined from the valuation segment of the material
        master. In this context, also refer to Note 84229.
    Here is some more useful documentation on VPRS.
    u2022Configure VPRS with condition category G, S, or T
    u2022Condition category G: the condition type VPRS goes into the valuation
    segment of the material master and determines from here the standard
    or
    average price (based upon Price Control flag set in transaction MM03)
    in the sales document.
    In the billing document the value is determined from the post goods
    issue document.  When the post goods value = 0 the VPRS will be pulled
    from the material valuation segment.
    Regards,
    Martina McElwain
    SD - Forum Moderator

  • Error with VPRS condition type in Quotation

    Hi,
    When go through the pricing conditions of my quotations, I see a red signal indicating error before the VPRS Condition type (Condition category G). When i do the condiotn analysis, the diagnosis read as below.
    "Error in quantity / value updation"
    Diagnosis:
    This condition has not been determined using condition records. The amount or value should be determined from another data source. For cost (condition category 'G') it is read using conditions from the material valuation segment, for a cash discount condition it is read using conditions from the terms of payment table.
    In this transaction an error occurs - the material valuation segment or the terms of payment table could not be read or a currency translation has failed.
    System Response
    The condition has been provided with the deactivated indicator 'X'.
    Could you please let me know what could be causing this?
    regards,
    Ashok

    Hi Ashok,
    Your problem seems intresting, may be this thread can help you
    [SCN|VPRS- Error in quantity/value determination]
    Please provide feedback after getting it solved.
    Thanks,
    Raja

Maybe you are looking for