‎2021 Jun 29 10:06 PM
Dear All,
I have observed the below syntax error in standard include MF05LFB0.
"Field "BSEGL" is unknown. It is neither in one of the specified tables "
I have recently downloaded a note which modified above include. I also observed same syntax error in quality system and production system. Also observed same error in other systems where this include exists.
Can anybody kindly guide what must be the reason for this error?
Regards.
‎2021 Jun 29 11:01 PM
I want to move the include to quality and production system. Being in syntax error state the TR will fail.so kindly help.
‎2021 Jun 30 4:37 AM
Hi!
If you got the syntax error when implementing the Note, you should probably contact SAP Support, but I assume you are talking about now that you went into SE80, opened the include and performed a syntax check there manually?
In that case...Well, the include does not know what BSEGL is as it's not declared in there. Instead, you need to do the syntax check on the main program. The program that uses the include.
You do that either by going to that main program to do the check, or Ctrl-F7 in the include. (Menu option Check -> Master Program)
‎2021 Jun 30 8:06 AM
Dear Jorgen,
Thanks for kindly replying.
Can you kindly confirm whether my TRansport request will fail because of this syntax error.
Regards.
‎2021 Jun 30 9:56 AM
I can leave no guarantees whatsoever without access to your system and transport. 🙂
But based on what you describe, if you simply implemented an SAP note and in that process put it in a transport... If the note fixed whatever problem it was supposed to in development system... Then this will also work in the test system when you import that transport there.
Syntax checks on an include alone may give this kind of errors, as it's meant to be used by a main program. You get no syntax errors when checking the main program, right?
‎2021 Jun 30 7:14 AM
You say "I want to move the include" (to quality and production system), I would rather say "move the SAP note" because after applying a note automatically, you should assign it to a new transport request, which will then contain all the relevant objects and the R3TR NOTE object.
‎2021 Jun 30 8:16 AM
‎2021 Jun 30 8:34 AM
The transport will issue a non-zero return code, but the code change will still be put through.
‎2021 Jun 30 8:54 AM
I think you are performing syntax check for single include MF05LFB0.
As the definition of BSEGL exist in top include MF05LTOP_ALV, so if you perform syntax check for MF05LFB0, you will get this syntax error. But if perform syntax this way: Menu>Program>Check>Master Program, you will not get the error.
This is a normal behavior of complier, You could also get this error in import log, just ignore it(it is harmless, you will not get runtime error when you execute the coresponding transaction/program). See Note: