2008 Jun 30 8:03 AM
i am not an abaper, i am a pp functional consultant. i just encountered this error when i try to save and create my production order, the abap debugger appears saying that
1 &----
2 *& Include ZXCO1U06
3 &----
4 breakpoint
on the top part it says:
SAPLXCO1 / ZXCO1U06 / 4 SY-SUBRC 4
FUNCTION EXIT_SAPLCOZV_001 SY-TABIX 1
2008 Jun 30 8:52 AM
It's not an error as such. The program is doing exactly what it has been told to do.
If you go to SE38, and look at ZXCO1U06, you'll find that there is a statement "BREAK-POINT". This is hard-coded way of opening the debugger.
Your best approach is to find the developer responsible for doing this, and ask them to change it. If this is happening outside of development system - perhaps in test or production, then perhaps
a) The programmer needs to be disciplined shot
b) The development team need to introduce some review procedure of ALL coding, before transport.
Regards
matt
i am not an abaper, i am a pp functional consultant. i just encountered this error when i try to save and create my production order, the abap debugger appears saying that
1 &----
2 *& Include ZXCO1U06
3 &----
4 breakpoint
on the top part it says:
SAPLXCO1 / ZXCO1U06 / 4 SY-SUBRC 4
FUNCTION EXIT_SAPLCOZV_001 SY-TABIX 1
2008 Jun 30 8:52 AM
It's not an error as such. The program is doing exactly what it has been told to do.
If you go to SE38, and look at ZXCO1U06, you'll find that there is a statement "BREAK-POINT". This is hard-coded way of opening the debugger.
Your best approach is to find the developer responsible for doing this, and ask them to change it. If this is happening outside of development system - perhaps in test or production, then perhaps
a) The programmer needs to be disciplined shot
b) The development team need to introduce some review procedure of ALL coding, before transport.
Regards
matt
2008 Jul 01 8:25 AM
hi..just go to any abaper and tell him to remove this statement