EBS configuration problem

[Misha13]

I try to set up a FEban transaction. All the necessary settings in OT83 and OT59 were correctly set up, yet the system still selects the main GL account as the customer number, even though I have created strings for account number and account type. Please advise how to fix this.

Posting rules

Feban

ot59

strings

table febep

[henk_hoogerbrug · Accepted solution]

Hello Misha,

Please try to setup the rule like this: 

And deactivate all the search strings, because you don't need them for the basic scenario. So first step is to test if it works without search strings.

Posting logic would be:

area 1

Bank
@ Clearing account

Area 2
Clearing account
@ Customer (open item clearing)

Best Regards,
Henk Hoogerbrug

[Misha13 · Accepted solution]

Hi Henk,

Thank you for the idea. I made changes as you suggested. The system stops picking the g/l account, but still can't read/match the customer or document number. Payments stay red. Additionally, it's strange that the string has stopped working. 

Any ideas why the system does not read the customer nr or doc nr from the statement

[henk_hoogerbrug · Accepted solution]

Hello Misha, please check the BELNR and XBLNR number ranges when importing the bank statement. The system will only recognise numbers form the note to payee if they are within the defined number ranges.

[Misha13 · Accepted solution]

I tried using both BELNR and XBLNR number ranges, but they didn’t work. However, I’ve successfully created search strings to recognize the customer based on the account number. The issue now is that the system still doesn’t pick up the document number from the statement.

[henk_hoogerbrug · Accepted solution]

Can you please share the note to payee information (from the bank statement) and the invoice number/reference number you want to clean?

if the invoice number is already in the note to payee, you do not need a search string.

if the invoice number is not complete in the note to payee, you can use a search string to search for a specific pattern and convert it into an invoice number.

[Misha13 · Accepted solution]

Below, you can find the data from the statement (910********) and the system. Sap does not match both numbers.

I tried to build a string, but don't know exactly which target field I need to use.

[henk_hoogerbrug · Accepted solution]

please check if you have assigned the interpretation algorithm to the external transaction code. You have to assign the posting rule AND interpretation algorithm to the external transaction code.
If you have assigned interpretation algorithm 000, the system will not search for any number. If you assign 001 it should work in this particular case.

[Misha13 · Accepted solution]

I have assigned the interpretation algorithm 000 to the external transaction code. When it was 001, the system was not reading anything, and the strings were not working

[henk_hoogerbrug · Accepted solution]

for the example you shared you don't need the search string, because the invoice number is already in the note to payee. If you then use algorithm 001, the system will recognise the number in the bank statement and add it to the clearing information in table FEBCL. You can also use the search strings in combination with algorithm 001, please check which algorithm you have entered in the search string usage customizing.

[Misha13 · Accepted solution]

I tried once again to run the statement with algorithm 001. Unfortunately, nothing has been matched. Is there a possibility to combine algorithm 001 with strings? For strings I use algorithm 000

[henk_hoogerbrug · Accepted solution]

yes that is possible (within the search string usage customising where you currently have 000). But if algorithm 001 doesn't work, you can also keep 000.

But please check the following, because 001 must work in your case:

1. The invoice has not yet been cleared in an earlier test
2. Posting rule setup according to my first comment.
3. External transaction assigned to the posting rule AND algorithm 001
4. No search string activated.
5. During import (FF_5 or other transaction) the BELNR number range must be 0 - 9999999999 (XBLNR is not relevant in your case)

Best Regards,
Henk Hoogerbrug

[Misha13 · Accepted solution]

Hi Henk,

Thank you for your input.

I followed your recommendation, and the system has started recognising document numbers, which is great progress. However, I’ve noticed that the customer number is no longer being picked up in FEBAN, likely because the search string is deactivated.

Additionally, I’d like to ask if it's possible for the system to also recognise quotation numbers, proforma invoice numbers, and support reclassifications—all via search string logic. Would this also be achievable?

[henk_hoogerbrug · Accepted solution]

that's good news.

You can add search strings to the standard algorithm to recognise more numbers. Please note that the system tries to find accounting documents, because that are the documents to be cleared.
So you can use a search string to find the quotation number, but normally it cannot be used to clear accounting document numbers.

Of you are requesting your customers to make advance payments (before you have created/send the invoice), you should investigate the down payment functionality and clear the incoming payments against the down payment requests.
Down payments can also be integrated in SD processes.

Best Regards,
Henk Hoogerbrug

[Misha13 · Accepted solution]

Could you please advise how to add a search string to the standard algorithm? When I try to activate my strings, either they don’t work correctly or the system pushes the data to advance payment. Regarding customer numbers, I’m not requesting advance payments. In our case, sometimes the customer numbers on the statement and in the system match, allowing the payment to be posted directly to the customer account.