Ansicht
Dokumentation

PYIN_P2E_APP_22 - Maintain Follow-on Actions for Policy Approval

PYIN_P2E_APP_22 - Maintain Follow-on Actions for Policy Approval

BAL Application Log Documentation   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you define the follow-on actions that the system must perform for each level in policy approval.

Based on the status of policy at each level, you maintain the following actions:

  • Information mail- Mail is sent to the specified recipient as soon as the action is performed
  • Reminder mail - Mail is sent to the approver when the approver has not performed any action within a time frame

To enable the system to send these mails, maintain the recipients agent code and mail template ID. Based on the agent code that you select; enter either data in the Actual Processorfield or the system fetches the value from the database.

For example, if you select the standard organization object as A - Work Center, C - Job or S - Position, then specify the value in Actual Processor field.

For sending a reminder mail, maintain the frequency and number of days after which the system must send reminder mail to the approver. For example, if you maintain 3 in Frequency field and 2 in No. of Reminder,the system sends a reminder mail once in 3 days and will send total of 2 reminder mails.

Note that you must create a mail template using the SO10 transaction. The system uses the class name and the interface component that you enter in this view, to derive the SO10 object.

You must create folder in Maintain Approver Rules for Policy Approval

  • Select New Entries.
  • Specify the sequence number.
  • Select the relevant level of approval for the specified group ID/ folder. Note that you can have a maximum of 10 levels of approval for a policy.
  • Maintain the Start and End Date.
  • Select the Outcome ID. Based on the outcome ID, the system must trigger the relevant follow-on action.
  • Select the relevant action type. Based on the value that you enter here, the system sends either a reminder mail or an information mail to the approver.
  • Specify the Actual Processorcorresponding to the value that you have specified in the Approver Code field. Here, actual processor refers to the person(s) who will receive the mail. Corresponding to the value that you maintain in Approver Code field, you must specify values such as user ID, employee ID of the person responsible for approving the policy.
  • Enter the Frequency, based onwhich the system must send a reminder mail to the approver. For example, if you maintain 3 in this field, it indicates that a reminder mail will be sent once in 3 days.
  • Specify the No. of Reminders mails that the system must send to the approver. For example, if you maintain 2 in this field, it indicates that 2 reminder mails will be sent to the approver.
  • Specify the object in the Text IDfield that the system must use to determine the content of e-mail. This is the e-mail that the system sends for the follow-on action mail. The object can be maintained using transaction code SO10.
  • Specify the Class/ Interface and Interface Component name. Based on this, the system fetches the relevant object that you have created using transaction SO10, from the backend.
  • Save your entries.






BAL Application Log Documentation   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 4456 Date: 20240523 Time: 185214     sap01-206 ( 74 ms )