SAP Note 11860 - Data transfer for functional locations (IL01/IL02).

Symptom

Conceptual design of data transfer (inheritance) is unclear to the customer.

Cause and prerequisites

Option to enter help texts for screens is missing.

Solution

Here is a summary of the concept of data transfer.

Firstly, a distinction should be made between:

1. Default data transfer/forwarding when you create a functional location

2. Individually defined data transfer/forwarding when you create or change a functional location

To point 1: When you create a functional location, the program attempts to calculate a higher-level functional location by generic name. If one is found, it is set automatically. In addition, when creating a functional location, reference can be made to a reference location, which enables further central data maintenance later using the data transfer function. If another functional location is used as a template when you create a functional location, its reference location is transferred if necessary.

The program assumes that, when functional locations are created, the data transfer should be as extensive as possible:

• If a higher-level functional location can be found, all the relevant data from this is transferred (no Customizing option).

• If a reference location is entered when you create a functional location (directly or using the copy reference), its data has priority over data from the higher-level functional location.
  

To point 2: Data transfer can be changed specifically for each functional location and reference location at any time. The following restrictions apply:

• Data from the higher-level functional location or reference location can only be transferred if one is assigned. These assignments can be changed at any time.

• For hierarchical dependencies in the key, the lower-level key can only be transferred like the higher-level one: The maintenance planner group from the reference location can only be copied over if, for example, the PM planning plant from the reference location is also transferred.
  

The easiest way to view the data transfer options for each field is to call up the cursor-specific function 'Data origin... ' for a particular field.

Overview of the dependencies during data transfer:
(Technical field names are specified in parentheses)
Maintenance plant (SWERK) -> Location (STORT) -> Room (MSGRP) -> Plant section (BEBER)
-> PP work center (ARBPL)
-> Company code (BUKRS)
Company code (BUKRS) -> Asset (ANLNR)
Company code (BUKRS) + Business area (GSBER) -> Controlling area (KOKRS)
Controlling area (KOKRS) -> Cost center (KOSTL) -> WBS element (PROID)
-> Standing order (DAUFN)
-> Settlement order (AUFNR)
PM planning plant (IWERK) -> PM planner group (INGRP)

Notes:

• The system ensures that maintenance plant and PM planning plant are in the same controlling area (error message I0231). If maintenance plant and PM planning plant are in different company codes, the system issues the warning I0230. The same checks are made with regard to maintenance plant and the plant of the main maintenance work center.

In the original R/3 design, it was intended to include a function to consider the business area during determination of the controlling area, but this has not yet been possible. Nevertheless, for the time being, the concept of data transfer remains unchanged with regard to the business area: The transfer of the business area from the superior functional location is still a precondition for transferring the controlling area and thereby the cost center and so on.

Additional key words

Program SAPMILO0, subscreen SAPMILA0 7000

Key word: Data transfer.