How To Fix BP165 - Unit costing is not allowed in plan integrated objects

BP165 - Overview

• Message type: E = Error

• Message class: BP - Budgeting and planning

• Message number: 165

• Message text: Unit costing is not allowed in plan integrated objects

What causes this issue?

Unit costings are only possible in orders/WBS elements where plan
integration is not active.

System Response

Choose the paths shown to check whether the plan integration indicator
is set:

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

in an order type
(Controlling -> Overhead cost controlling -> Overhead cost orders ->
Order master data -> Define order types
in a project profile
(Project System -> Project planning -> Costs -> Basic settings ->
Activate plan integration in the project profile.

How to fix this error?

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BP165 - Unit costing is not allowed in plan integrated objects ?

  The SAP error message BP165, which states "Unit costing is not allowed in plan integrated objects," typically occurs in the context of planning and costing in SAP, particularly when dealing with integrated planning scenarios. This error indicates that the system does not allow unit costing for certain planning objects that are integrated with other components or modules.
  
  Cause:
  
  
  Integrated Planning Objects: The error usually arises when you are trying to use unit costing in planning objects that are not designed to support it. This can happen if the planning object is linked to other modules (like production planning, material management, etc.) that do not allow unit costing.
  
  
  Configuration Settings: The configuration settings in the system may not permit unit costing for the specific planning scenario you are working with. This could be due to settings in the controlling area, cost center, or other related configurations.
  
  
  Data Type Mismatch: There may be a mismatch in