FEBAN FB05 wrong account type

[Dogan]

Hi guys,

i have a problem regarding the post processing of the electronic bank statement.

When i try to post in FEBAN (Save button to switch to FB05) i always get account type K with the according account number.
But what i really want is this

The gvc is 166 (incoming payment) and the posting rule allows both account types (D and K), with the intepretation algorithm 001.

I know that the system finds the IBAN of the vendor and therefore updates the table FEBCL with account type k and the account number.

I have tried to "overwrite" the dynpro fields through a search string (see screenshot), but its not working properly.

I also tried it with the targetfields EBAVKOA account type and EBAVKON account number but those didn't work either.

Is there a way to set the clearing screen as the screenshot above or ignore the found vendor?

Thanks and regards

Cemre

[Bohdan]

Hi dogan,

This is a known problem. It is partly described in the KBA-note 2435649 - Identify business partner when uploading bank statement. But it does not contribute much to the resolution.

Search string is not a reliable mechanism to set the account type for clearing. I'd not recommend using it. You can however use BADI FIEB_CHANGE_BS_DATA and define a custom logic there that will set the account type into the structure C_FEBEP-AVKOA and add a clearing parameter into table T_FEBCL with values KOART and AGKON (if known).

Otherwise, you will need to have to face these mediocre interpretation results.

Regards,

Bohdan

[Dogan]

Hi the.wirtschaftsmann ,

thank you for commenting. Yes, you are right. The search string is not realible. Because of that, I have used the user exit EXIT_RFEBBU10_001 to add the account type to the table T_FEBCL.

As you recommended the BADI FIEB_CHANGE_BS_DATA, which one would you prefer over the other: To use a BADI like FIEB_CHANGE_BS_DATA and FEB_BADI or to use a user exit like EXIT_RFEBBU10_001?

This may not be the current topic, but I have another problem on which i hope you can help me, as you are an expert on this field 😉

While uploading a bank statement, the note to payee should be changed to clearly identify the transaction. Currently, the note to payee is filled with many details from the bank, like a bank reference number, which does not help us. I would like to remove the unnecessary information and leave only what we need.

I tried it with the user exit EXIT_RFEBBU10_001, where i cleared the table T_FEBRE for a certain transaction code and added a new text. While debugging, i can see that the table is being updated but after the upload the note to payee never changes.

Did you by chance have a similar request or now how to manipulate the note to payee while uploading the bank statement?

Any help is appreciated.

Thanks and best regards

Cemre

[Bohdan]

Hi dogan,

User exit EXIT_RFEBBU10_001 was the original enhancement point introduced by SAP. It allowed the customers to implement their own logic before standard interpretation mechanisms kick-in. Later on SAP introduced the definition of BADI FIEB_CHANGE_BS_DATA. The interface of this BADI is essentially the same as that of the exit EXIT_RFEBBU10_001. Therefore if you ask me what is my preference among these two - the answer is clear - BADI. The main benefit of the BADI is that we have much better control over the enhancement due to the object-oriented design of the BADI.

I worked with the user exit EXIT_RFEBBU10_001 on one of the projects. There were a lot of legacy enhancements in this spot when I arrived. Essentially to structure the code, they introduced separate include per country. But it was not overly reliable / efficient, because there were a lot of global objects and conflicts between different countries. So eventually, I just defined a global class which encapsulated all logic and called it from the EXIT_RFEBBU10_001.

Now, when we speak about FEB_BADI - it is called later on in the processing i.e. after the interpretation took place. Here you have completely different options. I'd say at this stage it is a bit too late to do anything about the refinement of the OI-assignment. I use this enhancement spot as a rule whenever I have to adjust some parameters which cannot be adjusted via BADI FIEB_CHANGE_BS_DATA. Alternatively, you will need to use it when you need to change the structure of the posting. For example, when you need to split accounting posting into more lines e.g. split of loan repayment into loan & interest part or something like that.

On the last few projects, I've used both BADIs FIEB_CHANGE_BS_DATA & FEB_BADI just for different purposes.

P.S. There is another drawback: BADI FIEB_CHANGE_BS_DATA is called during both initial upload & subsequent post-processing in both GUI & Fiori landscape. FEB_BADI is called also in both instances if you use it in GUI landscape. But if you're using Fiori apps for upload / post-processing, this BADI won't be called in post-processing mode. At least that's my experience.

P.S. With regards to manipulation of note to payee - it is more or less a mundane task 🙂 You can do it either during upload (i.e. based on the raw file data) in the user exit EXIT_RFEKA400_001 (see sample details). Or you can do it via BADI FIEB_CHANGE_BS_DATA.

Regards,

Bohdan

[Dogan]

Hi the.wirtschaftsmann,

thank you for the detailed explanation. Maybe i will start using the BADI more often now 😄

Regarding the note to payee: I will test both of them and see which one fits better to our needs.

Thanks again

Best regards

Cemre