Configuring Action Type Handlers

The action hook framework (AHF) is a mechanism in SAP S/4HANA PEO that allows customers and partners to enhance the logic of how an action is executed by applying implemented methods. The action hook framework provides a flexible and configurable means of defining and executing sequences of action handlers that the system executes when a user selects an action.

To configure the action hook framework, choose Customizing (transaction SPRO) under Production Manufacturing for Production Engineering and Operations → Production Operations → Action Processing in activity → Define Action Handlers.

In this Customizing activity, you can assign action handler classes to action handlers, assign action handlers to object types and actions, and specify whether the system can execute the action handler before or after it performs the action.

Action handler classes are ABAP classes containing business logic, such as checks, executed when a user performs an action. An action handler class is assigned to an action handler, which determines when and for which objects the logic can run. For instance, an action handler class checks if planned components match assembled quantities for serialized materials, raising exceptions if there's a discrepancy. The action handler specifies that this logic applies to operation activities and must be executed before actions like Complete.

The following figure lists all action type handlers that are delivered out-of-the-box with SAP S/4HANA PEO:

• Object type 1 means that the type handler is applicable to an operation activity.
• Object type 4 means that the type handler is applicable to a serialized material in operation activity.

Action Assignment defines recommended and logically-relevant actions for an action type handler. The assignment can be modified if necessary or added if a new type handler has been introduced in the system.

Processing points are the locations in the coding of an action where a sequence of handlers is triggered. SAP provides the following processing points:

In Customizing, you enable each action handler to be called at a processing point.

You can create sequences of action handlers so that you can execute multiple action handlers when a user performs a single action. In addition, you can overwrite the default parameters that are defined in Customizing.

Action type handlers are the most convenient and reliable way to extend SAP S/4HANA PEO with custom logic – be it checks before a certain action executes, or activities that can be triggered after the action has been performed. How to define a new type handler.

In SAP S/4HANA PEO, you can assign type handlers to actions in the following SAP Fiori apps:

• Manage Action Settings
• Manage Shop Floor Routings

In the Manage Action Settings app, the user first selects a plant, an object type, and then an action where the action handler has to be assigned. Then the system allows the user to specify the following:

• OA Segment type: A type of an operation activity within an operation, for example, Setup, Produce, Teardown.
• Type Handler Processing Point: When the logic is to be triggered – before or after the action executes.
• Execution Sequence: The order in which action handlers will execute if more than one is assigned to an operation activity. "Sequence" here has more a technical meaning. For the end user it makes no difference, because if at least one check defined in any action handlers fails, the complete action is rolled back.
• Action Type Handler: The logic itself defined by the associated ABAP class.
• Action Handler is Active: Defines whether the assigned action handler shall be executed or not.

Points to note:

• Action handlers defined in the Manage Action Settings app are plant- and object-type-specific, meaning that they are called every time an action is performed on the specified object, independent of an operation activity.
• In the Manage Shop Floor Routings app, the user first selects a routing, then an operation activity, and then the Action Handlers view in the Details workspace. There, the system allows the user to add, change, and delete action type handlers defined for an operation activity. To add a new type handler, the user chooses the Add button and specifies all the same properties explained in this lesson.
• The main difference this assignment has is that this action handler is plant-, routing-, object-type-, and operation-activity-specific, meaning that it is called only when an action is triggered at the specified operation activity.

In the Action Handlers view, the system shows the Source of an action handler; in other words, where this action handler has been defined:

• Routing – in a routing for an operation activity
• Plant – for an action within a plant

In SAP S/4HANA Manufacturing for production engineering and operations, various action handlers are designed to enforce specific checks and validations during the production process.