The following are common BizSystemFlag errors encountered with loading a PPS model from the StagingDB: 

921- Duplicate Label found across New Row(200) and Existing Row(100)

922- Duplicate Label found within New Row(200)

926- MemberId must be NULL for New Row(200)

927- Label and Name must ... Read More »

If you have existing Planning applicatoins when installing SP1 for PerformancePoint, you must upgrade the databases to reflect the install.  Otherwise, you will not be able to see or connect to the applications after installing.  Also, you will receive an error in the planning server log:

Failed to load application [Application] due to incompatible versions. Please upgrade the application to version 3.0.3917.0

After installing SP1, to upgrade the existing applications, use Planning configuration manager:

Be sure to check the Upgrade Application Databases box, as it is unchecked by default.

**  After this process, you must go into the Planning Admin Console, and "Take Online" each application.

Before creating a new PPS Planning application, it is best to set up your shared directories first.  These will store your PPS Excel forms and reports, and the paths will be required when you set up the application in the Planning Administration console.  Also, you should just copy and past the machine path into the appropriate boxes during setup.

• Cell a1 = ! dimension = dimension name
• Cell a2 = ! hierarchy = All Members
• Cell a3 = Label (value required)
• Cell b3 = Name (value required)
• Cell c3 = Description (value optional)

 Values in the Label and Name columns are required. Values in the Description column are optional, but the header is required in the template. 

Also, you can include other columns with headers and data. ... Read More »

Best practice is to always use a domain account with the password set to never expire for the service identity account when installing PPS Planning.  These settings can be adjusted later, but can create unwanted problems that will be difficult to discover.  When the account designated as the service account has a password expiration, the information is not propagated through PPS and this account can no longer run services.

This is an installation level setting, so it is wise to understand the nature of this account and plan accordingly.  All applications created within your installation will be dependent on this account.

• Windows Server 2003 Standard, SP1 (XP pro, SP2 for the client)
• SQL Server 2005 Enterprise, SP2 (you will also want the client tools)
• IIS 6.0
• .Net 2.0 Framework
• ASP.NET 2.0
• Client only- MS Office (Excel) 2003, SP2, but 2007 is much better

PPS Monitoring and Analytics is more involved, requiring MOSS (Sharepoint Services) and even components of .NET 3.0.  Will get into that soon..