During customer development, customer-specific objects are created in the customer namespace.

Pay attention to the following when developing your own programs and modules:

How might authorizations be distributed amongst your developers?

Four areas of responsibility come into play here:

• Maintaining ABAP Dictionary elements such as tables, data elements, and domains
• Maintaining database tables
• Maintaining objects such as module pools, function modules, screens, and so on
• Writing documentation

Authorizations relate both to the object type (program, table, package, and so on) and to the activity (change, display, create, activate, and so on).

You need to find a way to allow your developers some freedom while ensuring system consistency.

You might assign authorizations as follows:

• Give developers authorization to edit all programs within an application (this authorization is assigned using the corresponding packages) and to display all ABAP Dictionary objects. Also allow them to create and activate structures and views (data in the database cannot be changed by structures or views).

• Give the person(s) responsible for the ABAP Dictionary authorization to create and activate all Dictionary objects. Give the person(s) responsible for the database authorization to create tables in the database.

• Documentation developers should have appropriate authorization for writing user documentation for the objects (developers may, however, choose to do this themselves).

All SAP objects have an original language; this is the language in which the object was created. To simplify the customer development process, you should agree on a development language in which all objects are to be created.