SAP ABAP IMG Activity OLQN-MPN (Define Standard Messages to Partners)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ QI (Package) QM IMG and area menu
IMG Activity
ID OLQN-MPN Define Standard Messages to Partners  
Transaction Code S_ALR_87004490   IMG Activity: OLQN-MPN 
Created on 19981222    
Customizing Attributes OLQN-MPN   Define standard messages to partners 
Customizing Activity OLQN-MPN   Define Standard Messages to Partners 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OLQN-MPN    

In this step, you can define standard texts for messages to a contact person for each notification type. These messages can be sent by the following methods:

  • Mail (SAPoffice)
  • E-mail (Internet)
  • Paging

Example

From the contact person screen in the notification, you can send messages to the following partner types:

  • Contact person
  • Customer
  • User
  • Employee

The system sends the message when the notification is saved and sets the corresponding notification status.

Requirements

  • The basic components SAPoffice or SAPconnect are available in the system.
  • The settings for the general application function address management, as well as the subtypes of the paging services are maintained.
  • The sending media and services (subtypes) that are used by the partner must be entered in the relevant master records, depending on the partner type.
    Note: If several services are entered, the system accesses the services in the following order:
    • a) Paging
    • b) Internet
    • c) SAPoffice

Standard settings

The following settings are used for the message short texts:

  • The text object TEXT
    If you choose this reference object, it allows you to enter texts as freely defined standard texts using transaction SO10. You can also use any other text objects, such as text for the notification header (object QMEL).
  • The text identification (text ID) QMQN
    Although transaction SO10 proposes the text ID ST, your own text ID QMQN gives you the advantage of differentiating message short texts from other standard texts.

You display and edit text objects with transaction SE75.

Recommendation

Use the text object TEXT that has been defined in the standard system and the text ID QMQN for all notification types.

Activities

  1. Determine whether you want to, or are able to use the services mentioned above, to send information to the partners involved in the notification. If necessary, you must make sure that the necessary prerequisites are fulfilled and:
    1. Provide the technical back-up
    2. Make the relevant settings in the SAP system (see above!)
  2. Determine whether you can use standard texts for the messages. If necessary, you must:
    1. Define the standard texts
      For more information, see the step Text formats / SAPscript in the section Basic Settings and Environment / Settings.
    2. Assign the texts to the notification types.

Further notes

Business Attributes
ASAP Roadmap ID 259   Establish Forms and Messages 
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 OLQN-MPN 0 ALR0077563 O  
SIMG OLQN-MPN 1 BIO0000031 O  
SIMG OLQN-MPN 2 HLA0006831 Creating Quality Notifications 
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
V_TQ80_PAGE V - View SM30 OLQN Assign Standard Texts for Messages to Notification Types 
History
Last changed by/on SAP  19991116 
SAP Release Created in