SE16N Debugging MARV

[former_member678982]

Hi all,

In SE16N, Even after debugging switched on (/H), and inserting GD-EDIT & GD-SAPEDIT= "X" in variables , why the editable table do not appear???

Kindly suggest solutions!!

Thanks & Regards,

MP

[Abinathsiva]

Hi M P,

Modifying data of standard table through this way is not a proper approach, it will hamper the functionality..

[michael_piesche]

After setting GD-EDIT and GD-SAPEDIT to 'X' in the debugger, set a Watchpoint on those two variables to see how they get initialized again, which is what I assume is happening.

If you still dont know when and why they dont stay filled, check the Include LSE16NF10 and especially debug FORM FILL_SAP_EDIT.

But maybe you are just doing it wrong? Do you start out in SE16N, type in the table name, hit enter, type in /h and then execute it, and in debugger set those two fields?

When you switch tables in SE16N, you will have to do it again.

I hope you are doing this in your own system or a sandbox or a dev or maybe a test system but not in a productive system. If you are asking questions about SE16N in the community, you probably shouldnt be changing values 😉

[DominikTylczyn]

If you are asking questions about SE16N in the community, you probably shouldnt be changing values 😉 - that's a good one :)))

[former_member678982]

Hi Micheal,

I understand it's not legal to change values. But what if there is a serious issue and needs to be resolved. Currently, doing it in IDES system just to know..

To start, I go to SE16N, enter the table name, insert the key values, then go to /H, and execute. After that put the variables..

However, it's not working may be due to no access.

Regards,

MP

[michael_piesche]

M P, please follow the other suggestions I made above.

1. After setting GD-EDIT and GD-SAPEDIT to 'X' in the debugger, set a Watchpoint on those two variables in the debugger to see when and why they get initialized again, which is what I assume is happening.
2. If you still dont know when and why they dont stay filled, type in &SAP_EDIT in SE16N (just before you want to execute the selection) and check the Include LSE16NF10 and especially debug FORM FILL_SAP_EDIT, set a session breakpoint in this form and see whether it does what it is supposed to. Since you filled GD-EDIT and GD-SAPEDIT directly, you might have to change some more values in debug mode here too, to successfully execute this form.

[former_member678982]

Hi Micheal,

MARV debugging done successfully. Posting periods changed in MMPV. But still citing an error for the same reason or the documents are unable to post in MIGO.

Why??

Hope for a correct solution to it!!

Regards,

MP

[michael_piesche]

saplmp, please elaborate on your current issue. Were you able to successfully change table entries of MARV via SE16N through setting GD-EDIT and GD-SAPEDIT in debug mode? And now you are having another, different issue with MMPV or MIGO?

[former_member678982]

Yes successful changed the table entries related to posting periods. But the document is unable to post in MIGO again showing the same error for posting periods.

Why is it so??

Regards,

MP

[michael_piesche]

saplmp, in this case I strongly suggest to close this question, as it is clearly has been solved. Either accept an answer or write your own answer and accept it giving clear guidance what the issue was and how you solved it, meaning why you initially had an issue with not being able to change database records via SE16N and how you finally were able to do so.

I hope you understand now, that simply changing values via SE16N is not always the best case, especially if you dont 100% know, what the outcome will be. It obviously did not fix your "serious issue" as you hoped for.

For your issue concerning MIGO and MMPV, I recommend researching the community first with keywords MMPV and posting period, e.g. look at the following community question: https://answers.sap.com/questions/12996501/posting-only-possible-periods-201304-and-201303-in.html. If you still cannot figure out what the issue is, open another question concerning MIGO and MMPV.

[DominikTylczyn]

Hello saplmp

It does work for MARV table. However better don't play with this table content so no to mess up MM posting periods.

Best regards

Dominik Tylczynski

[former_member678982]

Hi Dominik,

Thanks for your response.

People will not definitely play with the system, unless and until there is a situation like that. Community is there just to share knowledge. If u know the answer u can happily share else it's ok if u don't.

Regards,

MP

[DominikTylczyn]

Hi saplmp

I’ve just followed the usual steps to edit MARV in SE16N and they worked for me. Nothing special, nothing fancy, just the usual GD-EDIT and GD-SAPEDIT stuff. Hence the simple answer.

BR

Dominik Tylczynski