cancel
Showing results for 
Search instead for 
Did you mean: 

FEBAN custom interpretation algorithm can be combined with search string functionality?

0 Kudos
856

Hi experts,

I have the following question:

For FEBAN - for the automatic clearing of customer invoices with the incoming payments - a custom interpretation algorithm ZFIEB_9nn_algorithm Function module - was built.

What it does is derive the customer number and so find the open items in the BSID table by the ZUONR. The new custom algorithm comes in helpful whenever no reference number is in the Note-to-Payee but the customer number (ZUONR) can be derived.

Before we had the custom interpretation algorithm we were using standard algorithm '001' for this, to find open items by the reference number (XBLNR).

I built some search strings (OTPM) that remove spaces from the reference numbers in the Note-to-Payee.

So 12 23456 will become 1223456.

Now with the new custom algorithm these search strings are no longer interpreted: I see a number 12 23456 is not changed to 1223456.

Question is: what we would want is the best of both worlds, so custom interpretation algorithm + the search string functionality to remove the spaces.

Does anyone know a way to achieve this - or else maybe some example programming to remove the spaces from the reference numbers?

View Entire Topic
0 Kudos

Hi again,

I just found a Note that might provide the solution:

2183277 - FF.5: Customer-specific interpretation with initial T_AVIP_IN

Will try and tell if this indeed solved it.