This appendix describes profile options that affect the operation of your Oracle Projects application.
This appendix covers the following topics:
During implementation, users specify a value for each Oracle Projects user profile option to control access to Oracle Projects data and to determine how data is processed.
Each profile option is assigned to one or more of the profile option categories. Users can view only the profile options that pertain to their application or function.
This appendix describes the following profile option categories:
A required profile option requires a value. An optional profile option provides a default value, so you need to provide a value only if you want to change the value. In the List of Profile Options table, the following abbreviations are used in the Required or Optional column to show which products require each profile option.
PJF: Oracle Project Foundation
PJC: Oracle Project Costing
PJB:: Oracle Project Billing
PJP:: Oracle Project Portfolio Analysis
PJR:: Oracle Project Resource Management
PJT:: Oracle Project Management
PJL: Oracle Project Collaboration
The following table lists the profile options that are used in Oracle Projects.
See: Setting User Profile Options, Oracle Applications System Administrator's Guide - Maintenance.
*Either the MO: Operating Unit profile option or the MO: Security Profile profile option is required. If the latter is defined, then the former will be ignored.
You use profile options to specify default values that affect system processes, system controls, and data entry. Your System Administrator needs to set up Oracle Projects profile options in the System Profile Values Window.
We recommend that you set up the Oracle Projects application level profile options that affect system processing.
You may want to review the default values for all Oracle Projects profile options and modify them according to your site's needs. This appendix contains detailed information about each profile option in Oracle Projects.
In a multi-organization environment, you can confine a profile option value to a specific operating unit by defining the profile options at the responsibility level. You should review the following Oracle Projects system profile options to determine if you want to define responsibility-level profile option values:
PA: Cross-Project User - Update
PA: Cross-Project User - View
PA: Debug Mode
PA: Default Expenditure Organization in AP/PO
PA: Default Public Sector
You can also set the profile option MO: Operating Unit to specify which operating unit a particular responsibility corresponds to. With the Multiple Organization Access Control feature, a responsibility can have access to data from two or more operating units by defining a security profile with multiple operating units and assigning it to the MO: Security Profile profile option. You can set the MO: Default Operating Unit profile option to designate one of the operating units of the MO: Security Profile profile option as the default operating unit to ease transaction entry. For more details about implementing multiple organization support, see: Multiple Organizations in Oracle Applications.
Related Topics
Updating Profile Options for Integration With Other Products
Personal Profile Values Window, Oracle Applications User's Guide
Overview of Setting User Profiles, Oracle Applications System Administrator's Guide
Common User Profile Option, Oracle Applications User's Guide
This section describes the profile options by category.
The tables in this section provide profile option information as follows:
The Default column displays the default profile option value in italics or No Default if no default value is provided.
The User Access column indicates if users can view or update the profile option.
The System Administration: User, Responsibility, Application, and Site columns indicate at which levels the system administrator can update these profile options.
The key for these tables is:
Update: Users can update the profile option.
View Only: Users can view the profile option but cannot change it.
No Access: Users cannot view or change the profile option value.
Use the Personal Profile Options window to view or set your profile options at the user level. You can consult the Oracle Applications System Administrator's Guide for a list of profile options common to all Oracle Applications.
Profile options in the Accessibility Interaction category control user access to data. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Allow Future-Dated People as Project Members | Yes | View Only | View Only | View Only | View Only | Update |
| PA: Display Find Tasks | No | Update | Update | Update | Update | Update |
| PA: Process MS Excel Data | Standard | Update | Update | No Access | No Access | Update |
| PA: Process Structure Updates | Standard | Update | Update | No Access | No Access | Update |
| PA: Require Work Type Entry for Expenditures | No | No Access | View Only | View Only | View Only | Update |
| PA: Tab to Budget Matrix Comments Fields | No | Update | Update | Update | Update | Update |
Specifies whether users can include future-dated employees as key members.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Default value is Yes. Users can include future-dated employees as key members. |
| No | Users cannot include future-dated employees as key members. |
Internal name: PA_ALLOW_FDE_AS_PM
Indicates whether to display the Find Tasks window when a user chooses Tasks in the Projects, Templates window.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Tasks displays the Find Tasks window, and Oracle Projects automatically queries the top tasks (WBS Level = 1) |
| No | Tasks does not display the Find Tasks window |
| (No value) | Equivalent to No |
Internal name: PA_DISPLAY_FIND_TASKS
This profile option specifies whether Oracle Projects always performs the upload of financial plan lines from Microsoft Excel spreadsheets as an online step, or if uploads are performed online based on the row threshold setting specified by the profile option PA: Process MS Excel Data Threshold. The available values are:
| Variable | Description |
|---|---|
| Standard | Spreadsheet uploads are processed either online or as a concurrent program based on the row threshold value specified in the profile option PA: Process MS Excel Data Threshold. |
| Online | Spreadsheet uploads are always processed online. |
You can set this profile option at the site level and at the user level. The default value is Standard.
Internal name: PA_FP_WEBADI_DATA_PRC_MODE
When you make a change to a project structure by adding tasks, deleting tasks, or rearranging the task hierarchy, you invoke the Process Updates action to synchronize the update of plan and actual data against the latest structure as displayed in the View Budget or View Forecast pages.
This profile option specifies whether Oracle Projects always performs project structure updates online, or if it can process project structure updates using a concurrent program when the total number of tasks exceeds a limit set in the PA: Process Structure Updates Threshold profile option.
Note: When you invoke the Process Updates action for a program structure, the updates are always performed concurrently.
This profile option is required if you are using Oracle Project Management. The available values are:
| Variable | Description |
|---|---|
| Standard | Structure updates are processed online based on the task threshold value specified in the profile option PA: Process Structure Updates Threshold. If the total number of tasks in the structure is less than or equal to the task threshold setting specified by the profile option PA: Process Structure Updates Threshold, the system processes the tasks online. If the number of tasks exceeds that task threshold, the system processes the tasks concurrently with the PRC: Process Structure Updates process. |
| Online | Structure updates are always processed online. |
You can set this profile option at the site level, and, optionally, at the user level. The default value is Standard.
Internal name: PA_PROCESS_WBS_UPDATES
Determines whether work types are required for all expenditure items.
This profile option is optional. Available values for this profile option are:
| Variable | Description |
|---|---|
| Yes | Work types are required for all expenditure items |
| No | Work types are not required for all expenditure items |
The default value for this option is No. If you change the profile option to Yes, you must perform the following to update the work type attribute for existing transactions:
Enter an amount type for all existing work types.
Define a work type for all existing project types.
Run the UPG: Upgrade Transaction Attributes concurrent request program. Using the work types define for project types, this program updates the work type attribute on the following entities:
Projects
Tasks
Expenditure Items
Internal name: PA_EN_NEW_WORK_TYPE_PROCESS
Indicates how users navigate to the overflow (Change Reason / Comments / Descriptive Flexfield) region of the budget matrix window.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | User can tab to the overflow region. |
| No | User cannot tab to the overflow region. User may navigate to the overflow region by clicking on any of the fields there. |
| (No value) | Equivalent to No |
Internal name: PA_BUDGET_MATRIX_TAB_ALLOWED
Profile options in the Account Generation category enable you to override accounting FlexField values generated by Flexbuilder for project-related distributions in Oracle Payables and Oracle Purchasing. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Allow Override of Budget Accounts | No | View Only | View Only | View Only | View Only | Update |
| PA: Allow Override of PA Distributions in AP/PO | Yes | No Access | Update | Update | Update | Update |
| PA: Selective Flexfield Segment for AutoAccounting | No Default | No Access | No Access | No Access | Update | No Access |
Specifies whether users can manually override accounts generated by the Project Budget Account workflow process.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Users can manually override accounts. |
| No | Users cannot override accounts. |
Internal name: PA_OVERRIDE_BUDGET_ACCOUNT
Determines whether Oracle Purchasing and Oracle Payables pass user-entered account segment values to the Account Generator workflow. If you want to enable users to override generated accounts, then you must set this profile option to Yes and also set the Replace Existing Value attribute in the Account Generator workflow to False. The default value for the Replace Existing Value attribute is False.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | The user-entered values are passed to the workflow. The workflow may override these values if the Replace Existing Value attribute for the workflow is True. |
| No | The user-entered values are ignored and are not passed to the workflow. |
| (No value) | Equivalent to Yes |
Internal name: PA_ALLOW_FLEXBUILDER_OVERRIDES
Represents the segment number to be picked when building the flexfield select segment that queries the combination table. This is the most selective accounting flexfield segment to be used in AutoAccounting validation.
This profile option is required.
Set this profile option to the segment number to use. The segment number must start with 0.
For optimum performance, it is recommended that you set this value. The speed of the distribution processes can be dramatically affected by the setting of this profile option. You can achieve good results by choosing the most selective accounting flexfield segment to be used in AutoAccounting validation. This is the segment that has the least number of rows with the same value. If you change this profile setting, test it carefully before applying it.
Internal name: PA_SELECTIVE_FLEX_SEG
Profile options in the Batch Processing Size category enable you to specify the size of batches used in processing data. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Commit Size for Archive and Purge | 1000 | No Access | Update | Update | ||
| PA: Cost Distribution Lines Per Set | No Default | No Access | No Access | No Access | Update | No Access |
| PA: Expenditure Items Per Set | No Default | No Access | No Access | No Access | Update | No Access |
| PA: Expense Report Invoices Per Set | No Default | No Access | Update | Update | Update | Update |
| PA: Projects Per Set | No Default | No Access | No Access | No Access | Update | No Access |
Use the profile option PA: Commit Size for Archive and Purge to control the batch size for archive and purge processes.
Indicates the number of records the system processes before it issues a commit while purging a project.
The default value is 1000 records. The system administrator can view and update the profile option at the site level or user level.
This profile option is optional.
Internal name: PA_ARPUR_COMMIT_SIZE
See also: Commit Size in the Purge Project Data, Oracle Projects Fundamentals
Indicates the number of cost distribution lines to process in each set. This profile option affects the process PRC: Generate Cost Accounting Events.
A logical unit of work is performed on a set of cost distribution lines before the work is committed. For example, the PRC: Generate Cost Accounting Events process performs the following tasks on a set of cost distribution lines before committing the set to the database:
Processes the set through AutoAccounting
Generates cost accounting events
You can choose any numeric value to set this profile option, as long as it does not cause your system to exceed memory and database rollback segment sizes, and it is large enough to avoid unnecessary database accesses.
If you do not set this profile value, most of the processes use a default of 2000 cost distribution lines per set, but this value is operating system dependent.
This profile option is optional.
Internal name: PA_NUM_CDL_PER_SET
Indicates the number of expenditure items to process in each set. This profile option affects the following processes:
PRC: Distribute Labor Costs
PRC: Distribute Usage Costs
PRC: Distribute Expense Report Adjustments
PRC: Distribute Supplier Cost Adjustments
PRC: Distribute Total Burdened Costs
PRC: Generate Draft Revenue
PRC: Compute Forecast Labor Revenue
A logical unit of work is performed on a set of expenditure items before the work is committed. For example, the PRC: Distribute Labor Costs process performs the following tasks on a set of expenditure items before committing the set to the database:
Cost distributes the set
Processes the set through AutoAccounting
Creates cost distribution lines
You can choose any numeric value to set this profile option, as long as it does not cause your system to exceed memory and database rollback segment sizes, and it is large enough to avoid unnecessary database accesses.
If you do not set this profile value, most of the processes use a default value of 500 expenditure items, but this value is operating system dependent. This default value is defined in the header file of each distribution process.
This profile option is optional.
Internal name: PA_NUM_EXP_ITEMS_PER_SET
Indicates the number of expense report invoices (entered in Oracle Internet Expenses or Oracle Payables) for the process PRC: Interface Expense Reports from Payables to process in each set.
The set of expenditures is processed before the work is committed. For example, the PRC: Interface Expense Reports from Payables process does the following before committing the set to the database:
Selects the invoices and invoice distribution lines
Interfaces from Payables
Values: You can use any numeric value to set the profile option, as long as the value does not cause your system to exceed memory and database rollback segment sizes, and is large enough to avoid unnecessary database access. If you do not set a value, most processes use a default of 500, but the actual default value depends on the operating system.
This profile option is optional.
Internal name: PA_NUM_WEB_EXP_PER_SET
Indicates the number of projects to process in each call to AutoAccounting. This profile option affects the following processes:
PRC: Generate Revenue Accounting Events
PRC: Interface Invoices to Receivables
This profile option affects the amount of memory allocated for processing the specified number of projects through AutoAccounting. A single logical unit of work is performed independently of this profile variable.
You can choose any numeric value to set this profile option, so long as it does not cause your system to exceed memory and database rollback segment sizes, and it is large enough to avoid unnecessary database accesses.
If you do not set this profile value, most of the processes use a default of 100 projects, but this value is operating system dependent.
This profile option is optional.
Internal name: PA_NUM_PROJECTS_PER_SET
Profile options in this category enable you to specify the behavior of the costing processes. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Create Incremental Transactions for Cost Adjustments Resulting from a Burden Schedule Recompilation | No | No Access | No Access | No Access | No Access | Update |
| PA: Days to Maintain BC Packets | 3 | View Only | View Only | View Only | View Only | Update |
| PA: Enable Enhanced Period Processing | No | View Only | View Only | View Only | View Only | Update |
| PA: Retirement Cost Processing Enabled | No | No Access | View Only | View Only | View Only | Update |
| PA: Report Separate Burden Transactions with Source Resources | No Default | View Only | View Only | No Access | View Only | Update |
| PA: Transaction Billability Derived from Work Type | No | No Access | View Only | View Only | View Only | Update |
When you modify burden schedules and recompile burden multipliers, Oracle Projects identifies the existing transactions impacted by the changes and marks the items for reprocessing. You must reprocess the items by running the appropriate cost, revenue, and invoice processes.
When accounting for the adjusted cost, you can choose to reverse the original accounting entries and generate new ones for the adjusted cost, or you can choose to generate new accounting lines for the difference between the original and new burden cost amounts.
Use this profile option to select the accounting method that best fits your business needs.
This profile option is optional. Available values are listed below.
| Variable | Description |
|---|---|
| Yes | Oracle Projects creates incremental accounting lines to post the difference between the original and new burden cost amounts. |
| No | Oracle Projects reverses the original accounting lines and generates new lines to post the adjusted burden cost amounts. No is the default value. |
You can update this profile option at the site level only.
Internal name: PA_ENHANCED_BURDENING
Use this profile option to specify the number of days that the system maintains the results of transaction funds checks. The default value is 3.
This profile option is optional.
Internal name: PA_MAINTAIN_FC_PACKETS
For more information, see: Setting Up Budgetary Controls.
Indicates whether enhanced period processing is enabled.
This profile option is defined at the site level, and a value is required.
Available values are listed below.
| Variable | Description |
|---|---|
| Yes | Enhanced period processing features are enabled in Oracle Projects. |
| No | Enhanced period processing features are not enabled. |
Enhanced period processing is recommended.
Internal name: PA_EN_NEW_GLDATE_DERIVATION
Important: After you enable enhanced period processing, do not reset the profile option value to No. Enabling and disabling enhanced period processing features can result in accounting errors.
You can use the PA: Report Separate Burden Transactions with Source Resources profile option to have Oracle Projects assign summary burden transaction expenditure items to the same resource class as their source raw cost expenditure items. This option enables you to assign both burden costs and their source raw costs to the same resource class for reporting purposes.
For example, for timecards, if you set the profile option to Yes, then Oracle Projects assigns both the labor raw cost expenditure items and the related summarized burden transaction expenditure items to the People resource class. Alternatively, if you set this profile option to No, then Oracle Projects assigns the raw cost expenditure items to the People resource class and the related summarized burden transaction expenditure items to the Financial Elements resource class. These assignments takes place because labor raw cost expenditure items have an expenditure type class of Straight Time and burden transaction expenditure items have an expenditure type class of Burden Transaction.
This profile option only affects transactions charged to projects where the Burden Cost as Separate Expenditure Item option is enabled for the project type.
Note: If you set this profile option to Yes, then you must modify the Burden Resource Extension to specify the attributes that Oracle Projects uses when it groups summary burden transactions. For more information, use the Integration SOA Gateway responsibility to access the Oracle Integration Repository online and navigate to the Projects Suite to find the Burden Resource Extension.
| Variable | Description |
|---|---|
| Yes | Oracle Projects maps summary burden transactions to the same resource class as their source raw cost transactions. |
| No | Oracle Project maps summary burden transactions to the Financial Elements resource class. |
| (No value) | Equivalent to No. |
Internal Name: PA_RPT_BTC_SRC_RESRC
This site-level profile option determines whether retirement cost processing windows and features are enabled in Oracle Projects.
This profile option is optional. The available values are listed below:
| Variable | Description |
|---|---|
| Yes | You can access retirement cost processing windows and features. |
| No | You cannot access retirement cost processing windows and features. This is the default value for this profile option. |
If you enable retirement cost processing and you also use Oracle Assets group asset processing features, you can access all retirement cost processing features in Oracle Projects. However, if you do not use Oracle Assets group asset processing features, you can only use the retirement requests processing feature.
Internal name: PA_RET_COST_PRC_ENABLED
Determines whether a transaction is billable based on the assigned work type.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Transaction is billable based on the assigned work type |
| No | Transaction is not billable based on the assigned work type |
The default value for this option is No.
Internal name: PA_TRXN_BILLABLE_WORK_TYPE
Profile options in this category specify default dates. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Display Terminated Employees: Number of Days | No Default | Update | Update | Update | Update | Update |
| PA: Global Week Start Day | No Default | No Access | No Access | No Access | No Access | Update |
| PA: Require Assignment and Project Date Validation | Yes | Update | Update | No Access | No Access | Update |
| PA: Utilization Calculation Begin Date | No | No Access | No Access | No Access | No Access | Update |
This profile option controls how many days after their termination employees continue to be included on a selection list of employees in the Transaction Control and Employee Bill Rate and Discount Overrides windows.
This profile option is optional.
Internal name: PA_TERMINATED_EMPLOYEE_DAYS
This profile option specifies the weekday that is recognized as the beginning of the week. Set this profile option at the site level. You can select any day of the week as the value for this profile option.
Note: Global weeks use the date of the first day of the defined week as the name of the period. For example, the name of the global week for the week of April 1st through the 7th or the year 2001 is 01-APR-2001.
This profile option is optional.
Internal name: PA_GLOBAL_WEEK_START_DATE
Note: Do not change the profile option definition after you have generated utilization. Also, do not change this profile option after you have run PRC: Maintain Project Resources, or created requirements and assignments.
This profile option determines the start date and end date of a project requirement or assignment. You can set this profile option at the site level and at the user level.
This profile option is Optional. The available values are:
| Variable | Description |
|---|---|
| Yes | The project requirement or assignment start and end dates must be within the project transaction date range. This is the default value at the site level. |
| No | No validation is done |
| Warning | User is allowed to enter a date outside the project transaction date range, with a warning. |
Internal Name: PA_VALIDATE_ASSIGN_DATES
This profile option determines the calendar start date for a resource when you create a resource in Oracle Project Resource Management. Set the value of this profile option in the following format DD/MM/YYYY.
Internal name: PA_UTL_START_DATE
Profile options in this category control debug processing. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Debug Log Directory | No | No Access | No Access | No Access | Update | Update |
| PA: Debug Mode | No | No Access | Update | Update | Update | No Access |
| PA: Log Summarization Statistics | No | Update | Update | Update | Update | Update |
The PA Step Down Allocations workflow (paauto.wft) uses this profile option. For more information, see: AutoAllocations, Oracle Project Costing User Guide and Setting Up Workflow for AutoAllocations.
When Oracle Projects carries out the PA Step Down Allocations workflow, Oracle Workflow writes debugging information to a directory. Use this profile option to specify the directory. The default directory is:
/sqlcom/log
Important: The utl_file_dir parameter in the init.ora file must be set to the same directory that is specified in the profile option. If the two do not match, the PA Step Down Allocation workflow will fail (return an exception).
This profile option is required if you are using the Allocations feature in Oracle Project Costing.
Internal name: PA_DEBUG_LOG_DIRECTORY
Indicates if Oracle Projects reports and processes are run in debug mode. The debug mode enables a tracing feature and causes additional messages to be printed to the log file.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | System is operating in debug mode |
| No | System is operating in normal mode |
| (No value) | Equivalent to No |
Oracle Projects predefines a value of No for this profile upon installation.
Internal name: PA_DEBUG_MODE
Controls whether the system records the time required for the summarization processes to complete. The processes for which time is recorded are the Update Project Summary Amounts process (either for a single project or a range of projects) and the Refresh Project Summary Amounts process.
This profile option is optional. The available values are:
| Variable | Description |
|---|---|
| Yes | The system records time taken by the summarization processes. |
| No | The system does not record time taken by the summarization processes. |
| (No Value) | Equivalent to No |
Oracle Projects predefines a value of No for this profile option upon installation.
If you are attempting to track performance of the summarization processes, set this profile option to Yes.
The system writes the performance statistics to the table PA_ACCUM_TXN_TIME. You can use the scripts listed in the following table to query the table PA_ACCUM_TXN_TIME for statistics. You need the concurrent request ID of the process to query the table.
The following table shows the script that you use to query each summarization process:
| Summarization Process | Script |
|---|---|
| Update Project Summary Amounts | $PA_TOP/admin/sql/paxacmpt.sql |
| Refresh Project Summary Amounts | $PA_TOP/admin/sql/paxacrpt.sql |
Internal name: PA_LOG_SUMM_MODE
This category includes profile options that control access to products based on licensing or implementation options. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Enable Budget Integration and Budgetary Control Feature | No | Update | Update | View Only | View Only | Update |
| PA: Enable Microsoft Excel Integration for Budgeting and Forecasting | No | No Access | No Access | No Access | No Access | Update |
| PA: Licensed to Use Project Billing | No | View Only | View Only | View Only | View Only | Update |
| PA: Licensed to Use Project Collaboration | No | View Only | View Only | View Only | View Only | Update |
| PA: Licensed to Use Project Costing | No | View Only | View Only | View Only | View Only | Update |
| PA: Licensed to Use Project Management | No | View Only | View Only | View Only | View Only | Update |
| PA: Licensed to Use Project Resource Management | No | View Only | View Only | View Only | View Only | Update |
| PA: Project Costing Installed | No | No Access | No Access | No Access | No Access | View Only |
| PA: Upgrade Budget Types and Budget Versions | No | View Only | No Access | No Access | No Access | Update |
| PJP: Default Discount Rate | No Default | View Only | View Only | View Only | View Only | Update |
| PJP: Financial Plan Type for Project Benefit | No Default | View Only | View Only | View Only | View Only | Update |
| PJP: Financial Plan Type for Project Cost | No Default | View Only | View Only | View Only | View Only | Update |
| PJP: Licensed to Use Project Portfolio Analysis | No | View Only | View Only | View Only | View Only | Update |
| PJP: Nominate Risk from Investment Criteria | No Default | View Only | View Only | View Only | View Only | Update |
| PJP: Portfolio Organization Hierarchy | No Default | View Only | View Only | View Only | View Only | Update |
| PJP: Portfolio Selection Class Category | No Default | View Only | View Only | View Only | View Only | Update |
This profile option controls whether the budgetary controls windows and processes are displayed and run. The default value is No.
Note: You must set the value to Yes to enable budgetary controls and budget integration in Oracle Projects.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | The budgetary control windows and processes are displayed. |
| No | The budgetary control windows and processes are not displayed. |
Internal name: PA_BC_ENABLED
For more information, see: Setting Up Budgetary Controls.
Indicates whether the WebADI product has been fully installed. If WebADI is installed, you can use Microsoft Excel to import and export budgets and forecasts.
No action is required to enable this profile. It is automatically delivered and enabled by the WebADI patch.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Microsoft Excel is integrated with Projects for budgeting and forecasting. |
| No | Microsoft Excel is not integrated with Projects for budgeting and forecasting. |
| (No value) | Equivalent to No |
Internal name: PA_FP_WEBADI_ENABLE
Indicates if Oracle Project Billing is licensed. This profile option is required in order to use Oracle Project Billing.
This profile option is required in order to use Oracle Project Billing. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | In addition to Project Costing functions, Oracle Projects allows you to set up contract projects and perform all Project Billing functions. |
| No | Only Oracle Project Costing functions are allowed. Oracle Project Billing functions cannot be used. This is the default value for this profile option. |
| (No value) | Equivalent to No |
Internal name: PA_PROJECT_BILLING_INSTALLED
Indicates if Oracle Project Collaboration is licensed. This profile option is required in order to use Oracle Project Collaboration. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Oracle Projects allows you to perform all Project Collaboration functions. |
| No | Oracle Project Collaboration functions cannot be used. This is the default value for this profile option. |
| (No value) | Equivalent to No |
Internal name: PA_PROJECT_COLLABORATION_INSTALLED
Indicates if Oracle Project Costing is licensed. This profile option is required in order to use Oracle Project Costing. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Oracle Projects allows you to perform all Project Collaboration functions. |
| No | Oracle Project Collaboration functions cannot be used. This is the default value for this profile option. |
| (No value) | Equivalent to No |
Internal name: PA_PROJECT_COLLABORATION_INSTALLED
Indicates if Oracle Project Management is licensed. This profile option is required in order to use Oracle Project Management. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Oracle Projects allows you to perform all Project Management functions. |
| No | You cannot use Oracle Project Management functions. This is the default value for this profile option. |
| (No value) | Equivalent to No |
Internal name: PA_PROJECT_MANAGEMENT_INSTALLED
Indicates if Oracle Project Resource Management is licensed. This profile option is required in order to use Oracle Project Resource Management. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Oracle Projects allows you to perform all Project Resource Management functions. |
| No | You cannot use Oracle Project Resource Management functions. This is the default value for this profile option. If you change the profile option to Yes, you must perform the following to update the work type attribute for existing transactions:
|
| (No value) | Equivalent to No |
Internal name: PA_PRM_LICENSED
Indicates whether or not Oracle Project Costing is installed. Oracle Projects sets this profile automatically and uses it internally to determine access to features and functions specific to Oracle Project Costing.
This profile option is view only. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Oracle Project Costing is installed. |
| No | Oracle Project Costing is not installed. |
Internal name: PA_PROJECT_COSTING_INSTALLED
This profile option determines whether Oracle Projects displays an Upgrade check box next to each budget type in the Budget Types window. The Upgrade check box enables you to select the budget types and corresponding budget versions that you want to upgrade to plan types and plan versions when you submit the UPG: Upgrade Budget Types and Budget Versions process.
This profile option is optional. The available values are listed below:
| Variable | Description |
|---|---|
| Yes | The Upgrade check box is displayed. |
| No | The Upgrade check box is not displayed. |
This profile option is defined at the Site level only. The default value is No.
Internal name: PA_FP_UPGRADE_BUDGETS
The discount rate for a project portfolio is the minimum acceptable rate of return on an investment. You can use this profile option to enter a default discount rate for project portfolios.
This profile option is required if you are using Oracle Project Portfolio Analysis.
Internal name: PJP_DISCOUNT_RATE
This profile option identifies the financial plan type that is used by the system to calculate project benefits in Oracle Project Portfolio Analysis.
This profile option is required if you are using Oracle Project Portfolio Analysis.
Internal name: PJP_FINANCIAL_PLAN_TYPE_BENEFIT
This profile option identifies the financial plan type that the system uses to calculate project costs in Oracle Project Portfolio Analysis.
This profile option is required if you are using Oracle Project Portfolio Analysis.
Internal name: PJP_FINANCIAL_PLAN_TYPE_COST
Specifies if Oracle Project Portfolio Analysis is licensed.
This profile option is required if you are using Oracle Project Portfolio Analysis. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Oracle Projects allows you to perform all Project Portfolio Analysis functions. |
| No | You cannot use Oracle Project Portfolio Analysis functions. This is the default value for this profile option. |
| (No value) | Equivalent to No |
Internal name: PJP_PRODUCT_LICENSED
Use this profile option to specify which strategic objective group is used by the system to evaluate risk.
This profile option is required if you are using Oracle Project Portfolio Analysis.
Internal name: PJP_CRITERIA_RISK_CATEGORY
This profile option specifies the organization hierarchy that they system uses for your project portfolios.
Note: If you want to include projects in portfolios that are owned by child organizations, you must define a separate organization hierarchy for project portfolios. See: Define Portfolio Organization Hierarchy.
This profile option is optional.
Internal name: PJP_ORGANIZATION_HIERARCHY
This profile option specifies the class category that makes projects eligible to be included in a project portfolio. You must select a class category that allows entry of only one class code for a project (or, in other words, which has the Allow 1 Code Only box selected for its definition in the Class Categories and Codes window)..
This profile option is required if you are using Oracle Project Portfolio Analysis. Available values are listed below:
Internal name: PJP_PORTFOLIO_CLASS_CATEGORY
Each of these profile options enables you to specify a default value or select a processing option in a user interface. (Sys Admin = System Administration)
| Profile Option | Default | User Access | System Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Enable Long List of Resource LOVs | No | Update | Update | Update | Update | Update |
| PA: Override Approver | No Default | No Access | Update | Update | Update | Update |
| PA: Tasks to Display for Expenditure Entry | All Tasks | Update | Update | Update | Update | Update |
Indicates whether you can enter reduction criteria when you query the Resource Name field in the Budget Lines window.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Users can enter reduction criteria when they query the Resource Name field in the Budget Lines window. |
| No | All the resource names are displayed when users query the Resource Name field in the Budget Lines window. |
| (No value) | Equivalent to No |
Internal name: PA_RL_LONG_LIST
Indicates whether you can enter an overriding approver for timecards in Oracle Time and Labor. This profile option is optional.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | You can enter an overriding approver for timecards in Oracle Time and Labor. |
| No | You cannot enter an overriding approver for timecards in Oracle Time and labor. |
| (No value) | Equivalent to No |
Internal name: PA_ONLINE_OVERRIDE_APPROVER
Indicates which tasks to display in the Task Number list of values when entering pre-approved expenditures in Oracle Projects, supplier invoices in Oracle Payables, and requisitions and purchase orders in Oracle Purchasing.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| All Tasks | Displays the entire WBS of the selected project |
| Chargeable Tasks | Displays only the chargeable tasks of the selected project |
| Lowest Tasks | Displays only the lowest tasks of the selected project |
Internal name: PA_TASKS_DISPLAYED
Each profile option in this category enables you to specify a default value for the organization in a specific processing area. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Default Expenditure Organization in AP/PO | No Default | Update | Update | Update | Update | Update |
Indicates the default expenditure organization for project-related information in Oracle Payables and Oracle Purchasing.
This profile option is optional. You can select any organization that has the classification HR Organization.
Internal name: PA_DEFAULT_EXP_ORG
This category includes profile options that specify default values and that are not included in a function-specific category such as Staffing Defaults. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Default Burden Schedule Type | Firm | No Access | No Access | No Access | No Access | Update |
| PA: Default Public Sector | No | No Access | No Access | No Access | No Access | Update |
| PA: Transfer DFF with AP | No | View Only | View Only | View Only | View Only | Update |
| PJI: Default Reporting Calendar Type | No Default | No Access | No Access | No Access | No Access | Update |
| PJI: Default Reporting Currency Type | No Default | No Access | No Access | No Access | No Access | Update |
Indicates the default burden schedule type when entering a standard burden schedule using the Burden Schedules form.
This profile option is optional. Valid values are listed below:
| Variable | Description |
|---|---|
| Firm | Firm schedule type |
| Provisional | Provisional schedule type |
Oracle Projects predefines a value of Firm for this profile upon installation.
Internal name: PA_IND_RATE_SCHEDULE_TYPE
Indicates if a project is public sector when a user enters a project using the Projects form.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | By default, any new project is public sector |
| No | By default, any new project is not public sector |
| (No value) | Equivalent to No |
Oracle Projects predefines a value of No for this profile upon installation.
Internal name: PA_DEFAULT_PUBLIC_SECTOR
Specifies whether the process PRC: Interface Supplier Costs and the process PRC: Interface Expense Reports from Payables interface descriptive flexfield segments from Oracle Payables to Oracle Projects.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Descriptive flexfield segments are interfaced. |
| No | Descriptive flexfield segments are not interfaced. |
| (No value) | Equivalent to No |
Internal name: PA_TRANSFER_DFF_AP
Use this profile option to control the default calendar type used to report financial performance amounts on status reports, Project List, Project Home, and all project performance reporting pages.
Available values are global, GL, and PA calendar types. If you do not select a value, financial amounts displayed use the global calendar type.
Internal name: PJI_DEF_RPT_CAL_TYPE
Use this profile option to control the default currency type used to report financial performance amounts on status reports, Project List, Project Home, and all project performance reporting pages.
Available values are global, secondary global, project, and project functional currency types. If you do not select a value, financial amounts displayed use the project functional currency type.
Internal name: PJI_DEF_RPT_CUR_TYPE
These profile options affect processing related to integrating Oracle Projects with other applications. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Allow Adjustments to Receipt Accruals and Exchange Rate Variance | No | No Access | No Access | No Access | No Access | Update |
| PA: Allow Project-Related Entry in Oracle Internet Expenses | No Default | View Only | Update | Update | Update | Update |
| PA: Allow Time Entry of Negative Hours | No Default | View Only | Update | Update | Update | Update |
| PA: AutoApprove Expense Reports | No Default | View Only | Update | Update | Update | Update |
| PA: AutoApprove Timesheets | No Default | View Only | Update | Update | Update | Update |
| PA: AP Discounts Interface Start Date (mm/dd/yyyy) | 01/01/1951 | No Access | No Access | No Access | No Access | Update |
| PA: Default Expenditure Item Date for Supplier Cost | Source Document Exp Item Date | View Only | View Only | View Only | View Only | Update |
| PA: Enable Business Messages on Time Entry | No Default | View Only | No Access | No Access | Update | Update |
| PA: No of Instances for Auto Invoice Master Program | No Default | No Access | No Access | No Access | No Access | Update |
| PA: Pay When Paid | No | View Only | Update | Update | Update | Update |
| PA: Receivables Invoice Line UOM | No Default | No Access | View Only | View Only | View Only | Update |
| PA: Transfer DFF with PO | No | View Only | View Only | View Only | View Only | Update |
| PA: Use Auto Invoice Master Program | No Default | No Access | No Access | No Access | No Access | Update |
Determines whether a you can adjust receipt, receipt nonrecoverable tax, and exchange rate variance expenditure items in Oracle Projects when exchange rate variance exists and you convert journals to another currency. Conversion of journals to another currency happens in the following two situations:
When you assign a reporting currency to a ledger
When you assign a secondary ledger to a primary ledger, and the secondary ledger uses a different currency from the primary ledger
If you allow users to make adjustments in Oracle Projects to expenditure items that represent receipts, receipt nonrecoverable tax, or exchange rate variances, then Oracle Projects does not perform accounting for adjustments in the following ledgers:
Reporting currency ledgers
Secondary ledgers if the secondary ledger currency differs from the primary ledger currency
For additional information, see: Restrictions to Supplier Cost Adjustments, Oracle Project Costing User Guide.
Note: The profile option PA: Allow Adjustments to Receipt Accruals and Exchange Rate Variance does not affect your ability to adjust exchange rate variance expenditure items for period-end accruals.
This profile option is optional. You can set this profile option at the Site level and at the Organization level. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Adjustments are allowed. |
| No | Adjustments are not allowed. |
| (No value) | Equivalent to No |
Internal name: PA_ALLOW_RCV_ERV_ADJ_WHEN_JOURNAL_CONVERT
Indicates whether a specified employee can enter project-related expenses (that is, expenses associated with a project and task) in Oracle Internet Expenses. You must also set the profile option OIE: Enable Projects to Yes or Required. For additional information, see: Oracle Internet Expenses Implementation and Administration Guide.
This profile option integrates with the project user procedure. See: AutoApproval Extension, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
Available values are listed below:
| Variable | Description |
|---|---|
| Yes | The user can enter project-related expenses in Oracle Internet Expenses. |
| No | Employees can enter only those expenses that are not associated with a project and task. This is the default value. |
| (No value) | Equivalent to No |
Internal Name: PA_TIME_EXP_PROJ_USER
Determines whether you can enter negative hours on timecards in Oracle Time & Labor.
This profile option is optional. Available values are listed below.
| Variable | Description |
|---|---|
| Yes | You can enter negative hours. |
| No | You cannot enter negative hours. |
| (No value) | Equivalent to No. |
Internal name: PA_SST_ALLOW_NEGATIVE_TXN
Indicates whether to automatically approve project-related expense reports submitted in Oracle Internet Expenses.
Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Oracle Internet Expenses automatically approves project-related expense reports. You do not need to route or review your expense reports. |
| No | Expense reports require review and approval. This is the default value. |
| (No value) | Equivalent to No |
Internal Name: PA_PTE_AUTOAPPROVE_ER
Indicates whether to automatically approve timecards submitted in Oracle Time & Labor.
Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Oracle Time & Labor automatically approves project-related timesheets. You do not need to route or review your timesheets. |
| No | Timesheets require review and approval. This is the default value. |
| (No value) | Equivalent to No |
Internal Name: PA_PTE_AUTOAPPROVE_TS
Indicates when Oracle Projects will begin retrieving and interfacing payment discounts from Oracle Payables. For example, if you specify a date of 01/01/2002, then Oracle Projects will retrieve discount amounts with an expenditure item date on or after January 1st, 2002.
The system assigns a default start date of 01/01/2051. You can enter a different date to override the default system value. Oracle Projects allows you to enter either a historical date or future date. If you enter a historical date, then the system will retroactively retrieve discount amounts from the specified date forward the next time you run the PRC: Interface Supplier Costs process. If you specify a future date, the process will begin interfacing discount amounts as of that date.
This profile option is optional.
Internal name: PA_DISC_PULL_START_DATE
This profile option enables you to specify the source for the expenditure item date. Oracle Projects uses this profile option when you run the process PRC: Interface Supplier Costs to determine the expenditure item date for Oracle Purchasing receipts, invoice payments, and discounts. In addition, Oracle Payables uses this profile option during the invoice match process, and when you enter unmatched invoices, to determine the default expenditure item date for supplier invoice distribution lines. You can override the default expenditure item date for invoice distribution lines on the Invoice Workbench in Oracle Payables.
For additional information, see: Interfacing Supplier Costs, Oracle Project Costing User Guide.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Source Document Exp Item Date | The following table shows the source of the default expenditure item date for each transaction type if you specify the value Source Document Exp Item Date. |
| Transaction Type | Date Source |
|---|---|
| Invoice, Matched | Purchase order expenditure item date |
| Invoice, Unmatched | Invoice date
Note: A source expenditure item date does not exist for unmatched invoices. |
| Receipt | Purchase order expenditure item date |
| Payment | Invoice expenditure item date |
| Discount | Invoice expenditure item date |
| Variable | Description |
|---|---|
| Transaction Date | The following table shows the source of the default expenditure item date for each transaction type if you specify the value Transaction Date. |
| Transaction Type | Default Expenditure Item Date Source |
|---|---|
| Invoice, Matched | Invoice date |
| Invoice, Unmatched | Invoice date |
| Receipt | Receipt date |
| Payment | Payment date |
| Discount | Payment date |
| Variable | Description |
|---|---|
| Transaction GL Date | The following table shows the source of the default expenditure item date for each transaction type if you specify the value Transaction GL Date. |
| Transaction Type | Default Expenditure Item Date Source |
|---|---|
| Invoice, Matched | Invoice GL date |
| Invoice, Unmatched | Invoice GL date |
| Receipt | Receipt GL date |
| Payment | Payment GL date |
| Discount | Payment GL date |
| Variable | Description |
|---|---|
| Transaction System Date | The following table shows the source of the default expenditure item date for each transaction type if you specify the value Transaction System Date. |
| Transaction Type | Default Expenditure Item Date Source |
|---|---|
| Invoice, Matched | Invoice creation date |
| Invoice, Unmatched | Invoice creation date |
| Receipt | Receipt creation date |
| Payment | Payment creation date |
| Discount | Payment creation date |
Internal Name:PA_AP_EI_DATE_DEFAULT
This profile option indicates whether Oracle Time & Labor displays a business message. If the profile option is set to Yes, then Oracle Time & Labor calls the Business Message Display client extension. For information about the Business Message Display client extensions, see Oracle Time & Labor Implementation and User Guide.
This profile option is optional. Available values are listed below.
| Variable | Description |
|---|---|
| Yes | Oracle Time & Labor displays the custom business message field.
Note: This field displays a value only if the Business Message Display extension returns a value. Otherwise, the message field is empty. |
| No | Oracle Time & Labor does not display the custom business message field. |
| (No value) | Equivalent to No. |
Internal name: PA_SST_ALLOW_ENABLE_BUS_MSG
This profile option determines the number of instances that are passed as a parameter to the Auto Invoice Master Program. This profile option affects the PRC: Submit Interface Streamline Process concurrent program.
Internal Name: PA_AR_NUM_INSTANCES
Transactions, Oracle Receivables User Guide
Set this optional profile option to Yes at the responsibility level if you are using the Oracle Project Costing feature of Supplier Payment Control. This enables you to control supplier payments on project work that you outsource using Pay When Paid as the contract payment terms on your purchase order.
This profile option affects the PRC: Generate Draft Invoices and the PRC: Release Pay When Paid Holds concurrent programs. When generating draft invoices, the Generate Draft Invoices program automatically links supplier invoices on pay when paid holds to draft customer invoices. The Release Pay When Paid Holds program considers these linked supplier invoices, checks for payments received on corresponding customer invoices, and releases the hold on the supplier invoices.
Setting this profile option to Yes, enables you to manually link pay when paid supplier invoices to customer invoices and release holds from the Supplier Workbench and while reviewing invoices. It also enables you to track the submission status of supplier deliverables from the Supplier Workbench and release payment holds on supplier invoices against these deliverables.
To release Pay when Paid hold you must set the profile option to Yes and enable the Project: Subcontractor: Apply and Release Hold function security.
Internal Name: PA_PAY_WHEN_PAID
Note: If this profile option is not enabled but you have the function security, then will not be able to release Pay when Paid Hold on invoices, but you would still be able to release Deliverable Hold and Project Hold on invoices.
Indicates the unit of measure to use for all invoice lines interfaced from Oracle Projects and created in Oracle Receivables. Oracle Receivables requires a unit of measure for each invoice line. Oracle Projects creates each invoice line with a quantity of 1, a unit of the unit type you specify in your profile option, and an amount equal to the currency amount of the invoice line as it appears in Oracle Projects.
You need to define a unit of measure class before you define a unit of measure, because Oracle Receivables requires that you associate each unit of measure you define with a unit of measure class. Oracle Projects recommends that you define a unit of measure of Each or EA in Oracle Receivables for use with this profile. You must define a unit of measure and a unit of measure class before you can set this profile option. For detailed information, see Unit of Measure Classes, Oracle Receivables Implementation Guide.
If you are using Oracle Projects without Oracle Receivables, you do not need to set this profile. Oracle Projects uses the value EA.
You can choose from any unit of measure defined in Oracle Receivables.
This profile option is required if you are using Oracle Project Billing.
Internal name: PA_AR_INVOICE_UOM
Specifies whether the process PRC: Interface Supplier Costs interfaces descriptive flexfield segments from Oracle Purchasing to Oracle Projects.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Descriptive flexfield segments are interfaced. |
| No | Descriptive flexfield segments are not interfaced. |
| (No value) | Equivalent to No |
Internal name: PA_TRANSFER_DFF_PO
This profile option specifies whether the concurrent program PRC: Submit Interface Streamline Processes calls the Auto Invoice Master Program. This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | The PA: Submit Interface Streamline Processes concurrent program automatically calls the Auto Invoice Master Program. |
| No | The PA: Submit Interface Streamline Processes concurrent program does not call the Auto Invoice Master Program. |
Internal Name: PA_AR_MASTER_INVOICE_ENABLED
These profile options enable you to specify time durations, minimum values, and maximum values that affect processing. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Availability Duration | 2 | View Only | View Only | View Only | View Only | Update |
| PA: Overcommitment Percentage | 0 | View Only | View Only | View Only | View Only | Update |
| PA: Percentage of Resource Capacity | 100 | View Only | View Only | View Only | View Only | Update |
| PA: Process MS Excel Data Threshold | 1000 | Update | Update | No Access | No Access | Update |
| PA: Process Structure Updates Threshold | 50 | View Only | No Access | No Access | No Access | Update |
| PA: Streamline Process Sleep Interval | 60 seconds | No Access | No Access | No Access | Update | No Access |
Specifies how many years forward to calculate availability and overcommitment. Availability and overcommitment records are created from today's date through to the end of the specified time period.
For example, if you enter 2 as the value of this profile option, the availability and overcommitment of your resources is calculated from today to two years from today.
The stored availability and overcommitment information is used for display on the staffing pages, timelines, resource search results and overcommitment warnings.
This profile option is required if you are using Oracle Project Resource Management.
Internal name: PA_AVAILABILITY_DURATION
Specifies the maximum threshold of overcommitment.
For example, if you set this profile option to 10, resources are not considered overcommitted until their confirmed assignment hours exceed their capacity hours by 10% or more. With this setting, if a resource has a capacity of 40 hours per week, then the overcommitment threshold is 4 hours (40 hours * 10% = 4 hours). At overcommitment beyond this number of hours (44), the resource is considered to be overcommitted, starting from the date they meet this criterion.
This profile option is required if you are using Oracle Project Resource Management.
Internal name: PA_OVERCOMMITMENT_PERCENTAGE
Specifies the minimum threshold of availability.
For example, if you set this profile option to 20, then resources are not considered available until their capacity hours exceed their confirmed assignment hours by 20% or more. With this setting, if a resource has a capacity of 40 hours per week, then the available threshold is 8 hours (40 hours * 20% = 8 hours). At availability beyond this number of hours (48), the resource is considered to be available, starting from the date they meet this criterion.
This profile option is required if you are using Oracle Project Resource Management.
Internal name: PA_RES_CAPACITY_PERCENTAGE
This profile option specifies a row threshold value. When you upload a Microsoft Excel spreadsheet for a financial plan and the profile option PA: Process MS Excel Data is set to Standard, Oracle Projects evaluates the number of rows in the spreadsheet. If the number of rows is less than or equal to the threshold value, then Oracle Projects processes the upload online. If the number of rows is greater than the threshold value, then Oracle Projects performs the upload as a concurrent program using the process PRC: Upload Financial Plan Data from Microsoft Excel.
The default value is 1000. You can set this profile option at the site level and at the user level as necessary to meet the processing requirements of your enterprise.
Internal name: PA_FP_WEBADI_DATA_PRC_THSLD
This profile option specifies a task threshold value. When you update a project structure -- by adding tasks, deleting tasks, or rearranging the task hierarchy -- and you then invoke the Process Updates action, the system determines whether PA: Process Structure Updates is set to Standard or Online.
If PA: Process Structure Updates is set to Standard, the system evaluates the number of tasks in the structure. If the number of tasks in the structure is less than or equal to the threshold value set in the PA: Process Structure Updates Threshold profile option, the system automatically processes the changes online. If the number of tasks exceeds the threshold value, the system processes the updates concurrently using the PRC: Process Structure Updates process.
If PA: Process Structure Updates is set to Online, the system always processes the updates online whenever you invoke the Process Updates action.
Note: When you update a program structure and invoke the Process Updates action, the system always processes the changes concurrently with the PRC: Process Structure Updates process.
The default value is 50 and is set at the site level only. You can override the default value.
This profile option is required for Oracle Project Management.
Internal name: PA_PROC_WBS_UPD_THRESHOLD
Indicates the number of seconds that the Streamline process sleeps before it checks the status of its child process.
You can choose any numeric value over 30 to set this profile. If you do not set this profile value, or use a value that is less than 30, a default value of 60 seconds is used. Oracle Projects predefines a value of 60 seconds for this profile upon installation.
This profile option is optional.
Internal name: PA_STRMLN_SLEEP_INTERVAL
This category includes profile options that affect the processing of a reporting pack. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Reporting Pack E-mail Sender Address | No | View Only | No Access | Update | Update | Update |
| PA: Reporting Pack SMTP Server Address | No | View Only | No Access | Update | Update | Update |
| PA: Reporting Pack Worker Quantity | Yes | View Only | No Access | Update | Update | Update |
This profile option indicates the e-mail address that you can contact for assistance if you experience problems with generating and distributing reporting pack. At the site level, you must enter a valid e-mail, preferably that of the system administrator in charge of the reporting pack feature, to ensure that the reporting pack concurrent program completes successfully.
Internal name: PA_RP_EMAIL_SENDER
This profile option determines the outgoing mail server that the reporting pack concurrent program must use to distribute the reporting pack. You must enter the name of the outgoing server at the site level to ensure that the program completes successfully.
Internal name: PA_RP_SMTP_ADDRESS
This profile option determines the number of workers that the reporting pack concurrent program can use in parallel to efficiently generate and distribute the reporting pack. The default value is four. However, based on the number of reports being generated, you can optionally increase the value at the site level.
Internal name: PA_RP_WORKER_QUANTITY
This category includes profile options that affect revenue processing. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Interface Unreleased Revenue to GL | No | View Only | No Access | Update | Update | No Access |
| PA: Maintain Unbilled Receivables and Unearned Revenue Balances | No | View Only | No Access | No Access | No Access | Update |
Indicates whether the process PRC: Generate Revenue Accounting Events generates accounting events for unreleased draft revenue. Oracle Subledger Accounting uses revenue accounting events to create the final accounting entries that it transfers to Oracle General Ledger.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | The process PRC: Generate Revenue Accounting Events generates accounting events for unreleased draft revenue. |
| No | The process PRC: Generate Revenue Accounting Events does not generate accounting events for unreleased draft revenue. This is the default value. |
| (No value) | Equivalent to No. |
Internal name: PA_INTERFACE_UNRELEASED REVENUE
This profile option maintains unbilled receivables and unearned revenue balances. Choose Yes when you disable the interface revenue to GL option but want to maintain unbilled receivables and unearned revenue balances. The default value for this option is No. Set this profile at the site level.
This profile option is optional.
Internal name: PA_UBR_UER_FLAG
This category includes profile options that control access to data. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Cross-Project User - Update | No | No Access | No Access | Update | No Access | No Access |
| PA: Cross-Project User - View | Yes, at Site | No Access | Update | Update | No Access | Update |
| PA: Task Managers Must Be Project Members | No | Update | Update | Update | Update | Update |
| PA: View All Project Resources | No Default | Update | Update | Update | No Access | No Access |
| MO: Security Profile |
Indicates if a responsibility allows cross-project update access.
This profile option is optional. Available values are as listed below:
| Variable | Description |
|---|---|
| Yes | A holder of this responsibility can view and update any project |
| No | A holder of this responsibility can view and update only those projects for which the holder is assigned as a key member. A holder with cross-project view access can view information on any project, other than labor cost details. If users have access to the Expenditure Inquiry: All menu, this restriction does not apply and they will be able to view labor cost details. |
| (No value) | Equivalent to No |
Oracle Projects predefines a value of Yes for this profile for the Project Billing Super User and Project Costing Super User responsibilities upon installation.
Internal name: PA_SUPER_PROJECT
Indicates if a user has cross-project view access.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | A user can view information on any project, other than labor cost details. If users have access to the Expenditure Inquiry: All menu, this restriction does not apply and they will be able to view labor cost details. |
| No | A user can view only those projects for which the user is assigned as a key member. |
| (No value) | Equivalent to No |
Oracle Projects predefines a value of Yes for this profile option at the site level. By default, a Yes setting at this level grants cross-project view access to all users. The site level value can be changed and/or overridden at the responsibility and user levels by a system administrator. If you do not have cross-project view access, you can only view projects where you have a key member role.
Internal name: PA_SUPER_PROJECT_VIEW
Determines whether task managers can only be selected from the subset of project members in an enterprise.
This profile option is optional. Available values are listed below:
| Variable | Description |
|---|---|
| Yes | Task managers must be members of project teams. |
| No | Task managers can be any employee in an enterprise. |
| (No value) | Equivalent to No |
Internal name: PA_TM_PROJ_MEMBER
Indicates if view all resources access is granted.
This profile option is optional. Available values are shown below:
| Variable | Description |
|---|---|
| Yes | The user can view resource information for all resources in the enterprise. They can perform resource-related functions as granted for their responsibility. |
| No | The user can view resource information based on access granted for their responsibility. |
| (No value) | Equivalent to No |
Oracle Projects predefines a value of Yes for this profile option only for the Project Super User responsibility. Otherwise, the default value is No.
You can update this profile option at the responsibility or user level.
Internal name: PA_SUPER_RESOURCE
Note: This profile option is generally reserved for super users who need cross-project and cross-organization access.
These profile options contain default values for self-service pages.
All of the profile options in this category are optional. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Highlight Starting Tasks: Number of Days | 14 | Update | Update | Update | No Access | No Access |
| PA: Home Page Highlights: Number of Weeks | 2 | View Only | View Only | View Only | View Only | Update |
| PA: Retain Existing Period Spread Values for Plan Duration Changes | No Default | Update | Update | Update | Update | Update |
| PA: Team Home Page Layout | No Default | Update | Update | Update | Update | Update |
| PA: Workplan Tasks Default View | Hierarchy | Update | Update | Update | Update | Update |
This profile option determines which tasks are highlighted as Upcoming in the Open and Upcoming Tasks region. You indicate how may days before the task start date to display tasks The default value is 14 days.
Internal name: PA_TASK_PROGRESS_START_DUE
Specifies the number of weeks of future team activity to display in the Team Highlights table on the Project Home page.
Internal name: PA_HOME_HIGHLIGHTS_WEEKS
Use this profile option to set a default value for the budgeting and forecasting option that enables you to select whether or not to retain existing period spread values when you change the duration of a plan line.
Available values are shown below:
| Variable | Description |
|---|---|
| Yes | The existing period spread values are retained when duration of a plan line changes. |
| Variable | Description |
|---|---|
| No | The existing period spread values are redistributed when duration of plan line changes. |
| Variable | Description |
|---|---|
| (No Value) | Equivalent to No |
Internal Name: PA_RETAIN_SPREAD_VALUES
Specifies which Team Member Home Page Layout is used for a responsibility and user.
The implementation team can set this profile option to specify the page layout used for each responsibility and user. If no page layout is defined for a responsibility or user, the Default Team Member Home Page Layout is used.
Internal name: PA_TEAM_HOME_PAGELAYOUT
This profile option defines the default display view for workplan information on the Tasks page. Available values are shown below:
| Variable | Description |
|---|---|
| Hierarchy | The hierarchy view is the default view for task information. This view displays tasks in a hierarchical manner that makes it easy to see how summary tasks relate to subtasks. |
| List | The list view is the default view for task information. This view displays tasks as a list ordered according to outline level. |
| Gantt | The Gantt display view is the default view for task information. This view provides a graphic display of task information. |
Internal name: PA_WORKPLAN_DEFAULT_VIEW
These profile options contain default values for staffing functionality. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Availability/ Over- commitment Calculation Period | WEEKLY | View Only | View Only | View Only | View Only | Update |
| PA: Canceled Assignment Status | None | No Access | View Only | View Only | View Only | Update |
| PA: Canceled Requirement Status | None | No Access | View Only | View Only | View Only | Update |
| PA: Canceled Requirement's Candidate Status | None | No Access | View Only | View Only | View Only | Update |
| PA: Default Calendar | No Default | View Only | View Only | View Only | View Only | Update |
| PA: Default Starting Candidate Status | None | No Access | View Only | View Only | View Only | Update |
| PA: Filled Requirement Status | None | No Access | View Only | View Only | View Only | Update |
| PA: Invalid Resource Candidate Status | None | No Access | View Only | View Only | View Only | Update |
| PA: Project Resource Job Group | No Default | View Only | View Only | View Only | View Only | Update |
| PA: Staffing Home Default Organization | No Default | View and Update | View and Update | View Only | View Only | View Only |
| PA: Starting Assignment Status | None | No Access | View Only | View Only | View Only | Update |
| PA: Starting Requirement Status | None | No Access | View Only | View Only | View Only | Update |
Determines whether the available hours for each resource are calculated on a daily or weekly basis.
This profile option is required if you are using Oracle Project Resource Management. Available values are:
| Variable | Description |
|---|---|
| Daily | The number of confirmed hours and the number of capacity hours are compared for each day for each resource. If the number of capacity hours for the day exceed the number of confirmed hours for the day by more than the threshold percentage, then the resource is marked as available for that day. |
| Weekly | The number of confirmed hours and the number of capacity hours are compared for each week for each resource. |
Using the Weekly setting, a resource can be available on a daily basis and not get marked as available on a weekly basis. For example, if a resource with capacity of 40 hours (8 hours * 5 days), has 30 confirmed hours over 3 days (10 hours * 3 days), the resource is available for 16 hours on two days using the daily basis, but not on a weekly basis.
Note: Overcommitment calculation period is also done using this profile option. For an example refer to the discussion in Determining Overcommitted Resources, Oracle Project Resource Management User Guide.
Internal name: PA_AVAILABILITY_CAL_PERIOD
Specifies the status of an assignment when it is canceled.
This profile option is required if you are using Oracle Project Resource Management.
Internal name: PA_DEF_CANCELED_ASGMT_STATUS.
Specifies the status of a requirement when it is canceled.
This profile option is required if you are using Oracle Project Resource Management.
Internal name: PA_DEF_CANCELED_REQMT_STATUS
Specifies the candidate status when a candidate nomination is declined due to requirement cancellation.
This profile option is required if you are using Oracle Project Resource Management.
Internal name: PA_CNL_REQ_CAND_STATUS
Indicates the default calendar for project templates, project assignments, and resources. You can select any defined calendar.
This profile option is optional.
Internal name: PA_PRM_DEFAULT_CALENDAR
Specifies the default status of all newly nominated candidates, except for system-nominated candidates.
This profile option is required if you are using Oracle Project Resource Management.
Internal name: PA_DEF_START_CAND_STATUS
Specifies the requirement status when the requirement is filled and becomes an assignment.
This profile option is required if you are using Oracle Project Resource Management.
Internal name: PA_DEF_FILLED_ASGMT_STATUS
Specifies the candidate status for a candidate whose nomination is declined because the candidate is no longer a valid resource in Oracle Project Resource Management.
This profile option is required if you are using Oracle Project Resource Management.
Internal name: PA_INV_RES_CAND_STATUS
Specifies the job group that is used for resource searches and to determine resource eligibility for the resource pool.
You can use the master job group as the project resource job group, but be aware that the master job group includes every job. If there are jobs that you do not want included in job searches (such as accounts payable jobs, administrative jobs, and human resource jobs that are not related to staffing projects) then you can set up a separate job group specifically for searching. This job group should include all jobs that you want included in searches.
If your system is set up for cross business group access, you set this profile option once for the site. If you are using single business group access, set this profile option for each business group.
This profile option is optional.
Internal name: PA_PROJ_RES_JOB_GRP
Use the profile option PA: Staffing Home Default Organization to specify the default organization of the resources and requirements that a staffing manager will see on the Staffing Home page. Users can see resources and requirements for other organizations by using the Full list views from the Staffing Home page.
The setup of this profile option is optional. If you do not set this profile option, users will view on the Staffing Home page the resources and requirements belonging to only their own organizations. Staffing managers without resource authority over their own organizations will not see any resources on the Staffing Home page. Similarly, staffing managers without project authority over their own organizations will not see any requirements on the Staffing Home page. This profile option can only be set at the user level.
Internal Name:PA_STAFF_HOME_DEF_ORG
Specifies the default status of newly created assignments.
This profile option is required if you are using Oracle Project Resource Management.
Internal name: PA_START_STAFFED_ASGMT_STATUS
Specifies the default status of newly created requirements.
This profile option is required if you are using Oracle Project Resource Management.
Internal name: PA_START_OPEN_ASGMT_STATUS
These profile options specify default values for the utilization feature. (Sys Admin = System Administration)
| Profile Option | Default | User Access | Sys Admin: User | Sys Admin: Responsibility | Sys Admin: Application | Sys Admin: Site |
|---|---|---|---|---|---|---|
| PA: Resource Utilization Calculation Method | No Default | No Access | No Access | No Access | No Access | Update |
| PA: Resource Utilization Period Type | No Default | No Access | No Access | No Access | No Access | Update |
| PA: Utilization Calculation Begin Date | No | No Access | No Access | No Access | No Access | Update |
| PA: Utilization Manager Default Calculation Method | No Default | No Access | No Access | No Access | No Access | Update |
| PA: Utilization Manager Default Period Type | No Default | No Access | No Access | No Access | No Access | Update |
This profile option determines the calculation method used when you access personal utilization on the Resource Details: Utilization page. Your choices are Capacity or Total Worked Hours.
Note: Individual resources cannot change the calculation method on the screen, only view data using this value.
Internal name: PA_RES_UTIL_DEF_CALC_METHOD
This profile option determines the default period type used when you access personal utilization in the Resource Details: Utilization page. To report utilization by a choice of period types, you must first enable utilization and availability reporting, and additional period types on the Project Intelligence Setup page. For more information, see: Defining Oracle Daily Business Intelligence for Projects Implementation Options..
Internal name: PA_RES_UTIL_DEF_PERIOD_TYPE
This profile option determines the default utilization calculation method used when you access the Utilization by Organization workbook. The choices are Capacity or Total Worked Hours.
Internal name: PA_ORG_UTIL_DEF_CALC_METHOD
This profile option determines the default period type used to report resource utilization for the organization when you access the Oracle Discoverer workbooks to view utilization by organization, resource manager, and resource, and when you access your personal utilization on the Resource Details: Utilization page. To report utilization by a choice of period types, enable additional period types on the Project Intelligence Setup page. For more information, see: Defining Oracle Daily Business Intelligence for Projects Implementation Options..
Internal name: PA_ORG_UTIL_DEF_PERIOD_TYPE
This section lists profile options that Oracle Projects shares with other Oracle Applications.
This profile option indicates whether to purge the data used to build account combinations as soon as the account generator has completed.
For best performance, set this profile option to No and then purge the runtime data in a separate operation. Setting the profile option to No retains (in the Oracle Workflow tables) the data used by the account generator to generate code combinations. To purge the data, run the Purge Obsolete Workflow Runtime Data program after the account generator process has executed successfully. The System Administrator can add this program to a request security group.
Setting this profile option to Yes purges the Oracle Workflow data as soon as the account generator has completed, but may slow the performance of the account generator.
Internal name: ACCOUNT_GENERATOR:PURGE_DATA
Use this profile option to change tax rates and tax amounts for tax classification codes in the Transactions window of Oracle Receivables.
Internal name: ZX_ALLOW_TAX_UPDATE
Use this profile option to override tax exemptions in Oracle Projects.
Internal name: ZX_ALLOW_TRX_LINE_EXEMPTIONS
Use this profile option to override the default tax classification code on invoice lines in Oracle Projects.
Internal name: ZX_ALLOW_TAX_CODE_OVERRIDE
Determines the Invoice Transaction Flexfield attribute to display in transaction lists of values throughout Oracle Receivables. This further identifies the invoice based on project information and is displayed under the Reference column in the lists of values.
You can set this profile to display any project information Oracle Projects passes to Oracle Receivables. For example, if you want to select invoices by project number in Oracle Receivables, leave this profile option set to the predefined default value of INTERFACE_HEADER_ATTRIBUTE1.
The segments that you can use from your Invoice Transaction Flexfield are shown in the following table:
| Segment | Column |
|---|---|
| Project Number | INTERFACE_HEADER_ATTRIBUTE1 |
| Draft Invoice Number | INTERFACE_HEADER_ATTRIBUTE2 |
| Agreement Number | INTERFACE_HEADER_ATTRIBUTE3 |
| Project Organization | INTERFACE_HEADER_ATTRIBUTE4 |
| Project Manager | INTERFACE_HEADER_ATTRIBUTE5 |
Internal name: AR_PA_CODE
Choose whether you want to assign your credit memo to the same accounts assigned to the invoice you are crediting.
Oracle Receivables predefines this value as Yes at the site level. You must change this value to No for Oracle Projects invoices at the application level for Oracle Projects. AutoInvoice will reject Oracle Projects credit memos and write-offs if this profile option is not set to No.
Oracle Projects invoices must use the accounting transactions as determined by AutoAccounting in Oracle Projects to correctly debit and credit the unbilled receivables, unearned revenue, and write off accounts for credit memos and write offs.
Internal name: AR_USE_INV_ACCT_FOR_CM_FLAG
Use this profile option to specify your ledger.
Internal name: GL_SET_OF_BKS_NAME
Use this profile option to set up the project performance reporting feature and enable performance data to be reported by the enterprise calendar that you name and that you have defined in GL.
Use this profile option to set up the project performance reporting feature and enable performance data to be reported by the period type that you name for the enterprise calendar. For example, you may have periods in your enterprise calendar by week, month, quarter, or year.
Use this profile option to set up the project performance reporting feature and enable performance data to be reported by the global currency that you name.
Use this profile option to set up the project performance reporting feature and enable performance data to be reported by the rate type that you name. For example, you may have defined a corporate rate, an average daily rate, or an end of business day rate.
Use this profile option to set up the project performance reporting feature and enable performance data to be reported by an additional global currency that you name.
Use this profile option to set up the project performance reporting feature and enable performance data to be reported by the rate type that you name for the additional global currency. For example, you may have defined a corporate rate, an average daily rate, or an end of business day rate.
Use this profile option to set up the project performance reporting feature. Oracle Projects summarizes project performance reporting information for projects that are active as of the global start date. Please ensure that this date is on or after the start date of your enterprise calendar.
Use this profile option to determine the number of records Oracle Web Applications Desktop Integrator sends to the database at one time when you upload records. The default value is 100. You can update this value to the batch size that optimizes upload time for your environment.
Internal Name: BNE_UPLOAD_BATCH_SIZE
Use this profile option to define whether Single Business Group Access mode or Cross Business Group Access mode is used in your installation.
| Variable | Description |
|---|---|
| Yes | Allows Cross Business Group Access. |
| No | Allows only Single Business Group Access. |
This is a required profile option, set by the System Administrator at the Site level. The default value is No. Because this profile option is set at the site level, it affects all business groups across the Oracle Applications database instance.
After the initial implementation, you can change the HR: Cross Business Group profile option from No to Yes, but not from Yes to No.
Note: If you change the value of this profile option from No to Yes, you must recreate the job defaults for each role. See: Role Definition.
Internal name: HR_CROSS_BUSINESS_GROUP
For more information on Cross Business Group Access, see Security, Configuring, Reporting and System Administration in Oracle HRMS.
Use this profile option to control whether you use security groups within security. Only change the default to Yes at the application level if your enterprise is using Cross Business Group Responsibility security. If you change the default to Yes, you must run the Enable Multiple Security Groups process.
Internal name: ENABLE_SECURITY_GROUPS
For more information on Cross Business Group Responsibility security, see Security, Configuring, Reporting and System Administration in Oracle HRMS.
Use this profile option to point your responsibility to a specific business group. You can see/update the profile at the responsibility and Site levels only.
Internal name: PER_SECURITY_PROFILE_ID
Use this profile option to specify the default operating unit option for a responsibility.
Internal name:DEFAULT_ORG_ID
Important: This option is valid only when MO: Security Profile profile option is set. If the MO: Security Profile profile option is not set, then the MO: Default Operating Unit profile option is redundant.
Use this profile option to control which operating unit a particular responsibility corresponds to. See: Multiple Organizations in Oracle Applicationsand MO: Default Operating Unit.
Internal name: ORG_ID
Important: The value for this option must not be set unless you have implemented multiple organization support.
Note: This profile option is maintained for backward compatibility and will be ignored once multiple organization access control feature is enabled by setting the MO: Security Profile profile option.
Use this profile option to provide multiple operating unit access to a responsibility. You can see and update the profile at the responsibility, site and user levels.
Internal Name:XLA_MO_SECURITY_PROFILE_LEVEL
Use this profile option to control the minimum level (between 1 and 6) of details for debug messages. See: Daily Business Intelligence for Projects, Oracle Daily Business Intelligence Implementation Guide.
Internal name: PJI_DEBUG_LEVEL
Use this profile option to ensure that the global start date value for Oracle Projects project performance reporting is the same as that for Oracle Daily Business Intelligence for Projects. The global start date determines the date from which summarization of reporting data can begin. See: Daily Business Intelligence for Projects, Oracle Daily Business Intelligence Implementation Guide.
Internal name: PJI_GLOBAL_START_DATE_OVERRIDE
Use this profile option to control the number of processes (from 2 to 8) that the Load, Update, and Refresh Project and Resource Base Summaries concurrent programs can launch in parallel. See: Daily Business Intelligence for Projects, Oracle Daily Business Intelligence Implementation Guide.
Internal name: PJI_EXTRACTION_ PARALLELISM
Use this profile option to control the projects for which the user can view data on project performance pages. See: Daily Business Intelligence for Projects, Oracle Daily Business Intelligence Implementation Guide.
Internal name: PJI_SECURITY_ PROFILE_LEVEL
Use this profile option to control the location of generated log and output messages for Oracle Projects project performance reporting. See: Daily Business Intelligence for Projects, Oracle Daily Business Intelligence Implementation Guide.
Internal name: PJI_OUTPUT_DESTINATION
Use this profile option to control the running of the Delete Project Intelligence and Performance Reporting Data and the Delete Project Performance Reporting Data concurrent programs. The delete processes clear the base summary of reporting data and the data viewed on project performance reporting pages. See: Daily Business Intelligence for Projects, Oracle Daily Business Intelligence Implementation Guide.
Internal name: PJI_SUM_CLEANALL
Use this profile option to control if the materialized view refresh for Daily Business Intelligence for Projects is done using the Request Set Generator or by running individual concurrent programs. See: Daily Business Intelligence for Projects, Oracle Daily Business Intelligence Implementation Guide.
Internal name: PJI_USE_DBI_RSG
Use this profile option to enable users to view funds check results from Oracle Purchasing and Oracle Payables after a funds check. You must select Budgetary Control Results Template as the value for this profile option.
Internal name: PSA_BC_REPORT_TEMPLATE
When you implement integration with other Oracle Products, your System Administrator needs to update the following profile options in the System Profile Values Window. See: Setting User Profile Options, Oracle Applications System Administrator's Guide.
PA: Allow Adjustments to Receipt Accruals and Exchange Rate Variance
PA: Default Expenditure Item Date for Supplier Cost
PA: Expense Report Invoices Per Set
eBTax: Allow Ad Hoc Tax Changes
eBTax: Allow Override of Customer Exemptions
eBTax Allow Override of Tax Classification Code
FV: Federal Enabled
Fremont Corporation sets up the following profile options.
Fremont Corporation's implementation team sets the following profile options that affect Oracle Projects processing:
Note: These profile options are set at the application level, for the Oracle Projects application.
| Profile Option | Value |
|---|---|
| PA: Expenditure Items Per Set | 1000 |
| PA: Cost Distribution Lines Per Set | 2000 |
| PA: Projects Per Set | 500 |
To enable Oracle Projects to integrate with other applications, Fremont Corporation sets the profile options shown in the following table:
| Option | Value | Comments |
|---|---|---|
| PA: Default Expenditure Organization in AP/PO | Fremont Corporation | |
| PA: Tasks to Display for Expenditure Entry | Chargeable Tasks | With this setting, the task list of values displays only chargeable tasks when users are entering expenditures online (pre-approved expenditures in Oracle Projects, purchase orders and requisitions in Oracle Purchasing, or supplier invoices in Oracle Payables) |
| PA: Receivables Invoice Line UOM | Each | (The unit of measure of Each is first defined in Oracle Receivables) |
| eBTax: Tax: Allow Ad Hoc Tax Changes | No | Prevents users from changing tax rates in the Transactions window in Oracle Receivables |
| eBTax: Allow Override of Customer Exemptions | No | Prevents users from overriding the default tax exemption on invoice lines in Oracle Projects |
| eBTax: Allow Override of Tax Classification Code | Yes | Allows users to override the default tax classification code on invoice lines in Oracle Projects |
| AR: Use Invoice Accounting For Credit Memos | No | |
| AR: Transaction Flexfield QuickPick | INTERFACE_HEADER _ATTRIBUTE1 | Causes the project number to appear as the project attribute in QuickPicks in Oracle Receivables |
| GL: Ledger Name | Fremont Corporation |
Related Topics
Personal Profile Values Window, Oracle Applications User's Guide
Overview of Setting User Profiles, Oracle Applications System Administrator's Guide