Repricing in CRM deletes manual price

[Former Member]

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?

[Former Member]

Hi,

In CRM when you maintain a pricing procedure, you can set a condition type as manual. This is the seventh column in the pricing procedure maintenance. Check this setting out.

I hope this helps.

Gaurav Gera

[Former Member]

Thanks for the suggestion, Gaurav. However, we do have the manual flag set in the price procedure for the condition. But when the document is repriced, the manual condition disappears.

I am looking for a way to make it be retained unless manually deleted.

[i035338]

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

[Former Member]

Hi Pavithra,

We do have our config settings as you recommended. In addition, there is no access sequence on the condition type. We also investigated your suggestion regarding the Virtual Machine Container and found it does not apply as we are at Basis 620. Also, we do not have transaction SM35.

I appreciate your input and look forward to hearing any other ideas you may have.

My best regards,

Bill Shaw

[i035338]

Hi Bill,

Its Ok if you do not have any access sequence attached to your condition type. I have created manual condition types with no access sequences, but am still able to retain the manual conditions.

Could you please run transaction code 'SM53' again, and check if Kernel Patch no is set to 102 or may be higher.. I am not sure of the latest patch no. We are on SAP_BASIS 700 release Patch level 0012.

Also, check for the application log message for Java and RFC component as described in my earlier post.

Regards,

Pavithra