Use of ampersands in Planning object types under EPM 11.1.2.2 and Oracle ADF
We've got a few Planning applications where the use of ampersands
("&" ) is quite prevalent. We've already discovered that EPM
11.1.2.2 will not create a Plan Type (cube) such as "P&L". Support
stated that this is due to restrictions within ADF.
I need to know to what extent I can or cannot use ampersands in Planning 11.1.2.2/11.1.2.3 under Oracle ADF. We have one or more objects of the following types with and ampersand in the name:
Account
Alias
Attribute Member
Cube
Entity
Folder
Form
Group
Shared Member
User Defined Dimension Member
Has anyone run into this specific issue? I know this has been referenced here (Nancy D. in particular), but want to find out if some (or which of) of these object types are unaffected.
I need to know to what extent I can or cannot use ampersands in Planning 11.1.2.2/11.1.2.3 under Oracle ADF. We have one or more objects of the following types with and ampersand in the name:
Account
Alias
Attribute Member
Cube
Entity
Folder
Form
Group
Shared Member
User Defined Dimension Member
Has anyone run into this specific issue? I know this has been referenced here (Nancy D. in particular), but want to find out if some (or which of) of these object types are unaffected.
0