Name
|
Internal
Name
|
Description
|
PRC: Interface Assets to Oracle Assets
|
PAXCPCAL
|
The Interface Assets process sends valid asset
lines to Oracle Assets to become fixed assets. The process creates one mass
addition line in Oracle Assets for each asset line in Oracle Projects,
assigning the asset information you entered for the CIP asset to the mass
addition line in Oracle Assets. Interface the costs to General Ledger before
you run the Interface Assets process.
|
PRC: Interface Cross Charge Distributions to
General Ledger
|
PACCGLTR
|
The process identifies the cross charged
transactions that fit the parameters you specify and then interfaces the
cross charged distributions to General Ledger
|
PRC: Interface Expense Reports from Payables
|
PAAPIMP
|
This process gets expense report information from
Payables. This process creates pre- approved expense report batches from
expense report information entered in Self-Service Expenses or in the
invoices window (in payables).
|
PRC: Interface Expense Reports to Payables
|
PATTER
|
The Interface Expense Reports to Payables process
collects all eligible expense reports, including adjustments, in Oracle
Projects and interfaces them to the Oracle Payables interface tables.
|
PRC: Interface Intercompany Invoices to
Receivables
|
PATTAR-IC
|
This process collects all eligible intercompany
invoices in Oracle Projects and interfaces them to the Oracle Receivables
interface tables.
|
PRC: Interface Invoices to Receivables
|
PATTAR
|
This process collects all eligible draft invoices
in Oracle Projects and interfaces them to the Oracle Receivables interface
tables. The process also maintains the project balances of unbilled
receivable and unearned revenue and creates accounting transactions for these
amounts.
|
PRC: Interface Labor Costs to General Ledger
|
PAGGLT
|
This process collects all eligible labor costs in
Oracle Projects and interfaces them to the Oracle General Ledger interface
tables. The interface process also determines the liability account for the
labor costs.
|
PRC: Interface Revenue to General Ledger
|
PATTGL
|
This process collects all eligible revenue in
Oracle Projects and interfaces it to the Oracle General Ledger interface
tables. This process also maintains project balances for unbilled receivables
and unearned revenue and creates accounting transactions for these amounts.
|
PRC: Interface Supplier Costs
|
PAAPIMP_SI
|
The PRC: Interface Supplier Invoices from
Payables process retrieves the following items and interface them to Oracle
Projects: All eligible posted, project related supplier invoices from Oracle
Payables, Tax lines for project related intercompany invoices. The process
first populates the Transaction Import Interface table, creating a cost
distributed expenditure item and cost distribution line for each invoice
distribution line, and expenditure for each invoice.
|
PRC: Interface Supplier Invoice Adjustment Costs
to Payables
|
PAVTVC
|
This process collects all eligible supplier
invoice adjustment costs in Oracle Projects and interfaces them to Oracle
Payables. The process determines the liability account for the supplier
invoice costs.
|
PRC: Interface Total Burdened Cost to GL
|
PACTFTBC
|
This process collects all eligible total burdened
distribution lines in Oracle Projects and interfaces them to Oracle General
Ledger.
|
PRC: Interface Usage and Miscellaneous Costs to
General Ledger
|
PASGLT
|
This process collects all eligible cost
distribution lines of the following transactions in Oracle Projects and
interfaces them to the Oracle General Ledger interface tables: usage costs,
miscellaneous transaction costs, burden transaction costs, and Inventory and
WIP transactions not already costed or accounted. The interface process also
determines the liability account for these costs.
|
PRC: Transaction Import
|
PAXTRTRX
|
Transaction Import is an open interface that
enables you to load transactions from external cost collection systems into
Oracle Projects. Transaction Import creates pre-approved expenditure items
from transaction data entered in external cost collection systems.
|
This blog is to share the Oracle Knowledge, I have acquired through various sources. Thanks to Many. Share the Knowledge.
Oracle Project Interfaces
Oracle Project Tables
Table Name
|
Description
|
PA_PROJECTS_ALL
|
Information
about projects
|
PA_AGREEMENTS_ALL
|
Customer
contracts that serve as the basis for work authorization
|
PA_BILL_RATES_ALL
|
Information
about bill rates and markups of standard bill rate schedules
|
PA_BILLING_ASSIGNMENTS_ALL
|
Assignments
of billing extensions to a project type, project, or task
|
PA_COST_DISTRIBUTION_LINES_ALL
|
Information
about expenditure item cost distribution
|
PA_CUST_REV_DIST_LINES_ALL
|
Information
about expenditure item revenue distribution
|
PA_DRAFT_INVOICE_DETAILS_ALL
|
Intercompany
invoice details for cross charged transactions
|
PA_DRAFT_INVOICES_ALL
|
Information
about draft invoices generated for projects
|
PA_DRAFT_REVENUES_ALL
|
Information
about draft revenue generated for projects
|
PA_EXPENDITURE_COST_RATES_ALL
|
Cost
rates for non-labor expenditure types
|
PA_EXPENDITURE_GROUPS_ALL
|
Groups
of pre-approved expenditures
|
PA_EXPENDITURE_ITEMS_ALL
|
The
smallest units of expenditure charged to projects and tasks
|
PA_EXPENDITURES_ALL
|
Groups
of expenditure items incurred by employees or organizations for an
expenditure period
|
PA_PERIODS_ALL
|
Implementation-defined
periods against which project performance is measured
|
PA_PROJECT_ASSET_LINES_ALL
|
Summarized
project CIP costs
|
PA_PROJECT_ASSETS_ALL
|
Assets
defined for capital projects
|
PA_EXPENDITURE_TYPES
|
Implementation-defined
classifications of expenditures charged to projects and tasks
|
PA_EXPENDITURE_CATEGORIES
|
Implementation-defined
groupings of expenditure types by type of cost
|
PA_CLASS_CATEGORIES
|
Implementation-defined
categories for classifying projects
|
PA_CLASS_CODES
|
Implementation-defined
values within class categories that can be used to classify projects
|
PA_PROJECT_CLASSES
|
Class
codes of class categories that are used to classify projects
|
PA_BUDGET_VERSIONS
|
Versions
of project budgets
|
PA_BUDGET_LINES
|
Detail
lines
|
Change of Person Types
To change Person Type of the existing employee.
Navigation : People > Enter and Maintain > Others > Person Type Usage
Select the required person type to be changed.
Note: The person type change is limited to any of the user person types corresponding to the system person type effective on the date of change.
User Person Types are defined, as part of setup activity : Other Definitions > Person Types
Navigation : People > Enter and Maintain > Others > Person Type Usage
Select the required person type to be changed.
Note: The person type change is limited to any of the user person types corresponding to the system person type effective on the date of change.
User Person Types are defined, as part of setup activity : Other Definitions > Person Types
How to change Hire Date for the Employee
Many times, user may end up hiring an employee without considering the date to set before creation of record. This may lead to Incorrect hire date for the resource.
To correct the same, please follow the below
Navigate to People - Enter and Maintain - Query the employee.
Change the date in the field "Latest Start Date", which is available on the Person with the correct Hire Date for the employee.
This action is applicable only, if the payroll is not run.
To correct the same, please follow the below
Navigate to People - Enter and Maintain - Query the employee.
Change the date in the field "Latest Start Date", which is available on the Person with the correct Hire Date for the employee.
This action is applicable only, if the payroll is not run.
Error message "There are no new periods in GL to copy" when hitting the 'Copy from GL' button in Projects
Error - There are no new periods in GL to copy
No periods are copied from GL calendar and you cannot open next project accounting (PA) period. However, next month is defined in the GL calendar.
1. Open the calendar periods form (Navigate : Setup/ Financials / Calendar / Accounting)
2. Query up the defined GL calendar
3. Add new periods to the calendar
4. Open the PA periods form (Navigate : Setup / System / PA Periods)
5. Click the 'Copy from GL' button again
The new periods would be populated.
Please Set The Receivables System Options for This Operating Unit
When generating draft invoices (PRC: Generate Draft Invoices) the following error is occurring: Please Set The Receivables System Options for This Operating Unit
Set the Item Validation Organization in the Order Management System options:
Switch to your Order Management Responsibility.
Navigate to Setup -> System Parameters -> Values.
Select the appropriate operating unit
Select the category “Generic Parameters”
Enter the value for the “Item Validation Organization” parameter.
Set the Item Validation Organization in the Order Management System options:
Switch to your Order Management Responsibility.
Navigate to Setup -> System Parameters -> Values.
Select the appropriate operating unit
Select the category “Generic Parameters”
Enter the value for the “Item Validation Organization” parameter.
Cannot get remit to address
If you use AutoInvoice but have not defined a remit-to address that can be derived for a specific bill-to address, AutoInvoice will reject all invoices for which it could not determine a remit-to address with the following message in the AutoInvoice Import Execution report:
Errors: 1) Cannot get remit to address
Steps:
i. Identify The Customer Bill-To Address
For AutoInvoice this can be found
Responsibility: Receivables Manager
Navigation: Control > AutoInvoice > Interface Lines
Check your Remit-To Address Setup
Responsibility: Receivables Manager
Navigation: Setup > Print > Remit To Address
Create the remit-to-address and receipts form. In receipts set default for country and state
Errors: 1) Cannot get remit to address
Steps:
i. Identify The Customer Bill-To Address
For AutoInvoice this can be found
Responsibility: Receivables Manager
Navigation: Control > AutoInvoice > Interface Lines
Check your Remit-To Address Setup
Responsibility: Receivables Manager
Navigation: Setup > Print > Remit To Address
Create the remit-to-address and receipts form. In receipts set default for country and state
Not all AutoAccounting types are defined in Receivables
Error in Autoinvoice – Not all AutoAccounting types are defined in receivables.
Check that the following Autoaccounting rules are defined in AR,
Setup > Transaction > Autoaccounting
Check that the following Autoaccounting rules are defined in AR,
Setup > Transaction > Autoaccounting
- Frieght
- Receivable
- Revenue
- AutoInvoice Clearing
- Tax
- Unbilled Receivable
- Unearned Revenue
The Expenditure Organization is not active in OTL
Error in OTL while entering timecard entry, “The Expenditure Organization is not active ”
Check the Employee → Assignment → Organization
Check the Organization classification in Work Structures
Enable Project Expenditure Organization for the specific Organization
Include the Organization in Project Hierarchy
Save the changes.
Check the Employee → Assignment → Organization
Check the Organization classification in Work Structures
Enable Project Expenditure Organization for the specific Organization
Include the Organization in Project Hierarchy
Save the changes.
This parameter is not valid for this function to which this rule is assigned – Autoaccounting PROJECTS
Not all parameters are available for all autoaccounting functions. If a rule is using an invalid parameter for the function, the rule will not be included in the LOV.
Run the IMP: AutoAccounting Functions report. The IMP: AutoAccounting Functions report (PAXAAFTP) provides a complete list of the parameters and transactions associated with a particular AA function. All possible parameters used by the AutoAccounting(AA) rules to derive key flexfield segment values are listed. The transactions associated with the AA function are also displayed, as well as an indication of whether each transaction is enabled or not.
Run the IMP: AutoAccounting Functions report. The IMP: AutoAccounting Functions report (PAXAAFTP) provides a complete list of the parameters and transactions associated with a particular AA function. All possible parameters used by the AutoAccounting(AA) rules to derive key flexfield segment values are listed. The transactions associated with the AA function are also displayed, as well as an indication of whether each transaction is enabled or not.
To increase the time period of timecards – OTL
To increase the time period of timecards – OTL
Navigate to OTL Application developer
Preferences → Default Preferences Projects → Self Service → Worker → Timecard Status
Allowing Edits
Preference Value – Retro ; Past Number of Days – 365
Save.
Navigate to OTL Application developer
Preferences → Default Preferences Projects → Self Service → Worker → Timecard Status
Allowing Edits
Preference Value – Retro ; Past Number of Days – 365
Save.
Disable diagnostics/examine/personalization Password
To disable prompting the apps password for diagnostics and examine/personalization at form level
Set the value as Yes to the profile option “Utilities: Diagnostics” at any level.
Utilities: Diagnostics = YES
Set the value as Yes to the profile option “Utilities: Diagnostics” at any level.
Utilities: Diagnostics = YES
Approved Otl Timecards Are Not Retrieved Into Projects
Please check the following, if the Approved timecards are not being transferred to Projects.
1. Profile : OTL: Number of past days, for which retrieval considers changes (days) – It is recommended that you set the days to double the frequency that you run the retrieval process. So if you run the retrieval weekly, then set to say 15 days. If you run it daily, then, to be safe, set to 5 days.
2. OTL: Transfer Batch Size – It is recommended that this is set to 10. Please note that this is the number of timecards that are transferred to the retrieval applications, at one time. This will be performed many times within one retrieval process, until all timecards have been transferred. It does not mean that it will only transfer 10 timecards. This has been described as a chunk, so each chunk will contain 10 timecards, and there will be many chunks in one retrieval process, until all valid timecards have been transferred.
1. Profile : OTL: Number of past days, for which retrieval considers changes (days) – It is recommended that you set the days to double the frequency that you run the retrieval process. So if you run the retrieval weekly, then set to say 15 days. If you run it daily, then, to be safe, set to 5 days.
2. OTL: Transfer Batch Size – It is recommended that this is set to 10. Please note that this is the number of timecards that are transferred to the retrieval applications, at one time. This will be performed many times within one retrieval process, until all timecards have been transferred. It does not mean that it will only transfer 10 timecards. This has been described as a chunk, so each chunk will contain 10 timecards, and there will be many chunks in one retrieval process, until all valid timecards have been transferred.
Subscribe to:
Posts (Atom)