Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-TS-PPO (Application Component) Postprocessing Office⤷
/SAPPO/NOTIF (Package) Post-Processing Office: Notifications
IMG Activity
| ID | /SAPPO/VC_NF | Process Notifications for Orders in Worklist |
| Transaction Code | /SAPPO/16000009 | (empty) |
| Created on | 20091208 | |
| Customizing Attributes | /SAPPO/VC_NF | Process Notifications for Orders in Worklist |
| Customizing Activity | /SAPPO/VC_NF | Process Notifications for Orders in Worklist |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPPO/VC_NF |
Use
In this Customizing activity you make the settings for notifications for newly created postprocessing orders.
Requirements
You have activated the implementation /SAPPO/ORDER_CR_NOTIFY_DEFAULT for the Business Add-In (BAdI) Notification When Creating an Orders.
Note: This Customizing is evaluated only with the BAdI implementation.
Standard settings
Activities
Notifications of orders in the worklist
On this overview screen you define for the components, processes, and worklists for which the system sends notifications. The According to WL checkbox defines whether all users who are assigned to the worklist are to receive a notification. This includes those users who are assigned to the worklist indirectly through their organizational units.
Settings for the Print Workbench
This is where you define for Dispatch Control as of which priority notifications are sent and which Application Form is to be used. You can enter multiple dispatch controls. You can also enter different priorities and applications forms for each dispatch control. Example: Notification by e-mail as of priority 5 with an extensive form, notification by text message as of priority 2 with a short form.
You need to define the necessary Dispatch Controls so that the print parameters required for preparing the form are provided when sending the notifications. The dispatch control PPOM is available as an example for your own dispatch controls. Note that you cannot archive notifications. Therefore, you need specify Print Only as the storage mode. You also need to specify an output device.
We supply the following example application forms:
- /SAPPO/NF_NOTIFICATION_COLL for notification by e-mail
- /SAPPO/NF_NOTIFICATION_SF for notification by e-mail attachment
- /SAPPO/NF_NOTIFICATION_SMS_SF for notification by text message
You can use Customizing activity Define Application Forms to create application forms and adjust them to your needs.
Note: You need a sender address if you want to send e-mails. The system determines this address from the current system user of the application that creates the PPO order. Since PPO orders are created in background processes (such as mass runs, processing of incoming PI messages), you need to enter the e-mail address for the users executing these processes.
You use Customizing activity Assign Priority to business Processes to define the priority of postprocessing orders according to the component and the business process. Since you can also select both of these criteria on the overview screen, all PPO orders whose settings are valid in Print Workbench, have the same priority in the standard system. However, you can use the BAdI Creating a Postprocessing Order to overwrite the priority of a PPO order.
If a notification is not sent, you can use the activation variant SAPPO/NOTIF_LOG for the checkpoint group /SAPPO/NOTIF (Error while Sending Notifications) to activate the logging of the errors that occur by using the transaction SAAB.
Notifications for PPO Orders: Users
In this view, you can explicitly exclude a user from the notification or include a user in the notification. If you have not made any settings here or have not selected the According to WL checkbox, no one receives a notification.
You can add explicitly those users who receive a notification based on the worklist. These users continue to receive notifications even if the assignment to the worklist changes. On the other hand, you can exclude those users who are not assigned to the worklist from receiving a notification. The users do not receive a notification even if they are assigned to a worklist at a later time.
You use the transaction /SAPPO/WL_CHANGE to assign users or organizational units to a worklist.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | /SAPPO/VC_NF | 0 | /SAPPO/ABA0000332 | Postprocessing Office |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| /SAPPO/VC_NF | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20091217 |
| SAP Release Created in |
