Skip to Content
avatar image
Former Member

Condition type EK01 missing in pricing procedure A V (error message V1206)

Hi gurus,

We get error message "condition type EK01 missing in pricing procedure A V" when creating a Billing request from a SErvice Order through TX-DP90.

We reviewed customizing regarding this issue:

ODP4 - SD Document linked to condition EK01 (this condition shall bring the actual cost in the order)

ODP1 - Dinamyc item profile to create Billing Request.

Pricing procedure: sales area assignments, condition types (including EK01)

....

but error still shows.

Any idea what additional setting is necessary in customizing so EK01 is transfered to the SD doc in DP90?

Thanks,

VL

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Dec 07, 2010 at 04:47 AM

    You may be aware EK01 is predominently used in Make To Order scenario and DP90 is resourse related billing and I dont know why you consider EK01.

    If you want to know the configuration details of Resourse related Down Payment, have a look at note 858703

    thanks

    G. Lakshmipathi

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 07, 2010 at 08:05 AM

    Hi Lakshmipathi,

    Thanks for your answer.

    I have taken a look to note you mentioned but it is related to Resource Related Down Payments customizing, which is not our actual requirement.

    The note mentions though condition type EK01 for the purpose I am commenting: "...when the system processes a final invoice date, it determines condition type EK01 as the active price condition, thereby billing the actual costs".

    Condition Type is in our pricing procedure with all the usual SD customizing settings, why is the system unable to process the costs?

    Thanks for your always great help,

    VL

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 09, 2010 at 03:48 AM

    Hi Victor,

    Apart from maintaining the condition type EK01 in ODP4 the same condition type needs to be there in the pricing procedure determined during the debit memo request creation. Please check the pricing procedure determined during the service request creation by going to the Header Level & then go to T.Code V/08 to confirm whether EK01 is there or not.

    Br

    Dammi

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 09, 2010 at 04:18 PM

    Thanks dammi for your answer.

    Conditio type EK01 is maintained in pricing procedure.

    We are investigating why when we post costs against the order through IW41, real costs do show in the service order but no CO document is created. This might be reason why cost is not filling condition type EK01 and we are getting the error message.

    Thanks and best regards,

    Víctor Liedo

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Victor,

      could you please check if any custom requirement routine has been assigned to EK01 in the pricing procedure ?

      If so please ensure that KOBEV_nnn form just checks KOMK fields. See the SAP note 156230.

      Best regards,

      Ivano.