fieldvaluefield value requiredd是什么意思

Oracle Projects Implementation Guide
Browser version scriptProfile Options
This appendix describes profile options that affect the operation of your Oracle Projects application.This appendix covers the following topics:
Profile Options and Profile Option Categories Overview
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.
List of Profile Option Categories
This appendix describes the following profile option categories:
List of Profile Options
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
Oracle Project Billing
Oracle Project Portfolio Analysis
Oracle Project Resource Management
Oracle Project Management
PJL: Oracle Project Collaboration
The following table lists the profile options that are used in Oracle Projects.
List of Profile Options
Users cannot include future-dated employees as key members.
Internal name:
PA_ALLOW_FDE_AS_PM
PA: Display Find Tasks
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:
Tasks does not display the Find Tasks window
(No value)
Equivalent to No
Internal name:
PA_DISPLAY_FIND_TASKS
PA: Process MS Excel Data
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:
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
PA: Process Structure Updates
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:
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
PA: Require Work Type Entry for Expenditures
Determines whether work types are required for all expenditure items.
This profile option is optional. Available values for this profile option are:
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:
Expenditure Items
Internal name: PA_EN_NEW_WORK_TYPE_PROCESS
PA: Tab to Budget Matrix Comments Fields
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:
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
Account Generation Category
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)
Account Generation Category
Users cannot override accounts.
Internal name:
PA_OVERRIDE_BUDGET_ACCOUNT
PA: Allow Override of PA Distributions in AP/PO
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:
The user-entered values are ignored and are not passed to the workflow.
(No value)
Equivalent to Yes
Internal name:
PA_ALLOW_FLEXBUILDER_OVERRIDES
PA: Selective Flexfield Segment for AutoAccounting
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
Batch Processing Size Category
Profile options in the Batch Processing Size category enable you to specify the size of batches used in processing data. (Sys Admin = System Administration)
Batch Processing Size Category
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
PA: Days to Maintain BC Packets
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:
PA: Enable Enhanced Period Processing
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.
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.
PA: Report Separate Burden Transactions with Source Resources
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.
Oracle Project maps summary burden transactions to the Financial Elements resource class.
(No value)
Equivalent to No.
Internal Name:
PA_RPT_BTC_SRC_RESRC
PA: Retirement Cost Processing Enabled
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:
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
PA: Transaction Billability Derived from Work Type
Determines whether a transaction is billable based on the assigned work type.
This profile option is optional. Available values are listed below:
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
Date Defaults Category
Profile options in this category specify default dates. (Sys Admin = System Administration)
Date Defaults Category
No validation is done
User is allowed to enter a date outside the project transaction date range, with a warning.
Internal Name: PA_VALIDATE_ASSIGN_DATES
PA: Utilization Calculation Begin Date
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
Debug Category
Profile options in this category control debug processing. (Sys Admin = System Administration)
Debug Category
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
PA: Log Summarization Statistics
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:
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:
The budgetary control windows and processes are not displayed.
Internal name:
PA_BC_ENABLED
For more information, see: .
PA: Enable Microsoft Excel Integration for Budgeting and Forecasting
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:
Microsoft Excel is not integrated with Projects for budgeting and forecasting.
(No value)
Equivalent to No
Internal name: PA_FP_WEBADI_ENABLE
PA: Licensed to Use Project Billing
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:
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
PA: Licensed to Use Project Collaboration
Indicates if Oracle Project Collaboration is licensed. This profile option is required in order to use Oracle Project Collaboration. Available values are listed below:
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
PA: Licensed to Use Project Costing
Indicates if Oracle Project Costing is licensed. This profile option is required in order to use Oracle Project Costing. Available values are listed below:
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
PA: Licensed to Use Project Management
Indicates if Oracle Project Management is licensed. This profile option is required in order to use Oracle Project Management. Available values are listed below:
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
PA: Licensed to Use Project Resource Management
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:
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:
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:
Expenditure Items
(No value)
Equivalent to No
Internal name: PA_PRM_LICENSED
PA: Project Costing Installed
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:
Oracle Project Costing is not installed.
Internal name: PA_PROJECT_COSTING_INSTALLED
PA: Upgrade Budget Types and Budget Versions
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:
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
PJP: Default Discount Rate
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
PJP: Financial Plan Type for Project Benefit
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
PJP: Financial Plan Type for Project Cost
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
PJP: Licensed to Use Project Portfolio Analysis
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:
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
PJP: Nominate Risk from Investment Criteria
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
PJP: Portfolio Organization Hierarchy
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: .
This profile option is optional.
Internal name: PJP_ORGANIZATION_HIERARCHY
PJP: Portfolio Selection Class Category
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
Forms Interaction 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)
Deployment - Forms Interaction Categoryprofile optionscategoriesforms interaction
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
PA: Override Approver
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:
You cannot enter an overriding approver for timecards in Oracle Time and labor.
(No value)
Equivalent to No
Internal name: PA_ONLINE_OVERRIDE_APPROVER
PA: Tasks to Display for Expenditure Entry
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:
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
Organization Defaults Category
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)
Organization Defaults Category
Provisional
Provisional schedule type
Oracle Projects predefines a value of Firm for this profile upon installation.
Internal name: PA_IND_RATE_SCHEDULE_TYPE
PA: Default Public Sector
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:
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
PA: Transfer DFF with AP
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:
Descriptive flexfield segments are not interfaced.
(No value)
Equivalent to No
Internal name: PA_TRANSFER_DFF_AP
PJI: Default Reporting Calendar Type
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
PJI: Default Reporting Currency 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
Other Product Integration Category
These profile options affect processing related to integrating Oracle Projects with other applications. (Sys Admin = System Administration)
Other Product Integration Category
Adjustments are not allowed.
(No value)
Equivalent to No
Internal name: PA_ALLOW_RCV_ERV_ADJ_WHEN_JOURNAL_CONVERT
PA: Allow Project-Related Entry in Oracle Internet Expenses
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:
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
PA: Allow Time Entry of Negative Hours
Determines whether you can enter negative hours on timecards in Oracle Time & Labor.
This profile option is optional. Available values are listed below.
You cannot enter negative hours.
(No value)
Equivalent to No.
Internal name: PA_SST_ALLOW_NEGATIVE_TXN
PA: AutoApprove Expense Reports
Indicates whether to automatically approve project-related expense reports submitted in Oracle Internet Expenses.
Available values are listed below:
Expense reports require review and approval. This is the default value.
(No value)
Equivalent to No
Internal Name: PA_PTE_AUTOAPPROVE_ER
PA: AutoApprove Timesheets
Indicates whether to automatically approve timecards submitted in Oracle Time & Labor.
Available values are listed below:
Timesheets require review and approval. This is the default value.
(No value)
Equivalent to No
Internal Name: PA_PTE_AUTOAPPROVE_TS
PA: AP Discounts Interface Start Date (mm/dd/yyyy)
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
PA: Default Expenditure Item Date for Supplier Cost
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:
Profile Option Value: Source Document Exp Item Date
Profile Option Value: Transaction Date
Profile Option Value: Transaction GL Date
Profile Option Value: Transaction System Date
Oracle Time & Labor does not display the custom business message field.
(No value)
Equivalent to No.
Internal name: PA_SST_ALLOW_ENABLE_BUS_MSG
PA: No of Instances for Auto Invoice Master Program
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
PA: Pay When Paid
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.
PA: Receivables Invoice Line UOM
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
PA: Transfer DFF with PO
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:
Descriptive flexfield segments are not interfaced.
(No value)
Equivalent to No
Internal name: PA_TRANSFER_DFF_PO
PA: Use Auto Invoice Master Program
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:
The PA: Submit Interface Streamline Processes concurrent program does not call the Auto Invoice Master Program.
Internal Name: PA_AR_MASTER_INVOICE_ENABLED
Processing Threshold Category
These profile options enable you to specify time durations, minimum values, and maximum values that affect processing. (Sys Admin = System Administration)
Processing Threshold Category
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
PA: Maintain Unbilled Receivables and Unearned Revenue Balances
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
Security Category
This category includes profile options that control access to data. (Sys Admin = System Administration)
Security Category
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
PA: Cross-Project User- View
Indicates if a user has cross-project view access.
This profile option is optional. Available values are listed below:
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
PA: Task Managers Must Be Project Members
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:
Task managers can be any employee in an enterprise.
(No value)
Equivalent to No
Internal name: PA_TM_PROJ_MEMBER
PA: View All Project Resources
Indicates if view all resources access is granted.
This profile option is optional. Available values are shown below:
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.
Self-Service Interaction Category
These profile options contain default values for self-service pages.
All of the profile options in this category are optional. (Sys Admin = System Administration)
Self-Service Interaction Category
Internal Name: PA_RETAIN_SPREAD_VALUES
PA: Team Home Page Layout
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
PA: Workplan Tasks Default View
This profile option defines the default display view for workplan information on the Tasks page.
Available values are shown below:
The list view is the default view for task information.
This view displays tasks as a list ordered according to outline level.
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
Staffing Defaults Category
These profile options contain default values for staffing functionality. (Sys Admin = System Administration)
Staffing Defaults Category
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
PA: Canceled Assignment Status
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.
PA: Canceled Requirement 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
PA: Canceled Requirement's Candidate 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
PA: Default Calendar
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
PA: Default Starting Candidate Status
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
PA: Filled Requirement 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
PA: Invalid Resource Candidate 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
PA: Project Resource Job Group
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
PA: Staffing Home Default Organization
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
PA: Starting Assignment Status
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
PA: Starting Requirement 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
Utilization Defaults Category
These profile options specify default values for the utilization feature. (Sys Admin = System Administration)
Utilization Defaults Category
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.
Internal name: HR_CROSS_BUSINESS_GROUP
For more information on Cross Business Group Access, see Security, Configuring, Reporting and System Administration in Oracle HRMS.
HR: Enable Security Groups
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.
HR: Security Profile
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
MO: Default Operating Unit
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.
MO: Operating Unit
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.
MO: Security Profile
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
PJI: Debug 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
PJI: Global Start Date Override
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
PJI: Number of Parallel Extraction Programs
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
PJI: Organization Security Profile
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
PJI: Output Destination
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
PJI: Truncate PJI Summary Tables
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
PJI: Use DBI Request Set Generator
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
PSA: Budgetary Control Report Template
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
Profile Options for Integration With Other Products
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.
Payables and Purchasing
PA: Allow Adjustments to Receipt Accruals and Exchange Rate Variance
PA: Allow Override of PA Distributions in AP/PO
PA: Default Expenditure Item Date for Supplier Cost
PA: Default Expenditure Organization in AP/PO
PA: Expense Report Invoices Per Set
Receivables Only
PA: Receivables Invoice Line UOM
AR: Use Invoice Accounting For Credit Memos
AR: Transaction Flexfield QuickPick Attribute
General Ledger
GL: Ledger Name
PA: Allow Override of Budget Accounts
PA: Enable Budget Integration and Budgetary Control Feature
PA: Days to Maintain BC Packets
Internet Expenses
PA: Allow Project-Related Entry in Oracle Internet Expenses
PA: AutoApprove Expense Reports
OIE: Approver Required
OIE: Enable Approver
OIE: Enable Projects
Oracle E-Business Tax
eBTax: Allow Ad Hoc Tax Changes
eBTax: Allow Override of Customer Exemptions
Allow Override of Tax Classification Code
Oracle Time and Labor
PA: Allow Time Entry of Negative Hours
PA: AutoApprove Timesheets
PA: Enable Business Messages on Time Entry
PA: Override Approver
Federal Financials
FV: Federal Enabled
Fremont Corporation: Setting Up Profile Options
Fremont Corporation sets up the following profile options.
Fremont Corporation Profile Options to Control Processing
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
PA: Expenditure Items Per Set
PA: Cost Distribution Lines Per Set
PA: Projects Per Set
Fremont Corporation Profile Options for Integration
To enable Oracle Projects to integrate with other applications, Fremont Corporation sets the profile options shown in the following table:
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
(The unit of measure of Each is first defined in Oracle Receivables)
eBTax: Tax: Allow Ad Hoc Tax Changes
Prevents users from changing tax rates in the Transactions window in Oracle Receivables
eBTax: Allow Override of Customer Exemptions
Prevents users from overriding the default tax exemption on invoice lines in Oracle Projects
eBTax: Allow Override of Tax Classification Code
Allows users to override the default tax classification code on invoice lines in Oracle Projects
AR: Use Invoice Accounting For Credit Memos
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

我要回帖

更多关于 field test是什么意思 的文章

 

随机推荐