Manual price condition item for the Idoc IDOC_INPUT_ORDERS

Hello,
I need to inform the item manual price using the function module for IDOCs IDOC_INPUT_ORDERS. I am trying by the segment E1EDP05, field Price, but it doesn´t work properly.
Thanks in advance
Regards

Manuel,
Merely putting the 'price' into a segment-field won't result in good result. You will need to (potentially)populate a few more fields to tell SAP what you want changed. Here is an example, I have a Condition Type called 'Z123' which is a manual condition record. It has been defined as a 'dollar-off' based discount (as opposed to a percentage etc). If I want to push through a discount of, say, $1.00 per unit then I will be populating the following fields within E1EDP05:
KSCHL - 'Z123'
KRATE - '2.21'
MEAUN - 'EA'
KOEIN - 'NZD'
Try that and see how you get on. Also check your EDI config around the handling of Messages for Inbound Orders.
Here's another hint... Simulate what you want to achieve by creating a sales order manually on the system with the relevant condition types populated and then trigger an outbound IDoc. Take a look at the E1EDP05 segment of the outbound IDoc and it will effectively tell you what you need to populate and where to populate it.
Since I'm on a roll and feeling altruistic, here's another hint for you... Use WE19 and use the 'Inbound function module' icon and from the dialogue box select the 'Process in the Foreground'. As this function module is effectively a dirty old BDC wrapped around a SAP standard FM, you can step through it and see how it is behaving...
If you are still having problems, let me know, and I will help you out as much as I can.
Cheers,
Paul...

Similar Messages

  • How to maintain price condition record for the following senario

    Hi Gurus,
    I have a scenario where storage charges can apply either per cbm or per sq.mt or  per day.
    for a single customer.
    Another situation --- Handling in Palletized charges per cbm or per pallet for a single customer
    can somebody help me on this.
    Thanks,
    RR

    Hi,
    Scenario 1:
    Go to VK11 tcode and Enter your KAD1 COndition Type.
    Now maintain the Condition Record for your Customer.
    Scenario 2:
    Go to VK11 tcode and Enter your KP00 COndition Type.
    Now maintain the Condition Record for your Customer.
    Note for Scnario 2: Please make sure for KP00, the field Plus/minus in Condition Type setting should be "A"  i.e the Surcharge. It is because the same condition Type can be used for Discount as well as for Surcharge.
    The condition Type setting for KP00 can be done by going to V/06 tcode
    Regards

  • Not possible to determine a condition type for the price in ME49

    Hi,
    While saving the price in ME49 i.e. comparision of Quotation i am getting below error:
    Not possible to determine a condition type for the price
    Message no. 06657
    Diagnosis
    When it attempted to generate the time-dependent conditions for the price you entered, the system was unable to determine a condition type. Price determination is therefore not possible.
    Procedure
    Contact your system administrator.
    The latter can maintain the calculation schema assigned to the purchasing document using the Implementation Guide (IMG).
    Utsav

    Hi Utsav,
    You can refer to the following link. it might be useful to you
    RFQ price
    Thanks
    Nisha

  • Missing items in the IDoc for the delivery

    Hi to all,
    Sorry if not posting in the right forum.
    In my customer's scenario, an IDoc is created against a delivery (via the delivery output), and sent via ALE to a distant warehouse system, for picking and GI posting (basic type SHPMNT03).
    For some times, the IDoc created against deliveries including BOMs is missing the main item of the BOM (though the BOM main item is in the delivery).
    Consequently, the integration in the distant system is failing, because the higher-level item referenced in the BOM sub-items is missing.
    Surprisingly, re-triggering the delivery output does re-generate a complete IDoc, where the segment for the main item is back.
    I looked almost everywhere, did many searches in OSS (on SHPMNT03, on HIPOS, on E1ELD24 - segment name in the IDoc -, on "Missing items in the IDoc for the delivery", etc...), I even simply googled the web, but I can't even figure out what is the cause for this (I imagined it could be caused by a missing commit in the program generating the IDoc, but don't know whether this make sense).
    Any help would be highly appreciated.
    Thanks in advance and best regards
    Yan
    Edited by: Yan Loiseau on Jul 8, 2010 12:52 PM
    Edited by: Yan Loiseau on Jul 8, 2010 12:56 PM

    Hello Yan
    Jelena is right, you are better off taking it up with SAP. I also did not find any relevant OSS notes.
    However the issue, according to my reading, is in the following areas:
    1) LV56KF05: INCLUDE LV56KF62 .  " FILL_E1EDL24"
    This fills the EIEDL24 segment, may be the main item is filled  initially and overwritten later.
    2) Function Module: IDOC_OUTPUT_DELVRY
    You can look at the following OSS notes (though not fully relevant)  for some clues:
    810981 - Reference data missing in DESADV IDoc from decentralized WMS
    537470 - BOM + batch split in decentralized WMS, confirmation fails
    752921 - VL563: Higher-level item does not exist
    705086 - Higher-level item does not refer to existing item
    Hope this helps. Good luck.

  • Manual price condition (%) in order creation (using ABAP)

    Dear community members,
    I could use some help on a problem I have encountered while creating a sales order (in the CRM system) using ABAP programming, the details are given hereunder:
    I have two manual price conditions used to set a possible discount, one using a straight value and one using a percentage:
    1. When the order is generated using the value (let us say 100€) it cointains the correct price condition.
    2. On the other hand, when the order is generated using percentages (i.e. 10%), it is created without explicit errors or warnings but with no price condition in it.
    For the latter case I have checked the IPC logs (from transaction SM53) finding this error message:
    Message: Condition cannot be processed manually
    --> com.sap.spe.pricing.transactiondata.exc.ManualChangeNotAllowedException: Condition YSCP cannot be processed manually
    at com.sap.spe.pricing.transactiondata.impl.PricingCondition.changeConditionRate(Ljava/math/BigDecimal;Ljava/lang/String;Ljava/math/BigDecimal;Ljava/lang/String;)V(PricingCondition.java:3124)
    at com.sap.spe.pricing.transactiondata.impl.HeaderCondition.changeConditionRate(Ljava/math/BigDecimal;Ljava/lang/String;Ljava/math/BigDecimal;Ljava/lang/String;)V(HeaderCondition.java:387)
    at com.sap.spe.pricing.transactiondata.impl.PricingDocument.addHeaderCondition(Ljava/lang/String;Ljava/math/BigDecimal;Ljava/lang/String;Ljava/math/BigDecimal;Ljava/lang/String;C)Lcom/sap/spe/pricing/transactiondata/IHeaderCondition;(PricingDocument.java :1472)
    at com.sap.spe.document.rfc.AddPricingConditions.handleDocRequest()V(AddPricingConditions.java:131)
    at com.sap.spe.document.rfc.DocHandlerAdapter.handleRequest()V(DocHandlerAdapter.java:72)
    at com.sap.spe.base.util.jco.HandlerAdapter.handleRequest(Lcom/sap/vmc/RFCContainer/Call;)V(HandlerAdapter.java:117)
    at com.sap.vmc.remserver.RFCDispatcher.handleRequest2(Lcom/sap/conn/jco/JCoFunction;)V(RFCDispatcher.java:995)
    at com.sap.vmc.remserver.RFCDispatcher.handleRequest(Lcom/sap/conn/jco/JCoFunction;)V(RFCDispatcher.java:746)
    at com.sap.conn.jco.rt.VMCServer.dispatchRequest(Lcom/sap/conn/jco/JCoFunction;)V(VMCServer.java:911)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(Lcom/sap/conn/jco/rt/ServerWorker;Ljava/lang/String;)V(MiddlewareJavaRfc.java:3415)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(Lcom/sap/conn/jco/rt/ServerWorker;)V(MiddlewareJavaRfc.java:2468)
    at com.sap.conn.jco.rt.VMCServer.listen()V(VMCServer.java:766)
    at com.sap.conn.jco.rt.VMCServer.run()V(VMCServer.java:689)
    at com.sap.vmc.remserver.RfcServer.run()V(RfcServer.java:376)
    at java.lang.Thread.startup(Z)V(Thread.java:1954)
    I have already debugged FM CRM_ORDER_MAINTAIN but to no avail, maybe I just missed something and I can assure that the customizing is correct and aligned between the systems and both the conditions are set to be processed manually.
    At this point, since the condition is applied when the commit is yet to be done I wonder whether it is possible to apply a discount percentage on prices which are yet to be generated, it would be illogical to do so and then again while using a straight value (which does not require a calculation) the order is correctly generated.
    Furthermore when I add the conditions in an order (from both the GUI and the WUI) the table IT_PRIDOC is alway empty, even if CT_INPUT_FIELD is populated.
    I know that there are similar posts here in SCN but sadly I was not able to find a solution so any help would be greatly appreciated.
    Thanks in advance for any replies given,
    Alessandro.

    Dear Padma,
    apologies for my late reply. I also thought it should be possible to use a percentage but I was not sure.
    Sadly the debugging did not bring about any positive result.
    I also tried to make a second CRM_ORDER_MAINTAIN call after the system generated all the pricing conditions but that also did not work.
    There is one thing that caught my attention though:
    - YSCV (fixed amount): still no problem at all (passed to KBETR);
    - YSCP (percent): if I assign a value to KWERT or if I leave all the fields empty, the condition is created in the sales order but it is always set to 0%. However, if I try to assign it to KBETR, I always get the message: "Condition YSCP cannot be processed manually".
    I made some attempts with the customizing, for example adding the condition to the "easy entries" or playing with the options of "Create Condition Types" (always aligning the systems) without getting positive output.
    I am beginning to think that it could be an IPC-related problem (which is not my area of expertise... yet).
    Alessandro.

  • Vistex IP Module - manual price conditions get replaced

    Hi all,
    We are experiencing strange behavior in Vistex Rebate Claim Requests. While processing claims, occasionally all the item level manual price conditions will get changed and replaced with the condition values from a completely different claim! We have been unable to isolate a set of common factors that causes this so we cannot discover the root cause.
    What we find is that after this happens, the Status Manual Price Indicator (field MPROK) changes from A to blank.
    We have submitted an OSS message to Vistex Support but they cannot find what the problem is.
    Does anyone have any ideas?
    Thanks & regards to all

    From my experience, when problems like this occur, there is always a pattern, but sometimes it's just difficult to see. Some issues took months to finally catch and explain, but everything has a reason.
    You said that conditions are getting replaced with the ones on a different claim. What is that claim? What does it have in common with the other claim? Are their numbers close and are they being processed in the same run?
    Also check in all the code that when reading line-level tables (e.g. XVBRP and such) the full key, including document number (VBELN) is being used to pull the data.
    Do you create documents in the background? There might be multiple threads/instances of the same program running at the same time and data that's stored in memoty could get mixed-up between them. True story - once I was debugging a sales order creation and in ABAP debugger under user ID (ERNAM) I saw not my name but another user doing testing at the same time. If you have a background run, it sometimes helps if you sort of make it slower, e.g. by running in batches or in a single process.
    What else is going on in the system at the same time that could influence the claim creation?
    If possible, try setting up some "traps" along the way - add some sort of a log or additional messages to see what exactly is going on at what time. The obvious thing to track would be when Manual Price Indicator is changing the value.

  • VA01 user exit to manually insert condition record for sales order

    Hello Experts,
    I have a req. to find a user exit through which I can insert a new condition record for a sales order everytime a sales order is created.
    Whenever a sales order is created I should check whether condition types X and Y are being generated for the particular sales order.If yes I have to insert a new condition record with type Z for that sales order after some calculations.
    Does anybody have an idea which user exit should be used so that my new condition comes up in the CONDITIONS tab for the sales order item.
    Thanks in anticipation.
    Vipul

    Hi,
    What I suggest is suppose you want condition type say 'XXX' to appear with some calculated value only when condition type 'X' & 'Y' are present, then let the consultant define that condition type in pricing procedure, with 'Manual Entry not allowd flag on, so that nobody can overwrite the value calculated by your routine in condition type 'XXX'  & let him 'attach; a routine say 901 to it. Now via VOFM in routine 901 you can put your logic. In routine 901 you can loop at xkomv & check if both condition types viz. 'X' & 'Y' are present. IF yes then calculate the value of condition type 'XXX' as per the logic required & pass it on to SAP by xkomv-kwert = w_amount, where w_amount is the value calculated by you as per the logic required.
    I hope this helps,
    Regards
    Raju Chitale

  • No commit item for the item

    hi,
    when i am creating purchase order against accoount assingnment group "K".
    i am getting an issue that it is saying
    "no commit item for the item 10 and the company code 1000'
    if i double click it
    it is saying that no cash maangement, funds maangement is actived for the g/l account.
    thanx in advance
    regards,
    balajit

    no cash maangement, funds maangement is actived
    Not sure but make a try as follows:-
    A separate number range is required for posting plan line items failing which, you will have this issue.
    Do the following:-
    1) Go to IMG Financial Supply Chain Management --> Cash and Liquidity Management --> Cash Management --> Structuring --> Manual Planning --> Define Number Ranges
    2) On the Cash Management and Forecast Number Ranges screen enter 1000 in the Company Code field.
    3) Choose the Change Intervals push button
    4) On the "Maintain Number Range Intervals" screen choose the Insert interval button and maintain the number range.
    5) Next go to IMG Path Financial Accounting (New) --> Financial Accounting Global Settings (New)  --> Global Parameters for Company Code --> Enter Global Parameters
    6) On the Change View u201CCompany Code Global Datau201D: Overview screen, select company code 1000 and choose u201CDetailsu201D (F2).
    7) On the Change View u201CCompany Code Global Datau201D screen, maintain as follows:-
    Field Name:::::::::::::User actions and values
    Cash Mgmt activated::::::::::::::X
    Now retry the process and update whether the above helps you.
    thanks
    G. Lakshmipathi

  • How to implement tooltip for the list items for the particular column in sharepoint 2013

    Hi,
    I had created a list, How to implement tooltip for the list items for the particular column in SharePoint 2013.
    Any help will be appreciated

    We can use JavaScript or JQuery to show the tooltips. Refer to the following similar thread.
    http://social.technet.microsoft.com/forums/en/sharepointdevelopmentprevious/thread/1dac3ae0-c9ce-419d-b6dd-08dd48284324
    http://stackoverflow.com/questions/3366515/small-description-window-on-mouse-hover-on-hyperlink
    http://spjsblog.com/2012/02/12/list-view-preview-item-on-hover-sharepoint-2010/

  • IDoc type could not be determined for the IDoc

    I am trying to Post the payment run through the transaction F110.
    In the payment run log i get the following message:
    "IDoc type could not be determined for the IDoc"
    But in fact the IDoc is generated and it is displayed in We05.
    I have configured the Message type PAYEXT-PEXR2002 and EUPEXR-IDCREF01 both for the partner.
    Has anybody Idea about why this error is coming and how i can resolve this?
    This is important because in Payment run log, they need to know the IDoc number generated for that run, else it may become difficult for user to identify which IDoc was created for a particular payment run.
    Would appreciate if anyone can please help on the same.
    Thanks & Regards,
    Narayanan

    Hi,
    If you are paying the payment through F110, if the payment exceeds the limit what you are spefied in available amounts in FI12 screen. First Please check this screen.
    still if you are having any problem
    Check in the below path:
    IMG- Financial Accounting (New) - Accounts Receivable and Accounts Payable - Business Transactions - Release for Payment - 1. Create Workflow Variant for Release for Payment
    2. Assign Release Approval Procedure for Release for Payment
    3. Define Users with Authorization to Payment Release
    Thanks
    Chandra

  • IDoc type could not be determined for the IDoc in F110

    Dear All,
    The below mentioned error is encountered by us in F110.We have check all the setiing  and not able to find the solution for this error.
    Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
    The system is not creating the IDOC file.....
    IDoc type could not be determined for the IDoc
    Message no. B1090
    Diagnosis
    The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
    The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
    The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type  from field DOCTYP.
    Procedure
    Possible error sources:
    - The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
    - The IDoc type  is not known in your system and must be maintained.
    Kindly do the needful.
    Regards

    If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
    see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

  • How to find out the printer name for the Idoc

    Hi guys
    I want to find out the printer name for the Idoc,,some default printer is attached for one idoc,then how can we see the printer name for this idoc.
    Regards
    Madhoo

    Hi,
    For ALE/IDOC the  medium will be either ALE or EDI but not printer.So it might be wrongly attached.As such there won't be any printer attached to idoc.
    Regards,
    Nagaraj

  • Same material can exist on multiple line items for the same order.

    Hi
    Is there any specific customising setting or web shop setting through which we can restrict user to add same material on multiple line items for the same order ?
    Regards

    No.
    But if this is a must requirement, you can do an elaborate check during order save in ORDER_SAVE BAdI and return error. So, it will be only during order save.
    Eawar Ram
    http://www.parxlns.com

  • Line items for the PO are not automatically displayed

    Hi all,
    When attempting to post an invoice against PO, the line items for the PO are not automatically displayed. When we went to the Listing of PO's and brought this up, we noticed under the "invoice"tab that the: Invoice Receipt & GR-BsdIV is checked.
    need your help
    Thanks
    Fayaz

    Hi,
    Can you check delivery complete indicator in PO. It is in PO item details delivery tab.
    In MIRO transaction, select the  tab Purchase order/scheduling agreement, enter PO number and press enter.
    Right hand side select the layout all information .
    Regards,
    Chandra

  • ABAP: How to add a Price Condition Item to an order item

    Hi experts,
       Is it possible to add a Price Condition Item to an order item by BAPI or Function in sap crm? (like: 0k04 10 USD 1 EA)

    Hi,
    You need to use CRM_ORDER_MAINTAIN and have to use structure IT_PRIDOC to update or add new pricing data.
    But do remember, you have to call FM 'BAPI_TRANSACTION_COMMIT' once you are done with call to FM CRM_ORDER_MAINTAIN, else all your updation will remain in buffer and will have no effect in Database, which will let u feel as if things are not working they should be.
    Best Regards,
    Pratik Patel
    <b>Reward with Points!</b>

Maybe you are looking for