Custom validation in VFX3

[former_member271701]

While posting a Billing document to Accounting thru VFX3 I need to put a validation that the document must not be posted till PGI is done. Could someone please tell me where i can put this check. any user exit/ BADI/ enhancement which is available

[VeselinaPeykova]

If you use delivery-related billing (billing relevance A) it should not be possible in a standard system to create an invoice (SD document category M) if you have not posted goods movement for the corresponding delivery. This means that if for delivery-related billing you generate invoices when goods issue is not posted you can search for custom developments that cause it. You can use transaction PRCAT or program SNIF, or read the available project documentation.

If you use order-related billing (Billing relevance B) or order-related billing on delivery quantity (billing relevance G) you can check how billing is prevented in standard for cash sales (copy requirement 002 in VTFA for BVN item category, BV billing type and CS order type). You can consider creating your own routine adapted to your business-specific needs.

Why do you want to prevent the release to accounting instead of stopping the billing generation? If you only need this billing for some printouts or reporting - just use proforma invoices.

[former_member271701]

The new scenario which I need to try out is such that the Invoice can be created early without Accounting doc generation . Later on the PGI will be done and the Accounting document will be released thru VFX3 but when this happens I need to keep a check that Accounting document will not be created without PGI.

To meet this requirement I have set the standard routine 11 in copy control of Delivery to Billing. Also at VOFA of the Bill type I have set a billing block. As of now I cannot use Proforma invoice . Hence the question. Do guide if you know of any exit/enhancement which will server my purpose

Nivedita

[VeselinaPeykova]

aroon.mehta I fail to understand the context and the motivation behind such change.

Would you please explain it?

Why using proforma invoices is not suitable for your process?

What would be the usage of this billing document exactly (without a FI posting)?

And why do you need the invoice to be generated before goods issue?

By the way, you forgot to mention what is the billing relevance.

[former_member271701]

It is a business requirement . I am trying to see whether it can be fulfilled.

There are some custom developments due to which Proforma Invoice cannot be introduced at the moment . The billing document has to be generated at an early stage and the same number will be carried forward to our custom built cycle.

You are mistaken. It is not there there will be no Accounting posting...just that the Accounting posting will be deferred that is the reason why a billing block is being put at VOFA which will be released later on during VFX3

Billing relevance is M - Delivery related invoices

[VeselinaPeykova]

aroon.mehta I actually understood that the billing should be released at a later point to accounting, but creating an invoice without posting to FI does not achieve much (other than creating additional work for employees, especially at month end).

In another company we used proformas and we carried over the proforma number to the final billing document. Such approach is acceptable in many countries, but it might be that in your case you are dealing with some very special case related to legal legislation.

I assume that you are a technical consultant. In this case I would highly recommend that you speak again with your functional SD/FI colleague and maybe think of revising the current concept.

If you really have to prevent release to accounting based on certain prerequisites - you can read about SD-FI billing interface: General Information About SD-FI Interface.

[former_member183501]

There are some custom developments due to which Proforma Invoice cannot be introduced at the moment . The billing document has to be generated at an early stage 

aroon.mehta

Even if there are custom developments you may very well write a separate logic for this process and introduce performa invoice.

and the same number will be carried forward to our custom built cycle.

What is this custom built cycle? Would you please mind to elaborate?