Logbook synchronization

The logbook technical object hierarchy is synchronized with the actual technical object hierarchy. If a change is made to the technical object structure, this change is reflected immediately in the Logbook application when the logbooks are reselected. There are two possible modes for running the logbook application.

If you want to use the synchronous logbook object, you must run report DIACL_CUST_LBK_SYNC_MODE. This clears the relations set for the sub-logbook nodes in the database. You access this report in Customizing under  Plant Maintenance and Customer Service Maintenance and Service Processing Logbook Display Synchronized Logbooks.

Note that this program acts like a switch. Once you have run the program for synchronizing logbooks, it cannot be reversed.

Logbook Options

You can create and hide logbooks in the master data for equipment and functional locations:

To view the new subscreen containing these options, in the view profile for technical objects, you must add screen 141. You do this in Customizing under  Plant Maintenance and Customer Service Master Data in Plant Maintenance and Customer Service Technical Objects General Data Set View Profiles for Technical Objects.

Update maintenance work order with project information

In the MEB, when orders are created for a revision with WBS elements, the WBS element is updated on the Location tab page as well as the Additional Data tab page. Previously, you could only see the updated WBS element on the Additional Data tab page and you had to manually enter the WBS element on the Location tab page. To enable the WBS element information to be copied to the Location tab page, you use user parameter DIWPS_WBS_LOC. This parameter must be defined in the user profile as 'X'. If you do not want to enable this function, do not define this parameter in the profile.

Authorization object check for PM technical objects in the MEB

Users with no authorizations for an authority group in a technical object (authorization object I_BEGRP) are restricted access to that technical object. This is done to restrict user access to some 'sensitive' technical objects, for example, a part inside a nuclear engine. These restrictions are also inherited by objects such as notifications and orders which are created for these technical objects. In core transactions for the maintenance of notifications and orders such as IW22/ IW32 these checks were already in place, but were not previously available in the MEB.

Authorization checks are now run on revisions, notifications and order objects in MEB and an authorization error is displayed on further processing of these objects. The checks are implemented in all the three work areas in the MEB.

In the notification work area, if the notification selection involves notifications for which a user has insufficient authorizations, then these notifications are removed from the selection.

In the revision work area, if the revision selection involves revisions for which the user has insufficient authorization, then such revisions are removed from the selection.

If a revision has one or more notifications assigned to it and the user does not have authorization to view all the notifications then those notifications are not shown below the revision. The same happens for orders below a revision. Such revisions which have partial data are always seen in display mode. No further planning can be done by the user on these revisions.

In the planning board, the unauthorized revisions and technical objects cannot be seen.