Example 2: Transaction Level Summary Limits
Transaction level limits enable you to limit the amount of billing and revenue on a subset of transactions. This example describes the steps and processing for a transaction level limit scenario. Note that a transaction limit applies to billing and to revenue also if the contract separates as incurred billing and revenue. A different transaction limit cannot be entered for revenue.
Setup
The system is defined in the following way:
-
The Summ. Limit for Govt Contracts (summary limit for government contracts) option is selected on the Installation Options - Contracts page.
-
The target excess type for billable transaction level amount in excess (Bil Tx Lvl Amount in Xs) is defined in the following way: Source Type is EXCES, Category is deselected, Subcategory is blank.
-
The target excess type for billable transaction level amounts that are reclaimed (Bil Tx Lvl Reclaimed Amt in Xs) is defined in the following way: Source Type is RECLM.
Contract Transaction
Define the contract transaction:
-
Create a contract with one rate-based contract line.
-
Associate a project and an activity with the contract line.
-
Set the contract line level limit to 10,000 USD.
-
Set a contract transaction level limit of 1,000 USD with a transaction identifier equal to DEVLAB.
The transaction identifier has a resource type (RT) equal to LABOR and a resource category (RC) equal to PROG.
-
Select the Target Excess check box for the project and activity.
Project Transaction
Create a transaction in PeopleSoft Project Costing:
| Analysis Type | Amount | Resource Type | Resource Category |
|---|---|---|---|
|
ACT |
5000 |
MATER |
ADMIN |
|
ACT |
2000 |
LABOR |
PROG |
Summary Limits Processing
These rows are created in PROJ_RESOURCE:
| Analysis Type | Amount | Transaction Identifier | Resource Type | Resource Category | Amount in Excess Flag |
|---|---|---|---|---|---|
|
BIL |
5000 |
NA |
MATER |
ADMIN |
NA |
|
BIL |
2000 |
NA |
LABOR |
PROG |
NA |
|
BIL |
- 1000 |
DEVLAB |
EXCES |
NA |
Y |
Note:
NA indicates that the field is not applicable.
Contracts to Billing Processing
The Contracts to Billing Interface process (CA_BI_INTFC) sends the billable (BIL) rows to the Billing interface table (INTFC_BI).
Billing to Project Costing Processing
When the Billing to Project Costing process (PC_BI_TO_PC) runs, the Analysis Type field in PROJ_RESOURCE is updated to billed (BLD):
| Analysis Type | Amount | Transaction Identifier | Resource Type | Category | Amount in Excess |
|---|---|---|---|---|---|
|
BLD |
5000 |
NA |
MATER |
ADMIN |
NA |
|
BLD |
2000 |
NA |
LABOR |
PROG |
NA |
|
BLD |
–1000 |
DEVLAB |
EXCES |
NA |
Y |
Note:
NA indicates that the field is not applicable.
Project Transaction
Add a transaction in PeopleSoft Project Costing:
| Analysis Type | Amount | Resource Type | Category |
|---|---|---|---|
|
ACT |
8000 |
MATER |
ADMIN |
Summary Limits Processing
These rows are created in PROJ_RESOURCE:
| Analysis Type | Amount | Transaction Identifier | Resource Type | Resource Category | Amount in Excess |
|---|---|---|---|---|---|
|
BLD |
5000 |
NA |
MATER |
ADMIN |
NA |
|
BLD |
2000 |
NA |
LABOR |
PROG |
NA |
|
BLD |
–1000 |
DEVLAB |
EXCES |
NA |
Y |
|
BIL |
8000 |
NA |
MATER |
ADMIN |
NA |
|
BIL |
–4000 |
NA |
EXCES |
NA |
Y |
Note:
NA indicates that the field is not applicable.
The BIL row of –4000 does not have a transaction ID because the resource type and resource category do not fall under the transaction ID that is associated with the contract line; therefore, it does not qualify for a transaction level limit. However, the row does qualify for a line level limit. The net calculation at the line level is current ITD processed = 5000 + 2000 – 1000 + 8000 = 14000. The limit available is 10000 – 14000 = –4000.
Funding Is Increased
If additional funding is received for the contact, then the contract is amended and the transaction limit is increased. For this example, the transaction limit is increased from 1000 to 2000 for transaction ID DEVLAB.
Project Transaction
Add a transaction in PeopleSoft Project Costing:
| Analysis Type | Amount | Resource Type | Category |
|---|---|---|---|
|
ACT |
2000 |
MATER |
ADMIN |
Summary Limits Processing
These rows are created in PROJ_RESOURCE:
| Analysis Type | Amount | Transaction Identifier | Resource Type | Resource Category | Amount in Excess | Reclaimed Amount in Excess |
|---|---|---|---|---|---|---|
|
BLD |
5000 |
NA |
MATER |
ADMIN |
NA |
NA |
|
BLD |
2000 |
NA |
LABOR |
PROG |
NA |
NA |
|
BLD |
–1000 |
DEVLAB |
EXCES |
NA |
Y |
NA |
|
BIL |
8000 |
NA |
MATER |
ADMIN |
NA |
NA |
|
BIL |
–4000 |
NA |
EXCES |
NA |
Y |
NA |
|
BIL |
2000 |
NA |
MATER |
ADMIN |
NA |
NA |
|
BIL |
1000 |
DEVLAB |
RECLM |
NA |
NA |
Y |
|
BIL |
–1000 |
NA |
NA |
NA |
Y |
NA |
|
BIL |
–2000 |
DEVLAB |
EXCES |
NA |
Y |
NA |
Note:
NA indicates that the field is not applicable.
The amount is reclaimed at the transaction level, but exceeded the line level limit, which results in the –1000 amount in excess that is reported as a line level amount in excess.
Note:
In addition, when you select this option, the system does not allow limits to overlap. For example, if two transaction IDs exist, then neither transaction ID can have common resource type, resource category, and resource subcategory with a wildcard option of %.