Relationship Program Positions and Enterprise Organization (SAP Library

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:

When you create new investment program positions, they inherit their organizational units (for example, company code, cost center) from the nodes of the enterprise organization.
A restructuring of the enterprise organization does not result in duplicate maintenance in the investment program. Changes in the hierarchy of the enterprise organization are reflected automatically in the structure of the investment program. Changes on the nodes of the enterprise organization are passed on to the investment program positions.
You can make assignments to the enterprise organization time-dependent. This means that positions of an investment program can be assigned to different nodes of the enterprise organization at different times, and thereby also have a time dependent assignment to cost centers, for example.

Integration

Recommendation

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 process 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 create a new program position on a node of the enterprise organization
You can assign existing, unassigned program positions to a node of the enterprise organization

Note

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.

This graphic is explained in the accompanying text

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

Caution

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.

Note

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 execute the Open New Approval Year- Repeat Run 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:

When the generation date is in the approval year of the new program, the system uses the generation date.
When the generation date is not in the approval year of the new investment program, the system uses the first day in the approval year of the new program.

Constraints

You cannot process more than one investment program in the enterprise organization at one time.

You cannot edit investment programs in parallel in the enterprise organization and in structure maintenance. The system allows you to change the investment program in structure maintenance, but changes to all program positions that are assigned to enterprise organization nodes are overwritten by the next generation run.

At the present time, you can only generate an investment program after you have created program positions and assigned them to enterprise organization nodes. There is currently no function for automatically creating the program structure and program positions to correspond to an enterprise organization. However, you can Generate Investment Programs from Organizational Units.

Existing investment programs cannot be automatically transferred to the enterprise organization.