Actions An action is a business operation that refers to business processes which take place in production planning/control .
You define actions in Customizing for the Action Handler in the process step
Define Actions and Action Networks
(transaction /N/SAPAPO/AHC1).
Actions are either triggered automatically by the system or manually by the user.
In the automated Action Handler, actions are triggered by events and then automatically carried out by the system. Example: In automobile production, when a vehicle reaches a certain action point on the production line, shop papers are printed automatically.
Actions consist of one or more functions . When an action is called up, the Action Handler processes these functions individually in the defined sequence. In standard Customizing, there is no difference between actions and functions, that is, each action has exactly one function assigned to it.
Note
It is possible for actions to contain the same functions and only vary in the sequence in which the functions are to be processed.
Each function can have one or several
parameters
(see table under
Action Parameters
, column
Customizing
Parameters
).
Parameters provide additional information on the functions (for example, printer, text of a message, message recipient). In the automated Action Handler you can define different parameter values at different action points for the same function (see
Assignment of Actions to Action Points
). When using the manual Action Handler, you can enter different parameter values every time you carry out an action/function (see
Manual Action Handler
).
You can classify actions as standalone actions , meaning that there are no dependencies regarding business processes; the actions can then be carried out at any time during the production process (for example, send messages, print documents).
You can link actions to form action networks .
Actions |
Standalone |
Automatic/manual |
Description |
|---|---|---|---|
01SAP_ACTIVITY_STATUS_DEFAULT
|
|||
No |
Only for automatic execution |
With or without iPPE Sets the status of an order activity to the specified value. |
|
01SAP_ALTERNATIVE_LINE_SWITCHSwitch lines within an alternative line group |
|||
No |
For automatic and manual execution |
Only with iPPE Switches between the lines of alternative line groups. Switching is only possible for activities for which partial/final confirmation has not yet been made. |
|
01SAP_ASSIGN_ACTIONNETAssign action network to order |
|||
Yes |
Only for manual execution |
Only with iPPE Assigns an order to an action network for the manual Action Handler. |
|
01SAP_COFFEE_REQUESTExample action “Order coffee” |
|||
Yes |
For automatic and manual execution |
Sends a message in which a coffee is requested. You can use this action as a template to program your own functions/actions. |
|
01SAP_CONFIGURATION_4_TRACKINGAdopt Evaluation for Tracking |
|||
Yes |
For automatic and manual execution |
Saves the configuration of an order, that is, the characteristics and their evaluation for production tracking. You can display the configuration in the transaction
For performance reasons, only carry out this function once for each order, and do not carry it out for several orders at the same time. |
|
01SAP_NOTIFICATION_SENDSend notification via SAPOffice |
|||
Yes |
For automatic and manual execution |
Sends notifications internally and externally via SAPOffice. The notification can also be sent as an express mail. |
|
01SAP_ORDER_CHECK_ATPCarry out ATP check for order |
|||
Yes |
For automatic and manual execution |
Checks whether the components of an order are available. |
|
01SAP_ORDER_DEALLOCATEDeallocate order |
|||
Yes |
For automatic and manual execution |
Deallocates the activities of an order. All activities which have the status
If it is not possible to continue producing an order, you can deallocate its activities on follow-up lines/resources so that they no longer take up capacity. |
|
01SAP_ORDER_DELETEDelete order |
|||
No |
Only for automatic execution |
Deletes an order. This function only makes sense for orders which have not been backflushed. You use this function in case something breaks during production. |
|
01SAP_ORDER_INITIALIZEReset Action Handler status (last action point/action point network) |
|||
Yes |
For automatic and manual execution |
Function for resetting the Action Handler status of an order: The action point reported last for the order is initialized, the assignment of an action network for the order is reset, and the status of the order within the action network is deleted. |
|
01SAP_ORDER_MODIFY_GENERICChange activity status and/or date |
|||
No |
For automatic and manual execution |
With or without iPPE Reschedules activities of an order according to the strategy profile and/or changes the status. This function is used for correction purposes in the following cases:
|
|
01SAP_PROCESS_ACTIONS_4_POINTCarry out actions for an action point |
|||
Yes |
Only for manual execution |
Manually reports an action point. You use this function to manually correct data inconsistencies that occur when an obligatory action point has not been reported. |
|
01SAP_PRODUCTION_BACKFLUSHCarry out production backflush |
|||
No |
Only for automatic execution |
You can only use this function if you have an SAP DIMP System as your OLTP System. The function can only be carried out at obligatory actions points and at optional action points without retroactive execution; it cannot be carried out at optional action points with retroactive execution. Starts the production backflush in APO. In this way, the following postings can be carried out in the APO System: inventory posting, reduction of requirements, adjustment of goods receipt dates, adjustment of reporting point quantities. In the DIMP System additional services and costs can be posted for components per reporting point. The connection between action points and the reporting points of the backflush must be managed in the production control system or provided by iPPE. If you want to carry out the backflush manually, you should use the regular backflush transaction or planned order management. |
|
01SAP_PRODUCTION_TRACKINGUpdate production tracking |
|||
No |
Only for automatic execution |
See production tracking . |
|
01SAP_FOT_ORDER_MERGEFOT: Merge orders |
|||
Action used within flexible order transactions (FOT). Merges two or more APO planned orders in order to create a new APO planned order. You have to mark one of the planned orders as the remaining order. The other orders are deleted. For further information, see the separate documentation on flexible order transactions. |
|||
01SAP_FOT_ORDER_PRODCHFOT: Change product |
|||
Action used within flexible order transactions (FOT). Changes the output product or the production version of an APO planned order. For further information, see the separate documentation on flexible order transactions. |
|||
01SAP_FOT_ORDER_SPLITFOT: Split order |
|||
Action used within flexible order transactions (FOT). Splits an APO planned order into several APO planned orders. For further information, see the separate documentation on flexible order transactions. |
|||
You can copy the function module /SAPAPO/AHTG_REFERENCE_EXAMPLE and use it as a template for programming other functions.
Examples of possible functions:
automatically print data specific to work center (shop papers, component lists)
create WM transfer orders for components that are not often required