Skip to content

Supplier Cost Interface Exceptions No Assignment Too Large


When you enter expenditure items, you charge hours, expenses, or the use of non-labor resources to a project and a task. Oracle Projects validates expenditure items against predefined criteria and any transaction controls and transaction control client extensions that you set up during the implementation of Oracle Projects.

The standard validation process performs the following checks:

      • Expenditure item falls within project dates
      • Project status allows transactions
      • Transaction controls and transaction control extensions allow charges of this type
      • Project allows cross-charges from the user's operating unit in a multi-organization environment
      • Expenditure item falls within task dates
      • Transaction controls and transaction control extensions allow charges of this type
      • Expenditure type is active
    • Existing expenditure item (for adjustments only)
      • Matching expenditure item exists (unless you enter an unmatched, negative transaction)
Oracle Projects may reject expenditure items for the predefined reasons listed below, whether the expenditure was created in Oracle Projects, Oracle Personal Time and Expense, other Oracle Applications, or an external cost collection system. If you receive a rejection reason not included in the list below, check with your implementation team for any rejection reasons specific to your company that were defined in transaction control extensions.
Oracle Projects validates pre-approved expenditure batches as you enter expenditure item details. Expenditures created using Oracle Personal Time and Expense and external cost collection systems are validated during the Submit and Transaction Import processes, but before Oracle Projects creates an expenditure.
Rejection Reason (Error Lookup Code)Troubleshooting TipsExpenditure (timecards, expense reports, usage logs, etc.)
You may receive the following rejection reasons when you use Transaction Import to import an expenditure.
Burdened cost is not valid for the given system linkage (INVALID_BURDENED_AMOUNT) A transaction with an expenditure type class of Burden Transactions should have a burden cost of NULL. For other expenditure type classes, if the transaction source or project does not allow burdening, then they burden cost should equal zero. all
CCID for credit is NULL (INVALID_CR_CCID) The code combination ID for the credit account cannot be NULL for transactions that have already been accounted for in an external system. GL accounted transactions
CCID for debit is NULL (INVALID_DR_CCID) The code combination ID for the debit account cannot be NULL for transactions that have already been accounted for in an external system. GL accounted transactions
Cannot lock original item for reversal
(CANNOT_LOCK_
ORIG_ITEM)
Another user or a process is currently accessing the original item to be adjusted. Try to revise the expenditure item later. all
Cross charge validation failed
(CROSS_CHARGE_
PROJECT_INVALID)
You will get this message only if you have implemented multiple organization support and are using Transaction Import to charge expenditure items to a project owned by an operating unit that does not share your operating unit's set of books, PA period type, and business group. Revise the expenditure item by entering a project owned by an operating unit to which you can charge. all
Different system linkage (DIFF_SYS_LINKAGE) During Transaction Import, Oracle Projects verifies that the expenditure type class of the transaction matches the expenditure type class of the expenditure type. You can either associate the expenditure type class with the expenditure type using the Expenditure Types window, or you can change either the expenditure type or the expenditure type class on the transaction so they form a valid combination. all
Duplicate item (DUPLICATE_ITEM) An expenditure item with the same transaction source and original system reference already exists. Change the transaction source or original system reference of the expenditure item to be imported. all
Employee is mandatory
(EMP_MAND_FOR_
ER/TIME)
Enter information into the employee number field (automatically entered in Oracle Personal Time and Expense). timecards and expense reports
Employee or organization is mandatory
(EMP_OR_ORG_
MAND)
Enter either the employee name and number or expenditure organization in the appropriate expenditure field. all except for timecards and expense reports
Expenditure item date is after the expenditure ending date
(EI_DATE_AFTER_
END_DATE)
The expenditure item date is after the expenditure ending date. Verify that both the expenditure item and the expenditure dates are correct and change, if necessary. all
Expenditure item date is not within the expenditure week (ITEM_NOT_IN_WEEK) Verify that the expenditure item date and the expenditure date are both correct and change, if necessary. You can also create a new expenditure for the expenditure item. timecards
Expenditure organization is not active (PA_EXP_ORG_NOT_ ACTIVE) The expenditure organization is not active or is not within the current expenditure organization hierarchy. all
Expenditure type/expenditure type class inactive (ETYPE_SLINK_ INACTIVE) The combination of the expenditure type and expenditure type class is inactive as of the expenditure item date. Refer to PA_EXPEND_TYP_SYS_LINKS for valid expenditure type/expenditure type class combinations. all
Expenditure type inactive (EXP_TYPE_INACTIVE) The expenditure type has been defined, but it is either not yet effective or has already expired as of the expenditure item date. Refer to the Expenditure Types window to view all valid expenditure types and their effective dates or to change the expenditure type's effective dates. all
GL date is NULL (INVALID_GL_DATE) A transaction that has already been accounted for in an external system must have a GL date. GL accounted transactions
Invalid burden transaction (INVALID_BURDEN_ TRANS) Raw cost and quantity must equal zero or NULL for burden transactions. burden transactions
Invalid employee (INVALID_EMPLOYEE) Oracle Projects does not recognize the employee number. Verify that you have entered the information correctly or add a new employee. all
Invalid ending date (INVALID_END_DATE) The expenditure ending date does not fall on the day of the week defined as your expenditure cycle end day. Refer to the Implementation Options window (Costing) for the valid expenditure cycle start day. all
Invalid expenditure type (INVALID_EXP_TYPE) The expenditure type does not exist. Refer to the Expenditure Types window for a list of all valid expenditure types or to create a new expenditure type. all
Invalid expenditure type class (INVALID_EXP_TYPE_CLASS) The expenditure type class of the transaction is invalid. Refer to PA_SYSTEM_LINKAGES for valid expenditure type classes. all
Invalid expenditure type/system linkage combination (INVALID_ETYPE_ SLINK) The combination of the expenditure type and expenditure type class is invalid. Refer to PA_EXPEND_TYP_SYS_LINKS for valid expenditure type/expenditure type class combinations. all
Invalid non-labor resource (INVALID_NL_RSRC) The non-labor resource does not exist. Refer to the Non-Labor Resources window for a list of all valid non-labor resources or to create a new new non-labor resource. usage logs
Invalid non-labor resource organization (INVALID_NL_RSRC_ ORG) The non-labor resource organization does not exist. Refer to the Non-Labor Resources window for a list of all valid organizations for a particular non-labor resource or to assign a new organization to a non-labor resource. usage logs
Invalid organization (INVALID_ ORGANIZATION) The expenditure organization does not exist. Refer to the expenditure organization hierarchy set up in Oracle Projects to determine all organizations defined as valid expenditure organizations. all
Invalid project (INVALID_PROJECT) The project number does not exist. Refer to the Projects Summary window for a list of all valid projects or to the Projects, Templates Summary window to create a new project by copying an existing project or template. all
Invalid project type (INVALID_PROJECT_ TYPE) The project type for the given project is invalid. all
Invalid task (INVALID_ TASK) The task number does not exist for the project, or the task is not a lowest task. Open your project and choose the Tasks option to view all valid tasks or to create a new lowest task. all
Invalid transaction source (INVALID_TRX_ SOURCE) Oracle Projects does not recognize the transaction source. Refer to the Transaction Sources window for a list of valid transaction sources or to create a new transaction source. all
No open or future PA period for the expenditure item and GL dates (INVALID_PA_DATE) There is no open or future PA period for the given expenditure item and GL dates. GL accounted transactions
Non-labor resource expenditure type different (NL_EXP_TYPE_DIFF) The non-labor resource is not associated with the expenditure type. Refer to the Non-Labor Resources window for a listing of all valid non-labor resources and their expenditure types or to create a new non-labor resource. usage logs
Non-labor resource inactive (NL_RSRC_INACTIVE) The non-labor resource has been defined, but it is either not yet effective or has already expired as of the expenditure item date. Refer to the Non-Labor Resources window for a list of valid non-labor resources and their effective dates or to change the effective dates. usage logs
Non-labor resource mandatory for usages (NL_RSRC_MAND_
FOR_USAGES)
A non-labor resource has not been specified. Enter the non-labor resource name for the rejected expenditure item in your usage log. usage logs
Non-labor resource owning organization mandatory for usages (NL_RSRC_ORG_
MAND_FOR_USAGES)
A non-labor resource organization has not been specified. Enter the appropriate organization name. usage logs
No assignment (NO_ASSIGNMENT) The employee does not have an active assignment to a specific organization and job as of the expenditure item date. Verify the expenditure item date and the employee assignment and make changes, if necessary. You can also refer to the Person Information window for the employee's organization and job assignments and their effective dates, to change an assignment's effective dates, or to create a new assignment. all
No matching item (NO_MATCHING_ ITEM) If the transaction is an adjustment with a negative quantity, and the unmatched negative flag is not set to Yes, an original, approved, unreversed expenditure item matching the transaction's employee/organization, item date, expenditure type, project, task, reversing quantity, reversing cost (if loading costed items via Transaction Import), and non-labor resource and non-labor organization (for usages) must exist. Also, the matching expenditure item must have been originally loaded from the same transaction source. If more than one item matches the original item, Oracle Projects uses the first one that was created. adjusting transactions
No raw cost (NO_RAW_COST) Raw cost amount is missing. Expenditure items with a costed transaction source must include this information. all
Organization does not own the non-labor resource (ORG_NOT_OWNER_
OF_NL_RSRC)
The non-labor resource has not been assigned to the non-labor resource organization as of the expenditure item date. Refer to the Non-Labor Resources window for a list of all organizations associated with the resource or to associate a new organization with the resource. usage logs
Project is not chargeable (PA_PROJECT_NOT_ VALID) The project is a template; has a transaction control that does not allow charges; does not share a business group, set of books, and PA period type with the user's operating unit; or the project status does not allow new transactions. all
Project does not allow burden transactions (PROJ_NOTALLOW_ BURDEN) Burden transactions are not allowed for this project. burden transactions
Transaction source does not allow burden transactions (TRXSRC_NOTALLOW_BURDEN) Burden transactions are not allowed for transactions you import from this transaction source. burden transactions
Transaction source inactive (TRX_SOURCE_ INACTIVE) The transaction source has been defined, but either is not yet effective or has already expired as of the expenditure item date. Refer to the Transaction Sources window for a list of all valid transaction sources and their effective dates or to change the effective dates. all
You may receive the following rejection reasons when you use Transaction Import to import an expenditure or when you enter an expenditure in Oracle Applications (pre-approved expenditures in Oracle Projects, purchase orders and requisitions in Oracle Purchasing, or supplier invoices in Oracle Payables). You may also receive additional rejection reasons if your company has implemented transaction controls.
Project/Task validation error (PA_EXP_INV_PJTK) The project or task does not exist, or the task does not belong to the project. Change the expenditure item's project or task. all
Project/Task-level expenditure transaction control violated (PA_EXP_PJ/TASK_TC) The transaction violates the project- or task-level transaction controls defined for the project. Refer to the Transaction Controls window (under Project Options or Tasks, Options) for a list of the transaction controls on the project or task or to change the transaction controls to allow you to charge the expenditure item. You can also charge the expenditure item to another project or task. all
The task is not chargeable (PA_EXP_TASK_ STATUS) The task's Allow Charges flag has not been enabled. Enable this flag from the task's Task Details window or charge the item to another task. all
Expenditure item cannot be charged to a Closed project (PA_EX_PROJECT_
CLOSED)
Project status does not allow transactions to be charged to this project. Change the status of the project or charge the expenditure item to another project. all
Expenditure item date is not within the active dates of the task (PA_EXP_TASK_EFF) Change the expenditure item date or the task's active dates, or charge the expenditure item to another task. all
Expenditure item date is not within the active dates of the project (PA_EX_PROJECT_ DATE) Change the expenditure item date or the project's active dates, or charge the expenditure item to another project. all

If you cannot access any of the windows mentioned in the table above to change project or expenditure information, contact the project's key member and request that certain information be changed.

Skip Headers

Profile 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

  • 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.

Specify Profile Options

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.

Multi-Organization Considerations for Profile Options Values

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

Descriptions of Profile Option Categories and Profile Options

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.

Accessibility Interaction Category

Profile options in the Accessibility Interaction category control user access to data. (Sys Admin = System Administration)

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

PA: Allow Future-Dated People as Project Members

Specifies whether users can include future-dated employees as key members.

This profile option is optional. Available values are listed below:

YesDefault value is Yes. Users can include future-dated employees as key members.
NoUsers 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:

YesTasks displays the Find Tasks window, and Oracle Projects automatically queries the top tasks (WBS Level = 1)
NoTasks 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:

StandardSpreadsheet 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.
OnlineSpreadsheet 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:

StandardStructure 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.
OnlineStructure 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:

YesWork types are required for all expenditure items
NoWork 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:

  1. Enter an amount type for all existing work types.

  2. Define a work type for all existing project types.

  3. 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

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:

YesUser can tab to the overflow region.
NoUser 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)

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

PA: Allow Override of Budget Accounts

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:

YesUsers can manually override accounts.
NoUsers 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:

YesThe 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.
NoThe 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)

PA: Commit Size for Archive and Purge 1000No 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

PA: Commit Size for Archive and Purge

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

PA: Cost Distribution Lines Per Set

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

PA: Expenditure Items 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 Costsprocess 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

PA: Expense Report Invoices 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

PA: Projects 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

Costing Transactions - Processing Category

Profile options in this category enable you to specify the behavior of the costing processes. (Sys Admin = System Administration)

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 3View 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

PA: Create Incremental Transactions for Cost Adjustments Resulting from a Burden Schedule Recompilation

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.

YesOracle Projects creates incremental accounting lines to post the difference between the original and new burden cost amounts.
NoOracle 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: Setting Up Budgetary Controls.

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.

YesEnhanced period processing features are enabled in Oracle Projects.
NoEnhanced 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.

YesOracle Projects maps summary burden transactions to the same resource class as their source raw cost transactions.
NoOracle 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:

YesYou can access retirement cost processing windows and features.
NoYou 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:

YesTransaction is billable based on the assigned work type
NoTransaction 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)

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

PA: Display Terminated Employees: Number of Days

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

PA: Global Week Start Day

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.

PA: Require Assignment and Project Date Validation

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:

YesThe 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.
NoNo validation is done
WarningUser 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)

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

PA: Debug Log Directory

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:

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

PA: Debug Mode

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:

YesSystem is operating in debug mode
NoSystem 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:

YesThe system records time taken by the summarization processes.
NoThe 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:

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

Deployment - Licensing and Implementation Category

This category includes profile options that control access to products based on licensing or implementation options. (Sys Admin = System Administration)

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

PA: Enable Budget Integration and Budgetary Control Feature

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:

YesThe budgetary control windows and processes are displayed.
NoThe budgetary control windows and processes are not displayed.

Internal name: PA_BC_ENABLED

For more information, see: Setting Up Budgetary Controls.

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:

YesMicrosoft Excel is integrated with Projects for budgeting and forecasting.
NoMicrosoft 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:

YesIn addition to Project Costing functions, Oracle Projects allows you to set up contract projects and perform all Project Billing functions.
NoOnly 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:

YesOracle 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

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:

YesOracle 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

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:

YesOracle Projects allows you to perform all Project Management functions.
NoYou 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:

YesOracle Projects allows you to perform all Project Resource Management functions.
NoYou 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:
  1. Enter an amount type for all existing work types.

  2. Define a work type for all existing project types.

  3. 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

(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:

YesOracle Project Costing is installed.
NoOracle 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:

YesThe Upgrade check box is displayed.
NoThe 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:

YesOracle Projects allows you to perform all Project Portfolio Analysis functions.
NoYou 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: Define Portfolio Organization Hierarchy.

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)

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

PA: Enable Long List of Resource LOVs

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:

YesUsers can enter reduction criteria when they query the Resource Name field in the Budget Lines window.
NoAll 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:

YesYou can enter an overriding approver for timecards in Oracle Time and Labor.
NoYou 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:

All TasksDisplays the entire WBS of the selected project
Chargeable TasksDisplays only the chargeable tasks of the selected project
Lowest TasksDisplays 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)

PA: Default Expenditure Organization in AP/PO No Default Update Update Update Update Update

PA: Default Expenditure Organization in AP/PO

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

Other Defaults Category

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)

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

PA: Default Burden Schedule Type

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:

FirmFirm schedule type
ProvisionalProvisional 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:

YesBy default, any new project is public sector
NoBy 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:

YesDescriptive flexfield segments are interfaced.
NoDescriptive 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)

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

PA: Allow Adjustments to Receipt Accruals and Exchange Rate Variance

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:

YesAdjustments are allowed.
NoAdjustments 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: