Understanding Revenue Performance Obligation Setup

A revenue performance obligation (RPO) is identified as a set of accounts that is associated with a job. You use an RPO to track specific costs and revenue for an obligation within a job.

An RPO has both master and detail information. Use the Revenue Performance Obligation Master program (P5102) to create a Revenue Performance Obligation (RPO) master record in the Revenue Performance Obligation Master table (F5102), similar to a job in Job Master Revision program (P51006).

After you set up the RPO master information, you add accounts to the RPO. The system stores these account details information in the Revenue Performance Obligation Detail table (F5103.) The system validates that any account (cost code and cost type combination) entered is not associated with another RPO. If you delete an RPO master record from the F5102 table, the system deletes the corresponding RPO detail records from the F5103 table.

You can copy the master information from an existing RPO to create a new RPO with unique detail information.

When working in the Job Cost Master Revisions program (P51006), you can quickly search for RPOs that are related to a specific job. Select a job and select RPO Master from the Row menu. The system displays the Work With Revenue Performance Obligation Master form with the selected job number populated in the QBE line of the grid.

To review how the system uses RPO AAI setup and the RPO record to select accounts, review the following example:

Example: Revenue Performance Obligation and RPO AAI Setup: Review Resulting Accounts