Our starting assumption in building BEAM was that PeopleTools was designed to build and run applications, but it lacks certain capabilities customer teams need to manage, control and administer its applications. Much work has to be done manually, complicating audits and compliance requirements. Customers do not generally complain about or have issues with PeopleSoft’s functionality, reliability, or scalability. But nearly all customers have issues with the difficulties of – and the cost of – maintaining the applications.

BEAM is software that extends and enhances PeopleTools to help minimize the difficulties and costs of managing and controlling PeopleSoft environments and applications.

BEAM is delivered to customers as a standard PeopleSoft project, and installed into an empty PT.SYS database. BEAM, when added to PeopleTools, creates a control and management environment from which developers can view and access all other PeopleSoft environments. The BEAM environment does not contain any PeopleSoft applications, or data. Instead it contains information about these other environments, as well as job definitions to be run against environments, the results of jobs, as well as logs, traces and audit trails pertaining to the jobs.

The BEAM database can be located on any server. BEAM uses DBLinks/Linked Servers to talk to other PeopleSoft environments. There are a number of advantages to a separate environment, but a key design goal was to leave no footprint in any customer PeopleSoft databases. Also, by being in its own environment, BEAM can work with any number of, and any combination of, platforms, databases and applications. This means, for example, if you were to run a BEAM Compare report, you can not only compare different environments to one another, but you can also compare different applications versions, running on different PeopleTools releases. We designed BEAM to work with, but independently from, your environments.



BEAM is organized into separate parts.

Configuration – BEAM Settings and Directory Locations, Trace Profiles, and BEAM Data Dictionary

Dashboard – The BEAM Monitor shows the status of current and completed BEAM Jobs

Job – A Job is a collection of Methods

Method – A Method is a collection of Steps

Steps – A Method Step is a specific operation (i.e. Compare)

Parameter – Run Time variables

Filter – List of columns/records to include/exclude



A BEAM Job is just a container. It executes one or more Methods in sequence. The basic structure is:

Basic BEAM Job Flow


BEAM Jobs can be run on demand, in background, or scheduled through the PeopleSoft Process Scheduler.