on 04-09-2014 6:50 PM
Hi experts,
I have made an application in SMP 2.3, which display Order detail.For this, i have used standard BAPI for displaying the order list.it is working fine.When i am entering wrong data, it is also giving me error.
Now, my requirement is to get the proper message from this error list.
Please have a look on the below screen:
This error comes, when i click on the Header details button, without entering any order.Although, error is quite right, but as mobile screen is no so much large.So,my requirement is to display, exact error info. i.e.(Enter Order Number(as indicated in above screen)).
Please suggest.
Thanks,
Rohit
Is this issue resolved ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In a SUP version when we are not creating an error screen by default it was bringing the error in an alert, but it's not happening now (SUP 2.2). But you can try whether it is working in that way for you. And, I haven't dig into the request/response code of online request to get the error in an alert.
Midhun VP
I can give you an alternative solution for this,
You will have 2 error screens, ErrorList and ErrorDetail.
Create a new screen called Error.
Go to ErrorDetail in the designer.
Click on the ListView in the ErrorDetail screen> Go to properties.
Assign Listview Detail Screen property with newly created Error Screen.
Hence you will get two keys in Error screen: Name and Value.
Create 2 editboxes in the Error screen and map the edit boxes with these keys, when the user reaches the screen ErrorDetail and click on message he will be able to see the error message properly.
Again, you can change the message description on the Error screen by writing custom code in custom.js.
Midhun VP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, Rohit--
This is the whole layer that you need to consider of mapping the low level errors from the back end to the end user screen.
My recommendation is to handle this at the back end.
Cheers,
Fouad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rohit,
Error messages typically come as an aggregation of different parts of the Return Message from a BAPI (ERROR_TYPE, ERROR_NUM, ERROR_MSG_1, ...). I may have the field names wrong, but you can investigate in SE37 or BAPI t-codes to see which errors generate what content in each field. I suggest using the test functionality there and review the field results to see which returns what sort of data. You should then be able to select the appropriate field to report rather than the aggregated result of several fields.
A note of warning. Any single BAPI has been created for different purposes, by different developers, over many years (decades in some cases), and with different data organization (and varying amounts of documentation with not much and not well written as the general rule). Don't assume that the same field of the Return Message contains the information of interest when you go from one BAPI to another. I have found that testing each BAPI is the safest way to proceed.
Regards, Mike
SAP Customer Experience Group - CEG
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
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.