SAP ABAP IMG Activity COCF_ALERTS (Settings for Sending Alerts)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ PP-SFC (Application Component) Production Orders
     ⤷ COCF (Package) Order and Confirmation Data
IMG Activity
ID COCF_ALERTS Settings for Sending Alerts  
Transaction Code S_EE5_50000169   (empty) 
Created on 20090402    
Customizing Attributes COCF_ALERTS   Settings for Sending Alerts 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name COCF_ALERTS    

Use

This document outlines the worksteps you have to perform to enable an Alert to be triggered when a shift note is created or changed and sent to a certain recipient.

For example, you can stipulate that the system is always to trigger an alert if you have created a shift note with reference to a certain category. You can then text the maintenance manager to inform that person when a shift note of the category machine outage has been entered in production and he or she is responsible for the relevant plant.

As standard, SAP supplies the following objects for the sending of alerts for shift notes:

  • Business object type: COCF_SN

    COCF_SN is the business object for the shift note.

  • Events: CREATED (shift note created) and CHANGED (shift note changed)

    The business object for the shift note includes the two events CREATED and CHANGED.

  • Alert category: COCF_SHIFT_NOTE_SAVED
  • Rule: 500001 (distribution list for shift notes)

    You specify the recipients of the alerts using the rule.

Requirements

Standard settings

Activities

You must carry out the following activities to enable an alert to be sent after the creation or changing of a shift note:

  1. In the Settings for the Shift Note Type (transaction ORPS8 ), you must set the Trigger Event At Time of Saving indicator in the Details area of the selected shift note type. A prerequisite for this is that the shift note involved is an independent shift note. You specify this in the Usage area in transaction ORPS8.
  2. In the transaction Event Type Linkage (transaction SWE2), you must activate the forwarding of the Shift Note Created (CREATED) or Shift Note Changed (CHANGED) event to the Alert Framework. In the standard system, the following entries are already supplied for the business object type COCF_SN in transaction SWE2:
    • Object category: BO BOR object type
    • Object type: COCF_SN
    • Event: CREATED or CHANGED

      You only have to set the Linkage Activated indicator for the relevant entry (CREATED or CHANGED).

  3. In the transaction Maintain Alert Categories (transaction ALRTCATDEF), you can check and adjust the alert category COCF_SHIFT_NOTE_SAVED. You will find the alert category in the structure tree under All Classifications --> ERP - Manufacturing --> Shift Note.

    You will also find the transaction in the IMG for SAP NetWeaver under Application Server--> Basis-Services --> Generic Business Tools --> Alert Management --> Alert Categories.

    Note that the alert category COCF_SHIFT_NOTE_SAVED is supplied by SAP with complete settings in client 000 only. For this reason, you must also do the following:

    1. In accordance with Note 601619, you must adopt the alert texts (title, short text, and long text) from client 000.
    2. In the alert category, you must manually enter rule 500001 on the Properties tab page.
    3. Then you must process the data flow. To do so, you must assign the element of the same name from the alert container to each element of the rule container. See also: Generate Container.
  4. To specify the responsible recipient of the alert, call up transaction OOCU_RESP:
    1. Enter the rule number 500001 and choose Change.
    2. The Responsibilities for Rule 500001 (distribution list for shift notes) screen appears.
    3. Choose the Create Responsibility icon.
    4. As object description, choose Distribution List for Shift Notes . You have a free choice of object descriptions. Enter a start and end date. By doing so, you define the validity period of your rule. Choose Enter.
    5. Specify the values for which an alert is to be triggered. By choosing the Change <-> Display icon (SHIFT+CTRL+0), you switch to change mode and can choose the desired objects. Note that the values must be specified in the internal technical format. You can get this via the F4 help.
    6. Save your selection and choose the Back icon (F3) to return to the previous screen.
    7. Now select your responsibility and choose the Insert Processor Assignment icon. If you choose the user via F4 there, for example, you directly specify the responsible recipient of your alert.

      Note:

      In the transaction Maintain Rule PFAC, you can check the standard settings for rule 500001 and copy the rule if necessary.

  5. In the transaction Personalization of Alert Delivery (ALRTPERS), you must specify how the recipient of the alert is to be notified (e.g. via mail or text). If the transaction ALRTPERS delivers a BSP error, you must proceed in accordance with SAP Note 1080668.
  6. In transaction SU01, you must specify the desired communication type for the recipient of the alert:
    • If the recipient is to receive a text, you must enter PAG (pager/text) in the Communication Type field. A dialog box then appears, in which you must enter the recipient's cell phone number.
    • If the recipient is to receive an e-mail, you must enter INT (e-mail) in the Communication Type field and specify the e-mail address.
    • If the recipient is to receive an e-mail, you can also enter RML (remote mail) in the Communication Type field. For more information on RML, refer to SAP Note 931675.
  7. In transaction SOST, you can check whether an alert was sent after you created a shift note with the relevant data.
  8. If the alert does not work as expected, you can activate the logging function using the transaction Maintain Alert Categories (ALRTCATDEF ) under Settings -> Configuration. You can then view the log in the transaction SLG1 for the object ALERT.

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 COCF_ALERTS 0 HLA0006433 Logistics - General 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20091117 
SAP Release Created in 605