Understanding Transaction-Related Control Data
Transaction-related control data consists of required and optional information that you use primarily to create transactions. This topic provides overviews of:
Analysis types
Analysis groups
Transaction identifiers
With the exception of programs (summary projects), each project is composed of, at the most basic level, transactions. Transaction rows in the Project Transaction table (PROJ_RESOURCE) contain the quantity and amounts associated with each transaction and all of the identifying information that accompanied those costs. Analysis types are assigned to individual transactions to identify different types of transactions, such as estimated costs, budgeted amounts, actual costs, and billed costs. For example, you can create an analysis type for the calculation of total budgeted amounts of the project compared to total actual costs, to see if the project is over or under budget at any time during the project.
A single transaction can result in multiple transaction rows as it moves through the system. For example, assume that a project has 1,000 USD budgeted for project labor. The actual cost of labor is 1,500 USD, and the amount of billing for the labor is 1,700 USD. The result is three transaction rows that record the same labor transaction as it moves from stage to stage through the project, as shown in this table:
|
Analysis Type |
Transaction Type |
Amount |
|---|---|---|
|
BUD (Budget) |
LABOR |
1,000.00 USD |
|
ACT (Actual costs) |
LABOR |
1,500.00 USD |
|
BIL (Billing) |
LABOR |
1,700.00 USD |
Many of the following analysis types are necessary for Project Costing analysis groups, reports, and processes to function properly. If you choose not to implement these analysis types, you still must configure these features. You can create additional analysis types for processing and analysis purposes.
|
Analysis Type |
Description |
|---|---|
|
ACT |
Actual Cost |
|
ASP |
Express Asset % Distributions |
|
BAJ |
Billing Adjustment |
|
BD1 through BD8 |
Total Cost Budget - Scenario 1 through Total Cost Budget - Scenario 8 |
|
BIL |
Billable Amount |
|
BLD |
Billed Amount |
|
BRT |
Billing Retainage |
|
BUD |
Total Cost Budget |
|
CAC |
Cost Sharing Actuals |
|
CAJ |
Cost Share Commitment Adjust |
|
CBA |
Cost Budget Adjustments |
|
CBU |
Cost Sharing Budget |
|
CCA |
Closed Commitment Adjustments |
|
CCO |
Cost Sharing Commitment |
|
CCR |
Cost Share Commitment Reversal |
|
CFA |
Cost Sharing Finance and Administration |
|
CGE |
Cost Sharing General Ledger Expense |
|
CLS |
Asset Cost Summary |
|
COM |
Commitment including Purchase Order & Subcontractor |
|
COR |
Cost of Removal of Asset |
|
CPY |
Cost Share Payroll |
|
CQR |
Cost Share Requisition Reversal |
|
CRQ |
Cost Sharing Requisition |
|
CRR |
Cost of Removal Cost Summary |
|
CRV |
Commitment Reversals |
|
CST |
Costing (without PeopleSoft Contracts) |
|
CV1 through CV4 |
Historical Cost Budget Version 1 through Historical Cost Budget Version 4 |
|
DEF |
Billing Deferred Amount |
|
DSC |
Billing Discount |
|
ESB |
Proposal Management Bill Estimate |
|
ESC |
Proposal Management Cost Estimate |
|
ETB |
Bill Estimate to Complete |
|
ETC |
Cost Estimate to Complete |
|
EXP |
Expenses |
|
FBD |
Fixed Cost Billed Amount |
|
FCC |
Completion Cost |
|
FDF |
Federal Distribution |
|
FDL |
Local Distribution |
|
FDR |
Fund Distribution Reversals |
|
FDS |
State Distribution |
|
FND |
Funds Distribution |
|
FRD |
Forward Pricing for Revenue |
|
FRV |
Fixed Cost Revenue Amount |
|
FTC |
Forecast Cost to Complete |
|
GLE |
GL (General Ledger) Expense |
|
GLR |
GL Revenue |
|
GNT |
Grant Reimbursement |
|
IUP |
Inter/Intra-Unit Payable |
|
IUR |
Inter/intra-Unit Receivable |
|
MBA |
Manual Billing Adjustment |
|
MMC |
Maintenance Management Costs |
|
MRA |
Manual Revenue Adjustment |
|
NPY |
No Pay Time and Labor Actual |
|
ODL |
Over Distribution Limit |
|
OFA |
Offset Revenue |
|
OLT |
Over Limit Amount |
|
ORD |
Order |
|
PAY |
Time and Labor Actual |
|
PCA |
Profile Adjustment |
|
PCL |
Profile Cost Summary |
|
PFS |
Proceeds from Sale of Asset |
|
PMR |
Proposal Management Reversal |
|
PRV |
Billing Provisional Pricing |
|
PSD |
Purchase/Sold Time Discount |
|
PSR |
Proceeds from Sale Summary |
|
PST |
Purchase/Sold Time |
|
RAJ |
Released Retainage Adjustment |
|
RB1 through RB3 |
Revenue Budget 1 through Revenue Budget 3 |
|
RBD |
Revenue Budget |
|
REB |
Rebate |
|
REQ |
Requisition |
|
RET |
Retirement Cost |
|
REV |
Revenue |
|
ROL |
Revenue Over Limit |
|
RRT |
Released Billing Retainage |
|
RRV |
Requisition Reversals |
|
RV1 through RV4 |
Historical Revenue Budget Version 1 through Historical Revenue Budget Version 4 |
|
SFA |
Sponsor Finance and Administration |
|
SHD |
Shared Discount |
|
SHR |
Shared Revenue |
|
SUT |
Sales/Use Tax |
|
TLA |
Time and Labor Estimate |
|
TLB |
Time and Labor Estimate for Billing |
|
TLC |
Time and Labor Contractors |
|
TLX |
Cost from Time Traveler |
|
TUG |
Maintenance Management Tools Usage |
|
UAJ |
Prepaid Utilization Adjustment |
|
UTL |
Prepaid Utilization (Billing) |
|
VAR |
Variance |
|
VIN |
Not Recoverable Value Added Tax |
|
WAJ |
Withholding Adjustment |
|
WFA |
Waived Facilities and Administration |
|
WRJ |
Withholding Release Adjustment |
|
WRL |
Withholding Release |
|
WTH |
Withholding |
|
WTO |
Write-off |
|
WWO |
Withholding Write-off |
Project Costing delivers cost sharing analysis types that are used exclusively by PeopleSoft Grants. If a transaction line for a PeopleSoft Grants project meets the criteria of cost sharing that is defined at the Grants business unit level, the system assigns the cost sharing analysis type to the transaction.
You use analysis groups to:
Analyze projects
Map analysis types
Enhance system performance
Many analysis groups are necessary for Project Costing project analysis functions and mass changes to execute properly. If you choose not to use the analysis groups that are delivered with Project Costing, you still have to configure the analysis groups or create new ones to use with these functions. This table describes the analysis groups:
|
Analysis Group |
Description |
|---|---|
|
ACT |
Actual Cost |
|
ADJST |
PC (Project Costing) Transaction Adjustment |
|
ALL |
All Analysis Types |
|
AMCOR |
Project Costing to Asset Management Cost of Removal |
|
AMPFS |
Project Costing to Asset Management Proceeds from Sale |
|
AR |
Receivables |
|
BFEE |
Billing Fee |
|
BI |
Billing |
|
BLD |
Billed Transactions - Worksheet to Project Transaction table |
|
BUD |
Budgets |
|
CBU |
Cost Sharing Budget |
|
CLOSE |
Project Costing to Asset Management Asset Summary |
|
COM |
Commitments |
|
COPY |
Template Copy |
|
COSTS |
Estimated and Actual Costs |
|
CRQ |
Cost Sharing Requisition |
|
CSCOM |
Cost Share Commitment Balance |
|
CSTSH |
Cost Sharing Analysis Group |
|
EAC |
Estimate at Completion |
|
FNA |
Facilities and Administration |
|
FOR2C |
Forecast Cost at Completion |
|
FREV |
Forecast Revenue |
|
GBUD |
Grants Budgets |
|
GL |
General Ledger Analysis Types |
|
GMACT |
Grant Reporting Actual Expense |
|
HBPV1 through HBPV4 |
Historical Budget Version 1 through Historical Budget Version 4 |
|
INT |
Interest Calculation |
|
LABOR |
Labor Cost and Time |
|
MMCST |
Maintenance Management Costs |
|
OPENC |
Open Commitment Balance |
|
PCADJ |
Project Costing to Asset Management Profile Adjustment |
|
PCBUD |
All Projects Budget Types |
|
PMBIL |
Mgr Trans Review (Manager Transaction Review) - Billing |
|
PMCST |
Mgr Trans Review - Cost |
|
PMEXP |
Proposal Management - Expense |
|
PMPOP |
Mgr Trans Review – Period of Performance |
|
PMREV |
Mgr Trans Review - Revenue |
|
PMSHR |
Mgr Trans Review - Sharing |
|
PMTIM |
Proposal Management - Time |
|
POADJ |
Purchasing Adjustments |
|
PRECL |
Project Costing to Asset Management Profile Summary |
|
PSBLD |
Billing to Project Costing |
|
PSCST |
Accounting Costs |
|
PSDEF |
Funds Distribution Defaults |
|
PSDST |
Funds Distribution |
|
PSECC |
Estimated Costs to Completion |
|
PSITD |
Inception to Date Costs |
|
PSLMT |
Limit Processing - Billing |
|
PSREV |
System Revenue |
|
PSROL |
Limit Processing - Revenue |
|
PSRV2 |
GC (Government Contracting) System Revenue |
|
PSTDR |
Sharing |
|
PSUAB |
Revenue on Unapproved Billing. Analysis types included in this group and the PSREV group are eligible for revenue recognition prior to being reviewed or approved for billing. |
|
PSVP |
If using variance pricing, use this analysis group to map a converted analysis type to its original analysis type during the Variance Pricing process (PC_VAR_PRICE). As a transaction progresses through the billing process, the analysis type is changed. For example, a BIL analysis type is changed to BLD when the transaction is invoiced in PeopleSoft Billing. This can cause issues when trying to net new pricing rows with historic rows. Therefore, in the example, this analysis group assists the Variance Pricing process to map the BLD transaction row to the BIL transaction row. You can modify this analysis group. |
|
PSVPX |
If using variance pricing, use this analysis group to prevent analysis types from being included in historical rows. For example, a sales tax row that is generated in Billing may be considered to be outside the contractual rate. This transaction carries the original resource from ID, and would normally have been included in the netting process and the historical rows. You can modify this analysis group. |
|
PSWKS |
Billing Worksheet Grouping |
|
RBUD |
Revenue Budget Group |
|
REQ |
Requisitions |
|
RFEE |
Revenue Fee |
|
SPACT |
Grants Sponsor Actual Costs |
|
SPENC |
Grants Sponsor Commitments |
|
UNBLD |
Unbilled Transactions |
|
VARY |
Variance |
Using Analysis Groups to Analyze Project Costs
You use analysis groups to define relationships among analysis types to analyze project costs using Project Costing pages, queries, or reports.
Creating an analysis group to analyze projects follows this process:
Group the analysis types to include in the project analysis.
Apply the appropriate multiplier to each analysis type to create a relationship.
A multiplier determines how amounts and quantities for a specific analysis type are factored into the analysis. The multiplier is applied to total quantities and amounts in all transactions identified by a specific analysis type. For example, to add amounts to the analysis, enter 1. To subtract costs from the analysis, enter −1. To add half of the amounts to the analysis, enter 0.5.
The easiest way to create analysis groups for analyzing projects is to start with an equation. An equation makes it easier to determine what multiplier to assign to an analysis type. For instance, to create an analysis group to determine whether or not a project is over budget, you might start with this equation: Budgets − Actuals = Budget-to-Cost Variance.
You assign a multiplier of −1 to the Actual Cost analysis type and a multiplier of 1 to the Total Cost Budget analysis type. When using this analysis group for online analysis or reporting, all actual costs from the analyzed project are subtracted from budgeted costs. If the result is a negative number, the project is over budget. To set up the analysis group so that a positive number means that the project is over budget, reverse the multipliers so that budgeted amounts are subtracted from actual costs.
You can apply multipliers to quantities for each analysis type included in an analysis group. When you create analysis groups to analyze project costs, multipliers will probably be the same for both the amount and the quantity.
Using Analysis Groups to Map Analysis Types
New projects or activities can be created from copies of existing projects and activities. You can specify an analysis group to map analysis types from the existing project or activity to the new project or activity. For example, when you create a new project from an existing project, you can create an analysis group that maps actual (ACT) transactions from the existing project to the newly created project as budget (BUD) transactions. By using analysis groups, you can also manipulate mapped amounts. For example, you can enter a multiplier of 2 to double the budgeted quantities and amounts in the new project.
Using Analysis Groups to Enhance System Performance
On some PeopleSoft Project Costing pages, analysis groups limit the number of resource transactions that appear on a page at one time. For example, when there are tens of thousands of transactions per project in the system, performance is greatly reduced if you try to access all of those transactions every time that you open a page. By using analysis groups, you can limit the number of transactions that appear on a page to transactions of specified analysis types.
To do this, create an analysis group that identifies a group of analysis types. When an analysis group is entered as part of the selection criteria, only the resource transactions that contain the analysis types specified in that analysis group are available for use on the page.
PeopleSoft delivers the following source types as default; however, if you do not need any of the functionality provided with the source types, then they can be modified or removed.
ITEMS (Inventory Items)
LABOR (Total Labor)
MATER (Total Material)
The high-level steps to establish source groups are:
Define source types.
Define resource categories.
Define resource subcategories.
Combine multiple source types for award analysis and billing.
Add descriptions to resource groups.
Tiered pricing enables you to adjust the rate applied to cost transactions during the Pricing Application Engine process (PC_PRICING) based on quantities that accumulate against a contract line. This type of pricing applies to rate-based, contract-line processing only. Implementing tiered pricing requires that you create transaction identifiers, which are similar in concept to using analysis groups. Transaction identifiers provide users with the flexibility to identify and group project ChartField values and eliminate the need to identify the ChartField values each time they define tiered pricing for a new contract line.
Transaction limits, another feature that is available if you use PeopleSoft Contracts, also requires the use of transaction identifiers. Transaction identifiers enable you to apply specific limits to transactions with Project Costing ChartField values that match the contents of the transaction identifier for a specific contract line.
Note: You must use PeopleSoft Contracts to implement the Tiered Pricing and Transaction Limits features.