Show TOC

 Change Authorization

Use

In a distributed system environment, technical object data must always have a consistent status and can therefore be changed in one location only. This applies to objects such as equipment, functional locations, maintenance plans, measuring points, orders, notifications, revisions, and work centers. For measurement documents, see Measurement Documents in Distributed Systems .

When you call a transaction that allows changes to maintenance objects, the system checks whether you have the relevant authorization for processing data. You can change data only if this check is successful.

In a standalone system, a consistent status is attained using SAP lock management, whereas in multiple system scenarios it must be possible to manage authorization. This is done using the change authorization function, with which you can monitor and define the system in which an object can be changed. Change authorization can be assigned in several ways.

If you relocate a technical object (change of utilizer) across systems (for example, using a purchase requisition), the system automatically forwards the change authorization with all other relevant equipment data when the goods issue is posted. This is an implicit transfer of change authorization.

If you forward notifications and orders to another responsible work center in another logical system, the change authorization is also forwarded automatically if this system is the operational system of the force element to which the work center is assigned.

You can also transfer change authorization manually using a transaction. This is an explicit transfer of change authorization (holder change).

Note Note

Note that the change authorization is only a technical function and does not check authorization in the sense of user and role authorizations.

End of the note.
Information Function for Change Authorization

You can use reports in the central system to monitor the following at all times:

  • Which change authorizations were forwarded?

  • Which logical system currently contains the change authorization for a technical object?

  • Which objects have change authorization in the current logical system?

To be able to provide this information, the central system is informed every time a change authorization is transferred. This information is distributed from the central system to the relevant systems (utilizer system, owner system, holder system).

Changing the Technical Status

The technical status for master equipment (for example, an aircraft) must be changed in the logical system of the master equipment to ensure that the technical status is determined consistently. Changing the technical status is therefore allowed only in the system containing the change authorization for the master equipment.

Restricting Change Authorization

You can use the Limit Change Authorization Business Add-In (/ISDFPS/PM_CP_CHECK) to restrict change authorization functions to suit your specific needs. In Customizing for Defense Forces & Public Security , choose Start of the navigation path Maintenance Next navigation step Business Add-Ins. End of the navigation path

Prerequisites

  • In terms of system architecture, you are familiar with the basics of distributing data to decentralized systems; see Distribution to Decentralized Systems .

  • You have configured the required settings in Customizing for Defense Forces & Public Security under Start of the navigation path Distributed System Landscape Next navigation step Application-Specific Settings Next navigation step Distributed Maintenance End of the navigation path . You have, for example:

    • Assigned the UPS package types ( Assign UPS Package Types activity (view /ISDFPS/CPMUTYP)).

    • Defined the required settings for alternative data transport ( Set Up Alternative Data Transport activity (view cluster /ISDFPS/PMDISA)).

      Also see Distribution of Change Authorizations .

Activities

Initial Activation of Change Authorization

When you first set up the change authorization function in an operational system, you need to use report /ISDFPS/PM_CP_GENER ( Change Authorization: Initial Setup ) in the central system to generate the required data from the existing dataset. For more information, see the report documentation.

Manual Transfer of Change Authorization

You can use the Forward Change Authorization transaction to explicitly transfer the change authorization. This is possible only in the system in which the change authorization currently exists.

From the SAP Easy Access menu, choose Start of the navigation path Logistics Next navigation step Plant Maintenance Next navigation step Distribution Next navigation step Forward Change Authorization End of the navigation path (transaction /ISDFPS/PMCP1). On the initial screen, specify the object data and the logical system to which the change authorization is to be forwarded (receiving system). When you choose Execute , the system transfers the change authorization and subsequently issues a log of all processing steps performed. You can use the Refresh pushbutton to update the displayed data. You can also display a detailed log for each processing step by choosing the status icon.

If you have to resend the data forwarded to a receiving system, you can access this data in the Monitor “Forward Change Authorization” (see the Information Functions section below ). The data is provided in ZIP format.

You can use the user parameter PCP ( PC Path Name ) to define the storage path of the forwarded data in the receiving system specifically for the user. Enter the required path as a parameter value. If you do not enter a path, the system uses the SAPGUI work directory as a default value.

Transfer of Maintenance Objects Without Simultaneous Forwarding of Change Authorization

If you want to distribute maintenance objects without distributing the change authorization at the same time, you can use the Generic Distribution of Maintenance Objects application. From the SAP Easy Access menu, choose Start of the navigation path Logistics Next navigation step Plant Maintenance Next navigation step Distribution Next navigation step Generic Distrib. of Maint. Objects End of the navigation path (transaction /ISDFPS/PMDIS2).

Forwarding Maintenance Objects by Data Carrier (Alternative Data Transport)

If there is no data link between the systems involved, you can use the following applications to forward technical objects using data carriers (for example, DVD). From the SAP Easy Access menu, choose Start of the navigation path Logistics Next navigation step Maintenance Next navigation step Distribution Next navigation step Alternative Data Transport End of the navigation path :

  • Transaction /ISDFPS/PMDIS3: Alternative Data Transport: Outbound Processing

    You use this transaction to start the /ISDFPS/PM_ALT_DATEN_EXP report, which you use to transfer the selected objects, including the relevant change authorizations, to a data carrier.

  • Transaction /ISDFPS/PMDIS4: Alternative Data Transport: Outbound Processing Without Change Authorization

    You use this transaction to start the /ISDFPS/PM_ALT_DATEN_GEN_EXP report, which you use to transfer the selected objects to a data carrier without the relevant change authorizations.

  • Transaction /ISDFPS/PMDIS5: Alternative Data Transport: Inbound Processing

    You use this transaction to start the /ISDFPS/PM_ALT_DATEN_IMPORT report, which you use to import objects transferred to the data carrier to the target system.

Information Functions
Monitoring Change Authorization Transfer

The report for transferring change authorizations provides an overview of which change authorizations were forwarded.

From the SAP Easy Access menu, choose Start of the navigation path Logistics Next navigation step Maintenance Next navigation step Distribution Next navigation step Monitor “Forward Change Authorization” End of the navigation path (transaction /ISDFPS/PMDISRUN1). Enter your selection data in the Data Selection dialog box if required and choose Execute . The system issues a list of all existing data on transferred change authorizations.

Change Authorization for an Object in the Logical System

You can use the transaction Objects with Change Authorization in System (transaction /ISDFPS/PMCP_OBJ) to determine which objects in the current logical system have change authorization.From the SAP Easy Access menu, choose Start of the navigation path Tools Next navigation step Administration Next navigation step DFPS Administration Support Next navigation step Distribution Next navigation step Objects with Change Authorization in the System. End of the navigation path

Required Resetting of Change Authorizations

In an emergency, you can use the central system to reset change authorizations forwarded to logical systems. This may be necessary if, for example, the change authorization was submitted for an object but not transferred to another logical system.

Caution Caution

Use the following reports only if it is absolutely necessary, otherwise the system will contain inconsistent data for change authorizations.

End of the caution.

You can use the following reports to reset the change authorization for individual objects or entire logical systems for the central system:

  • /ISDFPS/PM_CP_EMRNCY_CORR_OBJ

    Reset change authorization for individual objects

  • /ISDFPS/PM_CP_EMRNCY_CORR_SYS

    Reset change authorization for entire systems

Deleting Runtime Data

The /ISDFPS/PM_DIS_RUN_REORG report is available for deleting runtime data that is no longer required to transfer the change authorization. The system creates the runtime data if change authorizations are transferred. A large quantity of runtime data can affect the performance of the monitor for forwarding the change authorization (transaction code /ISDFPS/PMDISRUN1). This report deletes all runtime data up to a specified key date. You can run the report in test mode. If you run the report in forced mode, the report also deletes the data for which it determined errors during deletion. After the report has run, all deletion processes are displayed in a log.

Automatic Transfer of Change Authorization to the Central System

In Customizing, for orders and notifications , you can specify how many days after the technical completion of these objects the change authorization is automatically transferred from the decentralized system to the central system. The transfer of the change authorization to the central system, for example, is a prerequisite for the archiving of orders and notifications.

For each individual order and notification type, you can specify a retention period in days after which the change authorization is automatically transferred to the central system. In Customizing for Defense Forces & Public Security , choose Start of the navigation path Distributed System Landscape Next navigation step Application-Specific Settings Next navigation step Distributed Maintenance Next navigation step Define Retention Period of Orders End of the navigation path (view /ISDFPS/V_CP2CWO) or Define Retention Period of Notifications (view /ISDFPS/V_CP2CNO).

To automatically transfer the change authorization to the central system, you must schedule report /ISDFPS/PM_CP2CENTRAL.

Business Completion of Orders

The automatic transfer of the change authorization to the central system enables the business completion of an order without first having to manually retransfer the change authorization from the decentralized system.