SAP Note 28463 - SE06 Setting up the Workbench Organizer

Symptom:

Operational ambiguities

Cause and prerequisites

The system is not initialized for the Workbench Organizer

Solution

Using SE06:
This transaction, for setting up the system for the Workbench Organizer has a few preconditions:

• What is the system status (depends on the past) ?

• Was the system freshly installed ?

• Was the system created by a database copy ?
  This option has more far-reaching consequences than the installation or the option: "modified with the Workbench Organizer". In addition, all repairs are completed and the tasks and requests which did not originate in the current system are also completed. The requests that can be transported are not exported.
  Furthermore, the control tables for the upgrade and transport are initialized.

• Has the Workbench Organizer already been used ?
  By 'use', we mean objects have been changed with the Workbench Organizer. Tasks or requests have been created.

• Which configuration of the systems is to be created (where are the objects created/changed and where are they to be transported to) ?

• Individual system
  Only 1 system is installed from which no objects should be exported. Everything required to import a new maintenance level or release is generated.

• Test and production system
  A system group should be created which consists of a test system (create, change and test objects) and a production system.

• Any configuration
  You can define another system group here. In this case, the tables for the definition of the system group must be individually maintained. A consultant should be brought in to model any non-standard system environment. A check function exists to aid the correct definition. A message log is generated and the long texts can be displayed using help.

• 3 system group (from Release 3.0C)
  The system group consists of a development system (create, change objects), a quality assurance system (test objects) and a production system.
  The requests from the development system should first be imported into the quality assurance system before they are imported into the production system.

After entering the configuration and the respective systems, a list of the table entries that need to be generated is displayed. You can save the settings with the function Continue.
If this changes the consolidation methods of the system, a corresponding information popup appears.
Typical problems when using SE06

• The creation of a transport layer is refused because at least one of the specified systems is not listed in TSYST.
  Enter the required systems in the maintenance of TSYST and save the newly entered systems.

• When maintaining TASYS - Do you allow non-standard transports or not?
  Generally, they should not be allowed.

• Problems with the requests
  No requests are deleted. All requests are retained. Repairs and external requests are completed when using "Database copy".
  Note that problems occur with the number range of the requests if frequent database copies are made. If, for example, you imported a request from a system E11 and then rename the system E11, then the usable number range begins with the highest E11 request.