EDI1 Condition type not determined automaitcally in ORDERS process

Hi Experts,
         We are in the process of creating the Sales order by receiving EDI data from customer and converting in to IDOC format and trying to create the sales order. While executing the ORDERS IDOC message type sales order is getting created successfully. But Condition type EDI1 is not getting activated even after maintaining the value in E1EDP01-VPREI.
                   During foreground mode, if we maintain the EDI1 condition type manually then, its accepting without any issue. But during IDOC process its not getting added automatically.
Please give your suggestion on this.
Warm Regards,
Nag

Problem with the IDOC FM. We identified and rectified the issue. Thank u

Similar Messages

  • Condition type not determine in sales order

    I have condition record maintained for the condition type as per the order reason. When I create the sales order system is not reading the condition record so no condition type is getting determined. Pricing date from the sales order is within the validity period of condition record.Parmeters are also matching but still in the sales order condition type is not getting determine.
    Thanx
    PNU

    In that case, do update of pricing.
    To do that, Sales Order - Item data - Condition Tab - Click Update button and choose option B - Carry out new pricing.
    To know who manually remove this.
    Choose Enviroment from menu bar in sales order - choose Change for display of change in the doc.
    Regards
    JP

  • ORDERS Inbound EDI1 Condition type not getting updated

    Hi Experts,
            As per the client requirement, during ORDERS Inbound process we need to capture the "Customer expected Price" in EDI1 Condition type in the sales order. So we maintained the details in the E1EDP01 in field VPREI.
    But during ORDERS Inbound process this EDI1 field is not getting updated. Can anyone please help us on this.
    Warm Regards,
    VEL

    Problem of our ABAP coding distrubed the std functionality. In std SAP, this functionality will work without any issue.

  • Condition type not coming in sales order

    Hi,
    we have a condition type Z026. The issue is that  it is not set in the order but the condition records exists. The pricing analysis shows that condition reocrd is missing but the fact is the condition record is there. The acess seq is Z026 and there are many tables in the acess sequence.
    The first table in the access seq is 906 and the condition record exists but still the system says that the condition record is not found using  cond preliminary step (header fields like customer/sales org/div). the cond record is maintained for  relevant sales org/dist channel/customer/material. cond preliminary step means that system first looks for the header fields but everything is there.
    The condition is active and the conditon is created on 21.7.10 with validitity from 21.7.10 to 31.1.2010 and the pricing date in sales order is 27.7.10. so everyhting is fine but yet the condition is not coming in sales order
    what could be the issue.
    regds

    Hi,
    Now try creating a sales order with 20.07.2010 as the pricing date. It will work. Create another order with 21.07.2010 and it will not work. If so, it is due to the validity date. When you give 21.07.2010 as validity date and there is already another record which was valid on that date, the gap of one day can happen and we have experienced this. There is even an OSS note explaining this concept, which makes sense business-wise.
    However you check the scenarios I have mentioned. If the behaviour is as I have mentioned, then you have to change the pricing date of your problamatic sales order to one day earlier, or move the validity date one day earlier.
    If the behaviour is different, pls lemme know

  • Condition type not determined

    Hello All,
    I am using COPY CONTROL to create contract through VA41.
    Problem i am facing is condition type not getting picked up at item level, though correct pricing procedure is getting determined. In that pricing procedure this condtion type is maintained but still it is not picking the condition type.
    Rushikesh

    Hi,
    Can you check condition type detailed screen"Manual entries" field,the value in that field is either B or D.
    Regards,
    Chandra

  • Discount condition type not appearing in sales order but in invoice

    Hi,
    I have two discount condition types (MPDI,ZSDI) in my pricing procedure,at the time of sales order creation one discount condition is not appearing.
    On analyzing the condition type MPDI,system throws message "Access not been executed due to previous access",what would be the reason.
    In the billing ,i could see the condition type appearing.I have checked this,but i could not understand why it is happening.Even the condition catergory of condition is empty not L.
    Also please find the screen shots below,
    Pradeep

    Pradeep,
    Am sure user might have deleted the condition type in sales order, the same condition type woudl have entered manually in invoice.
    Please check my testing, i have done the same entered ZA09 manually and after saving have deleted again in sales order, after dilivery and when i created invoice here i have entered manually the same condition type.
    So in your case also the same thing could have happend, check the change log and also in invoce condtion tab check the condtion type in analysis ( Invoice analysis not order). so that you can udnerstand whether it was entered manully or not.
    On analyzing the condition type MPDI,system throws message "Access not been executed due to previous access",what would be the reason.
    This is because in the condtion tyoe the abvoe key combiantion was found with records hence the below key combition was ignored. this you observe in your screen shot with with 5.00
    So my guess is the condtion records was deleted in sales order.
    thanks,
    srinu.

  • EDI1 Condition Type - Not picking up Net Value - Document Incomplete

    Hi EDI Gurus,
    I have a quick question.
    I am processing an EDI Sales Order through Inbound Orders IDoc.
    When an IDoc is triggered, the EDI1 pricing condition is getting the customer expected proce from E1EDP01-VPREI. But it says document incomplete.
    Complete Data:
    Item 000010: Net Value missing
    Why I am i getting this??  What should be done?? Where??
    I also heard that we can make the order block, if EDI1 price is different from PR00 price. How to place delivery block?
    Can you please explain.
    Thanks.
    Matt

    I figured out the problem. the price for the material was not maintained in the PR00 pricing condition.
    The EDI1 condition was OK.
    Now , i have a question regarding the comparison between, standard SAP price (PR00) and customer expected price (EDI1).
    Where do we do the comparison. If cust expected price is not acceptable how we gonna put a delivery block.
    Do i have to implement this in Inbound Orders user exit or should I implement this elsewhere??
    Who is the owner of this process EDI or SD??
    Thanks,
    Matt

  • Tax Conditions types not appearing in CRM orders and quotations

    Hello All,
    I have created a new tax condition type in ECC and through initial load replicate the same to CRM. pricing procedure repliction with new tax condition is also successful.
    But, the new tax condition is not appearing in condition tab at item level when i create quotation in CRM. other condition types are coming. data for this condition type is there in custom condition table. mapping of tax classifiction to tax group is also done in SPRO.
    Please advise.
    THank and Regards
    Sudhir Grover

    Hello Sudhir,
    You should check the trace log for pricing at first. Set the user parameter:PRC_TRACE as 'X' on T-cd:SU01 for your user and check the Access analysis on the condition tab.
    Regards,
    Masayuki

  • Output type not determined in Sales Order

    Hello Friends,
    I am facing a problem.
    I have maintained the O/P condition record for O/P type for order confirmation.
    While creating sales order, in the determination analysis for O/P , it shows as O/P found, but the same is not added in the sales Order outputs.
    Can somebody advise me what is missing ?
    Regards

    Harsh Mathur ,
    1. You need to maintain Condition records in VV11 for BA00 (Key combination - order type)
    2. If already created Check whether the records are existing through VV12
    3. If yes, then enter into your sales order in VA02 Mode
    4. Check Extras --> Output --> Header --> Edit
    If status is yellow or green then it is ok. Output = BA00, Medium = Print output, Function = SP
    Then Choose the line and click "Communication Method" Enter Logical destination - LP01 and activate the indicator against "Print Immediately"
    Click Back button --> Click "Further Data"
    Under "Requested Processing" header
    Dispatch time = Choose the option accordingly
    save it.
    Then counter check the config by running sales transaction without saving check
    Check Extras --> Output --> Header --> Print Preview
    if the output is shown then you have succeded
    Regards
    Sathya

  • Condition type not appearing in Sales order

    Hi All,
    Iam using TAXINN, Copied ZINFAC to KINFAC,
    I have created JIVP and JIVC for VAT and CST,
    I have maintained Condition Records for JIVP and JIVC.
    Both these condition records are not reflecting in my sales order, i.e. the records are not coming.
    Please help me in this regard
    Siva Narayana.B

    hi,
    please check if the condition records are mentioned for the key combination matching the sales order. ie if the condition records are maintained for the required combinations. Then check if the correct tax codes are maintained in the condition record and properly determined at FTXP.
    Thanks
    Sadhu Kishore

  • VA00 condition type not getting determined for the returns order

    Hi All,
    I have a case where VA00 condition type not getting determined for the returns order that has been created with respect to the billing document.
    When the pricing conditions are being copied from invoice it is getting copied but later it is getting deleted in the include LV61AA42.
    Note:VA00 condition type is getting deleted from the  internal table tkomv[].
    If any one came across  this scenario can you please help me.
    Request your valuable inputs

    Hi,
    Please check the copy control setting in VTAA.
    Maintain the pricing type as "D" at item category level for the respective document type .
    Hope this will resolve your issue.
    Regards,
    Krishna O

  • Condition type not flown(not determined) into the sales order

    Hello Experts,
    There is one discount condition type which is having proper condition records, validity date.However, it is not getting determined properly and is not flown into the sales order. the user wants to know why this may happen.I tried to reason it may be the sales order date and the conditon record date may be different or the condition record is changed after the creation of the sales order.neither of the reasons seem to hold good. any ideas?
    Regards,
    Raj

    Hello,
    I have looked into the analysis and asked him to update the condition by clicking on that.also, I found that the condition record is having a proper valid date. now the user would update only after knowing the exact reason why it did not flow into the sales order,he knows he has to update the condition but would not do so till he knows the right reason why condition is not determined in the sales order. now this is the situation.
    the probable reasons as per analysis of the conditon type are as follows(for your information). can it be one ofThere are different reasons for this:
    1)The condition was deleted manually in the item condition screen.
    2)The condition record was created later. Please note that order processing and pricing have buffer mechanisms. This means that a newly added condition record might only be found after order processing has been left completely and then started again.  them?
    Regards,
    Raj.

  • Urgent:pricing condition not determined in sales order

    HI,
    i have defined a pricing condition for a material . when i am creating a sales order the pricing condition is not determined;

    hi
    You must have done all the pricing related settings like access sequence, determination, condition type. Please cross check them once again. Also see if the condition record is picked up properly , is it bypassing ?
    If every thing is fine, check the item category of that material and see if in business data of that item category Pricing is activated !!
    regards
    swapnil

  • Condition type not picked in Inquiry but picked up in order

    Hi Guys,
    We have a problem where a pricing condition type is picked up in order but it is not picked up in quotation/inquiry. So we have the price difference for the material. Points will be awarded.
    Can you guys please help?
    Thanks
    Venky

    Hi venky
    generally in Inquiry pricing is not at all required.
    but in quotation it may require sometimes. but when you create an order with reference to quotation , the price varies, this is because of the  pricing type .
    check the pricing type in VTAA quotation, the pricing type will be different for sales order and for quotation.
    Regards
    Srinath

  • Pricing Error- Condition type not found.

    Hi Gurus,
    I have a issue with pricing.
    Scenario :
    For a pricing procedure i have 3 condition types ;
    For example :
    ZXED, ZXE1 & ZXE2.
    Of these ZXED is Manual, Mandatory & Statistical in nature.
    ZXE1 & ZXE2 are Manual.
    When i create a sales order my pricing procedure is getting determined correctly.
    The issue comes in when i try to key in the values at the item level condition in the sales order:
    If i see the options(F4) available for me to select the condition types i get have see only one condition type i.e ZXE1. but esentially i should get to see all the 3 condition types as an choice of code(condition type).
    Can any one help me to find out the possible reason why i get to have only one condition type for selection.
    Your suggestion is highly appreciable.
    Rgd
    VIVEK.

    Hi,
    1. Understand onething that a particular condition type if maintained "mandatory" in the pricing procedure then you will have to create the condition record for it using transaction code <b>"VK11"</b>. If it is manual then you can give the rate directly in the sales order after selecting it. Since you have maintained <b>"manual", "mandatory" & "statistical"</b> for the condition type <b>"ZXED"</b> at the same time that is why the system is giving you the error <b>"Pricing error" Mandatory condition ZXED is missing."</b>
    2. Also you want the system to show you all threee condition types <b>"ZXED', "ZXE1", "ZXE2"</b> to choose manually as per your requirement. Do one thing go to transaction code <b>"V/06"</b> - select the required condition type say <b>"ZXED"</b> - double click on it - in the <b>"changes which can be made"</b> section you will see a field for <b>"Manual entries"</b> - in this select <b>"no limitations"</b> and save the <b>condition type</b>. Similarly do it for the other 2 condition types and save it.
    <b>I tell you</b> you must have maintained there <b>"D-not possible to process manually"</b>. If this is maintained then the system will never show you the condition type to choose from the condition type list in the sales order.
    Note: You have maintained for <b>"ZXED"</b> manual/mandatory/statistical. Now as it is mandatory also you have to maintain the condition record for it in <b>"VK11"</b>. Now if you change the rate of this condition type in the sales order then when you will create the invoice in <b>"VF01"</b> the system will show that value only which has been maintained using <b>"VK11"</b> because in billing also the system fetches the condition record from <b>VK11</b> for the mandatory conditions.
    Hope this clarifies and solves your doubt.
    Reward points if solution helps.
    Regards,
    Allabaqsh G. Patil

Maybe you are looking for