SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Showing results for 
Search instead for 
Did you mean: 

Note to Payee - several data in the same line

Former Member
0 Kudos
400

Hi everyone.


I have configured the Interpretation rules for Note to Payee. It works for the simple scenario where a subset of the whole line is one parameter that I need (for example: I can extract contract number from the note to payee, when its written in a form similar to this: contract_number-date-check_digit).


Our client wants the Note to Payee to consist of 3 numbers: contract number - contract account - month_year (for example: 10006722-2024472-314) as the regulations in our country allow only numbers and dashes to be in that field. Total field length is 22 characters (again, only numbers and dashes).


As I need to get both the contract number and the contract account number, I tried to set that up using options in Interpretation rules, but so far I havent been able to get it working. Does anyone has similar requirement or has an idea of how this could be achieved?


My config is as follows:

- Selection field: 1 Contract Account

- - Keywords: not used

- - Structure: Defined one structure line, with field length and partial transfer, with limited range (min and max value)

- - Assigned Selection Categories: contract account


What I tried is:

- adding new selection field (2 - Contract)

- adding new line in Structure section (second line with options like above, but for the contract number)

I would appreciate any help or ideas on this issue. Thanks in advance!

Marko

1 ACCEPTED SOLUTION

Former Member
0 Kudos
236

Since there are no replies, I will try to ask the same thing in a different way.

My current approach is to define as many parameters from the Note to Payee field as possible. That would mean identifying the bill which is paid in the Note to Payee (at the payment) level.

The other approach would be determining the contract account from the Note to Payee, and then dealing with identifying the bill itself in the clearing variants process.

Which of those two processes would be better approach? What are the practices in these cases?

Thanks!

Marko

View solution in original post

4 REPLIES 4

Former Member
0 Kudos
237

Since there are no replies, I will try to ask the same thing in a different way.

My current approach is to define as many parameters from the Note to Payee field as possible. That would mean identifying the bill which is paid in the Note to Payee (at the payment) level.

The other approach would be determining the contract account from the Note to Payee, and then dealing with identifying the bill itself in the clearing variants process.

Which of those two processes would be better approach? What are the practices in these cases?

Thanks!

Marko

0 Kudos
236

Hi Marko,

how did you resolved it? I have a similar problem.

Regards

M.

0 Kudos
236

Hi Marcos.

Unfortunately, I didnt completly resolve the issue. I set the note to payee in such way that the first information is contract account, which I can then identify. The second step was configuring the settlement/clearing control in several steps, in the way that the correct bill gets cleared. Its a workaround, not a solution. And Im still looking for a good way to handle it.

Marko

0 Kudos
236

Hi Marcos.


I resolved the issue in the following way:

- enabling Classification Key (under Prepared enhancement) - This gave me classification key in FI-CA documents.

- filling the Classification Key field in event R429 - event is triggered during invoicing, which is exactly what I needed. With custom function module Im filling this field with the upper form: invoice number - contract account - month_year.

- configuring note to payee interpretation rules - Im having rule which has selection category Classification Key.

- upgrading the clearing rules / variants with the Classification Key field.


Combining these options gave the solution to the issue.


Hope this helps to resolve your business case, too.


Marko