Transaction Limits

Transaction limits enable you to apply limits to one or more subsets of transactions for a specific contract line. Transaction limits are only visible and must be managed at the contract line level.

Transaction limits consist of the following main elements:

• Transaction identifiers.

• Transaction limit amounts and sequence numbers.

Transaction Identifiers

Transaction identifiers are configurable and allow you to identify a subset of transactions by applying specific criteria to one or more PeopleSoft Project Costing ChartField values (source type, category, and subcategory).

You associate the transaction identifier with a contract line and then establish the limit for that transaction identifier on the line. Multiple contract lines can use the same transaction identifier, but the limit is always specific to the contract line. Transaction Limits are applied when the PeopleSoft Project Costing ChartField values on the billing or revenue transaction match the criteria defined for the transaction identifier. Billing and revenue transactions must first pass the transaction limit before they can be checked against the contract line billing and revenue limits. Transactions not meeting the criteria for a transaction identifier are included in the contract line billing and revenue limits only. These amounts are entered on the Billing and Revenue Allocation pages.

WARNING:

After a transaction identifier is defined and associated with a transaction limit, it should not be modified, because data conflicts may occur for any transactions already processed using the transaction identifier.

Transaction Limit Amounts and Sequence Numbers

After you have defined transaction identifiers, you assign them to the contract line. A contract line can have multiple transaction limits, each with its own transaction identifier and limit enabling you to limit revenue and billing on multiple subsets of transactions. For more complex limit processing scenarios, you can create multiple transaction limits based on the types of transactions associated with the contract line and you can set up your transaction limits to overlap one another.

When assigning multiple transaction limits to one contract line, the system uses sequence numbers to determine the order in which a limit amount is applied to a transaction. These sequence numbers are defined by you and must be unique to the contract line. In the event that you set up overlapping limits, the system uses the sequence numbers to identify which transaction limit should be processed first.

Limits processing always consider transaction level limits first, and then billing and revenue limits defined at the contract line level, when determining whether a transaction can pass limit checking. Only transactions that pass transaction limits, or transactions for which transaction limits are not applicable, are checked against overall billing and revenue limits. Depending on your limit setup, when a transaction is processed, a portion of the transaction could be determined to be over-the-limit for the transaction level limit, even though it might have been within the available overall funded and revenue limit amount.

Note:

When assigning multiple transaction limits to a contract line, sequencing defines the order in which limits are applied to transactions. Because the over-the-limit transactions generated can vary depending on the order of the transaction limits, you need to carefully consider your setup and any potentially negative results from overlapping limits.