Community
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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

SE54 - View Cluster maintainence problem

Former Member

‎2009 Sep 03 8:06 PM

0 Likes
2,578

Hello Guys

I'm creating a VC for bunch of tables which is working fine but for one of the table it give me error message when I enter data and save it. Error is:

Please only enter valid values.

Message no. SV530

Diagnosis

You have entered a value which is formally correct, but not allowed in this context.

Table maintenance is working fine when I save directly from the table. Only using VC gives the problem.

Any valuable input will be highly appreciated.

Regards

Ajay

Hello Guys

I'm creating a VC for bunch of tables which is working fine but for one of the table it give me error message when I enter data and save it. Error is:

Please only enter valid values.

Message no. SV530

Diagnosis

You have entered a value which is formally correct, but not allowed in this context.

Table maintenance is working fine when I save directly from the table. Only using VC gives the problem.

Any valuable input will be highly appreciated.

Regards

Ajay

Reply
3 REPLIES 3
Read only

Sandra_Rossi
Active Contributor

‎2009 Sep 03 8:37 PM

0 Likes
1,571

Maybe there is a foreign key in your view/table which links to another table in the view cluster which is not already saved... Or something like that. Or maybe a SAP bug (check sap notes). You may also add break-point to MESSAGE statement, and then you can back-debug when you reach the MESSAGE sv530

Read only

Former Member
In response to Sandra_Rossi

‎2009 Sep 04 9:03 PM

0 Likes
1,571

Thanks Sandra

Actually the problem is resolved just after I posted. You are right as it was related to the primeray key/foren key relationship, which was getting generated automatically after I click on 'field dependence' button.

I manually remove the kew relation among tables and it worked fine.

Anyway, your answer is close ot I would say its right. So I'll be awarding you the points.

Regards

Ajay

Read only

abaprogerio
Discoverer

‎2021 Jul 22 10:51 PM

1,571

Actually, the problem is not in the foreign key relationship. You can leave it there.

When you created the se54 cluster view, you have probably used field-dependence button, which generated field dependence for the table fields that you have foreign keys. You just need to select your table, go to Field-dependence level, and remove those entries. Leave only your view/table name, and itself as the predecess. This way, it won't have any dependencies when the value is empty...

It worked for me.

Sorry for the late (12 years) reponse 😉 But I hope that this can help other people that face this same issue.