Being an SAP ABAP Developer sometimes feels like being the designated scapegoat of the SAP world. Any hiccup, any glitch, and suddenly the whole world conspires to blame the developers. Just like for any airplane crash, the poor pilots are the easy targets. No, we did not refer to BOEING.🛫💥💥
Well the other day my functional friend showed the below error. “Account 123456 0143 defined for tax postings only” during dunning run FPVA/FPVB. I was quick to hint, Amigo, it looks like a config issue. Can you please check with our FICA expert if he has maintained the G/L correctly? I tried to rub off this responsibility from my shoulder. 😜😜 You know how busy ABAP Developers are. 😜😜 We do not need another debug session of configurations.🤭🤭

My friend goes back to his seat, disappointed (but he does not show it to me). He keeps looking at data. These are new error he knows and there was no configuration change moved recently. His gut feeling tells him, this has to do with some ABAP change. After one week, he comes to my desk again and gently says. Amigo, looks like some code change moved to production on 05/08 and the issue started from 05/09.
Me: OOPs, now that looks fishy. 🐠🐟
I scrambled through my transport list which moved on 05/08. And I was hoping there was none. 🤞🤞Not lucky. I did move one transport that night. I thought it looked harmless. But.. but.. There cannot be smoke without fire. 🔥🔥So I did the same what every developer does. Debug and see what is happening behind the scene. 🐞🐜🪳🪲
I debugged and debugged and did not find anything suspicious. I had a grim on my face. Thank Goodness. It was not me. The moment, I was about to proclaim my innocence, I stumbled on below entry.

In ISU SAP system, FKKOPK is the structure which holds “G/L Account Items in Open Item Account Document“. OK, my error is also for G/L Account. Why am I passing a 0.00 to the G/L? System does not like it. Although the error says Particular G/L Account is defined for tax posting only, the error for this scenario actually means, ABAP Developer, please pass some value for tax posting. Do not misuse me with 0.00 please.😉😏
So, after almost annoying my Functional friend, I realized, I was excluding some documents based one some logic and in that process, I was ending up with a late fee charge which rounded off to zero. This zero was causing the issue.
SOLUTION?
Simple. Do not send that entry at all when you do not need it. REFRESH the entry of FKKOPK if you are passing 0.00. DONE.


Please do not hold my neck for not writing in OOPs ABAP and Class Method. Also for not using FREE or REFRESH statement or modern ABAP. In my defense I have to say, I just reused an existing sub routine please. 😎😎
I am NOT saying, the error cannot be config. I am sure, most of the time, when you see the error “Account xxxxxx xxxx defined for tax postings only” it should be config error. The first thing to evaluate is the G/L setting. May be t-code FS03. But once the config move to production and works fine for all other cases, and only for your change it fails, you know it is time to introspect your code change. Sadly but true. 😜😛
If you go to the Performance Assistant, check the Diagnosis. It says only tax postings are permitted. But the solution is a the Procedure. It says, “If you entered the account number manually and it is incorrect, correct your entry“. If my case, I indeed passed incorrect entry manually and it is the root cause. I removed my incorrect data and boom. No more error.

NEW TRAINING ANNOUCEMENT
Enrolment Link – SAP BTP Overview and Administration
Day wise break up – SAP BTP Overview and Administration
Course Days – 26, 27 July, 2, 3, 9, 10, 16, 17, 23 & 24 Aug 2025 IST Dates
Time – 7:30 AM to 10 AM IST
Conclusion:
As a developer, we may be swamped with too many requests. Yes, 90 percent of time we get assigned tickets which should not even be assigned to SAP Team forget about ABAP. Yes the incident should have gone to the data ware house team, the process integration team or the web team. But ends up in your queue. Which is not at all amusing. But having said that, sometimes the unassuming error which obviously does not look ours, might actually be ours.
So, lets keep an open mind when some issue is assigned to us. Afterall, bugs and new enhancements keep us relevant. Thankfully AI bots cannot be logical and perform the complex business logic. Why? they cannot have custom business logic training data. At least for now. And what a real ABAP Developer can do, AI will never be able to do.
What do you feel friends? Apart from ABAP Programming, what all duties do you do as a Developer? Please COMMENT. It can be anything like, Help in Audit, Look after Month End Activities, Prepare Agile team Dashboard for upper management to report etc. Please mention yours.
If you are looking for Premium SAP Video courses to keep yourself abreast with the current skill set. Check our video training partner ZAPcademy.com.
SAP IS-U Process Overview
- ISU – 1 – Introduction
- ISU – 2 – Master Data in SAP ISU Overview
- ISU – 3 – Master Data, Customer Structure & Devices
- ISU – 4 – Installation, Meter Reading, Bill Order, Billing, Invoice and Invoice Printing Process Overview
- ISU – 5 – Payment Lot Processing Overview
- ISU – 6 – Bankruptcy Overview and Write-Off Process using BAPI_CTRACDOCUMENT_WRITEOFF
- ISU – 7 – FQEvents – How to Find & Implement?
- ISU – 8 – SAP Dunning Procedure & Process – Tips & Tricks
- ISU – 9 – Account XXXXXX Company Code XXXX defined for tax postings only ERROR – SAP FICA
Please follow our LinkedIn Page, LinkedIn Group , Facebook Page, Facebook Group, Twitter & Instagram.
Do not forget to SUBSCRIBE to our YouTube Channel for Free Courses and Unconventional Interesting Videos.