The following reports provide cost-related information to Costing users in Oracle Manufacturing Cloud:
Work Order Operational Analysis (A): This report provides detailed information on the operations performed in a work order, including cost-related data, helping costing users analyze production efficiency and associated costs.
WIP Balance by Plant (C): This report gives costing users insight into work-in-progress (WIP) balances for each plant, showing the costs associated with incomplete work orders and materials in the production process.
Incorrect options:
Receipt Accounting Dashboard (B) is used for receipt-related accounting, not work order costs.
Purchase Variance Summary (D) focuses on purchase price variances, not work order-related costs.

In Oracle Manufacturing Cloud, when performing a cost analysis using Cost Planning Scenarios, all components and resources involved in the assembly must be associated with the material cost plan to be included in the rolled-up cost estimates. The reason the extended costs of purchase components (P1 and P2) are not included in the rolled-up scenario is that:
Purchase components PI and P2 are not associated with the material cost plan of the Cost Planning Scenario. This means that although the components are defined in the system, they haven't been linked to the cost planning scenario, so their costs are not included in the rolled-up calculations.
Incorrect options:
Costs for purchase components PI and P2 are not defined in Cost Accounting (A): While defining costs is necessary, the issue here is the components not being associated with the cost plan.
Create Accounting (C) and Create Accounting Distributions (D) are not relevant to the rolled-up scenario in this context, as they relate to the accounting process, not cost planning.

When pick release creates movement requests for project-based work orders, there are several key points regarding expenditure information:
Statement D: The expenditure type and the expenditure organization from the work order are not referenced onto the shop floor movement requests - This statement is correct because the expenditure type and organization are not typically included in the shop floor movement requests. These requests focus more on the material movement aspects, while expenditure details are managed elsewhere in the system.
Incorrect Statements:
Statement A: The expenditure type, date, and organization are derived when interfacing with Costing, which ensures that project-related costs are tracked accurately.
Statement B: The expenditure type for the item is derived based on the default expenditure type in Inventory Management, which is true for how items are picked for a work order.
Statement C: Expenditure type and organization from the work order are referenced in costing, but not directly on movement requests.

User-defined work order statuses provide flexibility in managing the lifecycle of work orders in Oracle Manufacturing Cloud. However, the following is not true:
The system does not automatically update user-defined work order statuses. These statuses are manually updated by users to reflect the work order's progress through custom-defined states.
Correct statements:
Displayed on work order reports: User-defined statuses are visible in work order reports, allowing users to track the status of different orders.
Name changes to system status: It is not recommended to alter system-defined status names as it could disrupt core system processes and workflows.
Searchability of new statuses: User-defined statuses are searchable, making it easier to manage and track work orders.