on 05-14-2020 9:34 PM
Hi
Adding to Veselina's comment,
When I check the table knb1 using tcode se11 (table display), BUKRS field is set as not null. Please check in your system also. It might be "white spaces". Somebody might have changed this field value in "classical debugger" or some other code might have updated wrongly(or somebody might have done accidentally or intentionally). You can also check the "created by" field and "date" fields for further clue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you enter company code in FD03 ? If not, key in the company code and execute.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What error message you were getting when you try to display that customer via FD03 or XD03?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My best guess is that the screenshot is from a sandbox or a development system and that this is the result of testing custom code or playing with function modules.
I hope you do not have a company code ' ' in the system...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If I understand correctly the screenshot, the value for BUKRS is blank.
In the systems where I checked, there are no such entries in KNB1 where BUKRS is with initial value.
I assume that you have already checked that no entry with company code <blank> exists in your system.
This is why I think that this entry was not created in the usual way, e.g.via XD01. I don't know, maybe you have some custom programs that you use to create master data. Another (very unlikely) reason might be that somebody manually modified the entry with direct update. This should not be the case in a productive system, but it may be a good idea to look for tickets about this customer in whatever tool you use for recording work on incidents.
I am not aware of correction notes causing such side effect. I did a quick search, so I might have missed something.
Did you check whether you have implemented any notes recently, performed an upgrade, activated business functions?
This would be the first thing that I would do in such cases.
User | Count |
---|---|
89 | |
8 | |
7 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.