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.

Similar Messages

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.

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...

Update Sales Order to enter a Manual Price Condition

Hello all,
SAP R/3 ERP
It is already created the Sales Order, Picking and Delivery (good issue is NOT created yet).
I can not continue my flow because is missing a pricing condition.
However the condition that is missing is an Header Manual Condition Price.
As we are dealing with a Header Condition and Good Issue and Billing is not created, it is possible to update the Sales Order and then enter the header manual condition .
My question is:
'--- In order to update the Sales Order to enter the header manual condition, do I need to delete the Delivery and Picking? If yes, what are the transaction de delete both of them? .
Thanks a lot,
Barbara

In my opinion, there is no need to delete the delivery. Just add the manual pricing condition and click on update pricing button ->carry out new pricing. This will add the manual pricing in the sales order. Still if you want to delete the delivery, then first check whether the picking is done using transfer order. If so, use t.code LT15 to cancel the transfer order. If transfer order is not used, then just remove the pick quantity from delivery line items and then in t.code VL02N, enter the delivery document go to menu delivery document ->delete. This will delete the delivery document.
Regards,

Is there a BAPI or function module for price condition?

Hi experts,
I just want to create price condition info record to purchase order.
we create price condition through tcode MEK1/MEK2/MEK3.
it is more different from tcode ME11. it doesn't need to input purchase group, tax code etc.
but I can't find the BAPI or function module for this tcode.
does anyone know it?
thanks in advance.
looking for your reply.
jack

Please check this answered link:
Re: Bapi_prices_conditions does not delete old condition properly
Re: bapi for condition recaords
Edited by: Afshad Irani on Jun 13, 2010 3:38 PM

Manual Price Conditions doesn't determine the new exchange rate in billing

Hallo People
We are using TAXBRJ in our company and sometimes is used a manual condition to determinate a price. The process is a exportation and is used exchange rate USD to BRL . When we create a billing (VF01) with copy of delivery the exchange rate dosen't update with the rate of the day.
We made the following analyses :
- For Automatic Conditions the redetermination(update) of exchange rate is updated correctly, don't have problems.
- On the copy control delivery to billing, the exchange rate determination was set to carry the date of the day on PricingExchRate type (Type E "Exchange rate determination according to current date" because that the automatic conditions work correctly).
- I was tried change the copy control to pick the billing date ( Type C "Exchange rate determination according to billing date", but doesn't work. In the category item we put the Pricing dategual like billing date, but doesn't work too.
- In the first VF01 display we put manually the pricing date but to manual condition doesn't work.
I found just one note about copy condittion to billing and exchange rate, but this note is only for sap 4.7, and we sap version is 6.0.
I'd like to confirm if to manual conditions will haven't the redetermination of exchange rate on the billing, and I'd like to know if exist some note about this; Or I will have to make some development to redeterminate this rate?
Thanks,
Henrique.

Hi, Thanks for yours reply !!
The field where the problem happened is KOMV-KKURS, and the system is proposing the exchange rate according to M. As I said, the problem just occur when a Price is entered manually is sales order. When we make the VF01, to others conditions carry the new tax rate in KOMV-KKURS is update normally, just to this manual condition don't work.
The note that I mentioned on my last thread was 97487, but will not resolve the problem.
I think that if I am using in copy control on PricingExchRatetype like Type E "Exchange rate determination according to current dateu201D should work with any condition.
When I changed the copy control on PricingExchRate type to C like show note 92613 the process don't work too.
The currency of document is BRL, just the price is typed as USD.
Att,
Henrique

Preventing manual price condition maintenance in Purchase Order

Hi Guys
'I am seeking to add code somewhere either in the Purchase Order program or in pricing which will only allow some users to manually overwrite the automatic price. I am not sure however where to put the code (1) in a PO BADI (2) In a pricing requirement or (3) A.N. other suggestions. I am also unsure as to whether I should grey out the price field as default and open it for manual entries for certain Vendor account groups OR to re-run pricing when users try to manually change the price.
Kind Regards
Brett

Hi,
    You may use the standard condition type JEXC (Manual Excise) in MM pricing procedure. Maintain JEXC as statistical condition and maintain subtotal as 5 against JEXC in M/08.
Now, go to OBQ3 and maintain calculation type as 355 against JMOP.
   Now system will copy the JEXC value from MM pricing to JMOP in tax procedure.
Note: 1. Tax code should be assigned to company code.
          2. JMOP condition type should be maintained correctly in "classify condition type" configuration.
Test the scenario and revert back.
Regards,
AKPT

Manual Price Conditions

We have configured and working well manual conditions in sales orders but when the order is repriced by the system (for example when a date is changed) the manual condition is removed. We have tried changing the repricing method on the pricing procedure to type C (what we manually reprice with and that does not remove the condtions) but this has not made any difference.
Any ideas

if the system is automatically repricing- check in MV45AFZB - userexit_new_pricing_VBKD...make sure C.
Thanks
Sai

Copying manual price conditions

Hello,
We are creating sales order and if we deliver quantity less than the order quantity, we will create a back order with respect to the sales order.
In Sales order we are maintaining some manual condition type at header level and when we create back order these manual conditions are not flowing to the subsequent back order.
How to make this manual conditions to flow to subsequent documents.
Thanks,

Hi,
u can reslove ur problem with delivery item catagory .in delivery item catagory under untidy check minimum untidy there u have to use if blank no dialog A note about the situation B situation with error message.
Check minimum quantity to be delivered
Specifies whether the system checks the minimum delivery quantity, and, if so, determines how the system reacts if the minimum is not met.
Use
You can specify the minimum delivery quantity in the
Material master record
Customer-material info record
The value you enter in the Check Minimum Quantity field determines whether you receive a warning or an error when the minimum quantity is not met. If you leave this field blank and have specified a minimum delivery quantity, the system gives you a warning anyway.
Best regards,
venkataswamy.y

Repricing in CRM deletes manual price

When a manual price condition is entered in a CRM document, and pricing is refreshed, the manual price is deleted. In R/3, in price procedure configuration, there is a setting for 'pricing type' which allows control of manual prices. This feature does not exist on the CRM price procedure configuration, and I do not see it in Item category pricing choices.
Does anyone know how to hold manual prices, but redetermine others?

Hi Bill,
There are 2 steps to follow by which you can set a condition type to be manually processed
1. Set the value for 'Manual entries' for Condition type to 'Manual entry has priority'
2. Mark the 'Manual' flag for the relevant condition type in the pricing procedure.
If, after doing these customizing settings, the manual conditions get deleted, please check your SM53 log for the application component com->sap->conn->jco and rfc. If you get an error, as follows, then you may need to request your basis team to update your VMC kernel patch level to the latest version.
'com.sap.conn.jco.ConversionException: (122) JCO_ERROR_CONVERSION: Cannot convert field CALC_TYPE of type CHAR to char'
Hope this helps.
Regards,
Pavithra
**PS : Please reward points if this helps

Manual price have to prevail over automatic price

Hello experts,
SAP ECC 6
In my pricing procedure we have a Manual Price Condition (ZPMA) and I have an Automatic Price Condition (ZPR0).
On Sales Order creation, if we determine a Manual Price, this Manual Price have to prevail over the Automatic Price. How and where to define that?
Many thanks & Regads,
Barbara

Hi,
As said in earlier mail, use condition exclusion
IMG path..SD>>Basic functions>>Pricing>>Condition Exclusion>>
Go step by step:
1. define two different exclusion group say X group & Y group.
2. Assign individual condition type to each exclusion type. Condiiton ZPR0 to group X & ZPMA to group Y.
3. Select your pricing procedure.
Enter serial number say 100, Condition exclusion option as D ie if a condition type from the first group exists in the document, all conditions types that are found in the second group are set to inactive.
This works.
Regards,
Savita Swami

Price Condition&Price update are disabled in S.O even after partial invoice

Dear All,
We are using manual pricing condition in the Sales Order, when we do a partial delivery and billing for a Sales Order line item, the update prices function (button) is inactive and price conditions are greyed out.
We are using Pricing Type "C" in the VTFL item copy from Delivery to Billing.
Even after partial quantity invoicing from the Sales Order there will be pricing changes and users will need to enter manual price for the item that is partially invoiced.
Currently system does not allow any change in the manual price condition as the all the price conditions are greyed out in the S.O even if partial qty of the line item is invoiced.
Please let me know what needs to be done to enable manual condition entry and Price update functions in the Sales order even after partial invoice quantity of the line item in the Sales Order.
Regards
Venkat

Hai Venkat,
This is the standard functionality and system treat like
sales order conditions once invoiced should be freezed.
As a work around you can do like
in sales order order
Go to Item - Shipping
Part.dlv./item B Create only one delivery (also with quantity = 0)
Max.Part.Deliv. 1
This make only one delivery for the line item
Considering if you have a material Sales order of 2 KG and you added some manual price.
And you are doing partial delivery of 1 KG and Invoiced.
Now user can use the same sales order and create a new line item of the same material and can enter the balance qty and change the condition which is not grayed out.
Regards,
Mani

CRM 5.0 ISA insert new price condition from order entry screen

In CRM 4.0 we wrote a custom field on the order entry screen that shows the list price (sub 1), we allow the user to change this value (inserts a PB00 price condition in the item pricing) and validates the change is within a certain % of the list price.
The jco method we used in 4.0 no longer exist in 5.0, been using the 55 page IPC VMC PDF in note 809820 but still can't figure out how to replicate.
Any help on what class / method might help us insert a manual price condition from ISA would be appreciated.

It could be possible to use CRM BAdI to do this function.

Price Condition Update Function Module

I'm trying to identify the function module that updates the price conditions in a sales document. I know one exists as I used it years ago but can't seem to locate it. It replicates the manual process of clicking the update button on the screen.
this will be used in visual composer to update pricing prior to further processing of bapi's
Any help appreciated

Hi simon,
Please check the following
RV_CONDITION_SAVE
RV_CONDITION_COPY
SD_SALES_CONDITION_MAINTAIN
Do you want to add one more pricing condition type to the existing sales order??
Use BAPI_SALESORDER_CHANGE.
Hope this help

Function module or bapi to get condition value of condition types (vk11)

Hi Experts,
I have customer no(Sold to) , sales area and material as input.
and i need to get discount value(defined using condition types using vk11) that i give to customer for a given material for give sales area.
Pls help me with the standard FM or Bapi through which i can get my desired output.
Thanks in Advance.

Hi Ashwin,
thanks for the reply but, this fuction module retuns me condition table based on the Acess sequence selected by me.
where as what i require is that i should get condition record number or condition value, based on the access sequence configured (i.e i shouldn't provide the acess sequence).
Thanks in advance

Vistex IP Module - manual price conditions get replaced

Similar Messages

Maybe you are looking for