on 10-12-2009 7:04 AM
Hi Friends,
File to Abap Proxy interface was working fine for the past a month. Don't know what changes have got effected for this ... throwing the short dump like this.
Short text
Syntax error in program "ZWORKCL_WORK_MI_RECEIVER========CP ".
What happened?
Error in the ABAP Application Program
The current ABAP program "%_T00030" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"ZWORKCL_WORK_MI_RECEIVER========CP " in include
"ZWORKCL_WORK_MI_RECEIVER========CM001 " in
line 23:
"Accessing part of a field is not allowed for internal tables, deep str"
"uctures, or references."
" "
" "
________
I was trying to regenerate checking the and activating but still the Class and method is not identifying by the proxy.
When I check the MONI in ECC .. says System error in Queue. If I process it throws the dump.
Dont understand why the class is not identifying.
Thanks very mcuh.
Pothana
You could find out the exact issue by debugging the proxy with the inbound message from Moni
Check this
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
I think one of the structure or a deep structure has changed in the ABAP side . check it .
Check also the internal tables .....
Check if you are using any move-corresponding statement because both the structure got mismatch......
Regards,
Jude
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.