Dynamic members are members that users can create when working with business rules. They're sometimes referred to as “on the fly members”. An administrator enables end users to create dynamic members under a parent member and must refresh the database to create the required placeholders in Essbase. In business rules with runtime prompts, users can then create members by entering desired member names in the runtime prompts. Subsequent database refreshes will rename used dynamic children to the names specified by the end users and recreate the required placeholders in Essbase. For information about working with business rules and dynamic members, see Oracle Hyperion Calculation Manager Designer's Guide.
If a parent member is enabled for adding dynamic children (as described in this section), users can create new members by entering their name in the runtime prompt.
Edit the parent member and select the option Enable for Dynamic Children (see Adding or Editing Members).
Optional: Set the member property Number of Possible Dynamic Children (the default is 10). This setting determines the number of placeholders that are created for dynamically adding or loading members under the parent. If all placeholders are used, subsequently added children are added as normal members and cannot be used until the database is refreshed.
Optional: Set the member property Access Granted to Member Creator (the default is Inherit).
Create a business rule with a runtime prompt (of the Variable type Member). Under the Dynamic Member Parent column, use the Member Selector to select the parent member that you enabled for dynamic children in Planning.
For information about working with business rules, see the Oracle Hyperion Calculation Manager Designer's Guide.
In Oracle Hyperion Calculation Manager, selecting both the Create dynamic members and the Delete dynamic members options enables temporary dynamic members to be created for calculations, and those temporary dynamic members will be deleted after the business rule completes.
Selecting the Delete dynamic members option alone presents the end user with the Member Selector in the runtime prompt so he can delete any member that he created dynamically under the parent (if he has write access to that member). This enables the end user to have full control over cleaning up and managing the members under the parent. The key is proper design to fit your requirements, setting the appropriate access rights to dynamic children with the Access Granted to Member Creator member property.
If all the above conditions are met, when users run the business rule with the runtime prompt, they enter the name of the dynamic member, and then click Launch. If the business rule runs successfully, the member is created in the dimension hierarchy under the dynamic member's parent.
Child members that you import under parent members enabled for dynamic children are added as dynamic child members if there are dynamic member placeholders in Essbase. After the placeholders are full, any remaining children are added as normal members, and cannot be used until the database is refreshed.
If you load a parent member that is enabled for dynamic children and its child members during the same import, the child members are loaded as normal members. This is because the database must be refreshed to create the placeholders in Essbase.