This preface discusses:
PeopleSoft products.
PeopleSoft application fundamentals.
Common elements in this PeopleBook.
Pages with deferred processing.
Common elements used in this PeopleBook.
Note. This PeopleBook documents only page elements that require additional explanation. If a page element is not documented with the process or task in which it is used, then it either requires no additional explanation or is documented with the common elements for the section, chapter, or PeopleBook.
This PeopleBook refers to these PeopleSoft products:
Oracle's PeopleSoft Billing
Oracle's PeopleSoft Commitment Control.
Oracle's PeopleSoft Contracts
Oracle's PeopleSoft General Ledger
Oracle's PeopleSoft Inventory
Oracle's PeopleSoft Payables
Oracle's PeopleSoft Program Management
Oracle's PeopleSoft Project Costing
Oracle's PeopleSoft Proposal Management
Oracle's PeopleSoft Purchasing
Oracle's PeopleSoft Receivables
Oracle's PeopleSoft Time and Labor
The PeopleSoft Proposal Management 9.1 PeopleBook provides you with implementation and processing information for your PeopleSoft Proposal Management system. However, additional essential information describing the setup and design of your system resides in companion documentation. The companion documentation consists of important topics that apply to many or all PeopleSoft applications across the Financials, Enterprise Service Automation, and Manufacturing product lines. You should be familiar with the contents of these PeopleBooks.
The following companion PeopleBooks also apply to PeopleSoft Proposal Management:
PeopleSoft Applications Fundamentals 9.1 PeopleBook
PeopleSoft Global Options and Reports PeopleBook
PeopleSoft Working with Customers and Orders PeopleBook
PeopleSoft Supply Chain Management Integration PeopleBook
Most pages in PeopleSoft Proposal Management operate in deferred processing mode. Most fields on these pages are not updated or validated until you save the page or refresh it by clicking a button, link, or tab. This delayed processing has various implications for the field values on the page—for example, if a field contains a default value, any value that you enter before the system updates the page overrides the default. Another implication is that the system updates quantity balances or totals only when you save or otherwise refresh the page.
See Also
PeopleTools PeopleBook: PeopleSoft Application Designer, "Guidelines for Designing Pages"
A companion PeopleBook called PeopleBooks and the PeopleSoft Online Library contains general information, including:
Understanding the PeopleSoft online library and related documentation.
How to send PeopleSoft documentation comments and suggestions to Oracle.
How to access hosted PeopleBooks, downloadable HTML PeopleBooks, and downloadable PDF PeopleBooks as well as documentation updates.
Understanding PeopleBook structure.
Typographical conventions and visual cues used in PeopleBooks.
ISO country codes and currency codes.
PeopleBooks that are common across multiple applications.
Common elements used in PeopleBooks.
Navigating the PeopleBooks interface and searching the PeopleSoft online library.
Displaying and printing screen shots and graphics in PeopleBooks.
How to manage the locally installed PeopleSoft online library, including web site folders.
Understanding documentation integration and how to integrate customized documentation into the library.
Application abbreviations found in application fields.
You can find PeopleBooks and the PeopleSoft Online Library in the online PeopleBooks Library for your PeopleTools release.
Account |
ChartField that identifies the nature of a transaction for corporate accounts. This is a delivered PeopleSoft ChartField, specific use of which is typically defined by your organization during implementation of PeopleSoft General Ledger. |
Activity |
The unit of work in PeopleSoft Project Costing that provides a further breakdown of projects, usually into specific tasks. Resources are assigned directly to activities within a project, rather than being assigned directly to projects. |
A three-character, user-definable identifier that enables you to label the different types of costs in PeopleSoft Project Costing. For example, you might want to track budgeted costs (BUD), committed costs (COM), and actual costs (ACT). |
|
Currency |
Code that identifies the type of currency for an amount, such as USD (United States Dollar) or EUR (Euro). |
Department |
ChartField that indicates who is responsible for or affected by the transaction. |
Effective Date |
Date on which a table row becomes effective; the date that an action begins. For example, if you want to close out a ledger on June 30th, the effective date for the ledger closing would be July 1st. This date also determines when you can view and change the information. Pages and batch processes that use the information use the current row. |
An EIP is an instance of enterprise integration between your PeopleSoft application and an external system or application: a seamless connection between the two products to accomplish a specific business purpose. EIPs represent the formal methods that third-party applications use to exchange data elements. |
|
Operating Unit |
ChartField that is used to identify a location, such as a distribution warehouse or sales center. |
Process Monitor |
This is a PeopleSoft tool that you can use to review the status of scheduled or running processes. You can view all processes to see the status of any job in the queue and control processes that you initiated. See PeopleTools PeopleBook: PeopleSoft Process Scheduler, "Understanding PeopleSoft Process Scheduler." |
Product |
ChartField that captures additional information useful for profitability and cash flow analysis by product sold or manufactured. |
Program |
ChartField that identifies groups of related activities, cost centers, revenue centers, responsibility centers, and programs. Tracks revenue and expenditures for programs. |
The highest level of hierarchical organization within PeopleSoft Project Costing. PeopleSoft Project Costing provides the structure to which activities and resources are added. Proposal projects obtain their numbering from PeopleSoft Project Costing. This ensures continuity with the numbering process when the proposal project becomes a real project. The numbering process occurs when you run the generate process, request pre-award spending, or create the project team. |
|
A contract is a legal agreement between two or more parties. This is the highest level entity within the PeopleSoft Contracts module. Proposal numbering is obtained from PeopleSoft Contracts and a proposal becomes a contract after you run the generate process. |
|
A comprehensive estimate provided to a prospect or customer that contains projects, activities, resources, labor, assets, materials, and other projections. The proposal also includes a time frame for the proposed work. A proposal can contain multiple versions for modeling different scenarios prior to finalizing and running the generate process. You can run the generate process only once on the current version of a proposal. |
|
A unique number that is assigned by PeopleSoft Contracts to track the proposal throughout the proposal development and Contract Generation process. This ID is derived from the PeopleSoft Contracts auto numbering process and remains the same after the Contract Generation process so that the proposal and the contract contain the same ID. |
|
Report ID |
The report identifier. |
Displays an individual cost or bill row within PeopleSoft Project Costing. It is through resource transactions that individual costs and types of costs are tracked. Each resource transaction contains a cost, bill, and quantity, and other identifiers of the cost that may have been entered. Resource transactions are created when you receive information from other systems, run allocations with project resources as the target, or perform internal transactions such as billing, project closure, or adjustments. |
|
The Resource Transaction field in PeopleSoft Project Costing that identifies the resource associated with a given cost. Resource types may be general or specific depending on your needs; they are used in conjunction with resource categories, resource subcategories, and resource groups. |
|
Run |
This button takes you to the Process Scheduler request page, where you can specify the location where a process or job runs and the process output format. See PeopleTools PeopleBook: PeopleSoft Process Scheduler, "Understanding PeopleSoft Process Scheduler." |
Run Control ID |
Code that identifies the run parameters for a report or process. |
SetID |
Code that represents a set of control table information or tablesets. A tableset is a group of tables (records) necessary to define your company's structure and processing options. |
In PeopleSoft Proposal Management, status is also used to indicate the state of the proposal. The statuses used in PeopleSoft Proposal Management include: Draft, Ready, Denied, Committed, and Canceled. |
|
To track different scenarios, we support multiple versions of proposals. Note that users can select only one version (the current version) for sale. The other versions would, however, still be visible. Basic information, such as the proposal description, start and end dates, customer information, and contacts, remain the same for each version. To create a different version of a proposal, users enter resource details for the projects and activities that they want to associate with the proposal. |