Ansicht
Dokumentation

EAML_SM_NOTIFICATION_API - Split or Merge Maintenance Notification

BAL Application Log Documentation CPI1466 during Backup
This documentation is copyright by SAP AG.

Functionality

Allows you to split or merge maintenance notifications based on the split or merge of technical objects.

Use

You can use this function module when:

You want to split the maintenance notifications associated with a technical object that was already split. A technical object (a functional location or an equipment) which has linear property can be split into multiple technical objects. When a technical object is split, the maintenance notifications associated with the technical object can also be split.

You want to merge multiple technical objects into a single technical object. The maintenance notifications associated with the technical objects also can be merged.

This function module updates an existing maintenance notification or a new maintenance notification.

Input Parameter	Value
OBART	QM
TECHNICAL_OBJECT	IF
TECH_OBJ_OLD	FLOC1
TECH_OBJ_NEW	FLOC1, FLOC2
SAVE	‘X’
APP_LOG	‘X’ (Optional)

Where:

QM- Indicates the object type of the maintenance notification.

TECHNICAL_OBJECT - IFindicates the functional location. IEindicates the equipment.

TECH_OBJ_OLD: Indicates the functional location or equipment that is in the initial state. This is based on the above input for technical object.

TECH_OBJ_NEW: Indicates the list of functional locations or equipment after the split. This is based on the above input for technical object.

SAVE: ‘X’ – Indicates that the data needs to be saved. If you enter only a space, the data is not saved.

APP_LOG: ‘X’ indicates that application logs need to be created. If you enter only a space, then it indicates that application logs need not be created.

Output parameters:

ET_RESULTS – Indicates if the maintenance notification was created, changed, or unchanged.

ET_BAPIRET2 – Indicates if the log messages were created or not.

Additional Details:

Package– EAML

Function Group - EAML_SPLIT_MERGE

Example

We can look at an existing sample report EAML_SM_NOTIF_UTILITY_REPORT which was created using this function module.

Split Scenario:

Let us consider a road which has a functional location with linear properties whose start point is 0 Km, and the end point is 100 Km.

Split of Functional Location

Before the functional location is split, it will look like this:

Functional Location	Start Point		End Point	Unit of Measure
FLOC1	0		100	KM

After the functional location is split into two functional locations, it will look like this:

Functional Location	Start Point		End Point	Unit of Measure
FLOC1	0		40	KM
FLOC2	40		100	KM

FLOC1 has maintenance notification (Notif1) which has linear properties. Before the maintenance notification is split, it will look like this:

Maintenance Notification	Start Point		End Point	Unit of Measure
Notif1	30		60	KM

Run the function module with the below parameters:

Input Parameter	Value
OBART	QM
TECHNICAL_OBJECT	IF
TECH_OBJ_OLD	FLOC1
TECH_OBJ_NEW	FLOC1, FLOC2
SAVE	‘X’
APP_LOG	‘X’ (Optional)

Split of Maintenance Notification

After the maintenance notification Notif1 is split, it will look like this:

Notification	Start Point		End Point	Unit of Measure	Reference
Notif1	30		40	KM	FLOC1
Notif2 (copy of Notif1)	40		60	KM	FLOC2

,,Merge Scenario

Let us consider that a road is divided into two functional locations (0 - 40 Km and from 40 - 100 Km). These two functional locations are merged into a single functional location 0 - 100 Km.

Merge of Functional Locations

Before the functional locations are merged, they will look like this:

Functional Location	Start Point		End Point	Unit of Measure
FLOC1	0		40	KM
FLOC2	40		100	KM

After the functional locations are merged into a single functional location, it will look like this:

Functional Location	Start Point		End Point	Unit of Measure
FLOC1	0		100	KM

The maintenance notifications associated with the two functional locations are as follows:

Notification	Start Point		End Point	Unit of measure	Reference
Notif1	10		40	KM	FLOC1
Notif2	60		80	KM	FLOC2

Run the function module with the below parameters:

Input Parameter	Value
OBART	QM
TECHNICAL_OBJECT	IF
TECH_OBJ_OLD	FLOC1, FLOC2
TECH_OBJ_NEW	FLOC1
SAVE	‘X’
APP_LOG	‘X’ (Optional)

The maintenance notifications are now associated with the new merged functional location.

Notification	Start Point		End Point	Unit of measure	Reference
Notif1	10		40	KM	FLOC1
Notif2	60		80	KM	FLOC1

Additional Information

The following details must be kept in mind while using this function module:

You need to split or merge the technical objects (functional location or equipment) before using this function module.

When you split or merge maintenance notifications using this function module, you cannot revert them back to their original state using this function module.

After you split or merge a functional location, the functional location which was split or merged (original functional location) exists in the new split or merged functional location.

You can create an additional authorization object and use it in the object such as a report, class, or another function module which uses this function module so that you do not face authorization issues while using this function module.

The application logs that are saved can be viewed using the transaction code SLG1and using the object EAML_SPLIT_MERGE.

Maintenance notifications can also be split and merged.

Consider this scenario:

A maintenance notification has the status ORAS (Order assigned)

The maintenance order associated with the maintenance notification has the status CRTD(Created)

In this scenario, the maintenance notification will not be split.

Notes

Further information

Parameters

ET_BAPIRET2
ET_RESULTS
IS_CONTEXT
IS_SELECTION_FIELDS

Exceptions

Function Group

EAML_SPLIT_MERGE

Vendor Master (General Section) CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.

Length: 13853 Date: 20240523 Time: 101137 sap01-206 ( 68 ms )

Ansicht Dokumentation