on 07-20-2009 3:05 PM
Hi,
I am doing some analysis in a MI Server where one of their issues is that they get a "FORM OF ADDRESS KEY IS NOT DEFINED". They get this error when they post MAM30_010 with data in Child 030 back to the R/3 system but the previous record also has a error that is unrelated to the data. For example, The user post data to a notification that is closed in the backend, therefore he gets a "NOTIFICATION ALREADY CLOSED" error. Then the next record which is just a Notification that post data in the Child 030 gets the "FORM OF ADDRESS KEY IS NOT DEFINED." If the previous records does not have a error then the data is sucessfully posted.
It seems that error gets triggered only if a error is triggered in the previous record although both records are unrelated (i.e. different Notifications) Any suggestions will be appreciated.
Thanks in advance.
Hi
both the error message appear to be validation being thrown from backend. In this scenario from the application in backend.
Also you can check the error handling in the client application with respect to rejection message coming from MI. As a response to first erroneous message sent by client, the response from server is a rejection message and client application is expected to update this information in its database. Only after that it is supposed to send further updates .
regards
pradeep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.