Revive BCM batch after its sent to bank

[Former Member]

Hello SAP gurus,

We have a requirement to do a development to capture bank rejected BCM batches, remove the rejected line items from the batch, then send the batch again without the items in error. We need this due to our bank rejecting the entire SEPA payment batch if only 1 item(or more) is in error.

We intercept the incoming status of “Rejected” batch, and then remove the item from the batch that was rejected, and then send a new payment file. How we create a new payment file and assign this file to the BCM, I don’t know yet, any suggestions?

Kind regards

Greg

[Former Member]

Dear Greg,

This requeriment is nonsense, if I were you I would try explain the client that he has to eliminate those errors from the XML file that is sending to the bank.

Whatever reason there is an error you need to follow these easy steps:

1. You have to trace in which line of the XML is the error.

2. Your client has to contact their bank to ask why the line was rejected.

3. You need to fix de DMEE tree so that those lines never again produce an error.

Soon enough there won't be any errors, these aproach makes much more sense than just ignore errores.

Have you asked your client how is he expecting to pay those misleading lines, manually forever?

Please asign points if this helps.

Best regards,

Alfredo

[Former Member]

Hi Alfredo,

I would 100 agree with your approach. However, our DMEE is at a state where 99.9% of payments are accepted. This solution design is only for the small chance we get a value (not format or syntax) error, such as an invalid BIC, i.e. a master data error. Now, the problem is, as I explained in another reply to Anton, is that if we have this error, and due to us being forced to use this bank which provides insufficient return payment statues for SEPA, we have a problem that the entire batch gets rejected and we can't tell which payment is in error.

We are still looking at possible solutions and I will update once I have found a workable solution.

And to answer the question about paying the erroneous payments, they would be automatically reversed by an ABAP program already in place, and then will be paid in the next payment run, once the error is fixed.

Kind regards

Greg

[Former Member]

Dear Greg,

Then, it looks easier to me that instead of trying to solve the issue in the XML, try to validate the BIC master data.

You can access all your BIC codes in BNKA table, then make a simple program in order to validate all of them.

I found a method that should work:

Bank Key/BIC Validation (CHECK_V_BLZ_BIC)

Checks for a valid bank key and BIC in /PE1/T_BLZ and/PE1/T_BIC. The method checks the following attributes: Bank key BIC code (SWIFT address) Bank key reference account BIC reference account

You can find it in the following page: Recipient Item Checks - Payment Engine (FS-PE) - SAP Library

Please asign points if this helps.

Best regards,

Alfredo

[AntonFarenyk]

Hi Greg,

In ERP (from F110 point of view) there is no possibility to create MODIFIED payment file. You will need properly reverse whole payment run and recreate it all over again without rejected instruction. If for example your SEPA is in XML, it means new MsgID for batch, for every payment etc.

Although the requirement seems little strange to me. Say I’m your bank’s customer. I bring my business (paym.file with instructions) to the bank. Bank rejects the whole thing only because I made 1 error? Then I need to find another bank to bring my business to. May be a tough call for your company but the right one for APP process integrity.

Best regards,

Anton

[Former Member]

Hi Anton,

I agree with you that I would recommend my client find a bank that would not reject the entire batch due to 1 error (either syntax, format or values). However, my client is tied to this bank by the head office and we are literally forced to use this bank. What is even worse now is that I did a test where by I sent 5 SEPA payments in one file(batch) and sent an incorrect BIC in only one of the payments. The xml reply we got from the bank mealy had 1 status of reject, and the entire batch was rejected. This now make identifying the erroneous payment impossible based on the returned payment status.

The errors we are worried about are actually only value errors. If it were a format or syntax error, this should be corrected in the DMEE. Although this would hardly ever happen, you can imagine the implications if it did happen for a single payment in a batch of 100.

Thanks for the feedback. We are still investigating possible solutions and I will update once we have the final solution.

Kind regards

Greg

[AntonFarenyk]

Greg Ellis wrote:

What is even worse now is that I did a test where by I sent 5 SEPA payments in one file(batch) and sent an incorrect BIC in only one of the payments. The xml reply we got from the bank mealy had 1 status of reject, and the entire batch was rejected. This now make identifying the erroneous payment impossible based on the returned payment status.

Hi Greg,

I'm curious to know what would be the technical reason for entire batch. Because along with wrong BIC in one instruction you still may have other structural issue which might be overlooked.

In xml reply for batch near tag GrpSts which value should be something like RJCT you should have tag StsRsnInf. Is there something like Reason code (may be RsnCd) and additional infomation (AddtlInf) ??

Best regards,

Anton