Use

When maintenance objects are distributed, the special features described below apply.

Prerequisites

You are familiar with the overview of distributed objects as well as cross-system processes for maintenance .

Features

Note the following special features:

Distribution of Technical Objects

Distribution of Change Authorizations

Distribution of Transaction Data

Maintenance Plan Distribution

Copying Conversion Rules for Work Centers

Addition of Objects for the Distribution Scope

Distribution of Customer Enhancements

Rule-Based Reduction of Data Volume

You can use the Business Add-In /ISDFPS/PM_CO_DATAto control the distribution of dependent CO data. For this, see Customizing for Defense Forces & Public Security → Distributed System Landscape → Application-Specific Settings → Distributed Maintenance → BAdI: Define and Check CO Data Transfer

You can use the Business Add-In /ISDFPS/BADI_PM_OROPER_PERNR to control the distribution of personnel numbers that are assigned to a maintenance order. For this, see Customizing for Defense Forces & Public Security → Distributed System Landscape → Application-Specific Settings → Distributed Maintenance → BAdI: Delete Personnel Numbers from Operations in the Distribution

Historical time segments of equipment are not included in theFOXexplosion, meaning that dependent data is not distributed. The relevant maintenance applications are not affected by the absence of this data.

In Customizing, you can use the PM_NOT_ORD_HISTswitch to specify whether maintenance notifications and maintenance orders for historical installation locations are to be distributed . To do so, choose Defense Forces & Public Security → Distributed System Landscape → Setting Options for Distribution.

The following data for maintenance work centers is distributed:

Basic data

Default data

Capacity data

Calculation data

Scheduling

Dependent data from maintenance work centers assigned to force elements that were determined by maintenance relationships is not distributed.

The following data for functional locations is distributed:

General data (for example, classification, object type, manufacturer data)

Location data, excluding address data

Organizational data

Hierarchy of functional locations and associated equipment

Partnersfor equipment, functional locations, maintenance notifications, and maintenance orders are distributed. In theFOXexplosion for partners, only the data environment for the partner types work center, customer, and vendor is considered.

For all other partner types, only information is distributed but not the corresponding data environment. This allows the partners to be displayed in the respective target system. If data is missing, the decentralized system issues warning messages in change transactions; the central system checks the data if the user is on the Partner Data tab page. You must correct any incorrect data (exception: data for the user object type).

In theFOXexplosion for approvals, the corresponding approval object and the assigned class are determined along with the characteristic value. Plausibility is not checked when approval data is posted.

In Customizing you can use the PM_TASK_LIST switch to control whether maintenance task lists for material are to be distributed . To do so, choose Defense Forces & Public Security → Distributed System Landscape → Setting Options for Distribution.

The system provides the Generic Distribution of PM Objects application (transaction /ISDFPS/PMDIS2) as an administration tool for distributing objects from the maintenance area directly to another system.

For the special features of the Technical Status, see Distributed Maintenance .

If you want to distribute site equipment in a distributed system landscape and use systems with an earlier release in which the Site Equipment function is not available, seeSAPNote 1352791

The system prevents maintenance orders, maintenance notifications, equipment, functional locations, and measurement documents that are business completed in the central system, or for which the deletion indicator was set in the archiving process, from being included in further distribution processes.

For this, report /ISDFPS/PM_IBDU2DECENTRAL distributes the information about the status of the objects (table IBDU) from the central system to all systems involved. If the information fails to send, but the values in table IBDU were already deleted, you can use report /ISDFPS/PM_IBDU_ENTRIES_INSto recover these values.