Application Development 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: 

Cluster View not saving data

former_member324377
Explorer

‎2023 May 02 5:32 PM

685

Hello, I've a cluster view with 3 tables. All of them are header tables.

I'm calling this cluster view from a custom program using the FM VIEWCLUSTER_MAINTENANCE_CALL.

In DEV system, everything works fine but in QAS system is not (not an authorization problem).

I can add a new entry or delete one, but every time I try to change some data of an existing entry, I get the success message "Data was saved" (SV018) but the truth is, the data is not saved in the table.

Did someone already have this error?

Thanks

4 REPLIES 4

Sandra_Rossi
Active Contributor

‎2023 May 02 9:12 PM

0 Kudos
553

If it's a view cluster without any custom ABAP code then contact SAP support/check SAP Notes.

If you have custom ABAP code, then please post the custom code and explain more.

raymond_giuseppi
Active Contributor

‎2023 May 03 11:39 AM

0 Kudos
553

Have you not received any messages related to the transport or the client?

Does the SM34 transaction work when your program call does not?

former_member324377
Explorer

‎2023 May 03 11:57 AM

0 Kudos
553

I don't know if it's because I tried to do some changes directly in SM30 for the tables or if enter in SE54 and did a test of the cluster view (there also worked fine). When I got back to the custom program today (with a selection screen and a call to the FM VIEWCLUSTER_MAINTENANCE_CALL), the changes to the data were working. This is a very weird behavior.

Thanks to everyone that replied and tried to help.

Sandra_Rossi
Active Contributor

‎2023 May 03 12:15 PM

0 Kudos
553

Then probably it means that there were some data buffered, and your application server was out of sync.

Next time it happens (or anyone experiencing this), do this:

  • clear the SAP buffers, e.g. /$sync in the command field (be careful, tell the administrators/users as it will impact the performance to rebuild the buffers)
  • and repeat it on each application server (switch via SM51 as explained in the forum).
  • try again the view cluster

(of course, this solution may possibly work for anything else implying the SAP buffers, not only view clusters)