Renamings within Modeling Project

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

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 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:

0ALTITUDE
0CALDAY
0CALMONTH
0CALMONTH2
0CALQUART1
0CALQUARTER
0CALWEEK
0CALYEAR
0CURTYPE
0DATE
0DATEFROM
0DATETO
0FISCPER
0FISCPER3
0FISCVARNT
0FISCYEAR
0HALFYEAR1
0INFOPROV
0LANGU
0LATITUDE
0LONGITUDE
0PRECISID
0REQUID
0SOURCESYSTEM (in the planning stage)
0SRCID
0TCATADTO
0TCTACOMPM
0TCTATYPE
0TCTAUTH
0TCTHIEDATE
0TCTHIENM
0TCTHIEVERS
0TCTIOBJNM
0TCTNDEF
0TCTNIOBJNM
0TCTNODE
0TCTTLEVEL
0TIME
0WEEKDAY1
1ROWCOUNT