During shop floor manufacturing, production operators work through different phases marked by status transitions. The process begins with setup, followed by produce, and ends with teardown. Each phase includes various statuses, such as initiating production, holding due to missing parts, or completing a product. Transitions between statuses, known as actions, move the process from one step to the next.
In SAP S/4HANA Manufacturing for production engineering and operations (PEO), we differentiate between the following types of actions:
- SAS actions: Actions that lead to a status transition of an object such as operation activity or serialized material. Examples of SAS actions include start, pause, skip, complete, and so on.
- Non-SAS actions: Actions that do not influence the status transition for an object, but still need to be performed to manipulate a product or process. For example, hold, accept/reject buyoff, component assembly, and so on.
An action triggers a specific logic, such as changing an object's status, sending production confirmations, or blocking further processing. It may also require operators to provide additional details, like notes or reason codes, and verify their qualifications. This extra activity is defined using theManage Action Settings app in SAP S/4HANA PEO
Actions are specific to a plant and an object.
The Manage Action Settings app allows the user to perform the following tasks:
- Display a list of actions that are defined in status and action schemas (SASs) as well as non-SAS actions (for example, hold, accept buyoff, component assembly).
- View a detail screen for each action.
- Edit previously-defined actions.
- Define if a user has to specify a reason when he or she performs a certain action on the shop floor.
- Define if a user has to provide a note when he or she performs a certain action on the shop floor.
- Define if the system checks that the production operator has sufficient qualifications to perform a certain action.
- Add action handlers with their respective settings to an action.
Actions are dependent on the plant and object type.
Action settings are configured individually for each action. The user can define whether a reason code and a note are optional, mandatory, or not required. Later, based on these setting, the fields will be marked, and the user's entry will be checked.
If the setting for the Reason Code field is optional and/or required, the user must define a code group. On action, the list of codes that will be presented to the user are taken from the assigned code group.
The Check Required checkbox is used to specify whether the user must be checked for qualification when he or she triggers this action during production activities.
Summary
This lesson covers configuring action properties in SAP S/4HANA PEO for effective shop floor process management.
- Differentiate between SAS and non-SAS actions in managing production transitions.
- Use the Manage Action Settings app to tailor action properties for each plant and object type.
- Configure mandatory reason codes, notes, and qualification checks for specific actions.
- Customize action settings based on plant requirements to ensure compliance and accuracy.