Developing a Cross-Component Concept 

Use

If you want to implement specific components of the R/3 System, you must define the organizational units of a component in line with the requirements of the specific application area.

 

If, for example, you implement the component Financial Accounting (FI) first, the organizational unit company code is set up in accordance with the requirements of Financial Accounting and external accounting. If you implement other components of the R/3 System at a later stage, you may have to redefine the company code structure in order to meet different requirements.

To avoid unnecessary changes in the organizational structure of an R/3 System, it makes sense to develop an organizational concept for the entire R/3 System before configuring the different application components.

 

 

Integration

When you are developing a cross-component, organizational concept take reporting, business process, master data and legal requirements into account. Select the cross-component business processes on the basis of the organizational concept. The components are then configured based on these business processes.

Select the concepts for the organizational structure and the R/3 business processes on the basis of the integration requirements of the entire system. When you configure components account the R/3 System takes account of detailed requirements of the different application components in the R/3 System.