Overhead Codes Are Non-Project Timesheet Time

What a planner means

An overhead code lets a Team Member timesheet user log hours that are not on a project activity. Oracle examples: vacation, holiday, sick time, general administrative work. The API: hours “not associated with any current projects.” Internally the same object is a nonworktype.

This is not a calendar exception, not a cost account, not an activity, and not an assignment code. The hours live on the timesheet (ResourceHour), not on TASK or TASKRSRC, until something posts them. See Timesheets Are Approved Hours; Apply Actuals Posts Them.

Create: unique Name (the code) and unique Description. Enterprise-data Excel import matches on Name.

Two-level timesheet approval: a sheet that is only overhead bypasses the project manager and goes to the resource/cost manager. On a mixed sheet the project manager can view overhead rows but cannot approve them.

XER

Oracle’s project XER data map has no OVERHEAD / NONWORK table. Do not invent one. Overhead codes are enterprise data (API exportOverheadCodes, Excel “Codes: Overhead Codes”).

API fields (not XER column names): Name, Description, SequenceNumber, ObjectId. Do not write those as %T OVERHEAD columns.

Microsoft Project

Desktop Project has no overhead-code dictionary. Calendar exceptions and Project Server administrative time are different objects. Do not map overhead codes to a calendar non-work day or to Actual Work.

Don't

• Treat overhead hours as activity actuals or as TASKRSRC units.
• Treat an overhead code as a calendar exception, cost account, or assignment code.
• Invent an OVERHEAD table in a project XER parse.
• Assume a project manager can approve overhead-only timesheets under two-level approval.