VF01 Header data condition tab

[former_member696830]

Hi All,

Help me to resolve the my requirments. I am totally new to this area as i am HR ABAP guy.

We have a custome program which calculate the actual vaues for billing and stores it in Z table based on some key field.

Brief req,

When we create the billing document VF01, what I need is, my condition tab  should be filled with the values which is stored in ztable with reference to condition type.

Any expert help is highly appreciated.

Any

BADI

EXIT

Enhancement point?            

[Former Member]

Hi Anees,

you can add your code in sap standard user exit program RV60AFZC in the form USEREXIT_FILL_VBRK_VBRP.

Here you can put break point and check your respective value want to insert in z table and after that you can add your code in inside user exit.

Regards,

Prasenjit

[former_member696830]

Hi Prasenjit,

As suggested, I set the break point in   USEREXIT_FILL_VBRK_VBRP in standard program RV60AFZC and then tried to execute the t-code VF02 but control is not coming to this point.

Do I need to copy this standard program to Z program and assing this somewhere?

Totay morning I asked one more Question regarding enhancement of VF01. I thnik u replied to my question but dont know why moderator loked that question. anyway getting values in condition tab is importent for me now.

[Former Member]

Hi Anees,

RV60AFS* series user exit work in Billing documents. you can check one by one and add the code in inside  user exit , no need to copy and create z program for this.

Please try to check RV60AFZZ also.

Regards,

Prasenjit

[Former Member]

Hi Anees,

inorder to fill your condition table check the user exit : USEREXIT_ACCOUNT_PREP_KOMPCV

program : RV60AFZZ

fill the tkomk tkomP structures accordingly.

[thangam_perumal]

This message was moderated.

[Jelena_Perfiljeva]

Wow, so many suggestions... If only someone bothered to stop and think whether the requirement  makes any sense.

Anees, kindly go back to your SD consultant and explain that the billing document conditions must not (and cannot) be manipulated in such way. Pricing conditions need to be determined in the preceding document. It's actually very alarming that someone gave an ABAPer such requirement (unless I misunderstood it completely). You'll find many posts on SCN confirming that this is not the right approach and is not feasible.

P.S. Pinging to look at this in case I'm missing someting.

[former_member696830]

HI Jelena Perfiljeva and  All.

As per the SD consultant. There is no manipulation of billing document condition types anyhow. These sales document type are service related and no PGI at all and would refer the preceding sales document conditions at billing creation point. None of the pricing condition types deriving via preceding condition types are not touching and above said enhancement which we are looking for is to identify the value to input under 2 or 3 condition types  (which are manual condition types by origin) to arrive to the final net figure.

Currently users have to do some working outside of SAP (In excel) to get to know the figure which to be input for a respective manual condition type. This  ABAP enhancement is to get identify the indicated value within SAP itself via a predefined logic definition (Custome program).Therefore no manipulation of automatic condition types but try to arrive to the figure via a custom program which calculate the actual values for billing and stores it in Z table based on some key field and that value is trying to populate under the respective manual condition type.

So is that possible by any means?

Thanks and Regards

Anees

[former_member696830]

Hi All,

Waiting for expert help.

My requirement is add one more condition type with values in condition tab.

Condition type  ZPAA  values say 1000.

This condition type and values are there in some Ztable.

Request you explain in details.

Thanks and Regards

Anees

[Jelena_Perfiljeva]

Anees, VF01 is billing document. I doubt it's created out of thin air and should have some kind of preceding sales document (e.g. a service order). It doesn't matter how the conditions are derived, they still need to be maintained in the sales document, not added in the billing document. As an ABAPer you might not know such details, so an SD consultant should've explained this to you.

There are designated pricing user exits in the sales documents - google it ('pricing user exit site:sap.com), there are tons of SCN discussions on this and documentation is available as well. You can add any conditions there, as necessary, and write any code to calculate the values. The point is it must be done in the sales document, not billing document. You can find the preceding documents in the document flow (there is a button in VF03). The conditions will be copied to the consequent documents.

If you have any further specific issues with pricing user exits, please feel free to update the discussion. Otherwise if this answers your question, kindly close it (see this blog).

[former_member696830]

HI Jelena Perfiljeva and  All,

Thanks for your valuable input.

But my functional person is saying,

According to the business there are some condition types which can be exactly identify at the point of Billing  and not at the preceding sales order creation point.

As per functional consultant "If I can change or add the new condition type and values at the VF01/VF02 manually then why cant it is possible to add those values using any EXIT, BADi, Enhacement Point or SD routine"

[Jelena_Perfiljeva]

Ha-ha, welcome to the SAP world! To my knowledge, none of these exist to add pricing conditions in the billing documents. All the old SCN posts (here is one example) are dead ends. Google 'add pricing condition invoice site:scn.sap.com' and see for yourself.

VOFM routines are not meant to be used to add new conditions either, as far as I know. (There is a good document online if you google VOFM - just in case you're interested.)

The only thing I can imagine is something like a freight condition (see example here) that is added earlier but the value needs to change before invoicing. In this case I believe you'd need the condition to exist already, so that the value could be re-determined when billing.

[Former Member]

Thumbs up for this answer. I already had the exactly same discussion with an SD consultant as he wanted me to add a new condition to a Sales Order on SAVE_DOCUMENT_PREPARE, and call PRICING_COMPLETE again. Insane.