Glossary

Business Unit

A business unit is part of the basic account structure in the JD Edwards EnterpriseOne General Accounting system and denotes where transactions affect the organization, such as a warehouse, cost center, store, or job. For the purposes of this integration, business units, along with an extended job master record, are the equivalent of a Primavera Contract Management project. They are the lowest reporting level within your organization at which you need to account for assets, liabilities, equity, revenue, and expenses.

Budget Contract

A budget contract in Contract Management is the equivalent of the project budget in EnterpriseOne. Only one project budget can be sent from EnterpriseOne to Contract Management for this integration. However, the Contract Management system does allow for multiple budget contracts per project.

Change Order

Change orders are used in the Primavera Contract Management system to specify a redirection of plans or introduce new items to the schedule. Change orders also show any approved increases or decreases in costs and contract item allowances.

A change order in Primavera Contract Management is the equivalent of a change request in EnterpriseOne.

Change Request

Change requests are used in the JD Edwards EnterpriseOne system to track changes to a job as it progresses. You can enter a single line item or multiple line items for each change request. Typically, you set up a change request that relates to a specific aspect of the job. For example, if the job is to construct an office building, change request 1 might be for tracking foundation details, change request 2 for framing details, and so on.

A change request in EnterpriseOne is the equivalent of a change order in Primavera Contract Management.

Committed Contract

A committed contract is created in the Primavera Contract Management system, and is a written agreement in which one party agrees to perform specialized work for another party for a certain price. Contract work can involve labor only or labor and materials; examples include excavation, plumbing, and landscaping. A contract usually includes a description of the work to be performed, a list of special terms and conditions that apply to the contract, the start and finish dates, and the negotiated price.

A committed contract in Primavera Contract Management is the equivalent of a JD Edwards EnterpriseOne purchase order.

Cost Codes

Cost codes are used in the Primavera Contract Management system to break down costs in the Cost Worksheet. Cost codes are similar to categories in a checkbook. For example, if your mortgage payment is $1,000 a month, $400 may apply to principal and $600 to interest. When you record the $1,000 payment in your check register, you may distribute it to principal and interest categories for tax reporting purposes. Similarly, you may have a lump sum contract for $50,000, of which $25,000 is for rough carpentry and $25,000 is for finish carpentry. To track each carpentry cost separately in the Cost Worksheet, create two codes, Rough and Finish, and distribute $25,000 to each.

You must create cost codes before you can distribute costs to the Cost Worksheet. Consider building meaning into the cost codes. For example, some companies base their cost codes on standard CSI codes.

Cost codes in Primavera Contract Management are the equivalent of the account structure for a project in EnterpriseOne.

In EnterpriseOne, cost codes are used in project costing. The business unit, cost code, and cost type make up the WBS for a project. EnterpriseOne users typically use cost codes to define major groupings in a project, such as excavation, framing, or landscaping.

Progress Payments

In EnterpriseOne, progress payments are payments made to the subcontractors as they make progress against their contracts. You draw progress payments from the funds that are committed to their contracts.

In addition, you make progress payments to relieve some or all of the contract commitment, as well as any released retainage against a contract. Retainage is a percentage of the committed amount that is held until a specified date after the completion of the contract.

A progress payment in EnterpriseOne is the action of creating a voucher to initiate payment to a vendor in response to a requisition for payment from the Primavera Contract Management system.

Project

In EnterpriseOne, a project is defined by the existence of a Business Unit (F0006) and an Extended Job Master (F5108) record. A project has a group of related tasks, accounts, or cost codes, and in some cases, has a related budget.

Project Budget

A project budget in EnterpriseOne is the equivalent of a budget contract in Contract Management. For the purposes of this integration, only the original budget is sent to Contract Management. Furthermore, only one original budget can be sent from EnterpriseOne to Contract Management. If the budget changes after it has been sent to Contract Management, all changes must be done using the change order process.

Purchase Order

A purchase order is a document that details the information about goods or services that you are purchasing from a vendor.

A purchase order in JD Edwards EnterpriseOne is the equivalent of a committed contract in the Primavera system.

Requisition

Requisitions are formal requests for payment that are created in the Primavera Contract Management system, and are usually issued by general contractors (GCs) to the owner on a monthly basis as portions of work on a project are completed.

Requisitions in Primavera Contract Management are sent to EnterpriseOne to initiate the creation of progress payments.

Retainage

A portion of the total amount of a purchase order or committed contract that is held until a specified date, deliverable, or until after the completion of a project. Retainage can be a percentage of the total or flat dollar amount.

WBS (Work Breakdown Structure)

The set of tasks that make up the project in EnterpriseOne is referred to as the work breakdown structure (WBS). After setting up a project header record with information such as project description, branch/plant, planned start and end dates, and so on, you can add to the project individual tasks that represent the steps that are required to complete the project. You can add tasks to the work breakdown structure, provided that it is not yet locked.