Show TOC

  Assignment of Actions to Action Points

Use

You use this function in the automated Action Handler with iPPE or without iPPE .

Features

  • You can assign several actions to each action point. The sequence of the actions is not predetermined. This means that it is possible to run every action independently of others.

  • The same action can have different parameters at different action points.

    Example Example

    You want an internal mail to be sent at two action point. The mails are to have different texts and different recipients. You assign the following parameters to the action Send Mail at action point 1 and 2:

    Actions point 1:

    Action Send Mail

    parameter Text , parameter value "The order has passed action point 1"

    parameter recipient , parameter value Smith

    Actions point 2:

    Action Send Mail

    parameter Text , parameter value "The order has passed action point 2"

    parameter recipient , parameter value Smith

    End of the example.
  • If - on a production line - you always want to start the same function (such as saving production tracking information) at all defined action points , you can also assign the corresponding function module (here /SAPAPO/AHTG_TRACKINGINFO_SAVE) directly to the event TPOINT_REACHED ( Start of the navigation path Tools Next navigation step Business Workflow Next navigation step Development Next navigation step Definition tools Next navigation step Events Next navigation step Event linkage Next navigation step Type linkage End of the navigation path or transaction SWETYPV). This setting overrides the Customizing settings. SAP APO automatically carries out the function that is defined in the type coupling.

    With such a fixed assignment you can, if required, also define start conditions, such as time restrictions ( Start of the navigation path Tools Next navigation step Business Workflow Next navigation step Development Next navigation step Definition Tools Next navigation step Events Next navigation step Event Linkages Next navigation step Workflow Start Conditions End of the navigation path or transaction SWB_ COND ).

  • Please observe the following constraints :

    • The action Carry out Production Backflush 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.

    • The system cannot retroactively add standard interface parameters to actions at optional action points with retroactive execution. Therefore, it can only carry out actions at optional action points for which the entry of an order number and an action point is sufficient. Otherwise, the consistency of the data cannot be guaranteed.