cancel
Showing results for 
Search instead for 
Did you mean: 

SAP SD - Control Repeat Output in the Cancelled Invoice during Org Invoice Cancellation.

0 Kudos

We are facing challenge after enabling the Multiple Issue functionality for one of the Invoice Output where we send PDF attachment via email. As the Multiple issue function will retrigger the Output whenever there is a change in the Invoice Document which is valid. Our case is,

1. Customer Invoice *XYX* created in Nov 2017 - Output Triggered for the first time. This is ok.

2. Customer Invoice *XYZ* was cancelled in Dec 2017 and hence a cancellation Invoice created. Here, as per std, a Cancellation Indicator is updated automatically in the Customer Invoice *XYZ* which is a change and hence as per Multiple Issue Function, the Output retrigger in the Customer Invoice *XYZ*. How to control this repeat output during Cancellation Indicator update which the User do not want.

Pls share if there are any specific technical developments can be done to manage and exclude "Cancellation Indicator" update validation before Repeating the Output.

VeselinaPeykova
Active Contributor

Considering that after releasing a F2 invoice to accounting you cannot perform a lot of changes to the billing document (other than cancellation I can think of only text maintenance) and that sending a F2 to a customer before you have released to FI is not a good idea, I do not see much value in setting multiple issuing for pdf printouts for F2 in the first place.

In the rare cases where users need to maintain some text that influences what is printed you can just tell them to issue the output manually (if such change is allowed at all by local legislation).

Accepted Solutions (0)

Answers (1)

Answers (1)

siva_vasireddy2
Active Contributor
0 Kudos

Hi,

check what is the Routine that is assigned to the output type in the output procedure.

if it is a standard routine copy the same and create new one with Logic-Excluding the cancellation invoice and assign the same to the output type

former_member207059
Participant
0 Kudos

Yes... We could not build the logic to exclude Cancellation Indicator update, as tracking / validating technically from Cancellation Invoice to the Original Invoice for Cancellation Indicator update is a challenge for my technical team. By the time, they go back to track with org inv reference, the Output Messages are triggered and processed. So we are looking for more technical answer to fix this. thanks.

former_member183501
Active Contributor
0 Kudos

Hi,

Don't you wish to intimate customers about cancellation of invoices which were sent to them ?

How do they know that received invoices have been cancelled or Not ?

Is it not relevant for business to intimate their partner via automated process? Means when a mail is sent and when it contains cancelled indicator technically,wont it be a good idea to enter description that Invoices XYZ has been cancelled?

VeselinaPeykova
Active Contributor

This depends on the country legislation - if I am not wrong, in my country when you cancel a VAT invoice you prepare two documents - a credit note (number and date), where it is clearly stated to which original invoice (number and date) it refers, and a protocol for annulment.

former_member183501
Active Contributor
0 Kudos

Hi Madam,

in my country when you cancel a VAT invoice you prepare two documents - a credit note (number and date), where it is clearly stated to which original invoice (number and date) it refers, 

Once VAT invoice is cancelled then does it not create an accounting document for automatic settlement?

1st Invoice cancellation then creating a credit memo? How ? Why ? I think I could not understand clearly.

Regards

Kamlesh

VeselinaPeykova
Active Contributor

It is very simple, really 🙂

You have F2 number 0000002890/21.12.2017 posted to accounting. You have sent the invoice to your customer. It is recorded in your books and in the books of the customer.

Later you realize that there was a mistake which requires cancellation. You cancel the F2 invoice, which results in S1 0000000895/21.12.2017. On the S1 one of the mandatory attributes is that this is a credit note referencing invoice 0000002890/21.12.2017.

Credit note example layout:

You have to send this to the customer, based on which he will know that 0000002890/21.12.2017 is void and will reflect this in his books.

If at least one of the companies is VAT registered you need to sign also a protocol for annulment.

There is no need to resend the original invoice with a notification that it is cancelled because you stated this with the S1 document.

After that you proceed as usual - for example you correct the mistake and issue a new invoice F2 0000002895/21.12.2017, which you also send to the customer.

former_member183501
Active Contributor
0 Kudos
Thanks Madam!

But my queries are increasing from your reply.

Later you realize that
there was a mistake which requires cancellation. You cancel the F2 invoice,
which results in S1 0000000895/21.12.2017. On the S1 one of the mandatory
attributes is that this is a credit note referencing invoice
0000002890/21.12.2017.

Means Credit Note(Billing type ) is assigned to F2 which triggers its auto generation in VF11 and it means that same data will get copied? What could be the reason for cancellation if same data to be copied to credit note?

If there is a price deviation then Credit/Debit memo request could be created followed by Credit/Debit memo.As we can manually change the pricing in Credit/Debit memo request.

But, the example which you have given for cancellation of document due to mistakes then how could it be corrected?

There is no need to resend the original invoice with a notification that it is cancelled because you stated this with the S1 document.
After that you proceed as usual - for example you correct the mistake and issue a new invoice F2 0000002895/21.12.2017, which you also send to the customer.

This could be correct in your Country but here I guess OP doesn't create credit memo so in that case, how would customer know that second correct invoice sent to him is replacement of previous invoice which has been cancelled by company?

This depends on the country legislation

Yes! it is 100% true.

Madam, I can't understand the language of output.

Regards

Kamlesh

former_member183501
Active Contributor
0 Kudos

Hi,

Can't we add a logic i.e " Do not re-trigger output if VBRK-FKSTO=X" ?

VeselinaPeykova
Active Contributor

Your questions are side-tracking the original query of the OP and you are not doing him a favor by that.

The OP's question was about invoice cancellation (VF11 resulting in S1) and that he has the problem that with the current solution they send the cancelled F2 which is not a desirable outcome. The reasons why an invoice is cancelled can vary, it does not have to be pricing mistake and of course, in certain situations you are not allowed to do VF11 cancellation, but you have to use CR/DR. In all cases the customer needs to know which is the correct invoice to which he should refer in the future. When you use credit/debit memos you still refer to the original invoice and this reference is printed on the corrected invoice. In my previous reply I was not talking about CR/DR at all - I explained what we do with F2->S1.

As you cannot cancel F2 without generating a corrective reverse document (S1) it is sufficient to send the S1 to inform about voiding an invoice.

I am still curious what kind of changes the company does to a F2 invoice printout after it is released to accounting, if these are really necessary and good practice and if development can be avoided completely with different setup.

former_member183501
Active Contributor
0 Kudos

Thanks Madam for making it more clearer!

And yes my questions are somehow side-tracking but there was a lot of learning your your each replies and if OP had gone through your replies in which I had asked the questions then he may find alternative solutions.

Regards

Kamlesh