topic Re: problem editing data using SM30 - view dumps in Application Development and Automation Discussions

problem editing data using SM30 - view dumps

Former Member — Tue, 05 Nov 2013 13:59:24 GMT

hi there.

I got a table that contains interface data. Z-table.

No unluckily the client wants to edit the table content using tcode SM30. As the table contains some fields of type string I cannot generate a maintenance view on the table itself.

no problem with that. I try to get around that generating a maintance view that does not include the string fields and I do generate a maintenance view for that. So far everything works out fine.

But: once I try to call SM30 for the new maintenance view then it dumps.

Does anyone have a clue how to get around that?

Thanks for an answer.

Rob

p.s.

SAP-Release

EHP6 FOR SAP ERP 6.0

SAP_ABA 731

SAP_BASIS 731

Re: problem editing data using SM30 - view dumps

former_member201275 — Tue, 05 Nov 2013 14:04:05 GMT

Go to SE14 put your table name EDIT and then Adjust and activate it.

Re: problem editing data using SM30 - view dumps

Former Member — Tue, 05 Nov 2013 14:18:27 GMT

the object cannot be edited using SE14 / via DB utility

Re: problem editing data using SM30 - view dumps

arivazhagan_sivasamy — Tue, 05 Nov 2013 14:22:10 GMT

Please activate the table once again and generate the maintenance view once again.

Also check each data element and domains.

Regards,

Arivazhagan S

Re: problem editing data using SM30 - view dumps

RaymondGiuseppi — Tue, 05 Nov 2013 14:23:31 GMT

Not possible, read 777134 - Table maint. with strings:No maintenance dialog generation

Despise your attempt to "lure" the system with a maintenance view , the generated program is not able to map data top actual database table, remember maintenance views don't exist in database, those are only some "interface" which generate code in dialog maintenance generated program.

Regards,

Raymond

Re: problem editing data using SM30 - view dumps

Former Member — Tue, 05 Nov 2013 14:27:14 GMT

sounds reasonable and makes sense.

it seems I will have to discuss changing the string field on the basis table with the customer.

thanks