Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
ME0C (Package) Customizing R/3 Purchasing
IMG Activity
| ID | SIMGOLMEVNE3 | Define Output Types for Inbound Delivery |
| Transaction Code | S_ALR_87008815 | IMG Activity: SIMGOLMEVNE3 |
| Created on | 19990126 | |
| Customizing Attributes | SIMGOLMEVNE3 | Define Message Types for Shipping Notification |
| Customizing Activity | SIMGOLMEVNE3 | Define Message Types for Shipping Notification |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMGOLMEVNE3 |
In this step, you define the message types for inbound deliveries.
In the SAP System, the message type denotes different kinds of message (in Purchasing, these are generally communications sent to vendors), such as purchase orders, inbound delivery messages, and urging letters (expediters).
To define a message type, you must enter the following:
- Message type
alphanumeric key, up to four characters in length, uniquely defining a message type.
- Access sequence
Key for the access sequence.
- Description
Text briefly describing the message type.
- Detail data (only the most important items are explained):
- Multiple transmission
- Indicator denoting whether a message can be transmitted to the same partner more than once.
- Transmission medium
- Single-character, numeric key determining the type of message processing (e.g. printout, transmission as fax or e-mail).
- Time-spot
- Single-character, numeric key determining the time of message processing (e.g. immediately a document is saved or with the next selection run).
- Partner role
- Partner role defining the recipient.
- Condition access
- Indicator allowing you to specify that the default message is to be determined via the condition technique.
- Access TNADR
- Single-character, numeric key defining the conditions on the basis of which the print parameters are determined (see the step Adjust Forms for Purchasing Documents).
Note
The values for the transmission medium, time-spot, and partner role entered in the detail data are automatically adopted as default values when a message record belonging to the message type is created.
Fine-tuned control for message types
There is no fine-tuned control for inbound delivery messages.
Recommendation
- To create a new message type, copy a similar, already existing one and make the necessary changes.
- If you define your own message types, the key should begin with the letters Y or Z, since SAP keeps these name-slots free in the standard system supplied.
Activities
- Check the extent to which you can use the message types included in the standard SAP system or to what extent you have to change them.
- Define your message types for inbound deliveries.
Business Attributes
| ASAP Roadmap ID | 259 | Establish Forms and Messages |
| Mandatory / Optional | 3 | Nonrequired 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 | SIMGOLMEVNE3 | 0 | P450002031 | Message Determination |
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_E1 | C - View cluster | SM34 | OLMEVNE3 | Define Message Types for Inbound Delivery |
History
| Last changed by/on | SAP | 20000107 |
| SAP Release Created in |
