adjustment of the technical status at equipment dismantling

7/25/2019 Adjustment of the Technical Status at Equipment Dismantling

http://slidepdf.com/reader/full/adjustment-of-the-technical-status-at-equipment-dismantling 1/13

SAP

Adjustment of the technical

status at equipment dismantlingAn enhancement of the industry Defense And Public

Security

© by SAP 5/16/2014



SAP Page 1 of 12

Table of Contents1 Current situation and motivation .................................................................................................... 2

2 New functionality to adjust the technical status ............................................................................ 5

2.1 Overview.................................................................................................................................. 5

2.2 Description of the new functionality in detail ......................................................................... 6

2.2.1 General remark on functionaluity ................................................................................... 6

2.2.2 Mode 1: After dismantling of an equipment ................................................................... 6

2.2.3 Mode 2: Take up backlog ................................................................................................ 8

2.3 Customizing/Configuration ..................................................................................................... 9

2.3.1 How to switch on the functionality? ............................................................................... 9

2.3.2 Determination of the notification type for notification which is created in this process

as replacement ................................................................................................................................ 9

2.3.3 Determination of the technical status to sign the relevant status.................................. 9

2.4 Process flow ........................................................................................................................... 11

2.5 Report /ISDFPS/TST_ADJ_AT_DISM ...................................................................................... 12

2.5.1 Purpose of the report .................................................................................................... 12

2.5.2 Parameters of the report............................................................................................... 12



SAP Page 2 of 12

1 Current situation and motivation

Figure 1 is showing the simplified technical structure of an aircraft.

Figure 1 Technical structure of an aircraft

At the very top functional location AC the master equipment AC is installed

During the flight operation of the aircraft AC the turbine and the afterburner of the engine number 1

represented by the equipment structure below equipment ENGINE01 is damaged.

Due to this the notifications

N1 with reference to equipment TURBINE01

N2 with reference to equipment AFTERBURNER01

are created to document these incidents.

To document the operational disability of the aircraft to fulfill its flight operations these notifications

are provided with a technical status. This technical status does not describe the real cause of the

disability as this is not its purpose. For the technical status the detail that a blade in the turbineTURBINE01 is damaged and has to be repaired is not of interest. This repair operation is the part of

the MRO process. The technical status is reflected to the master equipment AC to indicate the

disability to fly at a central point e.g. by using the Status Board functionality of DFPS (see Figure 2).

In the example the two technical status values

Red cross

Red dash

are used, where the priority of the red cross is higher that of red dash.

Please keep in mind, that only relevant technical status are reflected to the master equipment! A

singed or deleted technical status is not reflected to the master equipment!



SAP Page 3 of 12

Figure 2 Technical structure of an aircraft, document the incident

For the MRO process the equipment ENGINE01 has to be dismantled via transaction IE4N to repair

the blade in the turbine and the afterburner. Doing this,

an additional notification N3 for the equipment ENGINE01 is created in addition indicating

the real cause for the dismantling

and a structure gap for the dismantled equipment ENGINE01 is created

via transaction IE4N. The damaged equipment might be passed to a stock for serviceable or

unserviceable parts.

The technical status inside notifications is kept and although the equipment ENGINE01 is dismantled

and isn't part of the aircraft anymore it influences the technical status of the aircraft represented by

master equipment AC (see Figure 3).

This leads to confusing situations inside the Status Board. An object - equipment ENGINE01 - that is

not relevant for the aircraft anymore, has an influence on the technical status of the aircraft. This

status is kept even though a new engine was installed or the former, dismantled engine ENGINE01

was scrapped.



SAP Page 4 of 12

Figure 3 Dismantled equipment ENGINE01 and influence on technical status

To stop this confusing situation a functional enhancement is introduced which is described in the

next chapter.



SAP Page 5 of 12

2 New functionality to adjust the technical status

2.1

Overview

The starting situation is the same than described in the example in chapter 1.

The difference, if the enhanced functionality is used, is starting with the dismantling of equipmentENGINE01 with transaction IE4N.

Following steps are performed due to the technical status while dismantling the equipment (see

Figure 4):

A new notification N4 is created with reference to the installation location of equipment

ENGINE01 which is the functional location AC-ENG01. Inside the notification the most critical

technical status of all the notifications and/or orders related to the dismantled equipment

and its’ subordinate equipment structure is safeguarded. In our example the red cross of

equipment TURBINE01.Please keep in mind that the notification N3 comes with the dismantling by the transaction

IE4N. This is existing IE4N functionality and not part of the DFPS functionality.

Depending on configuration the technical status of the notification N1 and N2 is deleted or

signed . In our example the technical status inside the notifications is signed. This means,

that these technical status haven’t got any influence on the master equipment AC anymore.

The ‘old’ reference to the master equipment AC inside the notifications N1 and N2 is kept.

Figure 4 Dismantled equipment ENGINE01 and ‘decoupling’ of the technical status



SAP Page 6 of 12

The further asset history of the dismantled engine (equipment ENGINE01) doesn't have any further

influence on the technical status of the aircraft represented by master equipment AC.

After a serviceable (new or repaired) engine is installed and the functionality and fitness for

operation is approved the technical status of notification N4 can be signed.

2.2 Description of the new functionality in detail

2.2.1 General remark on functionaluity

The functionality is able to work in two modes:

Mode 1: After dismantling of an equipment

Mode 2: Take up backlog

Mode 1 is recommended when an equipment is dismantled with IE4N.

Mode 2 is recommended to take up the backlog of the adjustment only

The two modes exclude each other!

2.2.2 Mode 1: After dismantling of an equipment

An equipment A is dismantled from a structure that contains a master equipment M at the very top

of the structure.

The dismantling must take place in IE4N!

There are existing notifications and/or orders with a relevant technical status for the equipment A or

subordinate equipment installed into equipment A. Before the dismantling of equipment A thesetechnical status of these notifications and/or orders are reflected into the master equipment M.

The functionality determines the most severe technical status of all these notifications and/or orders

after the dismantling and is creating a notification for replacement at the old installation location

containing this technical status.

This notification can be identified by the short text which is:

TST.REPL.DISM.EQ. <nnnnnnnnnnnnnnnnnn>

<nnnnnnnnnnnnnnnnnn> = number of dismantled equipment

In our example

TST.REPL.DISM.EQ. A

If a notification meeting the following conditions exists:

reference object of existing notification is current installation location and

notification type of existing notification fits to the notification type derived by customizing

and

the notification short text of the existing notification is identical to 'TST.REPL.DISM.EQ.<nnnnnnnnnnnnnnnnnn>' (see above) and

a status object for the technical status does exist in the existing notification and



SAP Page 7 of 12

the master equipment inside the existing notification does fit to the current one,

no new notification is created.

The technical status of the notifications and/or orders with a relevant technical status for the

equipment A or subordinate equipment installed into equipment A are signed or deleted dependingon customizing. This automatism does not make use of the authorization concept to sign or delete

the technical status, as the most severe technical status is taken over to the notification created at

the old installation location and thus preserved.

This adjustment does not take place if:

the current notification/order to be adjusted is locked by another user

the current notification/order to be adjusted has no change protection inside the current

system.

In general this adjustment can only take place when

the dismantled equipment A

o can be locked by this process

o

has a change protection in the current system

o is no master equipment

the 'old' installation location can be locked by this process

the master equipment M of the structure where equipment A was dismantled from has a

change protection in the current system.

Every important process information, warnings and errors are logged into an action log (see processflow in chapter 0).

It is possible, that notifications and/or orders to be adjusted with in the process can't be changed

because they are locked by other users. Such obstacles are documented

in the application log (Object name: /ISDFPS/LM_TST, Subobject name: ADJUST)

in the backlog table /ISDFPS/BLTSTADJ

You can take up the adjustment by starting the report /ISDFPS/TST_ADJ_AT_DISM directly via

transaction SE38.

The backlog table /ISDFPS/BLTSTADJ is containing the following fields:

CLIENT: actual client

OBJNR: object number of the object to be taken up (notification or order)

MEQUNR: number of the master equipment relevant at the point of time the dismantling of

the equipment take place

EQUNR: Number of the dismantled equipment

SUP_EQUNR: Number of the old installation location equipment

SUP_TPLNR: Number of the old installation location functional location

/ISDFPS/OBJNR: Object number of the technical status assigned to notification or order

QMNUM: Number of the notification to be taken up



SAP Page 8 of 12

AUFNR: Number of the order to be taken up

CR_AT: Point of time backlog record was created

CR_BY: Name of the user which has created the backlog record

This backlog table is very important when a change inside the dismantled equipment structure take

place. If we have a look into the example, this might happen when

the equipment TURBINE01 is dismantled form Equipment ENGINE01

and a backlog for a notification or order assigned to equipment TURBINE01 does exist.

Without the backlog table the adjustment won’t find the a notification or order to be taken up

anymore.

The backlog table is analyzed the following way:

1.

Read 'direct' backlog data from table /ISDFPS/BLTSTADJ using

current master equipment,

dismantled equipment and

old installation location (equipment or functional location)

Remark:

It might be possible that after initially performing the adjustment functionality via

IE4N a backlog of notification and orders remain to take up (e.g. because these

objects are locked by another user). These objects are stored inside the backlog table

to take them up within the next step. The 'direct' backlog data supposed to be

available after the equipment was dismantled from IE4N with the parameters(dismantled equipment and old installation location) from above.

2. No direct backlog available. The number of the dismantled equipment and all its subordinate

equipment are used as possible 'old' installation location to analyze the backlog table

/ISDFPS/BLTSTADJ.

Remark:

This kind of backlog data supposed to be still available when the dismantling action

from IE4N take place with the parameters (dismantled equipment and old installation

location) from above and the adjustment is running the first time. All possible

backlogs from the subordinate equipment from the dismantled equipment has to be

taken into account as possible 'old' installation location.

2.2.3 Mode 2: Take up backlog

In opposite to mode 1 this mode does not create or check the notification for replacement. This

mode is only taking up all entries in the backlog table /ISDFPS/BLTSTADJ for a given master

equipment. The backlog contains all notifications an orders were the technical status can't be

adjusted (signed or deleted). When the notification or order form one backlog entry can be signed or

deleted this backlog entry is deleted.



SAP Page 9 of 12

2.3 Customizing/Configuration

2.3.1 How to switch on the functionality?

Inside the general DFPS customizing table /isdfps/cdfpsk1 there must exist a record where

field DFPS_KEY = 'LM_TST_ADJ'

filed DFPS_VALUE = 'X' or 'D'.

If 'X’ is used, the relevant technical status of all notifications and/or orders for the equipment A or

subordinate equipment installed into equipment A is signed concerning the customizing described in

chapter 2.3.3.

If 'D' is used, the relevant technical status of all notifications and/or orders for the equipment A or

subordinate equipment installed into equipment A is set to the delete status from the DFPS technical

status customizing.

Please use the customizing report /ISDFPS/TST_ADJ_AT_DISM_CUS to adjust the customizing in

table /ISDFPS/CDFPSK1.

2.3.2 Determination of the notification type for notification which is created in this

process as replacement

Inside the general DFPS customizing table /ISDFPS/CDFPSK1 there must exist a record where

field DFPS_KEY = 'LM_TST_ADJ_NTYP'.

The field DFPS_VALUE of this record must contain a valid notification type which is taken over to

create the notification for replacement.

If no such entry exists in DFPS table /ISDFPS/CDFPSK1, the IE4N customizing for notifications created

at dismantling is used. If this customizing is also missing, adjustments cannot take place.

Please use the customizing report /ISDFPS/TST_ADJ_AT_DISM_CUS to adjust the customizing in

table /ISDFPS/CDFPSK1, too.

2.3.3 Determination of the technical status to sign the relevant status

The status to sign the relevant technical status is taken over from the additional customizing for the

technical status of DFPS which can be found in table /ISDFPS/CLMSTAD. Every relevant status (field

RELEV = 'X') must have an entry inside field ESTAT_COMPL which must contain a status that is able tosign a relevant status. Status which are able to sign a relevant status can be identified by the field

COMPL that contains the value 'X'.

When inside the general DFPS customizing table /isdfps/cdfpsk1 a record with

field DFPS_KEY = 'LM_TST_ADJ' and

field DFPS_VALUE = 'X'

every relevant status must contain a status for signing!

To change the customizing, please use the following customizing path:



SAP Page 10 of 12

Defense Forces & Public Security → Support for Flight Operations → Technical Status →

Semantics

To check your entries please use the report /ISDFPS/TST_CHECK_CONSISTENCY.



SAP Page 11 of 12

2.4 Process flow

The process to adjust the technical status is starting with a dismantling of an equipment inside

transaction IE4N. Please see the Figure 5 below.

Figure 5 Process flow of adjustment in transaction IE4N

It is possible, that notifications and/or orders to be adjusted with in the process can't be changed

because they are locked by other users. Such obstacles are documented in the application log (Object

name: /ISDFPS/LM_TST, Subobject name: ADJUST). You can take up the adjustment by starting the

report /ISDFPS/TST_ADJ_AT_DISM directly via transaction SE38.



SAP Page 12 of 12

2.5 Report /ISDFPS/TST_ADJ_AT_DISM

2.5.1 Purpose of the report

Adjust the technical status of all notifications and/or orders related to a dismantled equipment and

its' subordinate equipment by calling the function module /ISDFPS/TST_ADJ_AT_DISM. Please see

chapter 2.5.2 for details

2.5.2 Parameters of the report

Figure 6 is showing the user interface of report /ISDFPS/TST_ADJ_AT_DISM.

Figure 6 Report /ISDFPS/TST_ADJ_AT_DISM

Please find the parameter description in the Table 1 below.

Parameter MeaningParameter: Dismantled equipment

Sub screen area: Mode 1: After dismantling of an

equipment

Technical name: PEQUNR

Equipment dismantled before by IE4N

functionality.

Parameter: Equipment


equipment → Old Installation location

Technical name: PSEQUNR

Old installation location equipment

Parameter: - (invisible)



Technical name: PSTPLNR

Old installation location functional location.

This parameter is invisible and is used only for

background processing when this report is

called via SUBMIT from function module/ISDFPS/LM_TST_ADJ_AT_DISM_BTC. This

parameter contains the internal func. loc.

number.

Parameter: Functional location



Technical name: PSSTRNO

Old installation location functional location in

the external format. This parameter is used

when the report is used in foreground.

Parameter: Master equipment

Sub screen area: Mode 2: Take up backlog

Technical name: PMEQUNR

Number of the master equipment were the

backlog should be taken up.

Table 1 Parameters of report /ISDFPS/TST_ADJ_AT_DISM

adjustment of the technical status at equipment dismantling

Documents