Relationship Program Positions and Enterprise Organization 
Use
Maintaining investment programs in the enterprise organization hierarchy offers the following advantages over maintaining the investment program structure:
Integration
SAP recommends that you always use this function together with a Controlling (CO) hierarchy (cost center hierarchy or profit center hierarchy). In this way, you ensure that the structure of your investment program corresponds to that CO hierarchy. You maintain the enterprise organization in Controlling, not in Investment Management.
Features
Creating and Assigning Program Positions
You assign investment program positions to nodes of the enterprise organization. You can
For any given point in time, only one position of a given investment program can be assigned to each node of the enterprise organization. However, another program position of a different investment program can be assigned to the node of the enterprise organization at the same time. In a detail screen, you can display all enterprise organization nodes that are valid in a given time period.
When you create new program positions, the system initially treats them as top positions (that is, program positions without any program positions above them in the hierarchy). They are also displayed as such in structure maintenance. The system does not generate a new program structure, in which the newly created program positions are also displayed, until after the next generation run and subsequent saving. The same also applies to all other changes in the assignments between program positions and enterprise organization nodes.

Assignment of Program Positions to Enterprise Organization Nodes and Inheritance of Organizational Units

You are only allowed to use transactions for the enterprise organization and structure maintenance for editing the program hierarchy. Other transactions, such as those of the Personnel Management component are not allowed.
Deletion of Program Positions and Assignments
You can delete both the assignments of program positions to enterprise organization nodes (that is, make time limits on the assignment) as well as the program positions themselves. You can only delete program positions that have neither subordinate objects (measures, appropriation requests or other program positions) nor any budget.
Organizational Units and Master Data
During each generation run, the system automatically copies the organizational units from the enterprise organization nodes to the program positions assigned to them. The organizational units then cannot be changed on the program positions. The system adopts any changes that you make in structure maintenance during the next generation run. The master data that is copied from parent positions (superior program positions) serves as default values that can be changed.

Changes in Controlling (CO) (for example, assignment of company code to enterprise organization nodes) are not adopted immediately by the program positions. The system does not update the organizational units on the program positions until the next generation run.
Fiscal Year Change
First carry out the Open a New Approval Year from the Enterprise Organization function. If there is no program definition yet, the system creates one. Then choose the Carryforward of Measures, Approp. Requests and Values function. During the fiscal year change, the system uses the same logic for the inheritance as it does during the generation run in the enterprise organization. The difference is that the system creates a new investment program for the new fiscal year (target investment program) and assigns the program positions to the enterprise organization nodes.
Key date for the inheritance of organizational units:
Constraints