Hierarchy
⤷ SD-BIL-RB (Application Component) Rebate Processing
⤷ WCB1 (Package) IS-R: Volume-based rebate (Customizing)
IMG Activity
ID | SIMG_CMMENUOLMENF016 | Maintain Message Types |
Transaction Code | S_ALR_87099979 | (empty) |
Created on | 19990408 | |
Customizing Attributes | SIMG_CMMENUOLMENF016 | Maintain message types |
Customizing Activity | SIMG_CMMENUOLMENF016 | Maintain message types |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CMMENUOLMENF016 |
In this section, you define the message types for the settlement runs.
The message type is used to map various messages in the SAP system, such as arrangements and settlement runs for arrangements.
To define a message type, you must make the following entries:
- Message type
Alphanumeric key with up to 4 characters, which uniquely identifies the message type.
- Access sequence
Key of the access sequence.
- Description
Text that describes the message type
- Detailed data (only the most important detailed data is described:
- Transmission medium
One-character, numerical key that defines the type of message processing (e.g. printout, send by fax).
- Time
One-character, numerical key that defines the time of message processing (e.g. immediately when the document is saved or at the next selection run).
- Partner function
Partner function that defines the recipient.
- Condition access
Indicator that you use to define that the message default for the message is to be provided via the condition technique.
- Print parameters
One-character, numerical key that defines the conditions that are used to define the print parameters (see step Assign Output Devices and Print Parameters).
- Archiving mode
This field controls whether a document is printed, or archived, or both.
- Document type
This field identifies the archived messages and determines whether they are settlement runs for an arrangement, etc.
Note
The values entered in the detailed data for transmission medium, time, and partner function are automatically used as default values when a message record is created for the message type.
Example
Requirements
Standard settings
The following message types are provided in the standard system:
- WNAK: Settlement of credit-side arrangements
The condition granter can be informed of a settlement run. Printer and fax are supported as transmission media. The standard system contains a form routine for replacing text symbols. This form routine also replaces variables that relate to the fields of tables KONA and EBAB.
- WNAD: Settlement of debit-side arrangements
The rebate recipient can be informed of a settlement run. Printer and fax are supported as transmission media. The standard system contains a form routine for replacing text symbols. This form routine also replaces variables that relate to the fields of tables KONA and EBAB.
Recommendation
To create a new message type, copy a similar, existing message type and make the necessary changes.
If you define your own message types, take account of the name space conventions.
Activities
- Check the extent to which you can use the standard message types, and how much you would have to change these.
- Define your message types for the settlement runs.
Further notes
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | 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_CMMENUOLMENF016 | 0 | HLA0001533 | Subsequent Settlement |
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 |
VVC_T685B_WN | C - View cluster | SM34 | Message types settlement runs |
History
Last changed by/on | SAP | 19990409 |
SAP Release Created in |