Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Maintenance view - error message

Former Member
0 Likes
1,051


I have created a maintenance view using two tables as join and created a table maintenance for the same. However when i try entering data into the view, i get field validation error.

Entry 'A xxxx' does not exist in xxx check entry(RSTHIERNODE).

i have picked value from the search help (so value is actually correct), However i realized there is a OBJVERS field value 'A' prefixed to the value 'A xxxx' in the error message.

Thanks & Regards,

Tashi Norbu

7 REPLIES 7
Read only

Former Member
0 Likes
995

HI Tashi,

I think A is just an alias for the table.

and coming to field validation, does this value you entered stisfies the both tables ? I think we need to check this.

Please publish your opinion on the same.

Regards,

Bhaskar

Read only

0 Likes
995

Hi Bhaskar,

     The 'A' is the OBJVRS field from the secondary table.

When i created a maintenance view, The following condition was automatically created.

RSTHIERNODE OBJVERS EQ 'A' AND

I have a field this condition is some how affecting the value.

Please see the error message.

Entry  A 0015 does not exist in RSTHIERNODE (check entry)

This 'A' value on top is extra .. i dint enter this value.

regards,

Tashi

Read only

0 Likes
995

Tashi,

Can please mention the full condition which is automatically created ?

Regards,

Bhaskar

Read only

0 Likes
995

Given is the full condition in the maintenance view:

RSTHIERNODE OBJVERS EQ 'A' AND

thanks,

Tashi

Read only

0 Likes
995

Hi Tashi,

I am clue less with this.

But you can get the message class and number by clicking on the message.

after giving the value, give /h in the command bar and press enter for debugging mode.

in the debugging mode put a break point at that message and press F8.

system will stops the exection at that point.

so then we can analyse from where this is being concatenated.

Regards,

Bhaskar

Read only

0 Likes
995


Hi Bhaskar,

     I got lucky .. solved it..

The issue was caused becoz of a conversion exit present for the domain in the field of the check table.

In my maintenance view, The TMG created maintenance screen with conversion exit attached to it, So it was causing a mismatch in the check table.

I remvoed the conversion exit in the TMG generated screen, and now it match. Hence i could maintain the data in the maintenance view.

Thanks Bhaskar,

Regards,

Tashi

Read only

0 Likes
995

Hey Tashi,

Thats great,

we should always make use of debugger in ABAP.

Please mark this question as answered.

Thanks,

bhaskar