Search Results populate_default_copy_options

Overview

PA_PROJECT_CORE1 is a core PL/SQL package in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema and holding VALID status in both 12.1.1 and 12.2.2. It encapsulates the low-level programmatic logic used to create, number, copy, and revert project definitions. Its principal business role is to supply the shared services that higher-level APIs and maintenance packages rely upon when a project record must be generated, duplicated, or renumbered — particularly in the context of project copy, project templates, and automatic project numbering schemes.

The package is classified as API classification OTHER rather than as a published public API, indicating that it is an internal implementation component. It sits beneath the public project APIs and is referenced by six other packages, including PA_PROJECT_PUB, PA_PROJECTS_MAINT_PVT, PA_TASK_UTILS, PA_PROJ_ELEMENTS_UTILS, PA_FP_COPY_FROM_PKG, and PA_FP_ORG_FCST_GEN_PUB. This placement confirms it as a foundational utility layer rather than an entry point for direct external calls.

Key Procedures and Functions

The documented interface exposes eight procedures and functions:

• GET_PROJECT_NUMBER_BY_NUMCODE — retrieves the project number associated with a given project number code (numcode), supporting decoding of numbering scheme identifiers into fully qualified project numbers.
• GET_NEXT_AVAIL_PROJ_NUM — determines the next available project number for a numbering scheme, underpinning automatic project numbering at creation time.
• REVERT_PROJ_NUMBER — reverses the allocation of a project number, returning it so that a failed or rolled-back project creation does not permanently consume the sequence value.
• COPY_PROJECT — performs the core duplication of an existing project into a new project record, applying the selected copy options.
• POPULATE_COPY_OPTIONS — populates the copy option structure with the parameters supplied by the caller for a copy operation.
• POPULATE_DEFAULT_COPY_OPTIONS — establishes the default set of copy options when the caller does not supply explicit selections.
• COPY_BUDGETORY_CTRL — copies budgetary control settings from the source project to the target project during duplication.
• GET_MESSAGE_FROM_STACK — extracts the appropriate error message from the FND_API message stack, supporting consistent error reporting to calling packages.

Tables Accessed

Through APPS synonyms, the package reads and writes the tables required to materialise a complete project definition:

• PA_IMPLEMENTATIONS — supplies implementation-level configuration and business group context.
• PA_BUDGET_VERSIONS, PA_BUDGET_VERSIONS-related budgetary control settings — used by COPY_BUDGETORY_CTRL.
• PA_BILLING_ASSIGNMENTS and PA_BILLING_ASSIGNMENTS_S — billing assignment records duplicated with the project.
• PA_CREDIT_RECEIVERS and PA_CREDIT_RECEIVERS_S — credit receiver definitions copied to the new project.
• PA_COST_DIST_OVERRIDES and PA_COST_DIST_OVERRIDES_S — cost distribution override rules.
• PA_EMP_BILL_RATE_OVERRIDES and PA_EMP_BILL_RATE_OVERRIDES_S — employee bill rate override definitions.
• PA_IND_COST_MULTIPLIERS — indirect cost multiplier setup carried into the copy.
• FND_DESCRIPTIVE_FLEXS — descriptive flexfield metadata for project attributes.
• HR_LOCATIONS_ALL, HR_ORGANIZATION_INFORMATION, and HZ_PARTIES — location, organisation, and trading party data referenced during project setup.

Usage Notes

PA_PROJECT_CORE1 is invoked indirectly. The primary callers are PA_PROJECT_PUB (the public project API) and PA_PROJECTS_MAINT_PVT (the projects maintenance private package), which together service the Projects forms and the project definition concurrent programs. PROJECT COPY functionality in the Projects form ultimately routes through COPY_PROJECT and its option-population helpers, while project creation routes through GET_NEXT_AVAIL_PROJ_NUM and, on rollback, REVERT_PROJ_NUMBER.

Because the package is classified as OTHER and is not a public API, custom code should not call it directly. Supported custom development should use PA_PROJECT_PUB and the documented public APIs, allowing PA_PROJECT_CORE1 to remain an internal dependency. Error handling is channelled through GET_MESSAGE_FROM_STACK against the FND_API message stack, so callers must have an initialised API message stack when invoking any routine that can raise a validation error.