The managing (owning) organization of a project. Use the organization for reporting and AutoAccounting purposes. You can choose any organization that has the following characteristics:
The organization belongs to the project/task organization hierarchy assigned to the operating unit.
The organization has the project/task owning organization classification enabled.
The project type class is permitted to use the organization to create projects. This permission is determined when you define the organization.
The organization is active as of the system date.
See: Organizations.
When you attempt to change the organization on a project or task, or create a project template, the system calls the Verify Organization Change Extension.
You can override the default logic in the extension in one of the following ways:
Have your System Administrator assign the function Projects: Org Update: Override Standard Checks to your responsibility. See: Function Security: The Building Block of Oracle Projects Security.
Modify the logic in the Verify Organization Change extension. See: Client Extensions, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
If the change is allowed, Oracle Projects displays a dialog box when you save or exit the record. The dialog box asks if you want to mark existing expenditure items on the project. If you select Yes, the current date is used as the effective date of the change.
Note: If your user responsibility excludes the function Expenditure Inquiry: Adjustments: Recalculate Cost and Revenue, Oracle Projects does not display the dialog box and does not mark the items for recalculation.
If you need to change the owning organization for existing expenditure items on a project, you can use the Mass Update Batches window. See: Mass Update Batches.
If you need to change the owning organization on multiple projects and tasks, you can use the Mass Update Batches window to create a batch of projects and tasks to update. See: Mass Update Batches.