C h a p t e r 7 : P l a n n i n g M o d u l e i n P e r f o r m a n c e P o i n t S e r v e r 219
Field Explanation
Name This is the name of the application. This is a required field as denoted by the
asterisk (*) next to the field. The name of the sample application used in the
example in this chapter is Budget.
Label This is the label for the application, which is a unique internal identifier for the
application. This is also a required field. This may or may not be the same as the
application name.
Description An optional description of the application.
SQL Server Computer name The name of the server that hosts the back-end SQL Server databases.
Application Database name This is the name of the main database used by the Planning application. The
naming convention for the application database is
_AppDB.
In our example, it is named Budget_AppDB.
Staging Database name The staging database is where the data for the actuals are stored before loading
into the application database. The staging database plays an important role in
a planning application, as will be described later in the chapter. The naming
convention for the staging database is _StagingDB. In our
example, it is named Budget_ StagingDB.
Form Templates location This is the location of the templates that are the basis for the forms that are
ultimately available to the end users for entering the plan, budget, and forecast
data. The end users write their changes back to the system through these forms.
Pages:
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287