Project, Task, Expenditure, Organization
The DEAMS PTEO associates costs and transactions with projects and tasks, allowing the Air Force to group revenue and cost by organization, activities, and business area.
What is PTEO?
The DEAMS Project, Task, Expenditure, Organization (PTEO) structure is how DEAMS generates Standard Financial Information System (SFIS)-compliant Lines of Accounting (LOA). The PTEO is a project centric financial data structure that
associates costs and transactions with a project and task. The PTEO uses a set of codes to relate legacy data elements to
Accounting Flex Fields (AFF) in DEAMS. The AFF combines individual segments of code to create key data constructs that classify virtually all DEAMS transactions.
PTEO to SFIS LOA Conversion
When a user goes into the iProcurement module in DEAMS and selects the project, task, expenditure, and organization for their financial transaction, DEAMS converts the information into an SFIS structure that is stored in Oracle database tables behind the scenes, and then returns the SFIS LOA (or charge account). The PTEO provides the foundation for General Ledger (GL) accounting, reporting, and funds control in DEAMS.
The first item a user must identify in DEAMS to begin building the LOA for a requisition is the Project. The PTEO relates legacy data elements to the DEAMS AFF so you can expect to see legacy values in the project string. There are three types of Projects available in DEAMS:
Contract – For reimbursable projects used by Orders-to-Cash (O2C)
Indirect – For purchase requisitions, purchase orders, or invoices used by Procure-to-Pay (P2P)
Capital – For Property, Plant and Equipment (PP&E) and the least common type of project
After the user selects the project in DEAMS, they identify the appropriate Task. A Task is associated with a specific project and therefore provides greater detail about what is being purchased. Since each Task is associated with a specific project, once the project is selected, DEAMS automatically focuses the Task options to only those associated with the selected Project. The Task number relates to the DEAMS Budget Line Item Number (BLIN) and other elements depending on the appropriation [i.e. Sales Code, Performing Fund Code, Buyers Side Code, Cost Systems Indicator/Cost Descriptor (CSI/CD)]. For example, if it is a reimbursable project, then the Task number will display the Sales Code.
Expenditure Type is the SFIS Object Class/Object Sub-Class, which corresponds to a legacy Element of Expense/Investment Code (EEIC) value. The Expenditure describes the “what” in the LOA. For example, Object Class/Sub-Class 260.3312 represents the Government Purchase Card (GPC) and corresponds to EEIC 61950. Since SFIS is new, DEAMS allows users to search on a legacy EEIC value to return its associated Object Class/Object Sub-Class. DEAMS includes the legacy EEIC value at the beginning of the Object Class/Sub-Class description field. This allows users to search the description field for the EEIC value, which then returns its associated Object Class/Sub-Class.
The Organization is the Operating Entity (OE) from the Project, combined with the six-digit Cost Center (CC). The Organization describes the “who” in the LOA.
Requesting a New PTEO
There may be times when PTEO elements do not exist in DEAMS. The PTEO Request Form is located on the DEAMS Outreach Portal in Active DEAMS Users > DEAMS Forms > PTEO Request Form. Complete the form per the Instructions Tab in the form and submit to DFAS. Before requesting a new PTEO, it is important to validate the PTEO elements do not already exist in DEAMS; likewise, it is important to validate the PTEO after it is created in DEAMS and notify DFAS if there are errors.