Kontakt

Ansicht
Dokumentation

SPP_CUSTOMIZE_AMON - BAdI: Handling Customer-Specific Alert Types in SPP Alert Monitor

SPP_CUSTOMIZE_AMON - BAdI: Handling Customer-Specific Alert Types in SPP Alert Monitor

CL_GUI_FRONTEND_SERVICES - Frontend Services   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

The Business Add-In (BAdI) /SCA/SPP_CUSTOMIZE_AMON is used in the Service Parts Planning (SPP) component.

You can use this BAdI to handle and display the alert types in the SPP Alert Monitor that you developed and assigned to the SPP application in the Alert Engine.

The system calls this BAdI in the following cases:

  • When you start the SPP Alert Monitor.
In this case, the BAdI definition is always called.
On the SAP Easy Access screen, choose Logistics -> Extended Service Parts Planning -> Reporting / Monitoring -> Start SAP GUIand enter SPP in the Application IDfield. In the Shortage Overviewscreen navigate to the Alert Monitor.
  • When you display an alert by clicking the link of a particular alert type.
In this case, the system calls the BAdI definition only in case the selected alert type is already assigned to navigation class /SCA/CL_ALNAV_ITS in view /SCA/ALNAVCLASSV.

You have made the following settings:

  • In the Alert Engine Configuration (transaction /SCMB/ALENCFG) specify an SPP-specific alert object type for your alert type. In the Alert Object Typesview, in the Applicatn Alert Monitor Application) field, choose a value that is SPP-specific.
  • In Customizing for Extended Service Parts Planning, choose Monitoring -> SPP Alert Monitor -> Make General Settings for Alertsand create an entry for your alert type with the proper settings.
  • In transaction /SCF/ALERTCATCFG, assign your alert type to an alert category.
The name of the alert category must contain the prefix SPPafter the customer namespace. For example: [prefix in customer namespace]SPP[customer-defined alert category name].
  • In transaction /SCF/SCREENCFG,in the Screen Layout view, in the GUI component IDfield, assign the alert category name to the GUI component ID.
For example:
  • [prefix in customer namespace]ALSPP[customer-defined alert category name]

For the tab page component
  • [prefix in customer namespace]ASPP[customer-defined alert category name]

For the display of the form and table views and further ones for the display of the toolbars in these views in the Screen Layout configuration where Application ID = SPP and Screen ID = ALRTOVW
  • If you need a navigation URL to be assigned to your alert type, create an entry in /SCA/ALNAVCLASSV for your alert type.

The BAdI is not active in the standard system.

The BAdI is not filter-dependent.

The BAdI is designed for multiple use.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

When you create and use alerts of the alert types you have defined and assigned to the SPP application, you might want to display them in the SPP Alert Monitor. In this case, the basic display of alerts happens, but several screen fields might remain blank, being without proper field mapping. It is also not be possible to navigate from the alerts# detail view to the relevant transaction to maintain the alert-related data and solve the alert situation.

This BAdI definition provides two methods which enable the adjustment of the properties of customer-defined alert types, such as appropriate field mapping and setting an own navigation link.

This BAdI uses the interface /SCA/IF_EX_SPP_CUSTOMIZE_AMON. For more information, display the information in the Class Builder.






Fill RESBD Structure from EBP Component Structure   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 5541 Date: 20240523 Time: 152547     sap01-206 ( 143 ms )