Logbook

Use

All data is entered in the Logbook application for maintenance tasks executed to support flight operations. Flight data, such as flight times and the number of takeoffs and landings, is stored in the logbook in the form of measurement documents and faults are stored in the form of maintenance notifications. This makes it possible to document, monitor, and control the entire maintenance process.

Integration

The L ogbook is a DFPS-specific functional addition of the L ogbook application from the SAP for Aerospace & Defense industry solution .

You can use the L ogbook of the industry solution to:

  • Enter defect information

  • Enter operating data

  • Monitor received defects/assign solutions

  • Generate materials and capacity requirements

  • Complete maintenance procedures

  • Defer defects

  • Confirm completion of maintenance procedures

For more information about the Logbook , see SAP Library under Start of the navigation path SAP ERP Next navigation step SAP ERP Central Component Next navigation step SAP Discrete Industries and Mill Products Next navigation step SAP for Aerospace & Defense Next navigation step Maintenance, Repair, and Overhaul(MRO) Next navigation step Maintenance andService Processing Next navigation step Logbook End of the navigation path .

Prerequisites

You have familiarized yourself with the functions of the Logbook of the SAP for Aerospace & Defense industry solution.

You have configured all required DFPS-specific Customizing settings in the following IMG activity: Start of the navigation path Defense Forces & Public Security Next navigation step Support for Flight Operations Next navigation step Define Settings for Logbook End of the navigation path (view /ISDFPS/VDFPSK50). You have to carry out the following actions in this IMG activity:

  • Activate the DFPS menu in the Logbook application

  • Activate the automatic insertion of the required objects in the logbook, for example measurement documents

  • Activate the display of details about the master equipment as they are displayed on the Op. Equipment tab page in the Change Equipment transaction (transaction IE02),

  • Define notification types for the logbook entries Flight and Ground

You have to set the following switches:

LBK_DFPS_MENU - Activate Extended Menu

If this switch is set to “X”, the environment menu is displayed in the Logbook application. You can navigate from here to the following applications of support for flight operations: Flight , Flight Plan , Event Monitor , Status Board , Technical Status Overview , and Controlled Usage Rate .

LBK_LINK_FL – Activate Automatic Insertion of Flights in Logbook

If this switch is set to “1”, flights generate a logbook entry for the assigned aircraft automatically. This entry is not removed or reassigned if the flight is changed. If you change the assigned aircraft, this creates a new logbook entry for this aircraft and flight. If you want to use customer-specific implementations to automatically insert flights, you have to deactivate this switch by leaving it blank .

LBK_LINK_MD - Activate Automatic Insertion of Measurement Documents in Logbook

If this switch is set to “1”, measurement documents are automatically sorted by date in the logbook entries of type Flight for the corresponding aircraft. If the corresponding logbook entry cannot be found, the system searches for a standard logbook entry or generates one if it does not already exist. Existing objects are neither deleted nor reassigned when measurement documents are inserted automatically. If you want to use customer-specific implementations to automatically insert measurement documents, you have to deactivate this switch by leaving it blank .

LBK_LINK_NO - Activate Automatic Insertion of Notifications in Logbook

If this switch is set to “1”, the notification is sorted in the corresponding logbook entry of the relevant logbook for the aircraft. The logbook entry results from the assignment of notification types to the usage types Flight and Ground . You define this assignment using the LBK_NOTIF_FL and LBK_NOTIF_GL switches.

The relevant date for sorting the notification is the date on which the fault started. If the system does not find a suitable flight or ground logbook entry, it searches for a standard logbook entry or generates one if it does not already exist. Existing objects are neither deleted nor reassigned when notifications are inserted automatically. If you want to use customer-specific implementations to automatically insert notifications, you have to deactivate this switch by leaving it blank .

LBK_MEQUI – Display Master Equipment Details in the Logbook

If this switch is set to “X”, the detailed data for the master equipment is displayed in the logbook as it is displayed on the Op. Equipment tab page in the Change Equipment transaction (transaction IE02). Note that this function is possible only if there is no active customer implementation for this logbook screen.

LBK_NOTIF_FL - Notification Types for Flight Logbook Entries

You use this switch to define the assignment of notification types to usage type Flight in the logbook entry; for example, “M2M3M4”.

LBK_NOTIF_GL - Notification Types for Ground Logbook Entries

You use this switch to define the assignment of notification types to usage type Ground in the logbook entry; for example, “M1”.

LBK_TEC_STATUS - Display Technical Status in the Logbook for Notifications and Orders

If this switch is set to “X”, the relevant condition ID is displayed in the notification and operation lists.

Note that the LBK_TEC_STATUS switch currently has no effect.

Define Usage Types of a Logbook Entry

In Customizing for the logbook, you can use the IMG activity Define Log Entry Types (view DIACL_LETYP_T) to define the following usage types using the logbook entry types: Default Log Entry , Flight Log Entry , Ground Log Entry , or None (blank) . You can also call this view directly using transaction DIACLC4.

Features

In addition to the logbook functions from the SAP for Aerospace & Defense industry solution, DFPS-specific functions are available and you can navigate to other applications:

  • Creating, changing, displaying, and managing logbooks and sub-logbooks for aircraft

  • Displaying master data for an aircraft (master equipment)

  • Displaying data for flights

  • Displaying the status of an aircraft and the current inspections with reference to a flight

  • Entering operating data, such as flight hours, takeoffs, landings, and fuel used

  • Displaying malfunction reports and orders with condition ID

  • Postponing malfunction reports

  • Displaying due periodic inspections

  • Checking the controlled installed and deinstalled components

  • Managing documents and records for an aircraft in electronic form

  • Creating a report to save data on a mobile data carrier

  • Connecting the logbook to distribution to distribute it together with the technical object

  • Supporting the technical debriefing

Functions for Automatic Insertion of Flights, Measurement Documents, and Notifications
Automatic Insertion of Flights

For each created flight, the system creates a logbook entry of type Flight in the corresponding logbook or sub-logbook of the master equipment or the relevant functional location.

Automatic Insertion of Measurement Documents

The system inserts a measurement document only if there is a logbook or sub-logbook for the reference object of the measurement document (functional location or equipment). If this is the case, the system searches for a flight logbook entry and stores the measurement document there. If the system does not find a corresponding flight logbook entry, a standard logbook entry is created.

Automatic Insertion of Notifications

The system uses the reference object of the notification to determine the relevant logbook or sub-logbook for notifications. The system searches for a corresponding logbook entry in the following way:

First, the system determines the date and time of the notification in the following sequence until a date is found: start of fault, required start, notification date, current date. When the time has been determined, the usage type of the logbook entry (flight, ground, default) is determined using the assignment in Customizing and the system searches for a suitable folder of this usage type while taking the date into account. If a suitable folder is not found, the system stores the notification in a standard folder created for this purpose.

If the system does not find completed logbook entries, it searches for logbook entries that are partially or completely open (without start and end times).

Application Log For Automatic Insertion of Objects

The system writes an application log when flights, measurement documents, and notifications are inserted in the logbook automatically. You can call and evaluate this application log using the Analyze Application Log transaction (transaction SLG1). The relevant object in the application log is /ISDFPS/LMLBK.

Customer-Specific Implementations for Automatic Insertion of Objects

You can use customer-specific implementations to insert flights, measurement documents, and notifications automatically. To do so, you have to deactivate the SAP-specific functions in Customizing as described above and implement the following enhancements:

  • Flights

    Business Transaction Event (BTE) with event number PM000030 (transaction FIBF; application EA-DFP; function module /ISDFPS/BTE_PM000030_ORDER).

  • Measurement documents

    Business Transaction Event with event number PM000040 (transaction FIBF; application EA-DFP; function module /ISDFPS/BTE_PM000040_MEASUREMT).

  • Notifications

    Business Add-In NOTIF_EVENT_POST ( Notification Update : Retrieval of Notification Data ).

Navigation to Other Functions

You can navigate from the Logbook to the following applications using the menu or by double-clicking the corresponding object:

  • Technical status overview

  • Flight

  • Status board

  • Flight plan

  • Controlled usage rate

  • Event monitor

Activities

You call the Logbook of the SAP for Aerospace & Defense industry solution by choosing the following path in the SAP menu: Start of the navigation path Logistics Next navigation step Plant Maintenance Next navigation step Maintenance Processing Next navigation step Logbook End of the navigation path (transaction LBK1).