Abstract: Techniques are described for automatically selecting default dimensions of multidimensional data for publication. A computer-implemented system, for example, includes a data store having multidimensional data. The multidimensional data includes one or more data cubes having dimensions. The system further includes a publish module for accessing the data store and publishing the multidimensional data associated with the data cubes. The publish module selects a default dimension for publication for each of the data cubes based on attributes of the dimensions.

Abstract: Techniques are described for publishing multidimensional data from an enterprise software system. A relational database schema is automatically created for storing the multidimensional data. The database schema may be a relational star schema as described herein. The techniques may include processes for automatically producing the database schema based on the organization of the multidimensional data cube, and for populating the database schema with data from the data cube. The database schema may be used for reporting the multidimensional enterprise data, or may serve as a staging area to move the enterprise data toward a data warehouse within an enterprise software system. The reporting schema may support heterogeneous data types and heterogeneous formats. The reporting schema may also contain metadata that describes the schema, allowing for enhanced interpretation of the database schema. Also described is a process for automatically generating a reporting model from the database schema.

Abstract: Techniques are described for automatically selecting default dimensions of multidimensional data for publication. A computer-implemented system, for example, includes a data store having multidimensional data. The multidimensional data includes one or more data cubes having dimensions. The system further includes a publish module for accessing the data store and publishing the multidimensional data associated with the data cubes. The publish module selects a default dimension for publication for each of the data cubes based on attributes of the dimensions.

Abstract: Techniques are described for automatically selecting default dimensions of multidimensional data for publication. A computer-implemented system, for example, includes a data store having multidimensional data. The multidimensional data includes one or more data cubes having dimensions. The system further includes a publish module for accessing the data store and publishing the multidimensional data associated with the data cubes. The publish module selects a default dimension for publication for each of the data cubes based on attributes of the dimensions.

Abstract: An enterprise planning system includes a plurality of application servers, and an administration console to generate a deployment map that associates each of a set of enterprise planning models with a respective set of the application servers. The administration console, either automatically or in response to input from a system administrator, may finely control the allocation of computing resources to enterprise planning. The administrator console may adjust the deployment map based on approaching deadlines for the enterprise planning activities. When administrating a task associated with an enterprise planning activity, the administration console may break the task into a number of jobs, each job associated with a different slice of the model in accordance with the organizational hierarchy defined by the model. Consequently, allocation of computing resources to enterprise planning may be finely controlled, and may be adjusted to meet the current needs within the organizational hierarchy.

Abstract: Techniques are described for publishing multidimensional data from an enterprise software system. A relational database schema is automatically created for storing the multidimensional data. The database schema may be a relational star schema as described herein. The techniques may include processes for automatically producing the database schema based on the organization of the multidimensional data cube, and for populating the database schema with data from the data cube. The database schema may be used for reporting the multidimensional enterprise data, or may serve as a staging area to move the enterprise data toward a data warehouse within an enterprise software system. The reporting schema may support heterogeneous data types and heterogeneous formats. The reporting schema may also contain metadata that describes the schema, allowing for enhanced interpretation of the database schema. Also described is a process for automatically generating a reporting model from the database schema.

Abstract: Techniques are described for automatically selecting default dimensions of multidimensional data for publication. A computer-implemented system, for example, includes a data store having multidimensional data. The multidimensional data includes one or more data cubes having dimensions. The system further includes a publish module for accessing the data store and publishing the multidimensional data associated with the data cubes. The publish module selects a default dimension for publication for each of the data cubes based on attributes of the dimensions.

Abstract: An enterprise planning system includes a plurality of application servers, and an administration console to generate a deployment map that associates each of a set of enterprise planning models with a respective set of the application servers. The administration console, either automatically or in response to input from a system administrator, may finely control the allocation of computing resources to enterprise planning. The administrator console may adjust the deployment map based on approaching deadlines for the enterprise planning activities. When administrating a task associated with an enterprise planning activity, the administration console may break the task into a number of jobs, each job associated with a different slice of the model in accordance with the organizational hierarchy defined by the model. Consequently, allocation of computing resources to enterprise planning may be finely controlled, and may be adjusted to meet the current needs within the organizational hierarchy.