Example reports

The Process path variable is flagged as default and the folder where the example process reports are initially installed in the store is /Example Reports/Process/. The corresponding folder value for the Shared variable is /Example Reports/Standalone/, which is where all the other examples are initially installed for demonstration purposes.

Consequently, the Path to Executable field in the example Document Format records for most processes is blank.

Document Format records for Reference and other reports that are initially installed in the /Example Reports/Standalone/ folder contain /$Shared/ in the Path to Executable field.

Consequently, for any shortcuts that are created for standalone example reports, the $Shared variable must be specified in the Report Address property.

All three variables (not blank) can be used as the first element in a longer path value to specify a subfolder. For example, some example process reports are PK1 Business Unit specific and are initially stored in /Example Reports/Process/PK1. The value in the example Document Format record for such reports is thus /$Default/PK1/ but could equally have been /$Process/PK1/.

This naming convention is used for the file names of example reports:

• First character

  The SunSystems module or functional area the report relates to:

  • A: Assets
  • C: Corporate Allocation
  • F: Financials
  • I: Inventory
  • O: Order Fulfilment
  • P: Purchases
  • S: Sales
  • X: SunSystems
• Second character

  The type of report:

  • P: Process
  • R: Reference
  • T: Transactional
• Third and fourth character

  The name of the report or function (alpha)

• Fifth character

  Unique ID (numeric)