cancel
Showing results for 
Search instead for 
Did you mean: 

question removed. not required anymore. sorry for inconvenience.

Former Member
0 Kudos

question removed. not required anymore. sorry for inconvenience.

AlexGourdet
Product and Topic Expert
Product and Topic Expert
0 Kudos

Thank you for visiting SAP Community to get answers to your questions. Since this is your first question, I recommend that you familiarize yourself with Community Q&A, as the overview provides tips for preparing questions that draw responses from our members.

Should you wish, you can revise your question by selecting Actions, then Edit.

By adding a Picture to your profile you encourage readers to respond.

Former Member
0 Kudos

Dear SD / ABAP experts.

Is there a specific configuration activity or a particular VOFM Routine or Can an existing routine be copied and custom code be written in it for keeping the condition value like Freight same as in quotation ?

Would be greatful for your suggestions.

Thanks,

Mohan Joshi

SAP ABAP Developer

Accepted Solutions (0)

Answers (2)

Answers (2)

Jelena
Active Contributor
0 Kudos

The issue here is not in copy control. Based on the screenshots, it appears that a pricing condition is configured as a fixed amount but in fact behaves as a quantity-based. I.e. you change quantity and condition value changes too. It should not be happening for the fixed amount condition. It's supposed to work as a flat fee or discount, i.e. as you're expecting it to work.

Why is this happening is a million dollar question. I'd start with asking an SD consultant to review the pricing determination analysis in the document and potentially review all the configuration for this condition. I see it's set up as both header and item condition, as group condition and potentially as both manual and condition-driven (manual entry has precedence). I'm not an SD expert but to me this is just asking for trouble. Defining conditions more clearly is always beneficial.

ABAP-wise people do strangest things sometimes, so I wouldn't be surprised if there is also some code that causes such effect. Finding it can be tricky. First place to search would be all the custom VOFM routines (that start with 9..., you'll find specific numbers in pricing config) and if nothing there, well, do a code scan of SAPMV... program (parent program for MV45AFZZ) for sales documents for 'ZF03'.

That's pretty much it. In an unadulterated system, a fixed price condition should work as you expect. Something is wrong in your specific system, I believe. Good luck finding the root cause.

Lakshmipathi
Active Contributor
0 Kudos

With the standard configuration, this value will get changed based on your pricing configuration in v/06. I presume, in your case, for ZF03, it is set to "C" against Calculation type. Change this to "B" and retest the scenario.