Do not release into Accounting when saving Billing Document

[Former Member]

Hello,

My Customer what to implement this scenario:

We have a value field called VVXXX and we use User Exit COPA0002 / EXIT_SAPLKEAB_001 / ZXKKEU03 in order to calculate value to it.

Now, if  at the end of the CO-PA user exit value field VVXXX = 0, the billing document should be saved without release to accounting. Otherwise, the billing document should be saved with release to accounting.

Is anyone know Exit/Badi that works after the CO-PA valuation user exit (COPA0002)?

Is there any other suggests to implement this scenario?

Parallel, I published this question in CO module conversation. 

Best regards,

Lior

[Former Member]

Hello,

My Customer what to implement this scenario:

We have a value field called VVXXX and we use User Exit COPA0002 / EXIT_SAPLKEAB_001 / ZXKKEU03 in order to calculate value to it.

Now, if  at the end of the CO-PA user exit value field VVXXX = 0, the billing document should be saved without release to accounting. Otherwise, the billing document should be saved with release to accounting.

Is anyone know Exit/Badi that works after the CO-PA valuation user exit (COPA0002)?

Is there any other suggests to implement this scenario?

Parallel, I published this question in CO module conversation. 

Best regards,

Lior

[Lakshmipathi]

You can try with an enhancement COPA0005.  Also have a look at the following notes:-

• Note 456401 - COPA0005: Cannot prevent update
• Note 1008756 - COPA0005: Update prevention incorrect

G. Lakshmipathi

[Former Member]

Dear Lakshmipathi,

COPA0005 can prevent the Billing Document from been written to CO-PA only (The accounting Document is created). What I need is to prevent it from Release to account at all (Accounting Document and parallel CO-PA document.

Thanks,

Lior

[Jelena_Perfiljeva]

It'd seem logical to search for a user exit in the SD to FI posting for this purpose. These user exits are well documented, use Google.

However, I'm not sure this requirement makes a lot of sense - there are only few changes we can make in the invoice (certainly not quantities or amounts). So even if it's not released to accounting, what would you do with it? How would you fix it? Maybe it'd be more logical to prevent the invoice from being created? Or maybe this should be handled in the order or delivery? When you get to COPA posting it's way too late to fix/block stuff.

[Former Member]

Hello,

We are using CO-PA valuation user Exit (COPA0002) in order to calculate value field VVCST (Total Cost). Now, my client demand is that if the Value field is equal 0, then do not release the billing document into accounting. The logistic billing document will go on and the sale should not be stoped.

Now, first the user have to fix material master data and then to release the billing document to accounting.

That is the reason I need EXIT / BADI is SD module that is get active after CO-PA valuation user Exit and will get flag from memory id and will avoid the billing document to be released into accounting.

Thanks,

Lior

[Lakshmipathi]

Moved from SAP ERP Sales and Distribution (SAP SD) to ABAP Development