Macro Workbench Version Management in SAP APO

[former_member223083]

Dear all ,

I would like to discuss here in brief on advantages of Macro Workbench Version Management in SAP APO

1. Introduction to Macro Workbench Version Management

As of SAP Release 4.0 we can create versions of macro books. Is means that we can create back-up versions of a macro book. One can then continue making changes to macros. If we then decide to reject these changes later, we can then revert to a previous version.

2. Problem Statement

Without macro version management changes are made directly in the active version and the macro book is transported completely. However, when multiple people want to work on the same macro book, this creates problems when we have to move the changes made by only one person at a time.

3. Prerequisite steps for Macro Workbench Version Management

One must have authorization to change the selected macro book. This also means that one cannot create versions of the SAP macro books.

4. Features of Macro Workbench Version Management

We can only change a macro book in the active version. We cannot change any versions in version management. We must always start the Macro Builder directly from the macro workbench or from interactive planning, if we want to change a macro book.

When we start version management a table appears in which we can see:

• The version number - This counter automatically increases each time a version is generated.

• The request number - Each time you transport a macro book a version is automatically created. The request number is entered here and it shows

• The date and time when the version was created

• The user who created the version

• The description. If you create a version manually, this is the text you enter. Otherwise the system generates a text.

In version management we can:

• View individual macro book versions

• Compare two versions

• Delete a version

• Retrieve a version. This means that a new version of the currently active version is automatically created and the selected version then becomes the active version.

The active version is marked with a green traffic light. All other (inactive) versions have red lights.

5. Steps for Macro Workbench Version Management

1. Go into the Macro Workbench into the applicable Data View and go into Version Management.

2. We will see multiple versions as seen below. Versions are normally created when changes are transported or when created manually. The active version is marked with a green traffic light. All other (inactive) versions have red lights.

2. a. Select the version and click on “Retrieve”, if someone wants to make an older version active On confirming, the active version created would be a copy of the old version that is “Retrieved”.

Ensure you are first to make changes to macro

3. Before making any changes, go into version management and check if the last version was created by a transport request

Step 3a: If the last version was created by a Transport Request and that transport request is present in Production system then make your changes. The changes are now saved in the active version.

Step 3b: If the last version was created manually, contact the last change owner and check about the change. If the change is complete, does not affect your change and can be transported together, you can continue as in Step 2a. If this is not the case, retrieve the last transported version. This becomes the active version and you can build your changes on this.

4: When your changes are complete, create a new version and give a suitable description. Include a CD Number if possible.

The system will save your changes under your version. These changes will also be present under the active version.

5: Once you have screened your changes, transport the macro book. This will create a new version displaying the Transport Request No.

Note: Before you transport the macro book, check the last version was either yours or created by a Transport Request.

Important: Always, create your version after you make any changes!

6. Significance of Macro Workbench Version Management

Following are the significance of macro version management: -

1. With macro version management we can create back-up version of a macro book

2. If we decide to reject these changes later, we can then revert to a previous version

3. When multiple persons work on macros, it is much easier to identify and track who has done the changes first and move the changes made by one person at a time

References - http://help.sap.com

Regards,

Mrigendra Sharma