4 How SCM Works

This chapter provides an overview of how SCM works.

4.1 Setup and Configure Source and Target Environments

The ”source” application is where you do the customization. The "target "application is where you want to apply the customizing.

Before you can execute Export of Import, you must first setup or configure both the source application and the target application.

4.1.1 Overview of Source Application Setup

1. Define a vault where the loader files are checked in.

2. Set the LogiView constant EDB_SCM_CHG_DOC_ARE

3. Define the directory where the loader files are stored (EDB-FMS-ALLOWED-PATH)

4. Update the number variant for SCM. For more information see

For more information, see "Configuring the Source Environment" on page 5-1.

4.1.2 Overview of Target Application Setup

1. Update the number variant for SCM

2. Set the LogiView constant EDB_SCM_CHG_DOC_ARE

3. Define the directory where the loader files are stored (Refine the number server, number variant. EDB-FMS-ALLOWED-PATH)

For more information, see "Configuring the Target Environment" on page 5-2.

4.2 Select / Identify Modifications

There are several methods to assign an object to a bundle.

• Automatically by triggers

  SCM comes with triggers which automatically assign an object to the current bundle if the object has been changed. These triggers must be included as post action triggers in the corresponding (definition) forms.

• Manually by the user

  You can assign the current object to the current bundle by pressing Ctrl-A

• Automatically by searching for changes authored by a certain user and created or modified since a specified date and time.

The difference between CTRL-A and Post-Action Userexit is:

• CTRL-A

  If no bundle is active you are asked for the active/current bundle.

  The binary file has a variant number in the file name.

• Post-Action Userexit

  If no bundle is active, no changes recorded.

  There is no variant number in the file name.

4.3 CTRL-A

The basic CTRL-A process is:

1. Define a bundle where you book all modifications.

2. Set the bundle to active.

3. Perform customization tasks and track changes.

4. Use CTRL-A to book modifications to the bundle.

4.4 Export Modifications from the Source Environment

See Chapter 9, "Export Modifications from the Source Environment."

4.5 Import Modifications into the Target Environment

See Chapter 10, "Import Modifications into the Target Environment."