Your Hyperion Planning application may or may not have multiple Plan Types depending upon the clients requirement. If it is only one Plan Type in your application then Plan Type association concept is pretty straight forward which Hyperion Planning handles by default. But while designing a multiple Plan Type application you should have clear understanding on the plan types association with members and their accessibility within other Plan Types and artifacts. Keeping Multiple Plan Types in your application may be to meet the specific requirement of the client or any implementation logic used by the Application Developer or any other planning modules like Workforce or Capex. Hyperion Planning saves spaces by using a reference to the source Plan Type in background if a member is used in multiple Plan Types.(Except the Member is not linked to the source Plan Type). So, for a multiple Plan Type Hyperion Planning application we will clear our doubts by going throu...