Skip to Content
0

Pricing Requirement Restrictions RV61A-Include

Nov 01, 2016 at 04:27 PM

45

avatar image

Good morning,

in ERP Pricing it is possible to define requirements . Those requirements will be found in Abap namespace RV61Axxx (xxx = Number of the requirement).

I can remember that in those requirements one should NOT change the context. Does mean one should not change KOMK or KOMP field contents in order to change the access of the condition(record) to which the requirement is assigned to. Does mean the KOMK and KOMP field contents which are defined when PRICING or PRICING_COMPLETE function call starts should not be changed in the functioncall itself.

I can remember that in SAP CRM it is not possible to change the KOMP/KOMK context in the requirement as the requirement-method can only throw back "yes" or "no" and it is not possible to change other data within the CRM requirement but in ERP it can be done (but should not be done).

My problem is now: I can not find the SAP Note any more in which I found this important information. Can anyone remember this note and communicate it?

I also know that in chapter 9.2 in the book Preisfindung und Konditionstechnik in SAP ERP they exactly explain such a manipulation which in my opinion should not be programmed as CRM does also not allow this manipulation. Compatibility between ERP and CRM is not given.

Or am I wrong and my information stand is much too old.

Thanks for any feedback. We are still using CRM 7.0 and ERP 7.3x

Thanks and regards

Michael

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

0 Answers