Additional customer customizing - howto?

[Clemenss]

Hi,

this is just a comon task and I hope for valuable ideas:

It is a common task to do additional development of user exits, badis or customer-specific programs.

As it is no good practice, to use any customer-specific constants in ABAP code, we put thos values into customer customizing tables and create maintenance views for them.

But, for lack of documentation, people changing, processes stable for a quite long time, those tables get forgotten. When a change is required, it is hard to find out where to do what.

Recently we set up a complex interface for incomind SD objects. The customer already established a transaction similar to SPRO (with Transaction SIMGH) and we could create nodes for all customizing maintenance.

I think it would be better, to create extensions to the standard SPRO tree. Is this possible without modifications or which way is the best?

TIA,

Clemens

[Clemenss]

Yes, we can!

S_IMG_EXTENSION

is the name of the transaction. Define an extension ID in customer name space, nodes, activities, documentaion and everything - fine!

Regards,

Clemens