Skip to Content
author's profile photo Former Member
Former Member

Pricing Error

Hi SD Experts,

During sales order i receive this message "Pricing Error: Mandatory condition EK01/VPRS is missing"

So i tried creating condition record for these 2 condition types through t.code VK11, but error prompt no access sequences for condition type EK01/VPRS

What are the necessary steps need to be taken to get my EK01 & VPRS works in my Sales Order?

Please advise. Thanks!

Add a comment
10|10000 characters needed characters exceeded

Related questions

7 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2008 at 05:56 AM

    Hi,

    Ek01 and VPRS condition types are for costing of materials.

    So condition record cant be created for it.

    Instead maintain the std or moving Avg price in Material master record based on the functionality.

    So the price maintained in material master record is considered as cost and value is fetched into the sales order to calculate the profit.

    regards,

    vimal

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2008 at 06:07 AM

    Hi LEE,

    As you said EK01/ VPRS are two condition types which do not have access sequence. You cannot maintain condition record for these two condition types. In Pricing procedure attach a routine NO 4 against your condition type VPRS. This routine fetches your cost price from the materisl master accounting 1 tab. So attach a routine 4 in your pricing procedure and check out your requirement.

    regards

    prasad

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2008 at 06:11 AM

    NO 1

    in the customer master record specifies the customer pricing procedure has 1.

    NO 2

    GO TO /NOVKK GO TO NEW ENTRIES AND ASSIGN THE PRICING PROCEDURE RVAA01 TO THE COMBINATION OF SALES ORG,DIS CHANNEL,DIVISION,DOC PRO(A),CUSTOMER PRO(1).

    SEND ME THE RESULT, IS IT SOLVE OR NOT.

    OK BYE

    SREE

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2008 at 06:24 AM

    Hi Lee,

    go to transaction code OVKK and go to your pricing procedure and to the condition types EK01 and VPRS you will find the tick mark on the mandatory field just un tick it .

    your problem will be resloved

    Regards,

    Murali

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2008 at 06:32 AM

    EK01 and VPRS are Cost Condition. It is recommended not to maintain them as Mandatory Condition Type in Pricing Procedure.

    VPRS condition value is picked from material master, based on value maintained in Accounting Tab Page in Material Master.

    Regards,

    Rajesh Banka

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 12, 2008 at 07:10 AM

    Hi Yeow...

    I don't think that EK01 and VPRS should be made mandatory for your pricing procedure... If you got no reasons to maintain them as mandatory conditions please go to V/08 and remove the check for "Man" , so that it will not be a mandatory condtion.

    However, If you want this contions to be mandtory , as these condtions don't have any access sequence go to material master and in "Accounting 1" view enter the standard price and also the Price control field as "S"

    Hope you find this informative..

    Thanks,

    Safeer Rahman

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2008 at 07:40 AM

    Hello,

    you will get the pricing error because the flag 'mandantory' is set in the pricing procedure (transaction V/08).

    That means that the conditions should be determine in the document.

    VPRS

    The VPRS is the cost of the material. This will be maintain in the material masta data Condition type configuration:

    Configure cost condition (VPRS) with condition type G,S or T (this will trigger special logic)

    Condition category G: the VPRS goes into the valuation segment of the material master and determines the standard or average price (based upon Price Control flag set in transaction MM03) in the sales document.

    In billing the value is determined from the post goods issue document (see later). When the post goods value = 0 the VPRS will be pulled from the material valuation segment.

    Condition category S always accesses the standard price independent of the document type

    Condition category T always accesses the moving average price independent of the document type

    No access sequence should be set

    EK01

    1. General

    The unit cost estimate is the planned cost of goods manufactured for the material to be sold. The estimate is calculated based on the materials you intend to use, the services you intend to carry out, and additional costs such as shipping and insurance. In addition, you can use cost items to calculate overhead surcharges. The unit cost estimate is calculated in Controlling (CO-PC). The cost estimate is then copied into the sales document and can be used for pricing or for calculating the profit margin.

    Condition type Name Use

    EK01 Individual Determination Used as basis for pricing

    EK02 Unit cost estimate u2013 statistical Used to calculate profit margin

    The condition type EK01 can be used as a basis for pricing a make-to-order item in a sales document. The system calculates the cost of manufacturing and copies the result as an EK01 condition type into the pricing screen of the sales document.

    You can use the condition type EK02 to calculate the profit margin of a make-to-order item in a sales document. The system calculates the cost of manufacturing and copies the result as an EK02 condition type into the pricing screen of the sales document. The EK02 has no direct effect on pricing.

    2. Settings in Customizing

    Condition type configuration (for both EK01 and EK02)

    u2022 Basic configuration:

    Condition class [KOAID] B Prices

    Calculation type [KRECH] C Quantity

    Condition category [KNTYP] Q Costing

    u2022 No access sequence

    u2022 EK01/EK02 can only use as item condition. Group condition flag should not be set.

    Pricing Procedure Configuration

    u2022 EK01 and EK02 should be checked as manual in the pricing procedure since their value is not derived from SD condition records.

    u2022 EK02 must be set as Statistical in the pricing procedure.

    u2022 Subtotal value u201CBu201D should be assigned to the EK02 condition.

    See note 155212 and online documentation for additional details.

    I hope that the information are helpful.

    regards

    Claudia

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.