Data saving from a Z program into a Z table is not getting updated using SM30

[Former Member]

Hi Fellow Members,

I have a strange issue as follows.

I am reading data from IDOC (inbound) and updating it into my Z table.

After that when I try to update any value (that is update through the idoc) using SM30 for that Z table the record does not update even after the message Data was Saved.

Has anyone face this before. An old thread is there but this did not help as I have tried everything known to me while creating the TMG.

Also to clarify , I have deleted the TMG and recreated it, I have no events or custom module in the screen events. I have not changed anything in the screen layout or any property of the screen.

Thanks in advance,

Gaurav

[Former Member]

Hi

Have you checked what's happening in the routine for saving?

Max

[Former Member]

Hi Max,

Actually everything is passed through the save routines and the message is displayed.

Once I come out of the TMG and check the entries its again same as the old one.

Thanks.

[Former Member]

Hi

Yes that's ok, but a specific saving routine was generated, the message usually is triggered in that routine, but any validation is done: if that routine is triggered, the message will be raised.

So you should check if the date are really updated,

If you have used the fm group <ZXX> you should have the include L<ZXX>F00 having the form  DB_UPD_<Z-TABLE>, try to check there by debug

Max

[jay_kumar8]

Have you tried SE14...ACTIVATE and ADJUST DATABASE

and again create TMG.

Regards

Raj

[Former Member]

Hi Raj,

Yes I have tried that too.

Just that I have to try deleting the table and reacreting everything from the scratch only.

But this is strange isn't it.

Thanks

[former_member196331]

I have a small doubt. Any thing is happens to table. or the problem is at Sm30

Can u test it.

Go to Se16n /h Using Variables.

GD-EDIT

GD-SAPEDIT

Try to Add new Entries and update the Existing Rows.

[Former Member]

Hello team,

Thanks for the attention.

It was really a silly mistake of the characters getting updated in lower case while the domain does't accept lower case. When changing the data in TMG it was getting translated in upper case and mismatch of key fields avoided the database update.

I am still surprised with the success message after the failed update.

Hope this helps.