How to add new customer fields to a standard Maintenance view

[former_member373376]

Hi Experts

I have this scenario

I have a Maintenance view, that have a standard table

I can maintain the view with sm30, but I have added some customer field to the standard table with include and I want to include those fields in the view

is there any way to do that under the tab view fields.

Thanks

[raymond_giuseppi]

AFAIK you wont add your fields to the standard maintenance dialog without a sscr key. Did you

• consider creating your own customer dialog maintenance?
• check with SE11 for the Delivery Class of the Customizing class (Hope it's not a S-ystem table...)
• consider building a customer table with same primary key than standard one and a foreign key relation, and put your appended fields in this table...
• etc.

[former_member373376]

Thanks Raymond

The delivery class is C for both the standard table and view.

I can not build a customer table, the standard table is used in many programs

I just want to add the customer fields to the view, than I can customize with sm30.

Now only the standard fields are available.

BR

[raymond_giuseppi]

Either you call SE54 and change the standard dialog, but it will require a sscr key (it's a modification of a standard function group) Or build another dialog in your customer namespace (create a maintenance view with every field first and define the dialog on this view)

" the standard table is used in many programs

Did you actually intend to use your customer fields in each of those programs, what is the actual requirement, not the solution the initial requirement?

[former_member373376]

The requirement is to customize some customer fields for the creation of contract account, like interest calculation and strategy and so on.

I am thinking of taking a copy of the standard view to Z view add the required fields and create a new sm30 for the copied view.

please let me know if there is another solution.

BR

[raymond_giuseppi]

None without sscr key, as I suggested this solution too, I can only agree 😉