System Management Guide
System Management Guide
User Guide
Information in this document is furnished only under a Customer License Agreement or
non‐disclosure agreement, and may be used or copied only in accordance with the terms
of such agreement. The software described in this document is protected by copyright,
and may not be copied on any medium except as specifically authorized in the license or
non‐disclosure agreement.
This document is also protected by copyright, and may not be reproduced or transmitted,
in whole or in part, by any means, including photocopying, facsimile transmission, or
reduction to any electronic medium or machine‐readable form, without the express
written consent of Sage Software Inc.
© 2010 Sage Software, Inc. All rights reserved.
The Sage Software logo and the Sage Software product and service names mentioned
herein are registered trademarks or trademarks of Sage Software, Inc. or its affiliated
entities. Adobe and Adobe Reader are registered trademarks of Adobe Systems,
Incorporate. Pervasive, Pervasive PSQL, Scalable SQL, and the Pervasive Software logo
are trademarks or registered trademarks of Pervasive Software. Microsoft, the Microsoft
logo, MS, MS‐DOS, FRx, Microsoft Excel, Windows and Windows NT are trademarks of
Microsoft Corporation. Crystal Reports is a registered trademark and technology of
Business Objects, SA. HMIS® is a registered trade and service mark of the NPCA. Other
product names are trademarks or registered trademarks of their respective owners.
Contents
Preface
Contents of This Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Chapter 1: Introduction
The Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Three‐Tier Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Network File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Process Application Server (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Client Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
System Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
System Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Ways the System Permits/Restricts Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Setting up Login IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Setting Up User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Menu Item Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
System Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Processing Company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Processing Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Processing Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Data Integrity Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Update Conflict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Record Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Process Locking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Network File Server (NFS) Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Client Workstation Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
ii Sage PFW
Chapter 4: Operating the PAS
Starting a PAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
PAS Setup Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
How to Start the PAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
How to Reactivate a Stopped PAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Stopping the PAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Network Access from a Stopped PAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
How to Stop the PAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Changing the PAS Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Chapter 6: Templates
Designing Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Sample Template Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Creating a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
How to Define Template Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Adding, Modifying, and Deleting Lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Populating Fields using Find Historical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Customizing Help Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Viewing Work in Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Resetting the Shipping Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
How to Save a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Managing Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Assigning Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Removing, Loading, and Unloading Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Using Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Setting a Default Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
iv Sage PFW
Preface
Introduction
Sage PFW ERP is a suite of software applications that provide accounting, business
operation, process manufacturing and decision‐making functions for your organization.
This guide also contains directions for procedures that can be implemented by the System
Designer—the person in your company who has the authority to customize certain
screens and field behaviors.
Prerequisite knowledge
This user guide is based on the assumption that you have some accounting knowledge. It
does not attempt to teach accounting, but rather describes how to implement accounting
practices using Sage PFW applications.
It is also assumed that you have some working knowledge of personal computers
operating in a network environment, and a familiarity with Windows.
Contents list
The Sage PFW package includes the following items:
• CD‐ROMs
Sage PFW program CD, Crystal Decision program CD, FRx program CD, and
Pervasive PSQL v10 program CD.
System Configuration
The recommended system configuration can be found online at http://www.sagepfw.com.
Related Documentation
The following publications provide additional information on using Sage PFW.
Document Description
System Basics This user guide introduces the basic concepts common to
all applications; including forms, features, keyboard com-
mand keys, and common methods for entering data, gen-
erating and printing reports, and viewing online Help and
user guides.
Application User There is a separate user guide for each application, pro-
Guides viding the specific instructions for processing data in that
application.
All user guides are provided online and may be accessed
from the Help menu.
Online Help Each application contains online Help which provides
information on specific windows and fields. The user guides
and online Help are designed to be used in conjunction
with one another. Online help may be accessed by press-
ing F1.
Database This guide contains the data file layouts for the Sage PFW
Reference applications.
Guide
Introduction
Chapter 1:
Introduction
This chapter provides an overview of the Sage PFW environment, including the features
related to the management of system‐level options and configuration.
In this chapter
This chapter contains the following sections:
Topic Page
The Environment 2
System Access 6
System Processing 9
Data Integrity Controls 11
Directory Structure 14
The Environment
Introduction
This section provides an explanation of the components of the Sage PFW system and how
they relate within the three‐tiered architecture.
In this section
This section contains the following topics:
Topic Page
Three‐Tier Architecture 3
Network File Server 3
Process Application Server (Optional) 4
Client Workstation 4
System Integration 5
2 Sage PFW
Three-Tier Architecture
Three-Tier Architecture
Introduction
Chapter 1:
Components
Sage PFW consists of a three‐tier, client‐server architecture, which includes the following
components:
• Network file server
• Client workstation (one or more)
• Optional Process Application Server (PAS) ‐ one or more
Reports, listings, and posting processes can also be run in a more conventional two‐tier
architecture, where the Process Application Server is not required.
Server files
The network file server contains the executable files for each of the applications, as well as
the data files for your processing companies. Global resources include the blank data files
used to set up and initialize a new company, as well as other configuration files. The
network file server may also house the processing queue, used to hold jobs submitted by
the Sage PFW client workstations, for processing by the Process Application Server.
Note: If a PAS is not installed, all processing of reports, listings, and postings occurs
on the client workstation.
Since a queue can be defined to accept only certain job types (for example, only posting
jobs), the associated PAS can then be dedicated to processing only that type of job. The
types of jobs the PAS processes includes reports and listings, print and posts, and utilities.
It is not recommended to run a PAS on a client workstation.
PAS dispatcher
In Sage PFW, jobs are initially submitted to a queue, where they are held until the PAS is
available for processing. A dispatcher queries the queue periodically for pending jobs,
notifying the PAS of the next job to be serviced.
Client Workstation
Your system can have numerous workstations that enable users to access the global
program and data files with a Sage PFW interface.
The Sage PFW client workstation consists of a system connected to the network and
provides the Windows‐based interface to the Sage PFW database. It interacts directly with
the database on the network file server for simple data access, for example document
entry such as journal transaction entry.
For more complex operations, such as running reports or postings, the workstation may
send a job to a queue, where it is subsequently processed by the PAS or the workstation
may process these jobs locally. Regardless, if a job is submitted to the queue or processed
locally, once a job is submitted by the client workstation, the user is ready to proceed
immediately to another task.
4 Sage PFW
System Integration
System Integration
The different Sage PFW applications interface with each other to provide logical data
Introduction
Chapter 1:
sharing.
Integration examples
Some applications interface automatically upon installation, relying on each other’s data
to automate processing (for example, Sales Order and Accounts Receivable). For other
applications you determine if they interface with each other when you set up the system
(for example, Bank Book and Accounts Receivable or Inventory and Accounts Payable).
System Access
Security restrictions
Sage PFW allows you to permit and restrict user access to various parts of the system, at
various levels.
User definition
In Sage PFW, the term user refers to each workstation or PAS that requires access to the
Sage PFW network file server. In some cases, a single workstation may represent multiple
user access, enabling access either as a client workstation or as a PAS.
In this section
This section contains the following topics:
Topic Page
Ways the System Permits/Restricts Access 6
Setting up Login IDs 7
Setting Up User Access 7
Menu Item Access 8
Security components
System access can be permitted or restricted using the following security components:
• Login and password
A confidential login name and password allows only an authorized user access to the
system.
• Security group
The group to which the user is assigned designates which applications, and which
specific menu items the user is allowed to access (with read, write, or delete access or
any combination of these).
• My Tasks tab
Customize the work process flow for each user on the their own, unique My Tasks
tab. This allows you to determine the menu items that each user needs and organize
them in the desired order.
• User ID
Certain security elements can be defined on a user‐by‐user basis such as to which
security groups the user belongs, the type of user, and the companies the user can
access.
6 Sage PFW
Setting up Login IDs
• Templates
Custom entry screens can be created and used for specific security groups, globally,
or by company. This provides field level security which may be different for each
Introduction
Chapter 1:
group.
Based on a combination of these components, you can appropriately allow or restrict
access to various parts of the system, user by user, and security group by security group.
Network login
A network login name must be set up for each user, based on the procedures and
conventions for the network you are using.
Multiple logins
A separate network login is recommended to access the PAS, although the workstation
may also be accessed as a Sage PFW user.
When you subsequently configure each user in Sage PFW, you can differentiate the type
of user (Sage PFW Client or PAS Client), thereby maintaining separate user configuration
files for each type of user.
User record
In Sage PFW, you must set up and configure each user that requires access to the Sage
PFW database on the network file server. The procedure updates appropriate user
configuration files that specify the type of user (Sage PFW Client or PAS Client) and
defines a Sage PFW user login name and password, security access, and appropriate
companies with which the user can process data.
Security groups
Each user must be part of one or more security groups in order to access Sage PFW. You
can set up multiple security groups to define a level of access appropriate for users
associated with a particular department or job function. Users can belong to more than
one group and will have combined access.
If you need to provide admin rights to a fully functional user, you can do so when you are
setting up a user. The User Setup wizard has an option, Admin Privileges, that can be
assigned to any user. If a user has these privileges they have full access to the different
applications plus the ability to use any of the Admin wizards.
If a user is logged in as the System Administrator (PFWAdmin), selection of a menu item
enables the setup of a preferred queue for processing a particular type of job. If access to
the actual processing function is needed, the System Administrator must login, using a
client login who has admin privileges. Refer to “Setting Up User Information” on page 44
for additional information about setting up users with Admin Privileges.
8 Sage PFW
Processing Company
System Processing
Introduction
Chapter 1:
Introduction
System processing can involve:
• Entering, storing, and processing company data
• Queuing jobs for the PAS to process
• Running reports/listings locally
• Generating printed output on a printer.
In this section
This section contains the following topics:
Topic Page
Processing Company 9
Processing Queue 9
Processing Output 10
Processing Company
Data is processed and stored for a specified company database. If your company
represents a single business concern, in Sage PFW, you set up and configure one
processing company database. However, if your company consists of multiple business
concerns for which you want to process data separately (such as a parent and its
subsidiaries), you can set up and configure an unlimited number of processing
companies.
Processing Queue
A queue is the conduit between the Sage PFW workstations and the Process Application
Server (PAS), for the processing of more complex operations (such as reports and listings,
postings, and utilities). One or more queues may be configured for a single Sage PFW
installation on the network file server, where they reside. However, each must have at
least one dedicated PAS and can be serviced by multiple PAS’s. A queue can be set up to
accept only selected job types, thereby allowing you to define, for example, one queue to
accept only report or listing type jobs, and another only posting jobs.
If a PAS is not installed, a queue is not necessary. All complex operations run at the client
workstation level.
Preferred queue
The preferred queue (set up by the System Administrator) becomes the default queue
when designating the routing of a job. However, you can override the default and
designate the specific queue that is to be used when submitting a job.
Queue manager
The queue manager is a utility that enables users to view the jobs submitted. All users
have the ability to not only view, but delete, their own jobs. Users can view the status of
jobs submitted by other users, although the job cannot be deleted.
The System Administrator has the ability to delete any jobs from any queue.
Processing Output
When a job is submitted to the queue or run locally, a method of output is selected by the
user. This allows the user to determine where the output is sent.
If a job is submitted to run locally, the output can be sent directly to a printer or displayed
on the client workstation. From the viewer, the user can export the output, print the
output, or close the view.
If a job is submitted to run remotely, the output can be sent directly to a printer or to the
queue manager. Once in the queue manager, the output can be viewed repeatedly by the
user, sent to the printer, or emailed as an attachment.
Printing output
To generate printed output such as reports and listings, Sage PFW utilizes printers setup
in Windows.
When you distribute a report, a PDF format is used. This allows anyone to view an
attachment if they have Adobe Reader installed.
If a job is submitted to run locally or being viewed in the Crystal Viewer, it can be
distributed via email by using the export utility. Additionally, output can be published on
the Internet by exporting the output to HTML. Refer to the Crystal User Guides for
additional information on exporting.
10 Sage PFW
Update Conflict
Introduction
Chapter 1:
Introduction
Because Sage PFW provides multi‐user capabilities, the following mechanisms are used to
protect your data and ensure its integrity during processing.
In this section
This section contains the following topics:
Topic Page
Update Conflict 11
Record Locking 11
Process Locking 12
Update Conflict
Update conflict is a mechanism used to protect the integrity of your company data during
an update. The update conflict mechanism ensures that a record is always viewed with its
most current data before it can be changed. Multiple users can simultaneously read a
particular file maintenance record, but are restricted to saving changes to the record on a
first‐come, first‐serve basis. If an update conflict occurs, the system displays an Error 80,
notifying the user of the situation.
You can click OK to continue to try the update again. Once the record has been updated
by the first process, it will be available for additional updates.
Record Locking
Record locking is a mechanism used to protect the integrity of your company data during
posting, where the program is not protected by process locking, to prevent a record from
being updated by another activity. For example, in Accounts Receivable, record locking
prevents a record in the Customer Activity file from being updated simultaneously by
both the invoice post and the generation of the Aged Receivables report.
If an update conflict occurs, the system puts the subsequent processing activity in a delay
loop until the record is unlocked, or until the system has exhausted the number of retries
for accessing the locked record. In the former case, the subsequent activity can continue its
processing when the record is no longer locked. In the latter case, the system displays an
error message, notifying the user of the situation and allowing the user to retry or abort
the processing.
When a record lock is encountered on a job that is not monitored, the lock must be cleared
on the workstation or on the PAS by clicking OK or pressing Enter.
Process Locking
Process locking is a mechanism that prohibits more than one user from performing the
same or conflicting processes simultaneously. For example, in Accounts Payable, process
locking prevents two users from posting vouchers simultaneously.
If a process lock condition occurs, the PAS returns the subsequent job to the queue
manager’s inbox with an Access Denied message and terminates that job.
For example, Print and Post Voucher and Debit Memo is locked against Period End Close.
When one user processes Print and Post Voucher and Debit Memo on one PAS the system
updates the Process Locking (LOCKFILE) file. When another user attempts to process
Period End Close on another PAS, the system checks the Process Locking file and the PAS
then sends a message back to the appropriate client queue manager where the job
originated and terminates that job. The second job must be resent to the queue.
Each of the listed processes are locked from simultaneous use by multiple users within the
same company. However, some processes are locked against different processes that
cannot be run at the same time because one depends on the completion of the other.
General Ledger
Locked Against
Menu Option
Edit List Period Post, Period Close, Year End Edit List, Year
End Post, Year End Close, Gen Auto Transac-
tions, Sub System Transaction Import, Generate
Chart of Accounts, and itself
Period Post Edit List, Period Close, Year End Edit List, Year
End Post, Year End Close, Gen Auto Transac-
tions, Sub System Transaction Import, Generate
Chart of Accounts, and itself
12 Sage PFW
Process Locking
General Ledger
Locked Against
Menu Option
Introduction
Chapter 1:
Period Close Edit List, Period Post, Year End Edit List, Year End
Post, Year End Close, Gen Auto Transactions,
Sub System Transaction Import, Generate Chart
of Accounts, and itself
Year End Edit List Edit List, Period Post, Period Close Year End Post,
Year End Close, Gen Auto Transactions, Sub Sys-
tem Transaction Import, Generate Chart of
Accounts, and itself
Year End Post Edit List, Period Post, Period Close, Year End Edit
List, Year End Close, Gen Auto Transactions, Sub
System Transaction Import, Generate Chart of
Accounts, and itself
Year End Close Edit List, Period Post, Period Close, Year End Edit
List, Year End Post, Gen Auto Transactions, Sub-
System Transaction Import, Generate Chart of
Accounts, and itself
Generate Auto Edit List, Period Post, Period Close, Year End Edit
Transactions List, Year End Post, Year End Close, Sub System
Transaction Import, Generate Chart of
Accounts, and itself
Sub System Edit List, Period Post, Period Close, Year End Edit
Transaction List, Year End Post, Year End Close, Gen Auto
Import Transactions, Generate Chart of Accounts, and
itself
Generate Chart Edit List, Period Post, Period Close, Year End Edit
of Accounts List, Year End Post, Year End Close, Generate
Auto Transactions, Sub System Transaction
Import, and itself
Directory Structure
Introduction
The Sage PFW system configuration, as represented by the directories and the files
contained in each, is described in the following sections.
In this section
This section contains the following topics:
Topic Page
Network File Server (NFS) Directories 14
Client Workstation Directories 17
\PLATINUM
The \PLATINUM directory is the program directory into which the executable files
(.EXE) for each Sage PFW application are copied when you install the application with the
exception of the Purchasing Pro, Order Entry Pro, Inventory Pro, and System Manager
Pro. These application executable files are located in the \PFW directory. The \Platinum
directory is created in the root directory, on the drive you specify during installation.
Important! To ensure that Sage PFW operates successfully:
• the \PLATINUM directory must be located on the root directory, or
• you can use the SHARE directory using Windows to map the drive
\RESOURCE
The \PLATINUM\RESOURCE directory contains program resource files necessary for
the operation of Sage PFW. This directory stores *.TLF files, which contain the system
defined lookup values for each application.
\QUEUE
The \PLATINUM\QUEUE directory contains the queue files that record and track jobs
submitted to the defined queues for processing by the PAS.
14 Sage PFW
Network File Server (NFS) Directories
\DATA
The \PLATINUM\DATA directory serves as a perpetual storehouse of pre‐initialized
Introduction
Chapter 1:
data files and the DDFs for all applications found in Sage PFW. When you initialize an
application for a processing company using the Company Setup Wizard, these blank, pre‐
initialized data files are copied from this directory to the processing company’s directory.
\DATA\Default
This directory stores basic default values for a new company. Additional directories may
be added to reflect different sets of defaults for different industries. When initializing a
new company, the System Administrator may select one of these defaults.
\PFWADMIN
The \PLATINUM\PFWADMIN directory contains the files for the pre‐defined System
Administrator user, set up with specific access rights for the System Administrator. These
files also represent the global resource files needed for user access and processing. This
directory also contains prior versions of the DDF files, located in separate folders.
\PFWADMIN\DATA
This directory contains default security files. It can be used to restore system security back
to the new installation status. All security will have to be redefined after copying these
files to the \PFWADMIN directory.
\PFWCLIEN
The \PLATINUM\PFWCLIEN directory contains the setup programs necessary for
installation on the Sage PFW client workstations.
\GLICLIEN
The \PLATINUM\GLICLIEN directory contains the files required to install and run the
GL Import Utility.
Note: This directory only exists if you have updated from a prior version of Sage
PFW. A new installation will not have this directory.
\ACRCLIEN
The \PLATINUM\ACRCLIEN directory contains an .EXE file to be used for the
installation of Adobe Reader.
\PFWRES\ MASTER
The \PLATINUM\PFWRES\MASTER directory contains:
• Program resource files necessary for the operation of Sage PFW (for example, menu
item definitions)
• Online user guides and product publication files (for example, arguide.pdf)
• PDF files for every Sage PFW report. These are used by the User Guides as links to
sample reports.
\UPDATE
This directory stores the Sage PFW Service Pack Installer. Use this installer to install files
from service packs downloaded from the web.
\[company]
The \PLATINUM\[company] directory is created when you setup a new processing
company. The system creates a company directory with the key you assign for the
company. Your system will have one or more company directories, possibly including
one or more demonstration companies. The creation of separate directories for each
company safeguards the integrity of each company’s data.
\[company name]\ATTACH
This directory stores all the attachment files from the Universal Notes and Attachments
feature. When you add an attachment to a record in Sage PFW, a copy of the attachment
file is saved on the server in this directory.
\[company name]\ATTACH\ARCHIVE
The Universal Notes and Attachment feature can archive any attachment when the
attachment is purged. If you choose to archive an attachment, the attached file is moved
into this directory.
\[username]
The \PLATINUM\[username] directory is created for each user and PAS you set up and
configure. The directory is named according to the user ID you specify. For example, if the
user ID is JOHN, then the name of the user directory is \PLATINUM\JOHN.
Because each user or PAS has a unique directory, a unique configuration can be
established to suit each user or PAS needs. For example, different security information
can be set up depending on the tasks performed by each user.
16 Sage PFW
Client Workstation Directories
Introduction
Chapter 1:
database on the network file server and the appropriate interface files.
\PFW
The \PFW directory contains the user interface files for Sage PFW, including the
<username>.INI file, in which system operation parameters are designated. The directory
also contains and many of the executable files needed for processing in the manufacturing
suite of applications.
Caution: To ensure that Sage PFW operates successfully, the \PFW directory must be
located on the root directory.
\PFW\BMP
The \PFW\BMP directory contains the bitmaps used by the client workstation.
\PFW\TEMP
This directory contains temporary files for serial/lot files.
\PFW\HELP
This directory stores all of the help files (for example, armaster.chm).
18 Sage PFW
Chapter 2:
Configuring the System
Introduction
This chapter provides instructions on using wizards to set up those records that are
Chapter 2: Configuring
required before users can access or process data in Sage PFW. Setup consists of defining
the following, as applicable:
the System
• Processing companies
• Queues
• Security groups
• Users.
In this chapter
This chapter contains the following topics:
Topic Page
About Wizards 20
Setting Up Processing Company Information 26
Setting Up Queue Information 32
Setting Up Security Group Information 35
Setting Up User Information 44
Security Group Reporting 53
Recovering or Optimizing Data Files 54
Initializing Data Files 56
Optimizing Notes and Attachments 57
Conversion Wizards 58
About Wizards
Description
Sage PFW contains wizards that help you set up certain system information in a logical
step‐by‐step manner.
A wizard consists of a series of windows which allow you to enter setup information.
Although the windows vary according to the setup record you are defining, there are
certain elements that are common for all wizards.
In this section
This section contains the following topics:
Topic Page
Setup Wizards 20
Common Elements of Setup Wizards 23
Setup Dependencies 25
Setup Wizards
When available
A list of the available wizards is displayed on the Admin menu on the Business Desktop.
The Admin menu is only available if you are logged in as a System Administrator.
Types of wizards
The following wizards are available depending on your installed applications:
20 Sage PFW
Setup Wizards
Chapter 2: Configuring
Sample menu
the System
In the illustration below, the processing company has General Ledger (Premier Edition),
Accounts Receivable, and Project Costing installed, so the Account Configuration Setup,
Form Configuration Setup, and Project Configuration Setup wizards for those
applications are listed.
Setup order
When initially setting up the system, you should access the wizards in the sequence
presented in the table, with the exception of Registration and Auto Data Conversion
which are automatic. The information set up in one wizard is most likely part of the
information set up with the next wizard. For example, in the User Setup wizard, you
designate companies, queues, and security groups, as set up in the other wizards.
For details on the information you set up using the application‐specific wizards, refer to
the application user guide.
Wizards
Some wizards are specific to certain applications, while others are global. The following
table discusses each.
Wizard Description
Account Configuration For General Ledger (Premier or Standard Edition)
Setup users, this wizard is used to set up the format of the
account number.
Refer to the General Ledger User Guides for more
information.
Form Configuration For Accounts Receivable and Sales Order users,
Setup this wizard is used to configure invoices, credit
memos, customer statements, and sales orders.
Refer to the Accounts Receivable User Guide for
more information.
Project Configuration For Project Costing users, this wizard is used to
Setup configure project references.
Refer to the Project Costing User Guide for more
information.
Registration For new and upgrading users, this wizard is used to
register installed applications.
Refer to “Registering Sage PFW” on page 40 for
more information.
Auto Data Conversion For customers upgrading from Sage PFW 4.6 or
higher to the current version, this wizard converts
pre-existing data to the current version.
Refer to the Sage PFW Installation Instructions
and Upgrade Guide for additional information.
Optimize Data File This wizard is used to optimize your hard disk’s per-
formance by removing unnecessary records,
reducing the size of a file. This utility also creates a
log file which is used to capture information dis-
played on a message box upon completion of
the optimization process. Refer to “Recovering or
Optimizing Data Files” on page 54 for more infor-
mation.
Recover Data File This wizard rebuilds damaged data files.
Refer to “Recovering or Optimizing Data Files” on
page 54 for more information.
Initialize Data File This wizard initializes any specific data file.
Refer to “Initializing Data Files” on page 56 for
more information.
Queue Repair This wizard repairs damaged PASs and/or queues.
Refer to “How to Repair a Queue” on page 102
for more information.
Optimize Notes and This wizard optimizes notes and attachments or
Attachment Database removes expired notes and attachments.
Refer to “Optimizing Notes and Attachments” on
page 57 for more information.
Security Data This wizard converts user security if the security files
Conversion have been copied from a prior version.
Refer to the Sage PFW Installation Instructions
and Upgrade Guide for more information.
22 Sage PFW
Common Elements of Setup Wizards
Chapter 2: Configuring
the System
The Company Setup wizard has an additional option to Create DSNs for existing
companies.
Option Description
Initialize a new [setup Creates a new setup
record] record.
Modify an existing [setup Changes an existing
record] setup record.
Remove an existing [setup Deletes an existing setup
record] record.
Create DSNs for all existing Creates DSNs for all exist-
companies [only available in ing companies.
Company Setup wizard]
The option chosen (Initialize, Modify, or Remove) is displayed in the lower left corner of
each wizard window. Additionally, when changing or deleting an existing setup record,
the wizard displays a list of the existing setup records, from which you can choose the one
to change or delete.
WARNING: When you are running a wizard, make sure that all users are logged
out of Sage PFW. If you make changes or delete existing records while the user is
in Sage PFW, the wizard may not be able to completely update the appropriate
files.
To do this... Click...
Exit the wizard. If you haven’t completed the Exit
setup yet by choosing Finish, the system does
not initialize, modify, or delete the specified
setup record.
Back up a step, by returning to the previous Back
wizard window.
Go to the next step, by proceeding to the Next
next wizard window.
Complete the process of initializing, modify- Finish
ing, or deleting the specified setup record.
To... Use...
Move the cursor through fields and button Tab
commands.
Toggle the selection of a setup option. Space-
bar
24 Sage PFW
Setup Dependencies
Setup Dependencies
The setup of users is dependent on information defined in the other setup records:
company, queue, and security groups.
Therefore, when setting up the system for the first time, carefully prepare and double
check your company, queue, and security group information before setting up your users.
This procedure enables you to access user setup records only once, thereby streamlining
your workload.
Reference
Chapter 2: Configuring
For a listing of configuration files created and maintained by the setup wizards, refer to,
the System
“Appendix A: System Manager Files” on page 153.
Introduction
Sage PFW enables you to process your accounting and management information for an
unlimited number of companies. For example, you can set up separate processing
companies for a parent company and each of its subsidiaries. You set up a processing
company to have the system initialize the database files in which that company’s data will
be stored.
Important! During the 30 day registration period, you have access to
unpurchased applications for demonstration purposes. Use demonstration
companies, not real companies to experiment with these unpurchased
applications so that your real company data is not affected when you uninstall
unpurchased applications.
DSN Creation
The Customer Insights application and the Advanced Lookup Feature use the Pervasive
Relational engine for database access. This requires the creation of a DSN for each
company.
DSNs must be created both for existing companies as well as newly created companies.
The Company Setup wizard automatically creates a DSN on the server where the
company data files are located during creation of a new company, modification of an
existing company, or for all existing companies.
When you use the Company Setup wizard, one of the following may occur, based on the
option you select on the first screen of the wizard.
• When you select Initialize a new company, a DSN will be created for the new company.
• When you select Modify an existing company, either a new DSN is created or the exist‐
ing DSN is overwritten with any new information.
• When you select Remove an existing company and you elect to remove company data
files, the DSN for that company is deleted. Otherwise, the DSN is not deleted.
• When you select Create DSNs for all existing companies, a DSN is created for each
company in the PFWAdmin users UTMCFILE file. As the DSN is being created for
each company, the Company Key and Company Name is displayed to show the user
the status of the overall creation process.
You must be a part of the Pervasive_Admin group if you do not have full OS admin rights
on the machine where Pervasive PSQL server database engine is running. Pervasive PSQL
requires Administrative‐level rights to:
• create and configure named databases (DSNs) and tables
• set engine configuration options
• view and set engine monitoring values
• view certain engine configuration settings
26 Sage PFW
Information Required to Set Up a Company
• view or modify a table design with Table Designer
To have administrator‐level access to the Pervasive PSQL database engine you must:
• possess full administrator‐level rights on the machine on which the database engine is
running. Being a Domain administrator may not be enough because you still may not
have full permissions on certain local machines. OR
• be a member of the operating system group called Pervasive_Admin.
There is one exception to this rule:
• To modify a table design with Table Designer, you must have full administrator
Chapter 2: Configuring
rights on the machine on which the database engine is running even if you are a mem‐
ber of the Pervasive_Admin group.
the System
Pervasive_Admin option is offered so that you can grant users administrative rights to the
database engine without granting them administrative rights to the operating system
where the database engine resides (with one exception noted above).
In this section
This section contains the following topics:
Topic Page
Information Required to Set Up a Company 27
How to Complete the Company Setup Wizard 28
Modifying an Existing Company 29
Deleting an Existing Company 30
Demonstration Companies 31
Company key
Identify a unique 6‐character identification for each company.
The system uses this key to create the directory in which it will initialize the data files. The
company key must conform to the Windows naming conventions for directories and
cannot use a dash (‐). The system automatically converts any company key you enter to
uppercase characters.
Company name
Identify the full name for the processing company as you want it to appear on reports and
at the bottom of the Business Desktop.
Drive specification
Identify the drive, on the network file server, where the data files should be initialized for
all applications. This drive must be the same as where Sage PFW program files are
installed.
Drive Specifications for the sample companies default to your base Sage PFW drive letter.
Available Users
If you have already setup your users, you can select the users that you want to have access
to the current company using the company setup wizard. When you give a user access to
a company you have the option to assign an Effective Date and Expiration Date. If you
enter these dates, you can limit the amount of time that a user has access to a specific
company. For example, you can use these dates to allow someone to be temporarily
assigned to a company to cover vacation or temporary personnel assignment
requirements.
Note: To select all users using the keyboard, press the hot key <Alt‐L>.
Initializing applications
When you initialize a company, the system copies all of the pre‐initialized data files for
the selected applications from the \PLATINUM\DATA\DEFAULT directory to the
company directory you are setting up. This establishes the database for processing your
data for this company. Typically, this is a one‐time procedure.
If you are initializing a new company, the initialize options are automatically selected
when the Initialize Applications window displays.
Note: To select all applications, you can use the hot key <Alt‐A>.
• Set up a new company
• Modify an existing company
• Delete an existing company
• Create DSNs for all existing companies
28 Sage PFW
Modifying an Existing Company
Procedure
Follow these procedures to access the company setup wizard and set up a company:
Step Action
Chapter 2: Configuring
1 Close other Windows applications.
the System
2 From the Business Desktop, choose the Admin menu,
then choose Company Setup.
3 Choose OK to bypass the "Cannot access company..."
message, if it appears.
4 Follow the on-screen wizard instructions.
Drive specification
If you adjust the configuration of a previously installed company, consider the following
consequences.
You can change the drive specification if for some reason you found it necessary to move
the location of the company data files. Changing the drive specification in the setup
wizard does not move the data files automatically.
Note: The company data must reside on the same drive as the program files.
If you change the drive specification of the data directory for a previously established
company, the changes are not immediately recorded for each user. Therefore, any user
attempting to access and process data in the processing company will receive an error
message that the company data files cannot be found. To record the drive specification
change with each user, you must modify each applicable user in the User Setup wizard by
stepping through each wizard window until you can choose the Finish command. This
procedure updates the appropriate user configuration file with the changed drive
specification for the processing company.
Re-initializing files
If you re‐initialize the data files, the procedure clears any and all data from the processing
company files. Typically you would re‐initialize data files only for a company that had
been set up for training or testing purposes (for example, for learning about the system
features and functionality). Generally, once actual data has been entered and processed in
a company, you would not want to lose the data by re‐initializing the files.
Background
Typically, you would want to delete a company only if it has been set up in error, or if the
company had been setup for training or testing purposes (for example, for learning about
the system features and functionality).
WARNING: Before you delete an existing company, make sure that all users have
logged out of that company.
If you choose Yes the DSN created for this company will also be deleted. If you choose No,
the system deletes the company information from the global resource file, but does not
delete the company data files on the server.
Note: If you choose to remove an existing company, be aware that the system
only removes those files that it created. If you created some files of your own
within that company directory, the wizard will not delete those files. If you wish
to remove the remaining files and the company directory, you must do it manu‐
ally using Microsoft Explorer.
30 Sage PFW
Demonstration Companies
Demonstration Companies
When you first install Sage PFW, the Company Setup wizard includes pre‐defined sample
companies containing demonstration data, available for training and testing purposes.
Chapter 2: Configuring
The demonstration companies include:
the System
Company Company
Purpose
Key Name
CHEM Chemical Demo data based around a chemical manu-
Demo Data facturing company.
FOOD Food Demo Demo data based around a food manufac-
Data turing company.
GLSDEM Demonstration, General Ledger - Standard Edition demo
Inc. data.
PREMGL Demo Golf, Inc. General Ledger - Premier Edition demo data.
PRMCON International Premier Consolidations & Inter-Company
Golf, Inc. demo data.
PRMTRN Premier Premier Currency Translation demo data.
Translation
Installation
During the installation of the server files, you have the option to install CHEM, FOOD,
GLSDEM, or PREMGL demonstration companies. If you choose to install the Premier
Consolidations application, the installation automatically installs the PRMCON company
data. If you choose to install the Premier Translations application, the installation
automatically installs the PRMTRN company data.
Introduction
To enable the system to remotely process a report or listing, the printing of a document
form, or the running of a posting or a utility, the job must be submitted to a queue, where
the job waits to be processed by the PAS.
If you didn’t install a PAS, the Queue wizard is not available.
Queue setup is not necessary when processing locally, without a PAS. A hidden queue
ships with the system for local processing.
In this section
This section contains the following topics:
Topic Page
Information Required to Set Up a Queue 33
How to Complete the Queue Setup Wizard 33
Modifying an Existing Queue 34
Deleting an Existing Queue 34
32 Sage PFW
Information Required to Set Up a Queue
Queue ID
Identify a 4‐character queue ID. This ID is used by the system to create the UTQxxxx.SRQ
file.
Queue name
Identify a descriptive name for the queue.
Chapter 2: Configuring
the System
Queue service types
Determine which job service types can be submitted to the queue. Your options are all
types or selected types, where you can then select Listing, Document Print and Post,
Report, and/or Utility.
Make sure that each of the job service types has been set up with at least one queue. If you
neglect to set up a particular service type with a queue, jobs of that service type cannot be
processed by the PAS.
• Set up a new queue
• Modify an existing queue
• Delete an existing queue
WARNING: When you are running a wizard, make sure that all users are logged
out of Sage PFW. If you make changes or delete existing records while the user is
in Sage PFW, the wizard may not be able to completely update the appropriate
files.
Procedure
Follow these procedures to access the queue setup wizard and set up a queue:
Step Action
Background
Once a queue has been set up, you can delete the queue. Typically, you would want to
delete a queue only if it had been set up in error. However, if a queue has been used for
submitting jobs, make sure all jobs have been completed before deleting.
Click OK and wait until the process is complete to try again.
34 Sage PFW
Deleting an Existing Queue
Introduction
For the purposes of controlling and restricting the level of access to and in the system, you
define user security in groups. User security includes setting up the following
components:
• Login and password
Chapter 2: Configuring
A confidential login and password to allow only an authorized user access to the sys‐
tem.
the System
• Processing company
The one or more processing companies in which the user is allowed to process data.
• Security group
The security groups to which the user is assigned, that designates which applications,
what job types, and which specific menu options the user is allowed to access.
• Templates
Templates provide an additional level of security by restricting the fields that display
on an entry screen or a file maintenance screen.
This section provides information on setting up one or more security groups, for
assigning to each user in User Setup. The login, password, and processing company
access is set up for each user in User Setup, described in “Information Required to Set Up
a User” on page 47.
In this section
This section contains the following topics:
Topic Page
Information Required to Set Up a Security Group 36
How to Complete the Security Group Setup Wizard 41
Modifying an Existing Security Group 43
Deleting an Existing Security Group 43
Group ID
Identify an ID for the security group.
Name
Identify a descriptive name for the security group.
36 Sage PFW
Information Required to Set Up a Security Group
Applications
Identify the applications to which the users assigned to this group will have access.
Chapter 2: Configuring
the System
Access definitions
Identify any specific menu items to which the users assigned to this group will have read,
write, and/or delete access, or no access.
Note: When you specify Write or Delete access, Read access is automatically
checked.
The available menu items are listed on the wizard window based on the applications
designated for this group.
Read/Write/Delete Rights
The following table shows what happens with each type of menu item when you have
selected different combinations of access.
38 Sage PFW
Information Required to Set Up a Security Group
Chapter 2: Configuring
Can add new presaved parameters;
Can edit/save existing presaved
parameters;
the System
Can delete existing presaved parameters;
Can run presaved parameters
Financial Explorer
Can execute, edit and save, and delete
views
Delete Exceptions
The previous table discussed the effects of setting security on different types of menu
items. This information is correct with the following exceptions. The following menu
items do not support Delete functionality, therefore the Delete rights access setting has no
effect on them.
Accounts Cash Receipts Apply On Delete rights access setting controls ability
Receivable Account to delete pre-saved parameter.
Bank Book Account Reconciliation Delete rights access setting controls ability
to delete pre-saved parameter.
Customer All Customer Insights Delete not available in this menu item
Insights Views
Inventory Physical County Entry Delete rights access setting controls ability
and Correction to delete pre-saved parameter.
Laboratory Comparative Properties Menu item does not save data to data-
Analysis base, just supports ability to print data.
Order Entry Inventory Bill of Lading Does not save data to database, just sup-
Pro ports ability to print data.
40 Sage PFW
How to Complete the Security Group Setup Wizard
Sales Order Sales Order Shipment Sales Order cannot be deleted. Ability to
Entry edit the Sales Order by inserting and delet-
Chapter 2: Configuring
ing comment lines is controlled by Write
access rights, since you must save the Sales
the System
Order Shipment after editing it.
Note: Some Document Entry menu items are processed with a parameter screen
first, followed by an entry screen displayed, like BB Journal Correction. The
Delete access rights setting will only control the ability to Delete presaved param‐
eters in these menu options. The Delete access rights setting does not affect the
ability to delete row entries within these menu items.
• Set up a new security group
• Modify an existing security group
• Delete an existing security group
Procedure
Follow these procedures to access the Security Group Setup wizard and set up a security
group:
Step Action
Special Buttons
When setting security at the menu item level, you have several buttons available to make
this process easier. The following table discusses these buttons.
42 Sage PFW
Modifying an Existing Security Group
Chapter 2: Configuring
the System
Collapse all items at current This button collapses the menu items into
level or lower the folders found on the tree view.
Show all menu items This button displays all application folders,
sub-folders, and menu items, regardless of
the assigned rights.
Introduction
For each user that needs access to Sage PFW, including each PAS you have available to
process jobs, you must set up a user record. You must also set up a user record for each
System Designer, assigning designer rights to those users and users that will have Admin
privileges. The user record specifies the various configuration options for allowing the
appropriate user access to the system.
Default user
As a default, the system includes a predefined user called PFWAdmin, who has access to
the wizards for configuring the system. This user also defines the look and requirements
of the passwording used by all other users.
In this section
This section contains the following topics:
Topic Page
Maintaining Standards Among Users 45
Selecting a User Type 45
Information Required to Set Up a User 47
Information Required to Set Up a PAS User 50
How to Complete the User Setup Wizard 51
Deleting an Existing User 52
44 Sage PFW
Maintaining Standards Among Users
Chapter 2: Configuring
the System
Maintaining system-wide date and time
It is recommended that the Sage PFW client workstations, the Network File Server, and
each PAS are set to the same date, time and regional settings, if your networking software
permits.
User types
There are two types of users you may set up with the user setup wizard:
• Sage PFW Client
(Sage PFW client workstation)
• PAS Client
(Process Application Server)
Username
Identify a username that represents the Sage PFW login for the Admin user. You can
assign a descriptive name that is more easily remembered by the user. The username is
case‐sensitive. The default value for the administrator user is Admin.
Password
This field allows you to change the password for the Admin user. The default password is
MASTER. Remember, this field is case sensitive.
Confirm password
Retyping your password makes sure that you entered it correctly. The field must match
the Password field.
Pervasive Password
Enter the Pervasive password for the PFWADMIN user that you created in the Pervasive
Control Center when you enabled the Pervasive Security feature. When you enable the
Pervasive Security feature, you need to add a Pervasive User Name of PFWADMIN and a
password in the Pervasive Control Center. After that is complete, you must also enter that
password in Sage PFW. This provides the Pervasive Security Password to Sage PFW. For
more information about using Pervasive Security, refer to , “Appendix D: Pervasive and
OS Security” on page 173.
Note: If the Pervasive Security has been enabled on the company database and a
valid Pervasive Username and Password are not known, the Advanced Lookup
Engine (ALE) and Customer Insights (CI) won’t work. They use the Pervasive
relational engine and need to be able to connect to a secured Pervasive database
by passing in a valid username and password.
To... Action
Force users to include alpha charac- Select Require Alpha
ters in their password Character
Force users to include numeric char- Select Require Numeric Character
acters in their password
Force users to include special charac- Select Require Special Character
ters in their passwords. Only the follow-
ing special characters are available:
!”#$%&’()+,-./:;<=>?@{|}~
Require users to create a password of Enter the Minimum Length for the
a specific size passwords. The minimum length is tied
to the value of the requirement
checkboxes. If all are checked, the
minimum length is 3.
Enter 0 to allow any size of password.
The maximum value is 99.
46 Sage PFW
Information Required to Set Up a User
To... Action
Limit the number of times that a user Enter the number of Login Attempts
can attempt to login to Sage PFW Allowed
before a lockout message displays. If the attempts allowed is unlimited,
enter 999. This is also the default value.
Force users to refresh their password Enter the Number of Days to Expire.
regularly The default number of days is 9999.
If this option is selected, the expiration Select Update Expiration Dates
dates for all users are recalculated
based on Number of days to expire
value currently in Admin.
Chapter 2: Configuring
If this option is not selected the non-
admin users expiration dates are not
the System
updated even if the Number of days
to expire value has been changed in
Admin user.
WARNING: Do not use the name of any Sage PFW subdirectory as a user ID. If you
do, the existing Sage PFW subdirectory is overwritten and data loss can result.
Type of user
Use the Sage PFW Client as the user type for the all those who actually process in the
system.
User ID
Identify a unique user ID for the user. This ID can reflect the user’s network login. Also,
many of the Sage PFW printing and posting programs, allow you to post by User ID.
Note: A User ID can not duplicate a Company Key created in the Company Setup
Wizard.
You can add additional users with Admin privileges if you need them to be able to
process in Sage PFW.
The user ID is used by the system to create a subdirectory, on the network file server, to
store the users configuration files.
The system stores the user ID in all upper‐case characters, regardless of your entry. If the
user being created has access to FRx, enter their network login name in the User ID field.
User name
Identify a username that represents the Sage PFW login for the user. You can assign a
descriptive name that is more easily remembered by the user. The username is case‐
sensitive.
Password
Identify a login password, if desired or required. The password is case‐sensitive.
Note: A user can change their own password from the login screen.
Confirm password
Retyping the password makes sure that you entered it correctly. This field must match the
Password field.
Admin Privileges
When you add a user you can determine if they should have Admin Privileges. If you
create a user that has Admin Privileges, that user:
• Has the Admin group on the tool bar
• Has access to all Admin wizards, except Security Data Conversion and the Auto Data
Conversion wizards
• Can not change the priority of a menu item.
Profile
Be aware that each regular user is identified as “normal,” rather than as an administrator.
A “designer” user will have access to the system design options, like creating templates
and define queries for the Financial Explorer. A “developer” user is only available when
the Customization Workbench (CWB) application is installed. A developer has specific
rights and are discussed in the CWB ‐ Developer Utilities User Guide.
48 Sage PFW
Information Required to Set Up a User
Chapter 2: Configuring
When the OK button is selected, the login window closes and the Administrator for Sage
PFW must reset the login count back to 0 for that user to login again.
the System
Change password at next login
Select this option to force the user to change their login the next time they login.
Note: A user can opt to change their password at any time when they login to
Sage PFW.
Companies
Identify each company in which the user can process data. Once you’ve selected the
companies to which a user must have access, you have the option to assign Effective and
Expiration Dates. This allows you to restrict the length of time that a user has access to a
particular company.
Groups
Identify the security group or groups to which this user belongs. Each user must belong to
at least one security group. The group determines the security level for a user.
In addition, you can control security access using effective and expiration dates as needed
for each user. Users can be assigned effective and expiration dates for each Security Group
to which they belong. The ability to assign access dates enables your IT department to
work ahead, setting up new employees before they actually arrive, and simplifies security
changes to accommodate vacation schedules and contract workers. And, by assigning
expiration dates to prevent access, you can retain user information for better auditing
capability.
Type of user
Choose PAS Client as the user type.
Note: It is not recommended to run a PAS on a client workstation. Refer to“Pro‐
cess Application Server (Optional)” on page 4 for additional information about
setting up a PAS.
User ID
Identify the network login ID you set up for the PAS machine. For example, you might
enter RPTPAS to denote that only reports will be processed by this PAS.
PAS Name
Identify a more descriptive name for the PAS.
Password
Identify a login password, if desired. The password is case‐sensitive.
Note: Password requirements apply to all user types, including PAS users.
50 Sage PFW
How to Complete the User Setup Wizard
Confirm password
Retyping the password makes sure that you entered it correctly. This field must match the
password field.
Queue name
Identify the queue name the PAS should be servicing.
Drive letter
Chapter 2: Configuring
Identify the drive on the network file server where the queue directory is located. This is
the System
the same drive where the server program files were installed.
Polling interval
Identify the polling interval of the service queue. The interval is based on the number of
seconds by which the PAS should check the queue for jobs to be processed. The
recommended polling interval is 5 seconds.
Identify the polling interval of the user queue. The interval is based on the number of
seconds by which the user private queue should check the PAS for new messages and
information. The recommended polling interval is 5 seconds.
Caution: When using the User Setup wizard to define a PAS, the recommended
Polling Interval is 5 seconds, as the PAS and Queue should communicate very
often. However, the value should not be set to one of the following numbers, as
they will result in receipt of an Illegal Function Call message, or a message caus‐
ing you to close Windows applications and restart your system:
44
300
556
812
• Set up a new user
• Modify an existing user
• Delete an existing user
Procedure
Follow these procedures to access the user setup wizard and set up a user:
Step Action
Background
You can delete an existing user who no longer needs any access to the system.
As an alternative to deleting a user, you may want to set the expiration date for the user’s
access to all companies or simply uncheck the user’s access to all companies. This will
leave a historical trail of who the user was while denying future access to the system.
52 Sage PFW
Deleting an Existing User
Description
Once security group and users are setup, you can print a report that documents the setup
information. This report is found under the System Manager application folder in the
Reports folder. This report can not be run by the PFWAdmin user, however, a user with
Admin Privileges can run the report, based on the security level for the report assigned
through the Security Group Setup wizard.
Chapter 2: Configuring
the System
Note: You should limit access to this report to only administrators or managers as
security sensitive information is included on the report.
Order by
This report offers three sorting methods; Security Group, Application or User. Each report
provides ranges that allow you to restrict the information you want to include on the
report.
Note: If, in Security Group Setup, Read, Write, and Delete access are set to “none”
for a menu item, that menu item will not display on the report. Only items that
have Read, Write, and/or Delete access are included on the report.
When you select the report from the menu, the following screen displays.
Sample report
To view a sample report, select the following button:
Introduction
There are two wizards available for recovering or optimizing data files.
Recover Data File utility ‐ allows you to reclaim all salvageable information from a
damaged data file by reloading the existing data into a new empty data file. For example,
you would following a hard disk failure. It is primarily used to fix data files that have
become corrupted and may contain corrupt records. This option can also be used for
adding new indexes to existing data files.
Optimize Data File utility ‐ allows you to optimize your hard disk’s performance by
removing unnecessary records, reducing the size of a file.
The optimize utility allows you to select one file or all files within an application to be
rebuilt.
Once an optimize is complete, a message box displays showing the file(s) that were
converted.
This utility also creates a log file which is used to capture information displayed on a
message box upon completion of the optimization process. If you optimize all files in an
application one log file is created. The log file is created in the company folder and
contains the following information:
• Whether or not the process was successful
• The start and end time of the Pervasive rebuild process
• The number of successful records processed
• The number of corrupted records rejected (not included in the rebuilt data file)
• The number of indexes rebuilt
Note: Do not cancel the Optimize Data File or the Recover Data File once optimi‐
zation (recovery) is in process, or the data file may be corrupted.
54 Sage PFW
Deleting an Existing User
Recoverable files
In the Recover Data File wizard and the Optimize Data File wizard, the application’s data
files are recovered for the current processing company. See Appendix A of each
application’s user manual for a complete description of each data file.
Note: A backup of the data file to be recovered or optimized should be made
before performing file recovery. If the file recovery or optimize fails, a person
with technical proficiency could then attempt further recovery procedures using
the backup of the damaged data file.
Chapter 2: Configuring
the System
How to run the Recovery or Optimize utility
Follow these steps to recover data files:
Step Action
Description
Once a company has been setup, you may need to initialize a data file. The Initialize Data
File option lets you selectively initialize one file at a time. If you are setting up a new
company, you will use the Company Setup wizard to initialize all data files.
Note: A backup of the data file to be initialized should be made before perform‐
ing file initialization.
Step Action
56 Sage PFW
Deleting an Existing User
Description
This wizard provides two services. This wizard can compact the Access data files
associated with the Universal Notes and Attachment feature and/or delete expired notes
and attachments.
Only notes with expiration dates prior to the current date are deleted, plus the file they are
Chapter 2: Configuring
stored in is optimized.
the System
How to run the optimize utility
Follow these steps to optimize and/or delete notes and attachments.
Step Action
Conversion Wizards
Description
There are two wizards not discussed in this chapter because they are covered in the Sage
PFW Installation Instructions and Upgrade Guide. Since these conversion wizards are
essential steps in the upgrade and conversion process they are covered in the Sage PFW
Installation Instructions and Upgrade Guide. They are the Auto Data Conversion and
Security Data Conversion.
58 Sage PFW
Chapter 3:
Setting Up System Manager
Introduction
This chapter provides information on how to set up System Manager menu items.
In this chapter
This chapter contains the following topics:
Topic Page
Business Desktop Overview 60
Setting up System Manager 61
Chapter 3: Setting Up
System Manager
Setting up System Manager Pro 82
Introduction
The Business Desktop allows you to select processing options from a list of folders and
menu items. It also allows you to define a user‐specific My Tasks tab that can be used to
streamline daily functions. My Tasks can include Sage PFW menu items, URL links, and
external shortcuts. Additionally, the Business Desktop provides you access to several
links on the Sage Software webpages.
60 Sage PFW
Setting up System Manager
Introduction
Regardless of the applications you’ve installed, the System Manager folder always
displays and must be setup. The File Maintenance menu items available to you are:
• Cash Account
• Chart of Accounts Lookup
• Country
• Item Master Lookup
• Tax Authority
• Tax Rate
The System Setup menu items are:
Chapter 3: Setting Up
• System Setup
System Manager
• Tax Setup
You only need to setup the menu items that you anticipate using, the others can be
removed from view on the desktop by using the Security Group Setup wizard or creating
a custom My Tasks tab.
In this section
This section contains the following topics:
Topic Page
Completing System Setup 63
Setting Up the Item Master Lookup 72
Setting up Countries 71
Setting Up Cash Accounts 65
Setting Up Tax Information 73
There are also several reports and listings, plus access to the Financial Explorer and
Business Insights and transactional taxing data.
Note: Information regarding Business Insights can be found in the Business
Insights User Guide found on the help menu.
Step Action
62 Sage PFW
How to Complete the System Setup Window
Description
The System Setup is used by all applications and only needs to be setup one time.
In this section
This section contains the following topics:
Topic Page
How to Complete the System Setup Window 63
Chapter 3: Setting Up
When you select System Setup from the business desktop, the following window appears:
System Manager
Default User ID for Posting
This option allows you to determine if a default user id displays when reporting and
posting in the sub‐modules or if the user id should be blank. If you choose to use this
option, each time this field is available, the current user’s id displays. You can always
change or remove the default user id.
The User ID is a tool used to restrict information being reported or posted.
Procedure
To complete the System Setup window, do the following:
Step Action
1 Select System Setup from the SM folder on the business
desktop. The System Setup window appears.
2 Complete the information on the System Setup win-
dow.
3 Select Save.
Need more information? Press F1.
64 Sage PFW
How to Complete the System Setup Window
Introduction
Completion of this menu item is required and one cash account must be set up prior to
entering vendor classes. The Cash Account file is used by both the Accounts Payable and
the Bank Book applications.
Since the cash accounts are used by more than one application, the setup is done in the
System Manager folder found on the Business Desktop.
The Cash Account menu item allows you to define all the cash accounts that you want
Accounts Payable and Bank Book to process and that are defined in the General Ledger.
You must define at least one cash account.
You must set up your cash account in order for you to:
• Create vendor classes
• Print Accounts Payable checks
Chapter 3: Setting Up
• Enter handwritten checks in Account Payable
System Manager
• Enter transactions in Bank Book
• Perform a Bank Book reconciliation
• Review the current cash position
• Process cash receipts and writeoff balances
• Void posted receipts.
In this section
This section contains the following topics:
Topic Page
How to Complete the Cash Account Window 66
Description of Cash Account Options 66
Check Information Tab 68
Bank Information Tab 69
Procedure
To complete the Cash Account window, do the following:
Step Action
3 Select Save.
4 Repeat Steps 1-3 for each cash account key you need.
Need more information? Press F1.
Account Type
You must select one of the available account types.
66 Sage PFW
Description of Cash Account Options
Note: If you are using Multi‐Currency Manager, all amounts are entered in the
currency in which the cash account is held.
WARNING: When Bank Book begins updating the last reconciliation and last dis‐
tribution dates and amounts, they are maintained by the system. Do not attempt
Chapter 3: Setting Up
to alter this information.
System Manager
Cash held in home currency
If Multi‐Currency Manager is installed, you can indicate if the cash account is held in your
home currency by placing a check mark in the Cash Held in Home Currency checkbox. If
the cash account is held in a natural currency, do not select this option.
Currency key
If you have installed Multi‐Currency Manager and the cash account is held in natural
currency, you can identify the key for the currency in which this cash account is held.
Bank Book uses this currency key to reference the applicable exchange rate when:
• Converting transaction amounts of another currency to the same currency as the cash
account, for reconciliation to the bank statement
• Calculating and posting to the General Ledger any buy/sell rate conversion discrep‐
ancies between natural account transactions and the home equivalent.
• Calculating and posting to the GL any gain/loss amounts based on the amount last
reconciled.
Note: Currency keys are defined in the Multi‐Currency Manager application.
The cash account is debited or credited in the General Ledger with the amount of the
difference, and the offset account defined in this field is posted with the offset transaction.
As an example of a buy/sell rate difference situation, suppose that 30,000 units of a natural
currency converted to $200 U.S. dollars (home currency) at the buy rate, and the same
30,000 units converted to $193 at the sell rate. The difference is a $7 amount ($200 minus
$193).
The following diagram illustrates the $7 amount posted to the cash account to compensate
for the difference between the buy and sell rate. The $7 offset transaction for the difference
adjustment is posted to the offset account defined in Cash Account.
68 Sage PFW
Bank Information Tab
All the information on this tab prints on the Cash Account Listing.
Chapter 3: Setting Up
System Manager
Introduction
If you are not interfaced to General Ledger, the Chart of Accounts Lookup menu item
allows you to create basic records containing an account number and account description.
These records can then be accessed and selected from the lookups for Account Number
fields in Sage PFW applications.
LOCHART file
In General Ledger, chart of account records are maintained in the NLCHART file. The
Chart of Accounts Lookup records are held in a file named LOCHART.
The system accesses LOCHART when the interface to General Ledger is not activated.
Therefore, regardless of whether you installed General Ledger, disabling the interface in a
specific application instructs the system to access—for that application only—the lookup
chart records maintained through the Chart of Accounts Lookup menu item.
Procedure
To complete the Chart of Accounts Lookup window, do the following:
Step Action
3 Select Save.
70 Sage PFW
Bank Information Tab
Setting up Countries
Introduction
The Country file allows you to setup and change abbreviations for all countries around
the world. The country key and descriptions you setup here are used by all other Sage
PFW applications.
Country file
When Sage PFW is installed, a basic country file is installed. This file has most countries
already entered. You can always make changes to existing countries, remove countries,
and add new ones.
Chapter 3: Setting Up
When Country file maintenance is selected from the Business Desktop, the following
System Manager
window appears.
Procedure
To complete the Country window, do the following:
Step Action
3 Select Save.
Introduction
If you are not interfaced to Inventory, the Item Master Lookup menu item allows you to
create basic records containing item information. These records can then be accessed and
selected from the lookups for Item Key fields in Sage PFW applications.
LOINMAST file
In Inventory, item master records are maintained in the INMAST file. The Item Master
Lookup records are held in a file named LOINMAST.
The system accesses LOINMAST when the interface to Inventory is not activated.
Therefore, regardless of whether you installed Inventory, disabling the interface in a
specific application instructs the system to access—for that application only—the item
records maintained through the Item Master Lookup menu item.
Procedure
To complete the Item Master Lookup window, do the following:
Step Action
3 Select Save.
72 Sage PFW
Determining How You Want to Calculate Taxes
Introduction
In Accounts Payable and Purchase Order, you have two options for entering taxes:
• You can manually enter taxes as line items.
• You can have the system automatically calculate taxes on a line by line basis when
you enter a tax rate key for each inventory and non‐inventory line item.
Note: If you do not install Accounts Payable, the tax‐related menu items in Sys‐
tem Manager are not displayed.
In this section
This section contains the following topics:
Chapter 3: Setting Up
System Manager
Topic Page
Determining How You Want to Calculate Taxes 73
Switching to Automatic Tax Calculation 74
Completing the Tax Setup Window 75
Defining Tax Levels 76
Document Processing Options 76
Determining the Tax Rate Key Default Method 77
Completing the Tax Authority Window 78
Completing the Tax Rate Window 79
Defining Tax Rate Keys 79
Taxes Included in Item Price 80
Including Settlement Discounts 80
Tracking Nontaxable Items 81
• Taxes are entered as tax line items. You can either enter the total tax on one line using
one tax rate key, or you can enter a tax line item for each item on an individual basis.
• Taxes can be calculated by the system using a tax rate key you enter if you select the
option to calculate the sales tax based on document total.
• Taxes are calculated when the voucher, debit memo, additional cost voucher, pur‐
chase order, or purchase order receipt is entered.
• Taxes are calculated on a line by line basis for inventory and non‐inventory line items
based on options set up for each vendor in Accounts Payable, item location in Inven‐
tory, and in System Manager.
• There is no tax line item.
• You can select to include tax in the price of items.
Step Action
For every unposted purchase order:
1 Open the unposted purchase order.
74 Sage PFW
Completing the Tax Setup Window
In this window, do the following:
• Define up to four tax levels
• Enter transaction information on an application by application basis
When Tax Setup is selected from the Business Desktop, the Tax Setup window appears.
Chapter 3: Setting Up
System Manager
Tabs
The following table is a description of the two tabs on the Tax Setup window:
Procedure
To complete the Tax Setup window, do the following:
Step Action
3 Select Save.
Need more information? Press F1.
For example, if you purchase goods in all fifty states of the United States, you might
define your first level as “State.” You will define a separate table for each state’s tax rate in
the Tax Rate window. During voucher entry, you can specify the appropriate state’s tax
table to be used for goods purchased in that state. Tax rates are calculated on a line by line
basis; thus, you can enter a different tax rate for each line item.
As another example, if your business were in a particular province in Canada which
charged a provincial tax in addition to the national GST, you might define your first level
as National and the second level as Provincial. Then, you can enter the Tax Authority Key
of GST as the first level authority, and QBPR (for Quebec province) to the second.
AP Taxes tab
If you choose the option to use the automatic tax calculation feature taxes are
automatically calculated on a line by line basis for inventory and non‐inventory line items
based on options set up for each vendor in Accounts Payable, item location in Inventory,
and in System Manager. Taxes are shown on a Tax sheet on the Line Items tab in
document entry. Tax line types are not available in document entry.
If you choose not to use the automatic tax calculation feature, taxes are entered manually
as tax line items and the Tax sheet is not available for entry.
If you want to include taxes in the unit price of items, such as in the case of value‐added
taxes (VATs) or Goods and Services taxes (GSTs) you would want to use this feature.
If you plan to use the Tax Included in Price option when you set up tax rate keys, the
system calculated amount defaults automatically regardless of whether you select this tax
default option.
76 Sage PFW
Determining the Tax Rate Key Default Method
Chapter 3: Setting Up
tax rate key should be obtained from the vendor record or the location record for the
System Manager
inventory item, if Accounts Payable is interfaced to Inventory. If Accounts Payable is not
interfaced to Inventory, the default is Do Not Default.
Note: If you are using Inventory, and your company uses value added taxes that
are included in the unit price of inventory items, you can define a tax rate (that
should default from vendor) that enables the system to separate the tax amount
from the tax‐included item price.
If your tax rate keys will be set up to include the tax in the price of the items, do not
choose the Do Not Default option.
Make sure the same tax authority keys are defined in both Accounts Receivable and
System Manager.
If you have not installed Accounts Receivable, the lookup contains tax authority keys
defined in the Tax Authority menu item in System Manager.
78 Sage PFW
Completing the Tax Rate Window
Chapter 3: Setting Up
System Manager
Procedure
To complete the Tax Rate window, do the following:
Step Action
1 Select Tax Rate from the System Manager folder in the Busi-
ness Desktop. The Tax Rate window appears.
2 Complete the Tax Rate tab and the tax level tab for each
level you defined in the Tax Setup menu item.
3 Select Save.
4 Repeat Steps 1-3 for each tax rate key you need.
Need more information? Press F1.
Procedure
To include taxes in the unit price, do the following:
Step Action
When vouchers are posted, the system subtracts the amount of the tax from the unit cost,
and posts the tax amount to the GL account specified for the appropriate level as defined
in the Tax Rate menu item.
Settlement discounts (predetermined percentage discounts) are assumed taken during
voucher, additional cost voucher, debit memo, purchase order entry, and purchase order
receipt entry. Any tax to be calculated is based on the extended line amount. Settlement
discounts are applied to the document total or a specific line item depending on whether
you are using automatic tax calculation.
This option is used mainly in the United Kingdom for value‐added taxes (VATS).
Procedure
To set up settlement discounts do the following:
Step Action
1 When you define a tax rate key in the Tax Rate window,
select Include Settlement Discount.
2 When you define a terms key in the Terms window in
Accounts Payable, specify the discount percentage in the
Percentage field.
Need more information? Press F1.
80 Sage PFW
Tracking Nontaxable Items
When entering a voucher, additional cost voucher, debit memo or purchase order for a
vendor set up to allow settlement discounts, the system defaults the appropriate tax rate
and terms, and then automatically reduces the entered line item extension by the discount
percentage before applying the tax rate.
Note: During line item entry, if you enter a tax rate key that includes the settle‐
ment discount, the default discount comes from the discount entered for the
terms key associated with the vendor. If you enter a discount in document entry
the system still uses the discount from the terms key.
Chapter 3: Setting Up
System Manager
Introduction
This section discusses processes relating to setting up System Manager Pro. The options
discussed in this section are accessed using the System Manager Pro folder found on the
Business Desktop. It is only available if you have installed any of the process
manufacturing applications.
In this section
This section contains the following topics:
Topic Page
Defining Company Defaults 83
Adding Company Name and Address 87
Adjusting Maximum Parameters 88
Adjusting Numeric Constants 90
82 Sage PFW
Completing the Company Defaults Window
Introduction
The Company Defaults menu item allows you to select parameters that define the current
processing companyʹs measurement systems and other variable characteristics. The
information you enter in Company Defaults allows calculations to be performed and
display data in ways consistent with how your company does business.
Chapter 3: Setting Up
Defaults window with the first page displayed as shown below. General field descriptions
System Manager
follow. For detailed information about completing the fields, refer to online help (F1).
Decimal Places
In the following fields you specify the number of decimal places to be included in certain
values that are used for computations and reports through out the process manufacturing
applications.
It is well to remember that, while up to nine decimal places are supported, report columns
only permit fifteen numeric characters, including commas and decimal points.
Note: You can specify decimal places for each installed application in the individ‐
ual Application Setup menu items found in each application. These decimal spec‐
ification would override the defaults set up here.
Lot Tracking
Completing these fields establishes default parameters for lot tracking. If you do not use
lot tracking, you can ignore these fields.
84 Sage PFW
Completing the Company Defaults Window
Chapter 3: Setting Up
Field Descriptions
System Manager
This window contains the following fields to be completed:
Numbering Options:
System English – U.S. gallons, pounds/ounces
Imperial – British gallons, pounds/ounces
Metric – liters, kilograms/grams
Note: You can set up any of these systems as Alternate Units of Mea-
sure in the Inventory -Pro application.
Text Definition
Fr Francs
DM Deutsche marks
Text Definition
$ U.S. dollar, Mexican dol-
lar, Canadian dollar
ASCII Definition
<Alt> +
0163 £ Pound
0165 ¥ Yen
0128 Euro
86 Sage PFW
Completing the Company Name and Address Window
Introduction
The Company Name and Address menu item allows you to define the processing
company information. This information is primarily informational, but may print on
reports or listings.
• Company name
• Address information
• Information telephone number
Chapter 3: Setting Up
System Manager
• Emergency telephone number.
When you select this menu item from the folder, the following screen appears.
Introduction
If you find that the default settings for any of the line item screens do not fit your
companyʹs needs, you can modify them to accommodate your requirements using the
Maximum Parameters windows.
WARNING: Theoretically, up to 99 formula line items can be maintained, as well
as up to 99 Q/C tests and bill‐of‐material items. However, increasing these values
to their maximum will degrade workstation performance, consume additional
resources, and require additional memory. You might want to adjust these values
to just a little over what you actually require.
Parameters
You can adjust the following values on the Maximum Parameters window:
88 Sage PFW
Completing the Company Name and Address Window
Chapter 3: Setting Up
System Manager
Introduction
The Numeric Constant menu item allows you to adjust many of the default values, which
are used to perform calculations when you size a formula.
WARNING: It is not recommended that you alter any of the values in the Numeric
Constants window. Altering these values will affect how formulas are sized in the
Formulas, Production, Laboratory, and Costing applications. Alter these values
AT YOUR OWN RISK.
90 Sage PFW
Chapter 4:
Operating the PAS
Introduction
This chapter provides the instructions for starting and operating the Process Application
Server (PAS).
In this chapter
This chapter contains the following topics:
Topic Page
Starting a PAS 92
Stopping the PAS 95
Chapter 4: Operating
the PAS
Starting a PAS
Background
Jobs submitted to a queue can be processed only if the associated PAS has been started
and is operating. Additionally, you must ensure that non‐Sage PFW related system or
network messages are not received by the PAS, since these messages may suspend the
operation of the PAS.
In this section
This section contains the following topics:
Topic Page
PAS Setup Information 92
How to Start the PAS 92
How to Reactivate a Stopped PAS 93
• The drive letter on the network file server specifying where the queue is located
• The queue ID
• The time interval by which the PAS should poll the queue for jobs to process.
Note: It is not recommended to run a PAS on a client workstation.
For complete instructions on setting up a PAS, refer to “Information Required to Set Up a
PAS User” on page 50.
Requirements
Once the PAS setup is complete on a workstation, an icon should be added to the
Windows desktop.
Choose the icon and login to start the PAS. Once the PAS has been properly started, it can
process jobs submitted to a queue.
92 Sage PFW
How to Reactivate a Stopped PAS
Procedure
Follow these steps to start a PAS:
Step Action
1 Choose the PAS icon from the Windows desktop.
2 In the PAS Name field, enter name of the PAS you want to start.
3 In the Password field, enter the password for the PAS Name you
entered.
Click OK to start the PAS.
Once started, a task is added to the Windows task bar, Process
Application Server.
4 Repeat steps 1-3 to start additional PASs on a workstation or
server.
Chapter 4: Operating
the PAS
How to Reactivate a Stopped PAS
When a PAS is shut down, for example due to a network time‐out, power loss, or other
unexpected event, you must reinitialize the active PAS file.
Background
When a PAS is started, the UTQACTIV.SRQ file in the \PLATINUM\QUEUE directory is
updated to show the PAS is active under the login ID. If the PAS shuts down
unexpectedly, that file is not updated to show a logout condition and the system assumes
the PAS login ID is still active.
Procedure
Do the following to reactivate the PAS:
Step Action
1 Make sure all users are logged off of the server, PAS, and
individual workstations.
2 Login to Sage PFW as the Administrator.
3 Select the Queue Repair wizard.
4 Select Repair Active PAS file
5 Click Next and Finish.
94 Sage PFW
Network Access from a Stopped PAS
Background
If the PAS is not needed for processing for a period of time, such as on the weekends, the
PAS can be stopped and the system used for other purposes. When you attempt to stop a
PAS, the system checks if a job is in process and stops the PAS only when the job is ended
(by the job being completed or canceled). A message displays informing you of this
situation.
In this section
This section contains the following topics:
Topic Page
Network Access from a Stopped PAS 95
How to Stop the PAS 95
Chapter 4: Operating
Network Access from a Stopped PAS
the PAS
Access caution
A stopped PAS should not be left unattended unless you secure the network or system
access. Another user should not be able to use the network while the system is still logged
in as the PAS.
Procedure
To stop a PAS, choose the Exit button.
96 Sage PFW
Chapter 5:
Managing Queues
Introduction
This chapter provides instructions for managing queues.
In this chapter
This chapter contains the following topics:
Topic Page
Setting Job Processing Options 98
Managing Jobs in Queue Manager 101
Chapter 5: Managing
Queues
Introduction
Any time a user attempts to process a job remotely (report, listing, print and post, or
utility), the user must send the job to the appropriate queue.
Default queue
For ease in routing the job, the system provides a default queue on the Routing window. If
a job should regularly be submitted to a different queue, a user can select a different
default queue for each pre‐saved parameter, or the queue can be changed every time the
job is submitted. Regardless, the System Administrator manages the default queue for
each menu item.
Scheduling a job
Any remote job can be scheduled to run on a particular day, at a specific time. If date and
time are not selected, the job is submitted to the queue and processed by the PAS based on
the priority and time submitted.
Directing results
The user must also determine where the results will be sent. When running remotely or
locally, the results can printed or you can email the output in .PDF format. Once the
printer option is selected, the user can choose the desired printer and the number of
copies to be printed.
98 Sage PFW
System Administrator Options
If the job is submitted remotely and you choose to send the results to the queue manager,
the output displays in the Inbox. From the queue manager, the user can print or email the
output in .PDF format.
Job priority
At the time the job is submitted to the queue, the job is assigned a priority, which
determines the order of importance (along with the date and time of submission) that the
PAS will use to determine which job—of the potentially many jobs in the queue—should
be processed next. Although the system can handle a priority range from 0 (highest
priority) to 32767 (lowest priority), in a business setting, a priority range is more
traditionally and manageably defined as 1 though 10.
In this section
This section contains the following topics:
Topic Page
System Administrator Options 99
User Options 100
The setting of the default queue and priority is performed from the Business Desktop, for
each applicable menu item. To do so, you must be logged in as the System Administrator.
Procedure
Chapter 5: Managing
To set the default queue and job priority, follow these steps.
Queues
Step Action
2 From the Business Desktop, open the menu item for which
you want to set the default queue and priority. This opens
the properties dialog box for the menu item, enabling you
to set the job options.
Step Action
6 Repeat Steps 1-5 for each menu item for which you want to
set the default queue and priority.
Need more information? Press F1.
User Options
Default queue
When running remotely, the individual user also has the option of setting the default
queue when defining the routing for a job on the Routing tab. This process does override
any default queue set by the System Administrator as discussed in the instructions
provided. However, only the System Administrator can set the job priority.
Scheduling
When running a job remotely, each user can also set a date and time when the report will
begin processing. These determine when the job will be available for processing by the
PAS. If the Set Schedule option is not selected, jobs are processed sequentially based on
their priority and submission dates and times.
Introduction
The queue manager is available to all users to enable them to track the status of their own
and other user jobs. If necessary, an individual user can delete or cancel his or her own
job. The user cannot delete or cancel another user’s job.
Reference
For details on using the queue manager, refer to the System Basics User Guide.
Deleting a Job
Deletion by user
If necessary, an individual user can delete or cancel his or her own job. The user cannot
delete or cancel another user’s job.
The deletion of a user job should be done by the System Administrator only in rare and
unusual circumstances. Typically, you may need to delete a job that was initialized in
error.
Procedure
If it becomes necessary for the System Administrator to delete another user’s job, follow
these steps.
Chapter 5: Managing
Step Action
Queues
From the Business Desktop, you can either select
the Load Queue Manager button or choose
View, then choose Queue Manager.
2 On the Outbox tab, select the queue from
which you want to delete a job.
3 On the Job List tab, select the job you want to
delete and choose Delete.
Need more information? Press F1.
• A PAS is shut down while a job is being processed, for example due to a network
time‐out, power loss, or other unexpected event
• A client workstation shuts down while processing a locally submitted job
• An error occurs on a client workstation while processing a locally submitted job.
Note: Queue Repair allows multiple users or queues to be repaired with SHIFT or
CTRL key selection.
Background
When a PAS is started, the UTQACTIV.SRQ file in the \PLATINUM\QUEUE directory is
updated to show the PAS is active under the login ID. If the PAS shuts down
unexpectedly, that file is not updated to show a logout condition and the system assumes
the PAS login ID is still active.
Procedure
Do the following to reactivate the PAS:
Step Action
1 Make sure all users are logged off of the server,
PAS, and individual workstations.
2 Login to Sage PFW as the Administrator.
The solution is to close Sage PFW and reopen. From this point forward, the Queue is
refreshed properly.
Note: This only occurs the first time Sage PFW is opened. For example, install
Sage PFW, login as Admin, setup companies, users, groups etc. When you login
as a different user and begin processing reports the Queue Manager is not
refreshed. By closing Sage PFW and logging in as a user, report processing
refreshes the queue.
Introduction
This chapter provides instructions on performing designer tasks for certain areas of the
system.
• Designing Templates
• Managing Templates
• Using Templates
An overview of templates and an example of a sample template begins the chapter, and
the detailed instructions for designing, managing and using templates follows the
example.
In this chapter
This chapter contains the following sections:
Topic Page
Designing Templates 104
Managing Templates 118
Using Templates 120
Chapter 6: Templates
Designing Templates
Introduction
The Template Properties and Template Manager features allow you to define multiple
views of many of the Sage PFW windows, as well as to define object properties and
behaviors. The templates are then available as selectable items from the File—Select
Template option of the corresponding window.
Templates can be created in entry menu items, like Invoice Entry, and file maintenance
menu items, like Customer file maintenance. By designing templates, you can;
• Enhance user security by adding field level security
• Control work flow by restricting entry to fields specific to your business
• Ease the data entry process by limiting the number of tabs and fields that a user must
visit
• Create screens that are specific to your business.
• Change the text caption of tabs and fields.
• Define certain field behaviors, such as making a field invisible (it will not appear),
restricting the field to numeric values, preventing or requiring user entry, setting min‐
imum and maximum ranges, creating a custom Help message, or specifying on which
Line Item sheet the field should appear.
• Change the Lookup window display of textbox fields.
• Define which fields are loaded when using the Find Historical feature
• Assign a template globally to all users, to certain companies, or to specific security
groups.
• Establish default values, in select entry screens.
In this section
This section contains the following topics:
Topic Page
Creating a Template 107
How to Define Template Properties 109
Adding, Modifying, and Deleting Lookups 111
Customizing Help Text 115
Viewing Work in Progress 116
Resetting the Shipping Configuration 116
How to Save a Template 116
Sample 1
Many of the fields have been defined as invisible, and the remaining fields (most with
caption changes) move up the entry grid.
Fields defined as invisible are filled in with defaults, and posted to the database in the
usual manner.
Chapter 6: Templates
Sample 2
The tab name has been changed to reflect the visible fields. Accrual and recur fields are
invisible, and captions have been edited.
If the tab names are designed with long descriptions, the user may have to scroll or use
the Alt+[tab number] to access the tabs that do not fit on the window.
Sample 3
The Conversion, Tax, and Account columns have been removed, and the Amount field
has been defined visible, but the user cannot enter information into the field. This would
assume the prices of the supplies is maintained in Inventory, and the entry user should
not have access to change the amount.
Sample 4
Tab captions can be changed to reflect the definition and use of the fields they contain.
Sample 5
You can easily establish default values. For example, in this company, every time a
vendor is added to the vendor file the check comment should be 02. By adding a default
value of 02 in the template, every new record now defaults with an 02 Check Comment
key.
Creating a Template
To design and assign templates, the System Administrator must use User Setup to set the
user up as a user with Designer privileges. When you log on and select one of the menu
items that is currently shipped with template options, the Template Properties option
becomes available from within the menu item that you want to customize, on the Window
menu. When you select Template Properties, the customization screen appears.
Procedure
The basic steps to creating a template (explained in detail in following sections) are:
Step Action
2 Display the menu item for which you want to create a tem-
plate.
3 Open the Template Properties window by selecting Template
Properties from the Window menu.
Step Action
The properties area displays the properties of the field highlighted in the scrollable area.
Scrollable area
Properties area
Customization options
The following chart lists the available customization options on the Template Properties
screen:
Step Action
• Field lookups (foreign key fields)
These are fields that already have a lookup, require field validation to a predefined
table, and can display a description associated with the field.
• Textbox fields
These are entry fields that have no field validation, may or may not be masked, and
may or may not already have a lookup.
• Date fields
There are two types of date fields, those that use a calendar lookup and those that use
a user defined date file (INPDATES or NLPDATES).
Check boxes, table lookups, and include lists do not allow the addition, modification, or
deletion of lookups.
Refer to the System Basics User Guide for definitions of the types of lookups.
• Do not delete the lookup definition
• The new lookup definition must use the same primary table as the original lookup
definition
• The new lookup definition should use the same primary table order by keypath as the
original lookup definition
• The first column in the new lookup definition should be the same as the first column
in the original lookup definition
Chapter 6: Templates
When you click the Lookup Definition button in the Lookup Definition field, the
following window appears:
Step Action
Step Action
Multiple languages
If you use multiple languages, you must make the lookup customizations separately in
each language.
Find Historical
The Find Historical feature is available in many document entry screens allowing you to
create a new document based on data from an historical document. The feature is only
available in document entry screens like Voucher Entry or Invoice Entry.
The following menu items support the Find Historical feature and templates:
• Accounts Payable ‐ Voucher Entry
• Accounts Payable ‐ Additional Cost Voucher Entry
• Accounts Payable ‐ Debit Memo Entry
• Accounts Receivable ‐ Invoice Entry
• Accounts Receivable ‐ Credit Memo Entry
• General Ledger ‐ Journal Batch Entry
• Sales Order ‐ Sales Order Entry
• Order Entry Pro ‐ Sales Order Entry
• Order Entry Pro ‐ Return Entry
• Purchase Order ‐ Purchase Order Entry
• Purchasing Pro ‐ Purchase Order Entry
• Purchasing Pro ‐ Return Entry
Chapter 6: Templates
Usage
Two fields that control Find Historical population exist on the General template tab; Find
Historical Populate and From. The Populate checkbox allows you to select or unselect the
population of the selected field during a Find Historical operation. If the Populate
checkbox is unchecked, the field is not be populated from the historical document, and the
From drop down box is be disabled. If the Populate checkbox is checked, the field is
populated from the field name defined in the From drop down box during a Find
Historical operation.
The From drop down box contains a list of field names from the Platinum Data Dictionary
(PDD). If the currently selected field resides on any Header tab, the From name displays
from the historical header table. If the currently selected field resides on a Line Items tab,
the From name displays from the historical line item table.
Find Historical Template Properties are not available on certain fields due to system
requirements. For a complete list of fields, refer to “Appendix B: Find Historical Template
Properties” on page 157.
Step Action
2 Choose the Help tab, and type your custom help text in the
area provided.
Chapter 6: Templates
Hint: During a first design session, you can save a template of the original shipping
configuration. This allows you to recall it (by loading) at any time, or assign it as you
would any other template.
Procedure
To save a template, do the following:
Step Action
Chapter 6: Templates
Managing Templates
Introduction
Once templates have been saved, the Template Manager is used to change assignments,
move, load, unload or review your templates.
In this section
This section contains the following topics:
Topic Page
Assigning Templates 118
Removing, Loading, and Unloading Templates 119
Assigning Templates
The Template Manager window allows you to assign a template as available to one or
more security groups, to one or more processing companies, or globally (available to all
Sage PFW client users).
Step Action
You can add multiple templates to a security group, or remove a template by highlighting
it and clicking Remove.
Assigning to a company
To assign a template to a Company:
Step Action
You can add multiple templates to a company, or remove a template by highlighting it
and clicking Remove.
Assigning globally
To assign a template globally:
Step Action
1 From the Global tab, type the name of the template in the
Template Name field.
2 Click Save.
Need more information? Press F1.
You can add multiple templates, or remove a template by highlighting it and clicking
Remove.
Remove button
You can remove a saved template by highlighting the template and clicking the Remove
button.
Load button
You can review saved templates by highlighting a template (from any tab) and clicking
the Load button. This will load the highlighted template into the open menu item for
viewing.
Unload button
Clicking Unload returns the menu item to the original shipping configuration. It is
recommended that you use this feature before beginning to customize a new template.
You can, however, load any of your saved templates to serve as a base for designing a
new one.
Chapter 6: Templates
Using Templates
Introduction
Users can select an assigned template from the Security Group, Company, or Global tab
list, select that template as the default view for a window, and perform regular entry as
documented in the application user guide.
Procedure
To set a default template, select an available template by highlighting it and clicking Set as
Default. The next time you access that menu item, the specified template is displayed.
Introduction
This chapter describes the changes made to accommodate Goods and Services Taxing
(GST) requirements in Australia. Also discussed are the steps necessary to facilitate tax
calculation and reporting. The flexible design allows Sage PFW to address similar
processing requirements in other tax jurisdictions and is not specific to Australian
requirements.
Topic Page
Features 122
Setting Up the Discount Taken Tax Adjustment Feature 125
Setting Up the General Ledger 126
Setting Up Accounts Receivable 127
Setting Up Accounts Payable 133
Daily Processing for Australia 139
Features
Introduction
The Discount Taken Tax Adjustment (DTTA) feature provides GST tax calculation and the
adjustment of the tax amount paid or collected when a payment discount is taken. For
example, in Accounts Receivable if an invoice is entered with a GST tax key assigned to
any line item(s), when payment is received from the customer, an early pay discount may
be taken. If the discount is taken, the tax is recalculated throughout the system.
Why might an adjustment be calculated?
• All or part of a sale or purchase is canceled.
• The price for a sale or purchase is altered (such as where a volume discount or early
payment discount is exercised).
• A sale becomes taxable or a purchase becomes creditable.
• A sale stops being taxable or a purchase stops being creditable.
• The purpose of the purchase changes.
• A bad debt occurs or failure to pay a debt arises.
The tax calculation adjustment may be on any tax level and each levelʹs adjustment will
operate independent of other tax levels. In this document, one tax level is used for
example purposes. However, the tax feature is designed to handle up to four tax levels,
with varying configurations.
In order to facilitate tax adjustments, the DTTA feature must be implemented and
processed as described in the following chapters.
Note: The changes will not effect tax calculations in North America or the Settle‐
ment Discount feature for users in the United Kingdom.
Additionally, a mixture of DTTA tax rates and upper limit tax keys, on one invoice, is not
supported. To calculate DTTA and upper limit taxes, a separate invoice must be entered
Accounts Receivable
Cash receipts must be entered in Cash Receipts Entry, not Invoice Entry or Sales Order
Entry.
Refer to“Cash Receipt Processing” on page 140 for detailed description.
Accounts Payable
Checks should be entered in Handwritten Check Entry or user selected in Voucher
Payment Entry. Do not enter handwritten checks in Voucher Entry or Purchase Order
Entry.
Additionally, if checks are qualified by the system for payment through the Print and Post
Voucher Payment option (without being selected manually), the total amount of discount
taken and tax adjustment may be understated.
See “Voucher Payment Processing” on page 140 for detailed description.
Note: If an invoice exceeds $1000 and the Tax Included in Price option for a tax
rate is not selected, the Tax on Total feature will work correctly. Any invoice less
than $1000 must include tax in the price of the line item.
When entering a document and the Tax on Total option is selected, the first tax key
overwrites every other tax key to match the first tax key. So, if multiple lines have
different tax keys, pressing Tax on Total resets all line item tax keys to be the same as the
first tax key.
According to the Australian Tax Office (ATO), for those businesses without an ABN,
48.5% of payments made to that business may be withheld. This amounts to the top tax
rate plus the Medicare levy. To avoid this your ABN must be quoted on all transaction
records. It is also needed on tax invoices so you can claim and collect the GST.
On-Account Entries
The DTTA feature does not work with on‐account entries. An early discount amount can
not be found when entering an on‐account entry.
Reporting
Three reports are available to handle ATO requirements: Business Activity Statement,
Adjustment Notes Due Report, and the Adjustment Note Report.
Australian Setup
GL account numbers are required so the tax collected or paid can be accumulated. A
second GL account for adjustments is required for each tax authority. For each tax
accumulation account defined, a second account is required to record the adjustment
amount.
The Australian Tax Office suggests the following names for the accounts:
• GST Payable Control Account ‐ this accumulates the taxes calculated on sales (liability
account).
• GST Payable Adjustment Control Account ‐ this accumulates the taxes reversed from
credit memos and adjustments when payment discounts are taken (liability account).
• Input Tax Credit Control Account ‐ this accumulates the taxes calculated on pur‐
chases (Asset account).
• Input Tax Credit Adjustment Control Account ‐ this accumulates the taxes reversed
on debit memos or prompt payment discounts taken (Asset account).
Additional GL accounts may be required depending on the accounting practices of your
firm.
Setup
The Application Setup window is where you enter:
• Company information
• Transaction information
• Tax levels
• Form options
To turn on the DTTA feature, choose the Application Setup, Tax Level tab. Establish the
levels of taxes required by entering a tax level name into the desired levels. If a tax level
name is left blank, that level will not be available when setting up tax rates.
Australian Setup
Define Tax Level 1 as GST. This text will print on invoices and is required by the
Australian Tax Office (ATO). Additional tax levels can optionally be activated.
Select the Adjust Tax When Discount Taken option to active this feature.
Setup
In Accounts Receivable file maintenance, define a tax authority for each tax jurisdiction to
which your firm will remit taxes. The Tax Authority window allows you to define the
necessary authorities.
To report taxes paid and taxes received correctly, this authority file must be identical to
Accounts Payable.
Since both applications can retain records of the same tax authority keys, you can include
taxes paid out for each authority in Accounts Payable along with those received through
Accounts Receivable.
Australian Setup
Create authority keys for each tax jurisdiction, and one for the Australian Tax Office
(ATO).
Setup
The Tax Rate window contains a record for each tax rate by which taxes will be calculated.
Taxes are calculated based upon the tax rate key entered during invoice entry.
Tax tables allow you to specify which tax authority key should be used, and define:
• Simple straight percentage tax rates
• Tax structures in which tax structures are based on tax brackets
• Tax adjustment keys.
Important! It is the Tax Authority Key that triggers the system to calculate the
tax.
Australian Setup
Several tax keys must be defined to meet the requirements of the Australian Tax Office
(ATO).
The following table lists the initial description for the tax types used in AR as specified by
the ATO. These keys relate to the form numbers of the Business Activity Statement (BAS).
Important! It is the first 3 characters of the Tax Description that sorts the data on
the BAS.
• Create one G07 tax key with the Tax Included in Price box checked. This tax key can
be used for Credit Memos which are not barred from the Tax‐inclusive option. This
adjustment tax rate must not be tied to a G01 tax rate key.
• Create anther G07 tax key with the Tax Included in Price box un‐checked. This tax key
is used when calculating an adjustment. Do not check the Tax Included in Price box
when setting up the Tax Adjustment key even if the original tax record is Tax
Included in Price.
Note: Do not enter an adjustment key on the adjustment records.
When setting up the G01 tax key, make sure to enter the adjusting tax key of the
appropriate GST Payable Adjustment Control Account (G07‐ the Tax Included in Price
option un‐checked). This is the link between these two tax rates and, if filled in with a
valid G07 tax rate, will properly trigger the posting routines.
Note: The Tax Included in Price field must be checked for all tax rates. However,
an additional tax rate can be created for invoices that exceed $1000 where the Tax
Included in Price field is left unchecked. For invoices that exceed $1000, the GST
may be broken out or included in the price.
Enter one or more tax keys to record any special tax requirements or GST Free items that
may be sold or purchased.
Setup
Use the Comment file maintenance to define comments that can be printed on invoices
and statements until forms are pre‐printed with this information.
Comment keys can be linked to default for a particular customer during invoice entry—or
be printed on statements—by entering a valid key in the Comment Key for Invoice and
Comment Key for Statement fields in the Customer window or in the Comment Key field
in the Ship To window.
Australian Setup
Tax Invoice: ABN followed by your (the company issuing the invoice) ABN number on the
comment line 1
And
T indicates Taxable Supply on comment line 2.
This comment key will be attached to all customer records. This facilitates the printing of
required information on invoices.
Note: The next time you order pre‐printed forms, this information could be
printed in any location on the form you wish. If you choose to do this, be sure to
clear out the original comment key.
Setup
The Customer window allows you to set up a record of information about each customer
for whom you will be processing transactions.
Australian Setup
The following changes must be made to each customer record.
1. Each customer record must have the same Comment Key for Invoice. This is the com‐
ment key that you created in Step 4. This allows the system to print the seller’s ABN
number on the invoice and the text Tax Invoice
2. A default GST tax key should be assigned for each customer. This default will be used
when entering an invoice, sales order, or credit memo.
Or
If you’ve elected to default the tax key from inventory, enter the correct tax key for
each inventory item.
Note: The ATO guidelines specify either the customer address or customer ABN
must print on each Tax Invoice. If you wish to print the customer ABN, go to tab 3
‐ Process Information. Add the Customerʹs ABN to the Customer Tax ID field.
Make sure to check the Print Customer Country and Tax ID on Invoice checkbox.
If you elect to print the Customer Tax ID on the invoice, you must preface the number
with ABN to identify the number per ATO requirements. When the number prints on the
invoice form it is already be prefaced by the term VAT No: used by another feature.
Setup
To turn on the DTTA feature, you must choose the Tax Setup option, Tax Levels. Establish
the levels of taxes required by entering a tax level name into the desired levels. If a tax
level name is left blank, that level will not be available when setting up tax rates.
Choose the Adjust Tax when Discount Taken checkbox to turn on the DTTA feature.
Australian Setup
Define Tax Level 1 as GST, this will print on Purchase Orders and is required by the
Australian Tax Office (ATO). Additional tax levels can optionally be activated.
AP Taxes Tab
On the AP Taxes tab, select the appropriate options for how your firm will process taxes.
Enter your ABN as the Resale Certificate Number. This number will print on purchase
orders.
Important! The Use Automatic Tax Calculation Feature must be selected,
manual tax lines are not supported with the DTTA feature.
Setup
The Tax Authority window allows you to define a tax authority for each tax jurisdiction to
which your firm will remit taxes. To report taxes paid and taxes received correctly, this
authority file must be identical to Accounts Receivable.
Since both applications can retain records of the same tax authority keys, you can include
taxes paid out for each authority in Accounts Payable along with those received through
Accounts Receivable when running the Tax report.
Australian Setup
Setup
The Tax Rate window allows you to create a record for each tax rate by which taxes will
be calculated in Accounts Payable and Purchase Order. Taxes are calculated based upon
the tax rate key entered during voucher, additional cost voucher, debit memo, and
purchase order entry. Tax tables allow you to specify which tax authority key should be
used and define simple straight percentage tax rates.
Australian Setup
Several tax keys must be defined to meet the requirements of the Australian Tax Office
(ATO).
The following table lists the initial descriptions for the tax types, used in AP, specified by
the ATO. These keys relate to the form numbers of the Business Activity Statement (BAS).
Important! It is the first 3 characters of the Tax Description that sorts the data on
the BAS.
Enter one or more tax keys to record other taxable and non‐taxable transactions using the
prefixes in the descriptions listed below.
• Create one G18 tax key with the Tax Included in Price box checked. This tax key can
be used for Debit Memos which are not barred from the Tax‐inclusive option. This
adjustment tax rate must not be tied to a G10 or G11 tax rate keys.
• Create anther G18 tax key with the Tax Included in Price box un‐checked. This tax key
is used when calculating an adjustment. Do not check the Tax Included in Price box
when setting up the Tax Adjustment key even if the original tax record is Tax
Included in Price.
Note: Do not enter an adjustment key on the adjustment records.
When setting up the G10 (Capital Acquisitions)/G11 (Other acquisitions) tax key, make
sure to enter the adjusting tax key of the appropriate GST Payable Adjustment Control
Account (G18). This is the link between these two tax rates and, if filled in with a valid
G18 tax rate, will properly trigger the posting routines.
Enter one or more tax keys to record any special tax requirements or GST Free items that
your firm may sell or purchase.
Setup
The Vendor window contains a record of information about each vendor for whom
transactions (vouchers, debit memos, and checks) are processed.
Australian Setup
The following change must be made to each vendor record.
If you’ve elected to default the GST tax key from the vendor, enter the correct key for each
vendor.
Or
If you’ve elected to default the GST tax key from the inventory, enter the correct tax key
for each inventory item.
Note: One time vendors must be added as vendors. The ATO requires keeping
accounting information for 5 years. Since one‐time vendors are purged at period
end, one‐time vendors may not be used and must be added as vendors.
Note: If one line item must use a different tax rate, break that line item into multi‐
ple line items, each with their own tax key. For example; if a purchase is partly
taxable, partly used in making input taxed supplies, break out the items and
assign different tax keys to the various portions.
Non-Taxable Freight
The non‐taxable freight field is not designed to work with the DTTA feature. Everything
entered on an invoice, voucher, sales order, or purchase order must carry a tax key.
Note: You may want to design a template removing the non‐taxable freight field
from the document entry screens. This may prevent users from entering a value in
this field.
One-Time Vendors
One‐time vendors must be added as vendors. The ATO requires keeping accounting
information for 5 years. Since one‐time vendors are purged at period end, one‐time
vendors may not be used and must be added as vendors.
Australian Usage
Either the general tax or the adjustment tax key is correct depending on the date of the
transaction the memo is being applied to. If the original transaction is in the current tax
period, the note may be applied to the general tax key. If, however the original transaction
is in a prior tax period the adjustment tax key must be used.
Note: Do not select the Tax on Total option for an invoice that tracks GST taxes.
Remember, you can turn this feature off in Application Setup.
For example; if an invoice worth $1000 with a tax value of $100 having a 2%10 Net 30
term, is selected for payment and the discount taken amount is 22.00, the following
occurs:.
Payment $1078.00
received
2% Discount 22.00 Manually entered
Taken
Total receipt $1100.00
New tax rate 1078/11 A 2.00 adjustment to
after discount =98.00 tax amount.
When the receipts are posted, adjustments to the Tax and the Tax Adjustment accounts
reflect the discount taken tax adjustment. This only occurs for invoices where the line
items are assigned a tax key with an adjustment key. These entries are assigned the GL
account number from the adjustment tax record.
A record will also be added to the Transaction Tax Detail History file (LOTAXLN) in
System Manager from which the BAS is calculated. The AR Tax file is also updated.
For example; if an voucher worth $1000 with a tax value of $100 and a 2% 10 Net 30 term
is to be paid, the system calculated discount is ((1100 ‐ 100) * .02)=20.00.
Based on ATO ruling, the discount available should include tax, using the following
formula 1100*.02=22.00. If you choose to override the system calculated discount, Sage
PFW will automatically calculate a tax adjustment based on the amount of the payment.
See the following table for an example.
When the payments are posted, adjustments to the Tax and the Tax Adjustment accounts
reflect the discount taken tax adjustment. This only occurs for vouchers where the line
items are assigned a tax key with an adjustment key. These entries will be assigned the GL
account number from the adjustment tax record.
A record will also be added to the Transaction Tax Detail History file (LOTAXLN) in
System Manager.
WARNING: If the Print and Post Voucher Payment option is used to qualify
vouchers to be paid, the discount taken will be understated. It is recommended
that all vouchers be manually selected for payment.
Introduction
This chapter presents an overall description of each report.
Chapter 8: Generating
For instructions on generating reports and listings, refer to the System Basics User Guide.
GST Reports
Topic Page
Reports 144
Reports
Available reports
To accommodate this feature, Sage PFW offers the following predefined Crystal reports
and one new form:
• Adjustment Note Report
• Adjustment Notes Due Report
• Business Activity Statement
All of these reports are located on the System Manager ‐ Reports folder in Sage PFW.
As part of the New Tax System you will be required to keep and issue tax invoices and
adjustment notes for your GST transactions. These are documents that you must keep, in
English, for five years.
You will want to make two copies, one to send to your customer and one for your records.
WARNING: Run Adjustment Notes before performing an AR Period End Close.
Information necessary to create the adjustment notes reside in the Current Trans‐
action (ARTRAN) file.
Order by
The Adjustment Note report is sequenced by document number.
Chapter 8: Generating
GST Reports
Customer Key Range
Choose a customer key or range of customers to create an Adjustment Note for a
particular customer or for the defined range of customers. If left blank, the default range is
[First] to [Last].
Document Number
To create an Adjustment Note for a particular invoice, select a document number from the
zoom window. Be sure to only select transactions with a P(Payment), D(Discount) or
A(Adjustment) type. If you leave the field blank, all adjustment notes print, based on the
customer key and tax period date ranges.
Note: Do not select I(Invoice) because this is the original entry and not associated
with an adjustment record.
Note: All Adjustment Notes in a batch will have the same description.
Sample Report
The following is a sample report.
Chapter 8: Generating
GST Reports
Tax Period Range
Enter the desired tax period range to get all adjustment notes for a particular period. To
print all adjustment notes, leave this range blank (this defaults to [First] to [Last]).
Sample Report
The following is a sample report.
Refer to the following table for suggested steps when creating and submitting the BAS.
Step Action
Chapter 8: Generating
BAS report created by Sage PFW onto the pre-
printed tax forms.
GST Reports
3 Submit these manually completed forms to the
ATO.
Order by
The BAS report can be sequenced by the tax rate key.
Note: This amount is not stored anywhere in the company database. You should
retain a copy of this report as a reference to the amount you declared.
Sample Report
The following is a sample report.
Chapter 8: Generating
GST Reports
Appendix A: System
Manager Files
System Manager Files
Introduction
This appendix provides:
• A list of configuration files created and maintained by the setup wizards. These files
are stored on the network file server
• A list and description of data files.
In this chapter
This chapter contains the following topics:
Topic Page
System Manager Files 154
System Manager Data Files 155
Introduction
This section contains a list of configuration files created and maintained by the setup
wizards and users with designer rights. These files are stored on the network file server.
Appendix A: System
Manager Files
Introduction
This section provides important additional information about the data files created or
accessed in System Manager during various Sage PFW processing options.
List
The following table lists the data files that comprise the System Manager database:
The Find Historical Template Properties may not be enabled on certain fields due to
system requirements. This appendix lists the fields where the Find Historical properties
cannot be edited.
Accounts Payable
Voucher Entry
Voucher Voucher Number Find Historical never populates this field as it could
cause duplicate Voucher Numbers.
Voucher Voucher Number Find Historical never populates this field as it could
cause duplicate Voucher Number.
Single Voucher per Find Historical value is overridden by foreign key link
Check from Vendor Key unless Vendor Key is also loaded
from Find Historical.
Historical Template
Appendix B: Find
Discount Taken Not loaded from the historical document.
Line Items Item Key Field is disabled, must be populated from Find His-
torical
Debit Memo Debit Memo Find Historical never populates this field as it could
Number cause duplicate Voucher Number.
Historical Template
Appendix B: Find
City There is no matching field in APHDRH.
Field is populated based on the Vendor Key.
Accounts Receivable
Invoice Entry
Credit Memo Transaction Number Find Historical never populates this field as it could
cause duplicate Invoice Number.
Credit Memo Status This field not be populated via Find Historical,
Assigned by system, can be overridden by user.
Credit Memo Date Defaults to today. This field should not be populated
via Find Historical, user should set appropriately
General Ledger
Batch Journal Batch Find Historical never populates this field as it could
Header Number cause duplicate batches. The Journal Batch Num-
ber is already loaded during Find Historical into an
invisible field
Historical Template
Appendix B: Find
Journal Batch Entry Defaults to today can be overridden by user.
Date
Sales Order
Order Sales Order Number Find Historical never populates this field as it could
cause duplicate Sales Order Number.
Sales Order Status This field should not be populated via Find Histori-
cal, Assigned by system, can be overridden by
user.
Misc Number of Times This field starts from zero for each new order.
Backordered
Order Sales Order Number Find Historical never populates this field as it could
cause duplicate Sales Order Number.
Sales Order Status This field should not be populated via Find Histori-
cal, Assigned by system, can be overridden by
user.
Number of Times This field starts from zero for each new order.
Historical Template
Appendix B: Find
Backordered
Return Entry
Purchase Purchase Order Find Historical never populates this field as it could
Number cause duplicate Purchase Order Number.
Address Vendor Name Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Address Line 1 Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Address Line 2 Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Address Line 3 Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Address State Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Zip Code Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Historical Template
Appendix B: Find
Ship To Name Not available, user maintained.
Purchasing Pro
Purchase Purchase Order Find Historical never populates this field as it could
Number cause duplicate Purchase Order Number.
Address Vendor Name Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Address Line 1 Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Address Line 2 Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Address Line 3 Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Historical Template
Appendix B: Find
City Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Zip Code Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Return Return Number Find Historical never populates this field as it could
cause duplicate Return Number.
Address Vendor Name Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Address Line 1 Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Address Line 2 Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Address Line 3 Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Zip Code Only enabled for One Time Vendor. Field is popu-
lated based on the Vendor Key.
Description
This appendix describes the use of the custom reports by company feature found in both
suites of products.
Appendix C: Crystal
Reports
If the*.RPT file is not found in the company’s custom directory, Sage PFW then checks the
\\PLATINUM\PFWRES\MASTER\CUSTOM directory. If it is found, that is the report
format used to generate the report.
Finally, if the *.RPT file is not found in the \PFWRES\MASTER\CUSTOM directory, the
report in the \PFWRES\MASTER directory is used to run the report.
Introduction
This appendix provides information for the successful configuration of Pervasive v10
security and Windows 2003 Server operating system security for Sage PFW v2010. This
must be done by a user that has Administrative rights on the Server.
The purpose of setting up Pervasive and OS security for Sage PFW is to provide an
environment where the Sage PFW programs, resource files and data files are accessible
through Sage PFW but can not be deleted (accidentally or intentionally) outside of Sage
PFW.
Pervasive Security
Pervasive v10 security can be set up in one of 3 modes:
• Classic mode (OS authentication and authorization)
• Mixed mode (OS authentication, DB authorization)
• Database mode (DB authentication and authorization)
Prior to Pervasive version 8.5, security was effectively the same as Classic mode. Users
were set up to log into a workstation and/or network server and this login information
Appendix D: Pervasive
was used by Pervasive to verify that the user had rights to the database server. In
and OS Security
Pervasive version 8.5 and later, in order to ensure the integrity of the Sage PFW database,
Btrieve security must be set to Database mode so that access to the Pervasive tables is only
permitted for valid Pervasive users.
The basic steps will be:
1. Install Pervasive v10
2. Install Sage PFW
3. Set Btrieve Security to Database mode
4. Set Server OS permissions
Procedure
The following table discusses the steps necessary for setting Btrieve mode security and
users. The steps discussed below begin after Pervasive v10 and Sage PFW v2010 are
installed. You can refer to“Chapter 2: Installation” on page 19 for instructions on
installing Pervasive v10 and Sage PFW v2010.
Steps Action
1 Before beginning, make sure you know the name and password
for your Pervasive Administrator. In order to properly use Database
mode security, you must create users for your Sage PFW
companies.
Steps Action
6 In the Security section, click on the Btrieve Security tab and select
Database (DB authentication and authorization).
Appendix D: Pervasive
and OS Security
8 Click the Apply button, then the OK button.
10 Enter the Name and password (leave the Group blank) and select
Finish.
13 Repeat steps 10-12 for each user. If all users are going to have the
same permissions, permissions can be granted to the default PUB-
LIC group instead of each user individually. Each user inherits the
permissions of the PUBLIC group.
Steps Action
14 Set the flags for Client Credentials so the user name and password
are saved.
• Under Engines, right-click on the server and Login
• Under Engines, right-click on the server and select
Properties
• Under Access, check Prompt for Client Credentials
• Under Access, check Allow Client-stored Credentials
Appendix D: Pervasive
assign permissions. You can use the SQL Editor of the Pervasive
and OS Security
Control Center. Here are some of the examples of the SQL state-
ments:
• to create a new group called PFWGroup, use CREATE GROUP
PFWGroup
• to create a new user called Larry with password as 'pw', use
GRANT LOGIN TO Larry pw
• to create a new user called Larry with password as 'pw', use
GRANT LOGIN TO Larry:pw in GROUP PFWGroup
• to grant Create Table permission to the PFWGroup, use GRANT
CREATETAB TO PFWGroup
• to grant Create Table permission to the user Larry, use GRANT
CREATETAB TO Larry
• to grant other permissions like Select, Update, Insert and
Delete to the group PFWGroup to all tables, use GRANT SELECT
ON * TO PFWGroup, GRANT UPDATE ON * TO PFWGroup,
GRANT INSERT ON * TO PFWGroup, and GRANT DELETE ON * TO
PFWGroup
• to grant Select access to the user Larry to all tables, use
GRANT SELECT ON * TO Larry
18 Enter the Pervasive password that you entered in step 10 into the
Pervasive Password field. Finish your change to the User Setup wiz-
ard.
The easiest way to manage permissions for the OS is to create a user group and then add
users to that group. Then you can set/deny permissions for the Group instead of having to
set/deny them for each individual user.
Example
We will assume that you have created a group called “PFWUsers” and have created and
added each Sage PFW user to that group. Also, you must have already set up Btrieve
Security to Database mode.
Steps Action
Steps Action
Appendix D: Pervasive
and OS Security
Steps Action
• UTGBKRTM.EXE
• LOCKS.BIN
• LOCKNAME.DFL
• LOCKS.PAS
• LOCKNAME.PAS
In addition, Sage PFW users should have full permission to the ??NOTE.MDB and
??ATTACH.MDB files in the company folder.
These file permissions can be set using the same steps outlined above for setting the Sage
PFW server folder permissions. To set the Write permissions for these files, highlight each
file in Windows Explorer and check the Allow checkbox for the following permissions:
• Create Files / Write Data
• Create Folders / Append Data
Appendix D: Pervasive
• Write Attributes
and OS Security
• Write Extended Attributes
Note that the other permissions granted to the PFWUsers group for the Platinum folder
have been inherited by UTGBKRTM.EXE.
Steps Action
1 Start Sage PFW. You will see the Pervasive Login Dialog Box:
2 Enter a valid Pervasive User name and Password. This is not your
Sage PFW Username and Password.
3 Check the Save User name and Password checkbox and click
OK.
5 You may get the Pervasive Login Dialog Box a few more times.
In each case enter the same valid Pervasive User name and
Password from step 3 and check the Save User name and Pass-
word checkbox.
6 After Sage PFW is completely loaded, exit Sage PFW and then
restart Sage PFW. This will prevent any further prompt for the Per-
vasive User name and Password and all future logins to Sage
PFW will be normal.
OS Security Only
If only OS security is used, you can protect most of the Sage PFW programs and resource
files from possible deletion. However, your Company data files are still at risk since delete
permissions are required in the Company folder for temp files, provisional files, sort files
etc.
[PLATINUM]\[COMPANY]
[PLATINUM]\[USER]
[PLATINUM]\QUEUE
The easiest way to accomplish this is to disallow Delete rights to the [PLATINUM] root
folder and then Add Delete rights to the folders listed above.
If you want to restrict access rights to the Sage PFW client folder because it just contains
program files, keep in mind that there are a few non‐program files in this folder that users
should have Write access. The PFW.INI and <user>.ini are examples. In addition, a user
must have full rights to his/her own user folder under \Platinum also.
1. Right‐click on the [PLATINUM] root folder
2. Select Properties, Security Tab, Add button
3. Input a valid network user name ([email protected]), Check Names to verify
4. Advanced button, Edit... button
5. Check Deny column for ʹDelete Subfolders and Filesʹ and ʹDeleteʹ
6. OK button, Apply button, Yes button to Security Warning about deny permissions
Following the same steps as above, you must add ʹDelete Subfolders and Filesʹ and
ʹDeleteʹ permissions for these specific /PFW folders:
QUEUE
[USER]
[COMPANY]
Appendix D: Pervasive
and OS Security
Further OS Security Only Permissions
You may further restrict userʹs permissions to other folders and files. Here are some
examples:
• Restrict Users from reading/deleting other Userʹs files by denying permissions to the
other Userʹs folders.
• Restrict Users that donʹt have access to some of the Sage PFW modules by denying
permissions to company data files for modules to which they donʹt have access.
• Restrict Users from reading/deleting company data files for companies which they
donʹt have Sage PFW access to by denying permissions for those company folders.
Symbols overview, 4
Comment window, 63
Company
[company] deleting, 30
directory overview, 16 for a PFW type user setup, 49
[username] initializing, 27
directory overview, 16 modifying, 29
step‐by‐step setup instructions, 29
company
A default settings, 83
Company Setup wizard
Access definition step‐by‐step instructions, 29
for a user security group setup, 37 Configuration files
Account Configuration wizard, 22 setting up, overview, 19
Accounts Payable summary of, 153
setting up taxes, 73 Confirm password, 46
Accounts Receivable conversion
taxes, 78, 79 weight‐to‐volume, 85
ACRCLIEN Conversion Wizards, 58
directory overview, 15 Creating Custom Reports by Company, 172
Admin Privilege, 48 Crystal Issues, 172
Applications Customizing entry screens
for a security group setup, 37 See Templates
Auto Data Conversion wizard, 22
Automatic tax calculation, 74, 76
D
B DATA
directory overview, 15
Bank statement Data files
reconciling, 67 for a processing company setup, 28
Broadcast messages re‐initializing, 30
when starting a PAS, 92 Data integrity controls
Business Desktop process locking, 12
defined, 8 record locking, 11
System Manager update conflict, 11
Index
Business Desktop, 60 decimal places
Buy/sell rate, 67, 68 settings for, 83
Default queue
setting for job processing, 98
setup, step‐by‐step, 99
C defaults
company, 83
Cash accounts Delete
buy/sell rate differences, 68 existing company, 30
CD‐ROMs existing queue, 34
included in package, vii existing security groups, 43
Client workstation existing user, 52
directory structure, 17 user job from queue, 101
interfacing to the database, 4 Demonstration companies
list of companies included, 31 J
Designer user type
defined, 48
Designing templates Job
See Templates deleting from a queue, 101
Disable Business Desktop Browser Address Bar, 48 Job priority
Dispatcher setup, step‐by‐step, 99
for polling a queue, 4 who can setup, 100
Document entry windows Job processing
creating template views of, 104 options for default queue and priority, 98
customizing views with templates, 104 Job types
Documentation processed by the PAS, 4
summary, viii See also Service types
Drive
for a PAS type user setup, 51
DSN Creation, 26 K
Keyboard navigation
E in a wizard, 24
Exceeding Admin login attempts, 46
Exchange rates, 67 L
LOINMAST
F file description and use, 71, 72
Lookups, 111
File maintenance windows lot tracking
customizing views with templates, 104 setting default parameters, 84
Form Configuration wizard, 22
M
G
maximum parameters
General Ledger setting, 88
setting up for posting, 67 Menu
Goods and Services Tax, 76, 79, 80 overview, 8
Group setting properties for items, 99
for a PFW type user setup, 49 Modify
Group ID existing company, 29
for a security group setup, 36 existing queue, 34
GST, 76, 79, 80 existing security group, 43
Monitored jobs, 12
Multi‐Currency Manager
cash account currency key, 67
H
cash held in, 67
entering amounts, 67
Help
creating custom help in Template Properties, 115
Home currency, 67 N
Natural currency, 67
I
Network file server
directory structure, 14
Item Master lookup overview, 3
overview and use of, 71, 72 Network login
overview, 7 modifying, 29
Non‐taxable items, 81 overview, 9
numbering systems Project Configuration wizard, 22
setting, 85 Properties
numeric constants setting for menu items, 99
setting, 90 Purchase Order
setting up taxes, 73
O
Q
Options
for a PFW type user setup, 48 QUEUE
directory overview, 14
Queue
P deleting, 34
deleting jobs by the System Administrator, 10, 101
managing jobs by the System Administrator, 101
PAS modifying, 34
message screen, 93 overview, 9
overview, 4 preferred, 10
reactivating, 93 relationship to a PAS, 9
setup information, 92 setting a default for job processing, 98
stopping, 95 setting job priority, 99
Password setup, 32
for a PFW type user setup, 46, 48, 51 step‐by‐step setup instructions, 33
Password Confirmation, 48 Queue ID
Pervasive for a queue setup, 33
resident on network file server, 4 Queue name
Pervasive Admin Rights, 26 for a PAS type user setup, 51
Pervasive Password, 46 Queue Setup wizard
PFW step‐by‐step instructions, 33
directory overview, 17
PFWADMIN
Index
directory overview, 15
R
PFWCLIEN
directory overview, 15
PFWRES Reconciling accounts
directory overview, 16 using the bank statement, 67
PLATINUM Record locking
directory overview, 14 overview, 11
Polling interval unmonitored jobs, 12
for a PAS type user setup, 51 Registration wizard, 22
Populating fields using Find Historical, 113
Printer
overview, 10 S
Printer ID
for a printer setup, 34
Priority Security
setting for job processing, 99 components of, 6
Process Application Server default, 35
See PAS deleting, 43
Process locking modifying, 43
overview, 12 overview, 6
Processing company Security group
deleting, 30 deleting, 43
initializing, 27 modifying, 43
Security Group Setup wizard
step‐by‐step instructions, 42 manual tax entry, 73
Security groups nontaxable items, 81
overview, 6 setting up, 73
Security Reporting, 53 tax rate key default, 77
Service types tolerance percentage, 77
for a queue setup, 33 tracking, 81
Settlement discounts, 80 Template Manager
Setup overview, 118
about wizards, 20 Template Properties window
processing company, 26 illustrated, 109
queue, 32 Templates
user, 25, 44 adding custom field help, 115
user security group, 35 adding lookups, 111
SSCC format, 84 assigning designer rights for access, 107
Startup method assigning to security group, company, or globally,
for a PAS type user setup, 51 118
Storage of company information, 27 basic steps to create, 108
System Administrator cannot override shipping configuration, 104
overview, 7 captions, 109
System configuration closing and reopening while designing, 116
recommended requirements, viii customizing a field or object, 110
System configuration windows deleting lookups, 111
customizing views with templates, 104 how custom help is viewed by user, 115
System Designer illustrated example, 105
overview, 8 menu item remaining open while designing, 109
System Manager modifying lookups, 111
setting up, 62 overview, 104
system manager setup properties window, illustrated, 109
company defaults, 83 restoring shipping default configuration, 116
saving, 116
setting default for user, 120
T table of template enabled entry items, 108
using saved templates, 120
viewing work in progress, 116
Tax authorities Type of User
setting up, 78 for a PAS type user setup, 50
Tax Authority window, 78 for a PFW type user setup, 47
Tax levels
defining, 76
Tax Rate window, 79
U
Tax rates
defaulting from item location, 77
defaulting from vendor, 77 Update conflict
defining, 79 overview, 11
Tax Setup window, 75 User
Tax sheet, 76 deleting, 52
Taxes selecting templates, 120
actual, 76 setup, 44
as line items, 73 step‐by‐step setup instructions, 52
automatic tax calculation, 74, 76 User configuration files
calculated, 76 setting up, overview, 19
calculating, 73, 79 summary of, 153
comparing, 77 User ID
defining tax levels, 76 for a PAS type user setup, 50
defining tax rates, 79 for a PFW type user setup, 47
included in price, 76, 77, 80 User login
including settlement discounts, 80 overview, 7
system administrator overview, 7
User password configuration, 46
User setup
unique configuration file, 27
User Setup wizard
step‐by‐step instructions, 52
User types
overview, 7
Username
for a PAS type user setup, 50
for a PFW type user setup, 45, 47
USERS.ADM
file description, 154
UTGD.SRF
file description, 154
UTGXR.SRF
file description, 154
UTMC
file description, 154
UTMCFILE
file description, 154
UTQDEF.SRQ
file description, 154
UTQMSG
file description, 154
UTQSL.SRQ
file description, 154
UTQxxxx.SRQ
file description, 154
Index
Value‐added taxes, 76, 80
VAT, 76, 80
weight‐to‐volume conversion, 85
Wizards
Account Configuration wizard, 22
Auto Data Conversion wizard, 22
changing or deleting, overview, 24
commands, 24
common elements, 23
Company Setup wizard, 29
Form Configuration wizard, 22
keyboard navigation, 24
overview, setting up user configuration files, 20
Queue Setup wizard, 33
Registration, 22
Security Group Setup wizard, 42
suggested setup order, 21
User Setup wizard, 52
Company Name:________________________________________________________________________
Sage Reseller
Name: _________________________________________________________________________________
Phone: _________________________________________________________________________________
Important: Registration, support, updates, and access to the application will not be granted unless your
software is registered within 30 days after installation.