Hierarchy

⤷

⤷

IMG Activity
ID | SIMG_CFMENUOLMRKOND | Maintain Conditions |
Transaction Code | S_ALR_87001762 | IMG Activity: SIMG_CFMENUOLMRKOND |
Created on | 19981222 | |
Customizing Attributes | SIMG_CFMENUOLMRKOND | Maintain Conditions |
Customizing Activity | SIMG_CFMENUOLMRKOND | Maintain Conditions |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUOLMRKOND |
Conditions are created for every message type.
If a message is to be created in an application, the system uses the message schema and the message type to try and find a condition record for the current application data. If the system does not find one, it does not send the message. If a condition record is found, this specifies how and when the message is to be generated (mail, printout, fax).
EXAMPLE&
In company code 0001, complaints for vendors A and B are to be faxed; complaints for all other vendors are to be printed out. To model this in the system, you have to create condition records 0001/A and 0001/B with transmission medium 'FAX' in condition table 048 and create condition record 0001 with transmission medium 'PRINT' in condition table 049.
Standard settings
In the standard system, no condition records have been maintained.
Activities
You must create conditions for the message types you use.
- Choose Create message: Invoice Verification.
- Enter the message type and choose Enter.
In certain cases, a dialog box appears in which you can select a key combination.
- Enter the partner function, the transmission medium, the language and the transmission time.
- The following settings are supported in Invoice Verification:
Mess.type Trans. med. Time Partner function
EINK Mail 4 ME,MP
MLPP Mail 4 ME,MP
REKL Print, Fax 1,3,4 RS
KONS Print, Fax 1,4 LF
RAP Print, Fax 1,2,3,4 LF,RS
RAP6 EDI 1,2,3,4 LF,RS
To define details for the condition, choose Communication:
- When sending by Mail, you can specify here if the mail is to be sent express or whether a reply is necessary. If the recipient is to be able to process the problem directly from the mail, enter a transaction code and additional parameters. You can use the same fields as parameters that you use as variables in the mail text. For example, if you want users to be able to go directly to a purchase order when processing mails of message type MLPP, enter transaction code ME23, parameter RSEG-EBELN and parameter ID BES.
- In the case of print output, you must specify the output device if you do not want to use a print parameter in the message type Printer Determination by Message Type/User.
- In the case of faxing, you can enter the fax number; if you do not enter the fax number, the system determines it from the partner data.
- Save your entries.
Notes on transport
Condition records are of a master data nature and cannot be transported.
Business Attributes
ASAP Roadmap ID | 259 | Establish Forms and Messages |
Mandatory / Optional | 1 | Mandatory 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 | SIMG_CFMENUOLMRKOND | 0 | HLA0009517 | Invoice Verification |
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 |
MRM1 | T - Individual transaction object | MRM1 | 9999999999 | Create Condition: Invoice Verification | ||
MRM1 | T - Individual transaction object | MRM2 | 1 | Change Condition: Invoice Verification | ||
MRM1 | T - Individual transaction object | MRM3 | 2 | Display Condition: Invoice Verification |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |