Locate and select one or more import files and click Open to return to the

4-22 Oracle Fusion Middleware Administrators Guide for Oracle Business Intelligence Discoverer ■ About creating EULs in Logical and Physical Standby or read-only databases What are identifiers? Identifiers are unique names that Discoverer Administrator uses to identify unique EUL objects and workbook objects in Discoverer Plus and Discoverer Viewer. Discoverer Administrator uses identifiers to recognize when an object imported from another EUL refers to the same business object in the EUL you are importing into. Identifiers enable customized or patched EUL objects to be preserved. For example, a folder named Sales in EUL A may refer to the same folder named Sales Figures in EUL B. Both folders have the same identifier and can therefore be recognized as referring to the same EUL object. Identifiers are visible in Discoverer Administrator but are hidden from Discoverer Plus users. Typically, you will never need to alter an identifier. Indeed, changing identifiers is not advisable because it can affect the relationships between EUL objects. However, in some cases you might want to modify identifiers. For example, you might want to modify identifiers: ■ to comply with strict naming conventions ■ to re-create an object with a specific identifier because the object was incorrectly deleted from the EUL and must be re-created with the same identifier In a future release of Discoverer, there will be a change to the valid characters that can be used in identifiers. The following characters will continue to be supported for use in identifiers in future releases of Discoverer: ■ the letters A to Z in upper case ■ the letters a to z in lowercase ■ the numbers 0 to 9 ■ the underscore character _ However, the following characters will be de-supported in future releases of Discoverer: ■ the exclamation mark ■ the tilde symbol ~ ■ the asterisk symbol ■ the left and right parentheses characters: and ■ the single quotation mark ’ ■ the hyphen character - For this release: ■ if you create an identifier that contains a de-supported character, a warning will appear ■ if you import an EEX file that has identifiers that contain de-supported characters, a warning will appear in the import log ■ if you upgrade an EUL that has identifiers that contain de-supported characters, messages will be displayed indicating the identifiers that contain the invalid characters