Skip to main content

Oracle Projects Data Model


This topic covers the Oracle Projects Data model.
Projects are created from the Projects Templates / other Projects .

Base Table:  PA_IMPLEMENTATIONS_ALL
This table contains a row for each projects implementation, i.e one per operating unit. This table contains the setup information specific to the operating unit. 
The table data corresponds to the front end: Projects implementation super user resp -> Setup->System->Implementation options.
Base Table:  PA_PROJECTS_ALL
Important Columns:
Project ID: uniquely identifies a project
Name: Name of the Project
Segment1: Project Number
This project number can be automatic/ Manual depending upon the System Implementation Option Setups, i.e., if the setting is automatic, there is no need of giving a project number when creating a project. If it is manual, then a project number should be provided while creating the project.
Carrying_out_organization_id : This is the project owning organization.
Pm_product_code: This identifies the source of the project, generally used whenever a project is created from a third party product.
Project_Status_code: Indicates the project status whether active, approved, closed, rejected etc.
Start_Date :  Transaction start date of the Project.
Completion_Date: Transaction End Date of the project.
(There are different dates for a project each having its own significance, we will see those in a different topic.)
 Tasks:
Base Table:  PA_TASKS
Important Columns:
Task_id :  uniquely identifies a task.
Project_id : – From the pa_projects_all table .
Carrying_out_organization_id : This is the task owning organization.
(Task owning organization can be different from Project owning organization).
Start_date : Transaction Start Date of the Task
Completion_Date:  Transaction End Date of the Task
 Wbs_level :Indicates the level of the Task in the WBS hierarchy.
(WBS – Work Break down Structure indicates the structure of the Project)
Parent_Task_id :  uniquely identifies the Parent Task
Top_Task_id  : uniquely identifies the  Top Task.
Pm_product_code : Indicates the source of the task(used in conversion projects).
Pm_task_reference: uniquely identifies the corresponding task in the source system (used in conversion projects).
Base Table:  PA_AGREEMENTS_ALL
This is the table which stores the Agreement information.
Agreement_id : uniquely identifies the agreement.
Customer_id : Agreement’s customer id.
Agreement_num : Agreement Number
Expiration_Date : Expiration Date of the Agreement
Revenue_Limit_Flag: Flag which indicates whether the revenue can exceed the allocated funding amount.
Invoice_Limit_Flag: Flag which indicates whether invoice can exceed the allocated funding amount.
Amount: Agreement Amount.
Base Table: PA_PROJECT_FUNDINGS
Project_Funding_id :  uniquely identifies the Funding
Project_id : id of Project to which the funding is allocated
Task_id : id of Top Task to which the funding is allocated
Budget_type_code : Status of the budget whether baselined or not.
Allocated_amount: the amount of funding allocated to the project or top task.
To be continued…

Comments

Popular posts from this blog

Oracle Subledger Accounting (SLA) Tables, Views

Oracle Subledger Accounting (SLA) Tables, Views Oracle Subledger Accounting Tables: TABLE NAME DESCRIPTION XLA_AAD_GROUPS The XLA_AAD_GROUPS table stores the merge dependencies analyzed during the merge analysis.  All application accounting definitions with the same GROUP_NUM must be merged together. XLA_AAD_HDR_ACCT_ATTRS The XLA_AAD_HDR_ACCT_ATTRS stores standard, system and custom sources assigned to an accounting attribute at the AAD level. XLA_AAD_HEADER_AC_ASSGNS Store the analytical criteria for the application accounting definitions. XLA_AAD_LINE_DEFN_ASSGNS This table stores the journal lines definitions for the application accounting definitions. XLA_AAD_LOADER_DEFNS_T The XLA_AAD_LOADER_DEFNS_T table is the interface table that facilitates the data transfer from data files and the database. XLA_AAD_LOADER_LOGS The XLA_AAD_LOADER_LOGS table stores the errors and logs generated by the application accounting definitions loader. XLA_AAD_SOURCES XLA_AAD_SOURCES table stores a...

Oracle Fusion Cloud: Supplier Import Process using File Based Data Import (FBDI)

 Supplier Data Migration or Upload to Oracle Fusion environment File-Based Data Import for Oracle Procurement Cloud Supplier import in oracle fusion   In this post , We will discuss about Supplier import in oracle fusion. Oracle has provided the FBDI tool to import suppliers from External  Source  to the Oracle fusion. Supplier Import in Oracle fusion we first need to  Download  the Supplier Import FDBI  templates  given by the Oracle fusion to import suppliers. Oracle has given 5 Different FBDI templates to Import supplier in Fusion. Here in this post , I will share the Complete steps for Supplier import in oracle fusion. You can refer this post for Supplier Import.   Steps for Supplier import in oracle fusion     Step1- First we need to download Supplier Data  Template  from Oracle Repository. Go to this path for Oracle Repository. ( select Based on your Cloud version) https://docs.oracle.com/en/...

Unbilled Receivables and Unearned Revenue Accounting in Oracle Projects

Unbilled Receivables and Unearned Revenue Accounting in Oracle Projects Introduction When it comes to contractual billing, invoice and revenue generation are two separate processes, which during the lifespan of a project may or may not always coincide with each other and so do the balances in revenue and receivables accounts.  This interim difference between revenue and invoice account balances is bridged using Unbilled Receivables (UBR) and Unearned Revenue (UER) Accounts. Unearned Revenue (UER) Unearned Revenue (also termed as deferred revenue or UER) signifies money received for the goods or services, which are yet to be delivered.  As per the principles of Revenue Recognition, UER is recorded as on the balance sheet unless it is converted to Revenue upon delivery of goods or services For Example XYZ Consulting Ltd. receives an annual maintenance contract of $ 12,000 on Dec 31, 2014 for the period of Jan 01, 2015 to Dec 31, 2015. At the start of the contract as of Dec 31, 2...