topic Re: Maintenance View customize in Application Development and Automation Discussions

Maintenance View customize

Former Member — Sun, 05 May 2013 14:29:45 GMT

Hi everybody,

I encountered one problem that I don`t know how to solve , that is :

I use maintenance view to maintain data , but the data in this table can have up to 1 line, so in the maintenance view ,when click "new entries" or "copy", it make sense to check if the DB is have one line already, and pop up the messages. But I don`t know how to do this .

And another question , I want to display the maintenance view`s column according to the configuration of from other table ,for example ,read data from other table , in one condition, all columns of table is displayed for maintenance , in other condition, only some columns are displayed for maintenance ,some columns are hidden, how to do this?

Thanks very much.

Best regards,

Xu Chris

Re: Maintenance View customize

arindam_m — Sun, 05 May 2013 16:01:06 GMT

Hi,

You can code the check in the PBO(Process Before Output) module of the maintenance view for the table to check if the DB is have one line already, and pop up the messages.

I think for the second requirement You will have to Put the logic to do so IN the PBO module again. The besy advice will be to design your screens and maintain rather that SM30 will give you better flexibility to design all the requirements.

You can get started with Screens and Module pool programming. Some links to help you.

http://help.sap.com/saphelp_40b/helpdata/en/9f/db9d0335c111d1829f0000e829fbfe/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/47/a19fd982841503e10000000a42189c/content.htm

Cheers,

Arindam

Re: Maintenance View customize

Former Member — Sun, 05 May 2013 19:09:32 GMT

Hello Cris,

what i will suggest not to use maintenance view for this as you have very customized requirement. instead use ALV for saving data or create a module pool. I will prefer ALV as the development time would be faster.

Regards

Animesh

Re: Maintenance View customize

kakshat — Mon, 06 May 2013 03:42:22 GMT

Hi Chris,

Since your table will have only one entry, if it's a client dependent table, have you considered making the MANDT (Client) field (and only the MANDT field) a key field? If you do that, the system should not allow making another entry automatically.

Regards,

Akshat