on 2023 Aug 17 8:53 AM
Gurus..
I have a scenario where the bank charges a direct debit for the credit card dues on a corporate credit card. in EBS (MT940) It appears like the below:
:61:2308160816D5600,00NMSC
:86:DEBIT TRANSACTION Credit Card Direct Debit 1234XXXXXXXX2345
There are some 15 credit card issued to different employees, the statement contains debits for the individual cards. now, my requirement is to post these transactions to the respective employees.
I tried through the posting rule as below:
Z31 1 40 Bank-OUT 50 Bank-MAIN ZQ 1
Z31 2 29 Z EE00100002 50 BANK-MAIN ZK 1
Assigned Z31 to NMSC transaction type. I am able to get this through for 1 employee, and also for multiple cards issued to 1 employee. But when I wish to have this for multiple employees, the same fails. Tried through string search as well, but could not achieve it. Any clues on how to handle the requirement?Appreciate your help.Regards / Rajan.Hi mridultii,
Something like that should be possible. The pre-requisite requirement is only one: note to payee in bank statement should contains some reference details that would allow you to uniquely identify your employee vendor in the system.
From what I understand, bank provides the reference as 1234XXXXXXXX2345. If that's so, you can try to leverage search strings to search for this number and change the vendor to a fix ID. But if you have 15 cards, you'll have to setup 15 search strings. I've described a similar scenario in my post, where I'm searching for a business partner based on a tax number.
But I'd not suggest to use the search string for that... first of all, it is a bit cumbersome and too complicated. It will require a lot of maintenance efforts besides, considering the length of the string you're looking for i.e. 16 characters, search string will easily fail as soon as there is any empty space. Besides, you have to maintain the vendor code in the settings of the string. Considering that you want to use it in production, you'll provide maintain the vendor code from production system. Question is: how do you plan to test it in DEV and QAS system ? To test something like that, you should have synchronized vendor ID across all systems.
A better way would be to do the enhancement via BADI FIEB_CHANGE_BS_DATA. There you have the table with note to payee details (T_FEBRE). You can leverage ABAP REGEX functionality to the full extent to parse the note to payee and find the reference. Once you identified the reference, you can search for the vendor. There you need to make a decision where to store the mapping between vendor ID & card number (or whatever reference you have).
If the vendor is found, you have to adjust C_FEBEP variables AVKOA = "K", AVKON = "vendor code". That's all. Once more, you can theoretically achieve the same via search string, but the maintenance efforts will be much higher and it won't be so reliable. You can trust me in that, I did these enhancements so many times that I can recite the pros & cons even if you'll wake me in the middle of the night.
Regards,
Bohdan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rajan,
I've checked once more the attributes of the posting rule from the original question. I guess there is a mistake (or a type-error) in the logic. Credit posting in the second posting are should balance out "Bank-OUT" GL account, not "Bank-Main". Second, I think the posting type in the second area should not be 1, but 2.
Assignment of the BTC NMSC - is ok. Not sure if you added any interpretation mechanisms, but just in case none is needed (i.e. there should be "No interpretation").
Otherwise, everything looks fine to me.
Regards,
Bohdan
User | Count |
---|---|
9 | |
4 | |
4 | |
3 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.