Transactions Eligible for Pricing and Repricing

The Pricing process uses not only effective date of rate definitions, but also distribution statuses and system sources to identify transactions that are eligible for processing.

Distribution Statuses

These distribution status fields in the Project Transaction table support rate set and rate plan processing:

  • Cost distribution status (CST_DISTRIB_STATUS): Indicates if a source row has been priced for costing.

  • Billing distribution status (BI_DISTRIB_STATUS): Indicates if a source row has been priced for billing.

  • Revenue distribution status (REV_DISTRIB_STATUS): Indicates if a source row has been priced for revenue recognition.

  • General ledger distribution status (GL_DISTRIB_STATUS): Indicates if a transaction row has been interfaced to the general ledger.

    Repricing cannot occur on a source row if any target transaction rows have been further processed downstream. If a source row results in multiple target rows, and any of the target rows have been sent to PeopleSoft Billing or PeopleSoft General Ledger, neither row can be repriced. For example, assume that a rate plan specifies that an incoming transaction from PeopleSoft Expenses (with a TLX analysis type) is the source row that will create two rows—a cost row (with a CST analysis type) and a bill row (with a BIL analysis type). If the BIL row has already been sent to PeopleSoft Billing, the system cannot reprice the TLX row, which means that the cost cannot be recalculated.

Transaction rows must have a distribution status of N (new or not distributed) to be included in the Pricing process. To process a transaction row for a cost rate definition type, the cost distribution status must be N for the row. To process a row for a billing rate definition type, the billing distribution status must be N. Similarly, to process a row for a revenue rate definition type, the revenue distribution status must be N.

The possible cost, billing, and revenue distribution status values are:

  • C: Created (cost and revenue rows only).

  • D: Distributed; done.

  • G: Generated (cost and revenue rows only).

  • I: Ignore; do not process.

  • N: New; not distributed.

  • P: Priced (billing rows only).

  • U: Unbillable/nonbillable (billing rows only).

  • W: Worksheet, billing calculations are in the Project Costing Billing Worksheet (billing rows only).

For projects assigned to contracts that separate billing and revenue, the billing distribution status indicates if a transaction row has been priced for billing, and the revenue distribution status indicates if the row has been priced for revenue. These statuses enable you to separately monitor pricing for billing and revenue.

Note:

The Process Project Accounting Application Engine process (PSA_ACCTGGL) assigns the G status value to the GL Distribution Status field (GL_DISTRIB_STATUS) for rows that are associated with contracts revenue. The Contracts Load Update Application Engine process (CA_LOAD_UPD) updates the GL Distribution Status value to D for these rows in the Project Transaction table.

System Sources

The Pricing process uses these system sources, in combination with distribution statuses, to identify transactions that are eligible for processing:

  • PRP: Indicates that a transaction is priced for billing.

  • PRC: Indicates that a transaction is priced for costing.

  • PRR: Indicates that a transaction is priced for revenue.

Repricing

Similar to the Pricing process, the Repricing process considers the pricing options that you select on the Pricing run control page.

You can reprice transactions that:

  • Have not been billed or sent to GL.

    A source row is ineligible for repricing if any of its target transaction rows contain a billing distribution status of W or D, or a GL distribution status of D or G.

  • Are not linked to an asset.

  • Have not been sent to PeopleSoft Asset Management.

  • Have not been used for fee calculations (billing and revenue fee worksheets) in PeopleSoft Contracts.

    This rule applies only to government contracts. A transaction with a Contract Fee Status (CA_FEE_STATUS) field value of Generated indicates that it has been used in a fee calculation.

  • Are not created by the Variance Pricing Application Engine process (PC_VAR_PRICE).

    Repricing cannot occur on any transaction rows that are created as a result of the Variance Pricing process.

You can view the distribution statuses of the source transaction row on the Transaction Detail page.

Related Topics