Data entry commentary and sheet reconstruction for multidimensional enterprise system

A computing device is described that includes a user interface to receive contribution data of an enterprise and to display a sheet of the contribution data, an annotation interface module to receive one or more annotations for objects of the contribution data, a planning application to retrieve a context definition defining a context in which each of the annotations was received, and an annotation table to store each of the annotations and the context definition corresponding to each of the annotations. The user interface may be configured to output the annotations. The computing device may improve the collaborative process of developing multidimensional data. Users of the computing device may quickly and easily share their thoughts, questions, and comments about the data through annotations. Recreating an annotated sheet may be done efficiently by storing relevant coordinates.

TECHNICAL FIELD

The invention relates to enterprise systems, for example, enterprise planning and performance management systems.

BACKGROUND

Enterprise software systems are typically, sophisticated, large-scale systems that support many, e.g., hundreds or thousands, of concurrent users. Examples of enterprise software systems include inventory management systems, budget planning systems, order management systems, inventory management systems, sales force management systems, business intelligence tools, enterprise reporting tools, project and resource management systems, and other enterprise software systems.

A computing device for a user typically connects to the enterprise software system via a computing network. The user computing device may provide an operating environment for concurrent execution of multiple planning applications that access multidimensional data stored to a cache on the computing device. Typically, the user computing device includes a cache to store datasets requested by the user. In many cases the cache stores complex, multidimensional datasets, i.e., data cubes, which the user computing device may download from the enterprise software system via the network connection.

Various users may enter, review, and/or change data in an enterprise system using the computing device. For example, a contributor may enter data in a cell, and a reviewer may review the data in the cell. The reviewer may accept, reject, or change the data. The reviewer may request that the contributor to look over the changes or re-work the data in light of the review when the reviewer changes or rejects the data.

SUMMARY

In general, the invention is directed to techniques for annotating data of an enterprise system. An enterprise system may store data in one or more multidimensional databases or data cubes. A user of the enterprise system may retrieve, observe, manipulate, and/or store the data within a sheet presentation of a view of the data. A plurality of users may cooperatively develop the data, and each of the users may need to recreate the same sheet of a particular data cube. The techniques described herein may improve the cooperative development of the data by enabling the users to communicate with each other through the use of annotations.

The techniques described herein may enable users to annotate various objects of the data. An annotation may include either or both of text-based commentary and attaching a file to the annotated data object. For example, a user may have a question or comment about a particular cell of a particular sheet. The user may be, for example, a reviewer who would like clarification about a particular data entry, such as how a different user, e.g. a contributor, arrived at the particular entry. An annotation from the reviewer may only be relevant with respect to a specific sheet. According to the techniques described herein, the enterprise system may store the annotation along with a context that defines the sheet and the coordinates of the cell to which the annotation applies. The context definition may define how to recreate the sheet, and the coordinates may identify a particular cell of the sheet. A computing device may use the context to recreate the sheet and the coordinates to identify a particular annotated cell.

The contributor may see that an annotation exists and instruct a computing device to recreate the sheet for which the annotation was relevant according to the context in which the annotation was entered. The contributor may then take an appropriate action with respect to the annotation. For example, the contributor may alter the entry or reply with an additional annotation explaining the reasons behind the particular entry. If the contributor replies with an additional annotation, the reviewer may again retrieve the data and see the original annotation as well as the annotation from the contributor. The techniques described herein may also enable a user to enter an annotation for other objects, such as the sheet as a whole or an entire data cube, and the techniques may permit other users to quickly recreate the view and observe the annotation.

In one embodiment, a method comprises receiving contribution data of an enterprise in accordance with a multi-level enterprise model, storing the contribution data within a database, receiving a first annotation for an object of the contribution data, retrieving a context definition defining a context in which the first annotation was received, receiving a second annotation for the object within the same context as the context in which the first annotation was received, storing the first annotation, the second annotation, and the context definition, and outputting the first annotation and the second annotation.

In another embodiment, a method comprises retrieving contribution data from an enterprise system, retrieving a first annotation for an object of the contribution data from the enterprise system, retrieving a context definition defining a context in which the first annotation was entered, generating a link to the context defined by the context definition, and outputting the link.

In another embodiment, a computing device includes a user interface to receive contribution data of an enterprise and to display a sheet of the contribution data. The computing device also includes an annotation interface module to receive one or more annotations for objects of the contribution data. The computing device further includes a planning application to retrieve a context definition defining a context in which each of the annotations was received. Moreover, the computing device includes an annotation table to store each of the annotations and the context definition corresponding to each of the annotations, wherein the user interface is configured to output the annotations.

In another embodiment, the invention is directed to a computer-readable medium containing instructions. The computer-readable medium may be a computer-readable storage medium, such as, for example, random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electronically erasable PROM (EEPROM), flash memory, or other suitable memory. The instructions cause a programmable processor to receive contribution data of an enterprise in accordance with a multi-level enterprise model, store the contribution data within a database, receive a first annotation for an object of the contribution data, retrieve a context definition defining a context in which the first annotation was received, receive a second annotation for the object within the same context as the context in which the first annotation was received, store the first annotation, the second annotation, and the context definition, and display the first annotation and the second annotation to a user.

The techniques described herein may offer several advantages. For example, the techniques may improve the collaborative process of developing multidimensional data. With the ability of a user to add annotations to a particular entry or a view of the data, users of the enterprise system may quickly and easily share their thoughts, questions, and comments about the data. These annotations may only be relevant with respect to a particular view. Because of the many possible sheets that are possible to create, a specific sheet may be difficult, if not impossible, to recreate, either by the system itself or from a user's memory. By storing the context that defines a specific sheet, recreating a specific sheet may be done efficiently and may easily allow users who work with the same data to coordinate their efforts toward contribution and review of the data more efficiently.

DETAILED DESCRIPTION

FIG. 1is a block diagram illustrating an example enterprise4having a computing environment10in which a plurality of users12A-12N (“users12”) access an enterprise system14, such as an enterprise planning system. In the system shown inFIG. 1, enterprise system14communicatively couples to a number of computing devices16A-16N (“computing devices16”) by a network18. Users12may interact with computing devices16to access enterprise system14. AlthoughFIG. 1depicts a one-to-one correspondence between users12and computing devices16, other embodiments may permit any number of users to access a particular one of computing devices16. Likewise, one user, e.g. user12A, may have access to a plurality of computing devices16.

Enterprise users12may utilize a variety of computing devices to interact with enterprise system14via network18. For example, an enterprise user may interact with enterprise system14using a laptop computer, desktop computer, or the like, running a web browser, such as Internet Explorer™ from Microsoft Corporation of Redmond, Wash. Alternatively, an enterprise user may use a personal digital assistant (PDA), such as a Palm™ organizer from Palm Inc. of Santa Clara, Calif., a web-enabled cellular phone, or similar device.

Network18represents any communication network, such as a packet-based digital network like the Internet. In this manner, system10can readily scale to suit large enterprises. Enterprise users12may directly access enterprise system14via a local area network, or may remotely access enterprise system14via a virtual private network, remote dial-up, or similar remote access communication mechanism.

For exemplary purposes, the invention will be described in reference to a performance management and enterprise planning system, such as an enterprise-wide financial management system or budget planning system. The techniques described herein may be readily applied to other software systems, including other large-scale enterprise software systems. Examples of enterprise software systems include order management systems, inventory management systems, sales force management systems, business intelligence tools, enterprise reporting tools, project and resource management systems and other enterprise software systems.

In one example embodiment, enterprise system14enables and automates the reconciliation of top-down targets with detailed bottom-up forecasts for an enterprise. Enterprise system14implements and manages an enterprise planning process, which can be divided into three stages: (1) a modeling stage during which a model is constructed, (2) a contribution stage during which planning data is collected, and (3) a review and performance management stage during which the planning data can be selectively accepted and analyzed.

Initially, high-level enterprise managers or executives, referred to as analysts, define organizational targets, and build planning models for the enterprise. The analysts may include, for example, financial analysts, such as the chief financial officer, senior financial analysts or product and sales analysts. More specifically, the analysts develop a model having a number of hierarchically arranged nodes representing various cost centers within the organization, such as business units or departments. The analysts specify corporate target data for each node of the organizational hierarchy. Corporate target data may include financial data, revenue data, order data, inventory data, and the like, depending on the particular enterprise planning activity being carried out by the enterprise.

Next, the analysts assign one or more enterprise users to each node, such as managers, supervisors, sales representatives, lab managers, or the like, that are responsible for enterprise planning for the cost center corresponding to the node. Each enterprise user may be designated as a contributor that provides planning data to enterprise system14, a reviewer that accepts or rejects contributions from the contributors, or both. The contributors and reviewers may be authorized users within the enterprise, e.g. users12, or within other entities coupled to network18, such as suppliers or customers.

Typically, enterprise users12that are designated as contributors interact with enterprise system14to input detailed forecasts in the form of contribution data. As described above, enterprise users12may provide detailed financial forecasts, revenue forecasts, order forecasts, inventory forecasts, estimated resource requirements, and the like, depending on the particular enterprise planning activity being carried out by the enterprise. Users12may also enter and/or review annotations from other users12in accordance with the techniques as described in greater detail below.

Enterprise system14automates the reconciliation of the forecast data with the corporate target data provided by the analysts. In particular, enterprise system14operates in accordance with a defined model, i.e., the enterprise planning model created by the analysts, to provide a hierarchical planning process having multiple reconciliation levels. As each of the contributors provides his or her contribution data, enterprise system14automatically aggregates the contribution data across the enterprise in real-time, and provides access to the aggregated data to enterprise users12designated as reviewers associated with higher levels of the enterprise. In particular, upon receiving contribution data from the contributors, enterprise system14identifies all higher levels of the organizational model affected by the newly received contribution data, and calculates new aggregate totals at each level in real-time.

Consequently, the reviewers view aggregated data across the enterprise in real-time during the enterprise planning session. At each level, enterprise system14ensures that the reviewers, as defined by the nodes of the enterprise model, reconcile the target data with the forecast data. Each of the reviewers may, for example, reject or accept the contribution data in view of corporate targets provided by the analysts. Moreover, enterprise system14may enable a user to annotate an entry of contribution data. Enterprise system14may store characteristics of the sheet in which a user entered an annotation at the time of the annotation in order to enable simple recreation of the sheet by the same user or a subsequent user who would like to review the annotation. The process of reviewing and accepting or rejecting, revising, and again reviewing continues until the contribution data is ultimately approved by the highest level of the organizational hierarchy, thereby ensuring that the contribution data from the contributors reconciles with corporate targets provided by the analysts. The ability to annotate data and to review the annotations may improve the efficiency of this process.

An annotation may contain various information. For example, the annotation may contain the name or a user identification (ID) of the user who entered the annotation, the date/time at which the annotation was entered, the value of the object being annotated at the time of the annotation, and a comment from the user. As an example of a situation in which an annotation may be used, a contributor may annotate an entry that the contributor believes is especially important, about which the contributor is unsure or has a question, or for other various reasons. As another example, a reviewer may also wish to annotate certain entries, such as an entry that the reviewer believes has an incorrect value. The reviewer may also add a second annotation to an entry from a contributor when the contributor has annotated the entry, for example, to ask a question. Enterprise system14may store an entire history of annotations for a particular entry. In continuing with the example, enterprise system14may store the original annotation from the contributor as well as the annotation from the reviewer. Each annotation may include the name/identification of the annotator, the date/time at which the annotation was entered, the specific value of the entry at the time of the annotation, a dimensional context for the annotation, such as the coordinates, and comments from the annotator.

Additionally, a user may annotate a cell or other data object by attaching a document or other file to the data object to be annotated. Enterprise system14may present an interface by which a user may request to attach a document to, for example, a cell. The user may then attach a particular document to the cell. When a subsequent user requests to view the comment, enterprise system14may open the attached document and display the attached document to the user.

Enterprise system14may enable annotations of any type of object associated with the data. In one embodiment, enterprise system14may permit annotation of an entire sheet. In this case, the annotation need not contain the current value(s) of any of the entries in the sheet. Enterprise system14may store coordinates defining how to reconstruct the sheet when an annotation is relevant to the entire sheet. Moreover, enterprise system14may store a history of annotations with respect to the entire sheet if another user enters an annotation relevant to the same sheet in which a different user had previously entered an annotation. In some embodiments, enterprise system14may enable annotation of all objects associated with multidimensional data, such as cells, sheets, datacubes, or other such objects.

Enterprise system14may enable organizations to reconcile corporate models and organizational targets with detailed forecasts. Enterprise system14may provide a platform that delivers collaborative, real-time planning capabilities, without requiring offline consolidation and aggregation of forecasts. Because enterprise system14can aggregate contribution data in real-time, all users12can be presented with an accurate, up-to-date view of the numbers. Enterprise system14may also present all users12with the ability to view annotations. Further, the architecture of enterprise system14can readily scale to thousands of users, and may be designed around best planning practices. In addition, the techniques enabling high participation by enterprise users12, i.e., the contributors and reviewers, allowing accurate planning cycles to be reduced.

Enterprise system14may utilize a “cut-down” process by which the multidimensional data store is “sliced” for each user12in accordance with the defined enterprise model. During this process, enterprise system14identifies areas of the defined model to which users12are assigned, either as contributors or reviewers, and “slices” the data store based on the assignments. When a given user12logs in and proceeds with an enterprise planning activity, enterprise system14communicates the respective data slice to the respective computing device16for display to the user via the extended spreadsheet application. In this fashion, enterprise system14need not communicate the entire model to each of users12, thereby reducing communication time as well as resource requirements. Instead, each user12receives only relevant information. Users12interact with computing devices16to capture contribution data, and to reconcile the contribution data with organizational targets.

A computing device, such computing device16A, may represent a particular slice of a data cube with one or more sheets. A sheet may be, for example, a cross tab display similar to a spreadsheet document. As described herein, sheets relate to a two-dimensional representation of data from a multidimensional data cube. On the other hand, a spreadsheet document, such as a Microsoft Excel document, is typically a representation of two dimensional data from a relational database. Although a sheet typically may not simultaneously display data for each of the plurality of dimensions from which the sheet is derived (due in part to the two-dimensional nature of display devices, such as monitors), sheets generally contain data retrieved from a plurality of dimensions of a data cube. For example, the sheet may select one value for each of certain dimensions, e.g. all but two of the dimensions, of the data cube. The sheet may then display all data for the two other dimensions in a cross tab display.

The techniques described herein may offer several advantages. For example, the techniques may improve the collaborative process of developing multidimensional data. With the ability of users12to add annotations to a particular cell or other object associated with the data, users12of enterprise system14may quickly and easily share their thoughts and questions about the data. These annotations may only be relevant with respect to a particular sheet. Because of the many possible sheets that are possible to view, a specific sheet may be difficult to recreate by the system itself or from a user's memory. By storing the coordinates of, for example, a cell to which an annotation relates, recreating a specific sheet may be done efficiently and may easily allow users who work with the same data to coordinate their efforts in a more efficient fashion.

FIG. 2is a block diagram illustrating one embodiment of a computing device16A for interacting with enterprise system14. In the exemplary embodiment, computing device16A includes planning application25that includes a user interface20, a calculation engine22, an object model interface26, an object model28, and an object store30. Computing device16A may include computer-readable media to store executable instructions for causing a programmable processor to carry out the methods described herein. The computer-readable media may be computer-readable storage media, such as RAM, ROM, PROM, EEPROM, or other suitable computer-readable media.

Planning application25represents a planning application executing on computing device16A. For example, planning application25may include user interface tools, reporting tools, modeling tools, spreadsheet applications, data collection templates, business intelligence tools, or other types of enterprise planning applications. Planning application25may specify operations that object model28performs upon data cubes32through interactions with object model interface26.

Object model interface26comprises an application programming interface (API)27that exposes object model28. For example, object model28may be a metadata model for data cubes32that represent multidimensional data from one or more data cubes. Object store30may comprise memory, such as a cache, that stores specific instantiations of object model28. Multidimensional data cubes32A-32N (“data cubes32”) of object store30each store multidimensional data in accordance with object model28.

In general, object model28represents any hierarchy of data objects, and may comprise a series of collections and objects within the collections. In other words, object model28may comprise a hierarchy of objects, each of which contains a collection which in turn provides access to one or more objects. Object model28may be wrapped to protect the objects within the collections. In this way, user12A and planning application25cannot directly alter the data within object store30of object model28. Instead, planning application25interacts with object model28via object model interface26, and more particularly API27, to specify operations object model28may perform. In particular, object model interface26receives operation calls from planning application25via API27and may return the result of the operations to planning application25.

In the example of enterprise planning, user12A may interact with user interface20to enter and manipulate enterprise planning data, such as budget or forecast data. User interface20may be, for example, a web browser front-end such as an ActiveX component, a Java applet, or any other suitable web browser front-end. As another example, user interface20may be a graphical user interface (GUI), for example, a GUI compatible with Microsoft Windows, the X Window System, Aqua, or other user interface and/or windowing systems.

Data cubes32may store multidimensional planning data, which may include top-down targets, and bottom-up contribution data, and may allow all calculations for an enterprise planning session to be performed locally by computing device16A using, e.g., calculation engine22.

Object model28may maintain annotation tables24A-24N (“annotation tables24”) in object store30. In the example embodiment as shown inFIG. 2, object model28maintains one annotation table per multidimensional data cube, as well as a global annotation table35. Although illustrated inFIG. 2as separate tables for the purpose of clarity, annotation tables24may be incorporated into respective ones of data cubes32. For example, data cube32A may include an “annotations” dimension, which may include cells that store annotations for other cells in data cube32A.

Planning application25may retrieve annotation data from enterprise system14through network18in addition to retrieving multidimensional data. Object model28may store annotations relevant to data cubes32in corresponding annotation tables24. Entries in annotation tables24may be relevant to a particular cell, sheet, data cube, or other higher-order data object. For example, an annotation in annotation table24A relevant to a particular cell may store the coordinates of the relevant cell of data cube34A as well as a context definition defining the context in which the annotation was entered. As another example, an annotation in annotation table24A may relate to data cube32A in its entirety.

Global annotation table35may include entries that store annotations for individual ones of data cubes32, for a set of two or more of data cubes32, for user planning data as a whole, and/or for other objects of enterprise system14. Although illustrated inFIG. 2as a separate table for purposes of clarity, global annotation table35may be incorporated into one or more of annotation tables24or into one or more of data cubes32.

User interface20may include annotation interface (IF) module38and commentary browser36. User interface20may present an interface by which a user, such as user12A, may interact with a particular sheet. A sheet, as described above, may be a particular view of the data stored in object store30. For example, a sheet may present a cross tab display, such as a spreadsheet view, of the data, wherein two of the dimensions of a multidimensional data cube may be displayed in full, while the remaining dimensions are isolated to a single value for each dimension. A sheet may also present an aggregation of the data, for example, as a result of a multidimensional data query. User interface20may receive a request for a particular sheet from user12A. User interface20may transmit the request to object model28through object model interface26to retrieve the requested data in order to populate the sheet with the correct values. Planning application25may retrieve multidimensional data from enterprise system14through network18with which to populate data cubes32. For example, planning application25may retrieve data corresponding to one or more data cubes from enterprise system14.

Annotation IF module38may present an interface by which a user, such as user12A, may enter an annotation with respect to a particular cell or other object. Annotation IF module38may retrieve the definition of the current sheet from user interface20. For example, annotation IF module38may retrieve information defining what dimensions were used to create the sheet. Annotation IF module38may store the definition of the current sheet along with an annotation entered by user12A such that when the annotation is retrieved, by either user12A or by another user, e.g., user12B, user interface20may reconstruct the sheet in which the annotation was entered. In this way, the user retrieving the annotation may more accurately interpret the annotation because the retrieving user may readily observe the context in which the annotation was entered.

A context is generally the sheet or other display in which a particular annotation is received. For example, a data cube may have N dimensions Di, 1≦i≦N. The data cube may be defined as {D1, D2, . . . , DN}. A cell of the data cube may be defined as {D1[x1], D2[x2], . . . , DN[xN]}, where 1≦xi≦|Di|. A sheet of the data cube may be defined as {D1[x1], . . . , Dj, Dk, . . . , DN[xN]} for some j, k such that 1≦j≦N, 1≦k≦N, and j≠k. Thus the context of an annotation for a particular cell {Dj[a], Dk[b]} of the sheet is the sheet itself, i.e. {D1[x1], . . . , Dj, . . . , Dk, . . . , DN[xN]}. Planning application25may store an annotation in a corresponding one of annotation tables24, as well as the definition of the context in which the annotation was entered. When the annotation relates to a particular cell, planning application25may further store the coordinates of the cell in the corresponding one of annotation tables24.

Annotation IF module38may also enable users12to enter a plurality of annotations with respect to the same data entry. For example, user12A may initially enter an annotation for a cell, and later, user12B may enter an annotation for the same cell. Likewise, user12A may enter an additional annotation for a cell for which user12A has already entered an annotation, with or without an annotation from a different one of users12. Annotation IF module38may maintain a list, such as an array, a linked list, or other data structure storing annotations for the cell in annotation tables24. Each of the annotations in annotation tables24may include, for example, the name or user ID of the user who entered the annotation, the date on which the annotation was entered, the current value of the cell for which the annotation is entered, and comments from the user. User interface20may present each of the annotations to a user viewing the sheet containing the cell for which the annotations were entered.

As an example, user12A, who may be a contributor, can modify his or her respective contribution data, and perform calculations necessary for the enterprise planning process without necessarily accessing enterprise system14. User12A may also enter an annotation with respect to a cell, a sheet, or other data object using annotation IF module38. User12A may save the planning data locally, and submit the planning data, including the annotations, to enterprise system14for aggregation with the planning data from other users12. One or more of the other users12may enter further annotations or delete annotations from user12A.

An annotation may be stored along with a definition of the context in which the annotation was entered. For example, a data cube may include five dimensions {A, B, C, D, E}. One of users12, such as user12A, may request the sheet defined by particular values of dimensions A, B, and D, e.g. A[3], B[2], D[7] while requesting C×E as a cross-tab display, wherein the notation M[i] denotes the ith value of dimension M. User12A may then enter an annotation in, e.g., cell C[5], E[13]. An entry stored in a corresponding one of annotation tables24may include the annotation data, such as user name, date, comment, and/or current value of the cell, the definition of the context, i.e. the sheet definition {A[3], B[2], D[7], C×E}, and the index of the annotated cell, i.e. C[5], E[13].

Planning application25may determine whether annotations exist with respect to a requested sheet or any of the cells of the sheet when populating the sheet with the data. For example, planning application25may search annotation tables24and global annotation table35for annotations relating to cells or other objects of data cubes32. For each cell or other object for which an annotation exists, user interface20may present an indication to user12A that an annotation exists. For example, when a particular cell includes an annotation, user interface20may present a flag within the cell, as shown in the exemplary screenshot ofFIG. 8. User interface20may indicate the existence of an annotation in other ways as well, such as highlighting the annotated cell in a particular color, presenting the text of the annotated cell in bold, italics, underline, or a different font, outlining the annotated cell with a border or partial border, or by other means.

User interface20may display an annotation when user12A requests to view the annotation. For example, user12A may request to view the annotation by using a pointer controlled by a mouse attached to computing device16A to hover over the cell for which an annotation exists; user interface20may interpret the hovering as a request to view the annotation and, when user12A moves the pointer away from the annotated cell, user interface20may determine that user12A no longer wishes to view the annotation. User interface20may display the annotation, for example, as a “tooltip,” i.e. a window that appears next to the annotated cell after the pointer has hovered over the annotated cell for a certain period of time and that disappears when the pointer is moved away from the annotated cell. User interface20may also display the annotation by other means, for example, by opening a new window containing the annotation or by presenting the annotation in a separate frame of the current window.

User interface20may call commentary browser36to present a list of annotations to user12A. For example, commentary browser36may present a list of one or more annotations in a commentary browser window, as shown in the example ofFIG. 11. Commentary browser36may furthermore display a link associated with an annotation, such that when user12A clicks the link, user interface20will present the sheet to which the annotation was relevant, highlight the cell for which the annotation is relevant, and/or display the annotation. The link may be a link to the context in which the annotation was originally entered. Continuing the above example, commentary browser36may present a list of annotations to user12A, including in the list an entry for cell C[5], E[13]. When user12A selects the annotation associated with cell C[5], E[13], commentary browser36may display a link to {A[3], B[2], D[7], C×E}. When user12A selects the link, commentary browser36may display the sheet defined by {A[3], B[2], D[7], C×E} and depict a flag or other indication of an annotation in cell C[5], E[13].

Commentary browser36and/or user interface20may further enable deletion of one or more of the annotations. User12A may accordingly request to delete one of the annotations. In response, planning application25may remove the deleted annotation from annotation tables24. When all annotations for a particular cell are deleted, user interface20may remove the flag that indicated the presence of an annotation from the display of the cell.

Enterprise system14may automatically aggregate the contribution data across enterprise4in real-time, and may provide access to the aggregated data to reviewers associated with higher levels of the enterprise. This process continues until the contribution data is ultimately approved by the reviewers associated with the highest level of the organizational hierarchy, thereby ensuring that the contribution data from the contributors reconciles with corporate targets.

In one embodiment, annotations may also be aggregated during data aggregation. For example, distinct users, e.g. users12A and12B, may have annotated two distinct cells. During data aggregation, the two cells may become aggregated into one cell. The data for the two cells may be combined mathematically or by some other means. Annotation table24may likewise aggregate the annotations. That is, the annotations for each cell may be joined to form a single list of annotations. In one embodiment, user interface20may present a single list of annotations for such an aggregated cell. In other embodiments, user interface20may differentiate the annotations relevant to each particular cell. For example, user interface20may present multiple lists of annotations, annotations differentiated by color wherein user interface20selects a distinct color for each of the cells being aggregated, or by other means.

In one embodiment, calculation engine22and data cubes32are loaded for use during the enterprise planning session. Calculation engine22may, for example, comprise a forward calculation engine22wrapped in an Active X object built in an array-based language. In other embodiments, calculation engine22may be implemented by creating layered function datasets within object store30. Calculation engine22may generally perform operations, such as mathematical operations, on cells of data cubes32.

FIG. 3is a flow chart illustrating an example process for entering an annotation. The example ofFIG. 3is directed to entering an annotation for a specific cell of a sheet, however a similar process may be used for entering annotations for higher-ordered objects, such as sheets and data cubes. As discussed with respect toFIG. 2, user interface20may present an option to a user, for example, user12A, to enter an annotation. When user12A selects this option, user interface20may receive the request to enter an annotation and call annotation interface (IF) module38(100).

In response, annotation IF module38may direct planning application25to retrieve the definition of the sheet in which user12A is entering the annotation (102). A sheet may be defined by context, e.g. selected rows and columns and single-value dimensions. Rows may be all entries in one dimension of a data cube, while a column may all entries in a different dimension of the data cube. The context may further include particular values of the remaining dimensions of the data cube. For example, data cube32A may have five dimensions {A, B, C, D, E}, one sheet may be defined as {C, E, A[3], B[2], D[7]}. This exemplary sheet would be a cross tab display of rows C by columns E, wherein the data is selected for A[3], B[2], and D[7]. Planning application25would retrieve the sheet definition {C, E, A[3], B[2], D[7]}.

Planning application25may then retrieve the coordinates of a cell for which user12A indicated a desire to enter an annotation (104). In continuing the above example, user12A may have selected the cell C[5], E[13]. Accordingly, planning application25would retrieve C[5], E[13] as the coordinates of the cell.

Planning application25may also retrieve certain information for the annotation to identify the annotation, to distinguish the annotation from other annotations, or for other reasons. In the example portrayed inFIG. 3, planning application25retrieves a userID, the current date, which may be a date/time according to any suitable format, and a current cell value (106). Other embodiments may retrieve this or other information.

Annotation IF module38may then prompt user12A for a comment (108). In one embodiment, for example, annotation IF module38may present a graphical text box, such as comment box330ofFIG. 7, to user12A. Annotation IF module38may display some or all of the information retrieved at (106) as part of the graphical text box, as in the example ofFIG. 7. User12A may then enter a comment and submit the comment, for example, by pressing an “OK” button also presented by annotation IF module38. In response, annotation IF module38may retrieve the comment entered by user12A.

Planning application25may then determine whether the annotation was the first annotation (112). For example, planning application25may examine annotation tables24to determine whether, for the selected data cube, an annotation exists in the selected cell of the selected data cube for the particular context. In continuing the above example, planning application25may examine annotation tables24, e.g. annotation table34A related to data cube32A, to determine whether a comment exists for cell C[5], E[13] in the context of {C, E, A[3], B[2], D[7]} of data cube32A. Notably, planning application25determines more than simply whether an annotation exists for the cell defined by {A[3], B[2], C[5], D[7], E[13]} of data cube32A, because annotations are typically sensitive to the context in which they are entered. However, other embodiments may utilize other storage schemas wherein annotations are simply stored according to the coordinates of the cells to which the annotations relate.

When planning application25determines that the annotation is the first annotation for the selected cell in the given context (“YES” branch of112), planning application25may store all of the details of the annotation (114). That is, planning application25may create a new entry in annotation tables24, defined by the coordinates and the context of the cell for which user12A entered the annotation. Planning application25may then store the details of the annotation, e.g. the userID, the date, the current value, and the user comment, in the new entry of annotation tables24.

When planning application25determines that the annotation is not the first annotation for the selected cell in the given context (“NO” branch of112), implicitly an annotation already exists for the selected cell in the given context. Accordingly, planning application25may store the details of the new annotation for the selected cell with the previous annotation (116). That is, a new entry is not necessarily needed in annotation tables24in order to store the new annotation.

In some embodiments, annotation tables24may store annotations in annotation tables24in an array indexed by the cell coordinates and context and an ordinal number according to the order in which the annotation for the cell was received. In other embodiments, annotation tables24may use a “date” field of an annotation to differentiate annotations for a particular cell in a particular context from each other. In any case, planning application25may enable users12to view each annotation for the cell individually or to view all of the annotations together. Moreover, planning application25may later receive a request to delete a particular annotation from the cell, therefore storing the annotations for a cell individually may enhance the efficiency of viewing and/or deleting individual annotations.

FIG. 4is a flowchart illustrating an example process for displaying a list of annotations. User interface20may present a user, such as user12A, with an option to view a list of annotations. When user12A selects this option, user interface20may receive the request (200) and call commentary browser36in response. In general, commentary browser36may display a list of available annotations to user12A, as well as provide the ability for user12A to select an annotation and see the context in which the annotation was entered. Commentary browser36may further enable user12A to apply one or more filters to the available annotations to aid user12A in finding a particular annotation or annotations of particular interest. Commentary browser36may also allow user12A to delete an annotation. Although not shown in the flowchart ofFIG. 4, in one embodiment, user12A may also select a “cancel” option at essentially any time during the process to end the process and close commentary browser36.

Commentary browser36may first cause planning application25to examine annotation tables24to search for all available annotations (202). Commentary browser36may retrieve this information from planning application25. Commentary browser36may also provide an interface by which user12A may apply one or more filters, as described with respect to the example ofFIG. 11.

User12A may request to view a particular annotation from the list of displayed annotations. In one embodiment, for example, user12A may control a pointer with a mouse attached to computing device16A. User12A may select a particular annotation from the list of annotations by pointing to the annotation and pressing a button on computing device16A, such as a left mouse button. Commentary browser36may then receive the request to view the selected annotation (208). In continuing the above example, user12A may request to view an annotation corresponding to cell C[5], E[13]. Commentary browser36may retrieve the sheet definition, i.e. the context, corresponding to the annotation from planning application25(210). That is, for the above example, commentary browser36may retrieve the context definition {C, E, A[3], B[2], D[7]} from planning application25.

Commentary browser36may then display the annotation and a variety of options (212). In one embodiment, for example, commentary browser36may display the annotation in a separate text box from that of a text box for displaying the list of annotations. Commentary browser36may generate a link to the context, e.g. the sheet, according to the retrieved context definition. For the above example, commentary browser36may display a link to the sheet corresponding to {C, E, A[3], B[2], D[7]}. Commentary browser36may also display an option to user12A to delete the annotation. Commentary browser36will then wait for user12A to select an option (214). User12A may select a different annotation, in which case commentary browser36will receive the newly selected annotation (208), retrieve the sheet definition (210) to create a link corresponding to the newly selected annotation, and display the annotation, link, and available options (212).

When user12A requests to delete an annotation (“DELETE” branch of214), commentary browser36may instruct planning application25to delete the annotation from annotation tables24. Planning application25may accordingly remove the annotation from annotation tables24(216). For example, if the annotation was for a cell of data cube32A, planning application25may delete the selected annotation identified by the context and the selected coordinates in annotation table24A. In the case that the deleted annotation was one of a plurality of annotations for the same cell in the same context, planning application25will only delete the selected annotation, not the entire list of annotations for that cell. Accordingly, planning application25may need to rearrange the annotations stored in annotation tables24. For example, if annotation tables24store annotations in an array data structure, planning application25may move subsequent entries in the array forward by one unit. As another example, if annotation tables24store annotations as a linked list data structure, planning application25may rearrange one or more pointers of the linked list. For other data structures, planning application25may act accordingly. Commentary browser36may also remove the deleted annotation from the displayed annotation list.

When user12A requests to view the sheet, (“VIEW” branch of214), commentary browser36may instruct user interface20to display the sheet in which the annotation was entered. User interface20may use the context definition to recreate and display the sheet (218). In one embodiment, user12A may click the link to the sheet by controlling a pointer with a mouse attached to computing device16A to request to view the sheet. In some embodiments, commentary browser36may close after user12A requests to view the annotation. In any case, user interface20may display the sheet corresponding to the annotation. In some embodiments, user interface20may highlight the cell corresponding to the annotation, for example, by displaying a box around the corresponding cell. In the above example, user interface20may display the sheet {C, E, A[3], B[2], D[7]} by retrieving values for A[3], B[2], and D[7] from planning application25and displaying the data for the dimension C in rows and the dimension E in columns. User interface20may also highlight cell C[5], E[13]. In some embodiments, user interface20may further display the annotation, for example, as a tooltip next to the annotated cell, although other embodiments may display the annotation with other suitable means. As another example, another embodiment may display the annotation in a distinct window. Yet another embodiment may display the annotation in a separate frame or toolbar of the same window.

FIG. 5is a screen illustration of a user interface300for viewing and entering planning data. User interface300is an example embodiment of user interface20ofFIG. 2. User interface300presents an exemplary sheet view of data from data cubes32. As discussed above, when one of users12(e.g., user12A) needs to enter or view, for example, planning data, user12A may cause computing device16A to execute planning application25. When planning application25executes, planning application25downloads a slice of planning data from enterprise system14and stores the planning data in one or more of data cubes32. This disclosure refers to this downloaded slice as user planning data. After planning application25stores user planning data, planning application25may cause computing device16A to display user interface300. User12A may request that user interface300display particular data from data cubes32, as described in greater detail below.

User interface300presents user planning data in a manner that may be readily understood by a human user. For instance, user interface300includes tabs302for each data cube in user planning data stored in data cubes32. Tabs302indicate a “Product Price and Cost” data cube, an “Employee Grades” data cube, a “Compensation Assumptions” data cube, an “Asset Purchases” data cube, an “Employee Plan” data cube, a “Revenue Plan” data cube, and an “Income Statement” data cube.

In order to view and/or edit data in a data cube of user planning data, user12A may use a mouse or other pointing device to click on the one of tabs302that indicates the data cube. In the example ofFIG. 5, user12A has clicked on the tab that indicates the “Revenue Plan” data cube. When user12A clicks on one of tabs302, planning application25may cause user interface300to include a row selection box304, a column selection box306, and a set of context selection boxes312. User12A may use row selection box304to select items of a dimension of the selected data cube to serve as the vertical axis of a table314that presents data in the selected data cube. In the example ofFIG. 5, user12A has used row selection box304to select all items of an “Indoor and Outdoor Products” dimension of the “Revenue Plan” data cube. Similarly, user12A may use column selection box306to select items of a dimension of the selected data cube to serve as a horizontal axis of table314. In the example ofFIG. 5, user12A has used column selection box306to select all items of a “Months” dimension of the “Revenue Plan” data cube.

User12A may then use context selection boxes312to select one item in each of the other dimensions of the selected data cube. In the example ofFIG. 5, the “Revenue Plan” data cube includes an “elist” dimension, a “Product Gross Margin” dimension, a “Channels” dimension, and a “Versions” dimension. Furthermore, in the example ofFIG. 5, user12A has selected the “A1” item for the “elist” dimension, the “Units” item for the “Product Gross Margin” dimension, “Discount Stores” item for the “Channels” dimension, and “Budget Version 1” item for the “Versions” dimension. In this way, user12A specifies a two-dimensional sheet of the data in the selected data cube.

After user12A uses row selection box304, column selection box306, and context selection boxes312to specify a two-dimensional sheet of the data in the selected data cube, user interface300presents the specified two-dimensional sheet of the data in the selected data cube as table314, for example, in a cross tab display as shown inFIG. 5. Each individual cell in table314contains data of a cell of the selected data cube that is indicated by an item in the selected row dimension of the selected data cube, an item in the selected column dimension of the selected data cube, and selected items in the context dimensions. For example, cell316, in the “14.4V Professional Drill/Driver Kit with Flashlight” row and in the “Mar-03” column of table314, contains value “29,415” corresponding to data of a cell in the “Revenue Plan” data cube that is located at the “14.4V Professional Drill/Driver Kit with Flashlight” item in the “Indoor and Outdoor Products” dimension, the “Mar-03” item in the “Months” dimension, the “A1” item in the “elist” dimension, the “Units” item in the “Gross Product Margin” dimension, the “Discount Stores” item in the “Channels” dimension, and the “Budget version 1” item in the “Versions” dimension.

FIG. 6is an example screen illustration of a user interface300for requesting to enter an annotation. User12A may add annotations to cells in table314or to other higher-level objects such as sheets or data cubes. An annotation may be text-based commentary or other descriptive data that user12A inputs in order to provide additional information about a particular cell. User12A may also attach a file to the annotated cell, as described in greater detail below. That is, an annotation of a cell or other data object may include attaching a file of any sort to the cell or data object in addition to, or in lieu of, text-based commentary. In one embodiment, annotation IF module38may automatically enter certain descriptive data about an annotated cell in the annotation. In order to add an annotation to a cell in table314, such as cell316, user12A may use a mouse or other input device to position a cursor318over cell316in table314. When user12A positions cursor318over a cell in table314, user12A may press a button on computing device16A in order to cause user interface300to display a cell options menu320. For instance, user12A may press the right mouse button in order to cause user interface300to display cell options menu320for cell316, as depicted inFIG. 6. Cell options menu320includes an annotate option322. If user12A selects annotate option322, user interface300may cease to display cell options menu320, but may instead display an annotation entry window that user12A may use to add an annotation to the cell. An exemplary embodiment of an annotation entry window is illustrated in the example ofFIG. 7.

Although not illustrated in the example ofFIG. 6, user12A may also position cursor318over one of tabs302. After user12A positions cursor318over one of tabs302, user12A may press a button on computing device16A in order to cause user interface300to display a data cube options menu. This data cube options menu may also include an annotate option. If user12A selects this annotate option, user interface300may display an annotation entry window similar to that which user12A may use to add an annotation to a cell. User12A may then use this annotation entry window to add an annotation to the data cube or to some other object. Likewise, user12A may position cursor318over a separate portion of user interface300and press a button on computing device16A in order to cause user interface300to display a sheet options menu, whereby user12A may select an annotate option to enter an annotation with respect to the currently displayed sheet. In alternative embodiments, other option selection means may be used without departing from the principles of the techniques described herein. For example, in one embodiment, user12A may select the “Tools” drop-down menu from the standard toolbar at the top of user interface300. The “Tools” drop-down menu may include an annotate option that user12A may select to annotate a cell, a sheet, a cube, or other data object.

FIG. 7is a screen illustration of user interface300upon which an annotation entry window330is superimposed. User interface300may present annotation entry window330when user12A selects annotation option322in order to add an annotation to a cell. Annotation entry window330includes comment box336. User12A may enter text into comment box336in order to provide additional information about a selected cell in table314. In the example ofFIG. 7, user12A has entered the text “Order placed for 500 additional units of 14.4V Professional Drill/Driver Kit with flashlight on Mar. 13, 2003.” This comment might be useful to another one of users12who may see the cell in table314and wonder why the data in the cell is 500 units higher than when the user previously saw table314. Annotation entry window330may also include an indication332of the name or user identification of the current user. Moreover, when entering an annotation for a specific cell, annotation entry window330may include an indication334of the current value of the cell. When entering an annotation for a higher-order object, such as a sheet, annotation entry window330may omit current value indicator334or may display “N/A” as the value.

Annotation entry window330also includes a set of input boxes that allow user12A to attach one or more files to an annotation for a cell in table314. For instance, user12A may attach a file present on a local hard disk of computing device16A by entering a path to the file in a path field384. User12A may also attach files present on other storage devices, such as network drives. In the example ofFIG. 7, user12A has entered the path “C:\Invoices\Products\Professional\order071007.pdf” into path field384. This attached file may contain an invoice for the order for 500 drill/driver kits alluded to in comments box336. A filename box386in annotation entry window330allows user12A to enter a user-friendly name for the file attached to the annotation. In the example ofFIG. 7, user12A has entered the name “Invoice for order” in filename box386. When a subsequent user requests to view the annotation of a cell that has an attached file, planning application25may permit the user to view the attached file. Planning application25may retrieve the attached file and display the file to the user. In continuing the above example, user12B may request to view the file attached to cell316. Accordingly, planning application25may retrieve the file “order071007.pdf” from location “C:\Invoices\Products\Professional.” Planning application25may also display this file to user12B. In general, user12A may attach any sort of file to an annotated object.

When user12A selects an “OK” button338of annotation entry window330, planning application25automatically adds the annotation to the cell. Planning application25may store the annotation in annotation table24. In addition, planning application25may upload and store any files specified in path field384. Alternatively, user12A may select “Cancel” box340of annotation entry window330to cancel the entry of the annotation, in which case planning application25will not save a new annotation and annotation entry window330will close.

FIG. 8is a screen illustration of user interface300displaying an annotation viewing window342, herein referred to as a “tooltip,” for cell316of planning data in table314. After user12A has added an annotation to cell316in table314, user12A or other ones of users12may view this annotation. User interface300may indicate the presence of an indication in a cell. In the example ofFIG. 8, user interface300has included a graphical flag348in cell316to indicate the presence of an annotation in cell316. User12A may view the annotation by positioning cursor318over a cell in table314that has an annotation, such as cell316. When user12A positions cursor318over a cell in table314that has an annotation, user interface300may automatically display tooltip342. Although the exemplary embodiment described with respect toFIG. 8uses a tooltip to perform the functions of annotation viewing window342, it should be appreciated that other means of displaying an annotation may also be used in other embodiments. For example, in another embodiment, annotation viewing window342may be a new window or a new toolbar within the same window.

In the example ofFIG. 8, tooltip342includes the text “Order placed for 500 additional units of 14.4V Professional Drill/Driver Kit with flashlight on Mar. 13, 2003.” Note that this text is the same as the text entered in comment box336. Likewise, tooltip342includes user identifier344that corresponds to user indication332of annotation entry window330and value identifier346that corresponds to value indication334of annotation entry window330. Tooltip342may also include date identifier345that may include an indication of when (i.e., the date and/or the time) at which the annotation was entered. Various embodiments may display the date/time in various formats.

User12A may edit entries of table314. For example, as shown inFIG. 8, user12A has changed the value of cell316from “29,415” to “29,915.” Users12may use the annotation feature of user interface300to track changes to the cells of table314, although no change in the values is necessary in order to enter annotations. In one embodiment, user interface300may present an auditing option to users12wherein, when the auditing option is selected, planning application25automatically records an annotation upon all changes to the data. Likewise, user12A can disable the auditing option and planning application25will accordingly stop automatically recording annotations for changes to the data.

FIG. 9is a screen illustration of user interface300upon which a subsequent annotation entry window330A is superimposed. One of users12may enter an additional comment to a cell, such as cell316, for which a comment already exists. The user entering the additional comment may be the same user or a different user than the user who originally entered the annotation. For example, user12A may enter a first comment, and user12A may enter a subsequent comment to correct the value of cell316and inform other users12of the change, or to answer questions from other users12. As another example, a different user, such as user12B, may enter an annotation to cell316for which an annotation already exists.

In the example ofFIG. 9, user12A has already entered a comment for cell316and user12B has requested to enter an additional comment. User interface300presents an annotation entry window330A that is very similar to annotation entry window330. For example, annotation entry window330A includes user identifier332A, value identifier334A, comment box336A, path field384A, and filename box386A, each of which may perform substantially similar functions to their respective counterparts in annotation entry window330. In addition, annotation entry window330A presents annotation history box350that presents previously entered annotations. In the example ofFIG. 9, annotation history box350presents the annotation previously entered by user12A. In one embodiment, when the text for annotation history box350exceeds the size of box350, user interface300may include scroll buttons on the side annotation history box350(not shown) in order for user12B to view the entire annotation history.

When user12B enters a comment in comment box336A and selects “OK” button338A, planning application25will save the new annotation along with previous annotations in annotation table24. In the example ofFIG. 9, user12B has entered the comment, “Please check the order history to confirm500additional units. I believe it is only 400 additional units.”

FIG. 10is a screen illustration of user interface300displaying tooltip342that includes multiple annotations342A and342B for cell316of planning data in table314. As inFIG. 8, user interface300includes a graphical flag348in cell316to indicate the presence of a comment in cell316. In some embodiments, user interface300may indicate the presence of multiple comments in a cell in a manner that is distinct from the manner in which user interface300indicates the presence of a single comment. In the example embodiment ofFIG. 10, however, user interface300uses the same graphical flag348to indicate the presence of one or more comments in a cell. In the example ofFIG. 10, user12B has also changed the value of cell316from “29,915” to “29,815.”

When a user, such as user12A, positions cursor318over a cell in table314that has an annotation, user interface300may automatically display tooltip342. For a cell that includes multiple comments, tooltip342may include multiple partitions, e.g. window342A and342B. In the example ofFIG. 10, window342A includes user identifier344A that corresponds to user indication332A of annotation entry window330A and value identifier346A that corresponds to value indication334A of annotation entry window330A. Window342B includes user identifier344B that corresponds to user indication332of annotation entry window330and value identifier346B that corresponds to value indication334of annotation entry window330. Moreover, windows342A,342B include respective date fields345A,345B that indicate the respective dates and times at which the respective annotations were entered.

FIG. 11is a screen illustration of user interface300upon which a commentary browser360is superimposed. Commentary browser360enables users12, such as user12A, to view all annotations in annotation table24related to downloaded data cubes32. User12A may see comments relevant to any sheet of any datacube. In the example ofFIG. 11, commentary browser360includes comment list364, comment box366, “Delete” button370, “Print” button372, and “Close” button374. User12A may open the commentary browser window by, e.g., positioning cursor318over a “browse” option and pressing a button on computing device16A, such as a left mouse button. The example ofFIG. 6depicts browse button324as part of option menu320. Other embodiments may include other means for opening commentary browser360, e.g., by including a “browse” option in the drop-down menu from the “Tools” option of the standard toolbar menu.

Comment list364displays a list of annotations available to user12A. User12A may narrow the list of annotations using commentary filter376and commentary view378. Commentary filter376may include a variety of filtering options for user12A. In the example ofFIG. 11, commentary filter376presents three check-boxes, “User Annotation,” “Audit,” and “Attached Document.” When the boxes are checked, annotations satisfying the respective filtering criteria are displayed. For example, if user12A checks the “Attached Document” filter, only annotations that include an attached document will be displayed. In other embodiments, other filtering criteria may be presented. For example, in another embodiment, commentary filter376may present a text box to users12as well as a “Search By” drop-down menu (not shown); user12A may select “User Name” from the “Search By” drop-down menu and type in the user name “STC” to view only annotations from user “STC.” Those skilled in the art will appreciate that other types of searches and filtering functions may be presented.

User12A may also narrow the list of annotations using commentary view378. In the example ofFIG. 11, commentary view378displays two radio buttons that allow user12A to view either all available annotations (i.e., “All Pages”) or only annotations regarding the current sheet (i.e., “Current Page”). Other embodiments may present other options as well. For example, an alternative embodiment may present radio buttons that allow user12A to view all annotations relevant to specific dimensions or specific data cubes.

User12A may select an annotation from annotation list364. Commentary browser360may illustrate the selected annotation by highlighting the selected annotation, as shown inFIG. 11. Once user12A has selected an annotation, commentary browser360may display the values of the annotation in comment box366. For example, comment box366may display the user identification of the user who entered the annotation, the date the annotation was entered, and the comment associated with the annotation. Moreover, comment box366may include a link368to the sheet for which the comment was entered. Link368enables user12A to quickly and easily retrieve the context in which the annotation was entered. That is, user12A may select link368by positioning cursor318over link368and pushing a button on computing device16A, such as a left mouse button. Upon selecting link368, user interface300may present the sheet in which the annotation was entered to user12A.

User12A may also perform other functions with commentary browser360. For example, user12A may delete an annotation using “Delete” button370. Once user12A has selected an annotation from annotation list364, user12A may select “Delete” button370by, for example, positioning cursor318over “Delete” button370and pushing a button on computing device16A, such as a left mouse button. In response to a user selecting “Delete” button370, planning application25may remove the selected annotation from annotation tables24. When planning application25connects to enterprise system14, planning application25may upload updated annotation tables24that do not include the deleted annotation, therefore the deleted annotation will no longer be present either on computing device16A or anywhere in enterprise system14.

In a similar fashion, user12A may print one or more annotations from annotation list364by selecting one or more annotations from annotation list364and selecting “Print” button372. Computing device16A may transmit data to a printing device (not shown) in response to user12A selecting “Print” button372, wherein the data sent to the printing device may include instructions to print the selected annotation(s). Likewise, user12A may select “Close” button374to close commentary browser360and to return to the sheet view of user interface300.