Renamings within Modeling Project

Open

The section “Renamings” saves all Renamings within a Modeling Project.

Open

Limitation of Renamings

A list of present InfoObjects which cannot be renamed or are not used as a proposal for Renamings can be found under “Renaming Restrictions”. Some central Objects, as for example 0LANGU, are excluded for any renaming process by the Docu Performer. These specific Objects have a grey background and can be hidden by the checkbox “Hide read-only restrictions”.

The list can be completed manually using the “Add” button. Not only Business Content Objects but also Objects in customer namespaces can be added to the list.

With a right-click or the “Delete” icon, Objects can be removed from the list.

All changes should be saved with the “Save”-button.

The objective is to ensure that:

• Central BW-Objects as 0DATE, for instance, cannot accidentally be renamed

• Own central InfoObjects are used on a cross-project basis

As a result, InfoObjects like 0FISCPER are deactivated when it comes to the renaming of InfoObjects:

When clicking the checkbox of Objects with the status “Not allowed for renaming” a warning emerges:

Objects with the status “Not proposed for renaming” are not initially activated, but can be done by selecting the checkbox. However, when using the automated renaming function during the import to the Modeling Module, those Objects commented “Not proposed for renaming” will be renamed.

Following Object names are forbidden to modify using the Docu Performer: