The project requirements work area is a work area that allows you to define and manage requirements for your projects using various methods and sources. Requirements are statements of needs or expectations that must be met by the project outcome. Backlog items are a type of requirement that are used for agile projects that follow an iterative and incremental approach. Three of the tasks that can be performed using the project requirements work area are:
creating projects and tasks in the context of backlog items: This task allows you to create new projects and tasks or link existing projects and tasks to backlog items. This helps you to plan and execute the work that is required to fulfill the backlog items.
creating issues for the backlog items: This task allows you to create new issues or link existing issues to backlog items. Issues are problems or risks that affect the progress or outcome of a project or requirement. This helps you to track and resolve the issues that are related to the backlog items.
tracking backlog item status from the requirement storyboard: This task allows you to view and update the status of backlog items from the requirement storyboard. The requirement storyboard is a graphical representation of the progress and completion of backlog items using various stages and lanes. This helps you to monitor and control the delivery of backlog items. Adding scrum master to backlog items and creating change orders for the backlog items are not tasks that can be performed using the project requirements work area. Adding scrum master to backlog items is a task that can be performed using the project team work area, as scrum master is a role that is assigned to a project team member who facilitates and coordinates the agile project activities. Creating change orders for the backlog items is a task that can be performed using the project change management work area, as change orders are documents that capture and approve changes to a project scope, schedule, or budget. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-execution.html#OAPFM2356321

The Cost Collection Flexfield is a descriptive flexfield that captures additional information about project costs. It has three core attributes that are required for every cost transaction: Billable Flag, Expenditure Type, and Capitalizable Flag. These attributes can be derived during import if not explicitly entered in a transaction document, based on various rules and sources such as expenditure type defaults, project type defaults, transaction source defaults, etc. Funding Source and Work Type are not core attributes of the Cost Collection Flexfield, but context-sensitive segments that can be optionally enabled for certain transaction sources or business units. These segments capture additional information about how the costs are funded or what type of work is performed. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-costs.html#OAPFM2356141

The Resource Qualification Score is a percentage that indicates how well an individual matches the qualifications required for a resource request. An individual's score is 100% if either of the following conditions are met:
The resource request has a qualification, but no proficiency is specified, and the resource has the qualification. This means that any level of proficiency is acceptable for the qualification.
The resource request has a qualification with a specified proficiency and the resource has the qualification that meets the specified proficiency. This means that the resource has the exact level of proficiency required for the qualification. An individual's score is not 100% if the resource request has a qualification with a specified proficiency and the resource does not have the qualification or has a different level of proficiency than required. In this case, the score is calculated based on how close the resource's proficiency is to the required proficiency. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-resources.html#OAPFM2356001

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/fapfm/implementing-project-execution-management-applications.html#FAPFM1724547 Topic - Submitting the Process to Maintain Project Resource Search Index: Procedure Submit the Maintain Project Resource Search Index job set to update the resources that appear on the Search and Evaluate Resources page when a resource manager searches for resources to fulfill project resource requests. The job set consists of a set of processes that facilitate efficient and rapid searches for qualified resources.
Resource managers can't search for resources or view resource details if the search index isn't available for a project resource request with qualifications or keywords. For project resource requests without qualifications and keywords, resource managers can search for and evaluate resources based on resource availability even if the search index isn't current or available.
Caution: The search index isn't available if the Maintain Project Resource Search Index job set process fails, or while the process is running.

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapfm/project-foundation-configuration-define-project-resource-breakdown-structures.html#OAPFM180158_2 Why can't I find persons in the list of resources when I enter team members, planning resources, or person rate schedules?
You can't find persons in the list of resources when you enter team members, planning resources, or person rate schedules in the following situations:
The administrator didn't assign a department while creating users. Persons must have an active assignment and be assigned to a department in Oracle Fusion Human Capital Management before they can be added as team members or entered as resources on the planning resource breakdown structure or person rate schedule.
The resource isn't active in Oracle Fusion Human Capital Management because the current date is before the effective date of the resource. If you want to include persons who will start in the future, select the Include people with future-dated effective start dates option when you search for the person.
Persons assigned as project managers aren't active as of the project start date.
The assignment of the person is terminated, and an appropriate value isn't set for the number of days to display people with terminated assignments. You can set the profile value appropriately at the site profile level using the Specify Number of Days to Display People with Terminated Assignments task in the Setup and Maintenance work area.