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 | SIMG_CFMENUOLMENAST | Tips for Fast Message Determination Setup |
| Transaction Code | S_ALR_87100744 | (empty) |
| Created on | 19991126 | |
| Customizing Attributes | SIMG_CFMENUOLMENASTB | "Tips for Fast Message Determination Set-Up": Attributes |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLMENAST |
In this step, you are shown how to set up the message determination (output control) facility quickly. In this case, you need not read the Implementation Guide (IMG) for the other steps to set up this facility, or need only read certain parts of it.
Setting up the Message Determination Process: Options
Message determination deactivated
You can output purchasing documents without the message determination facility. In this case, you must not assign any message determination schemas to the the individual purchasing documents (RFQ, purchase order, etc.). The system then generates a message of the type NEU (new) for each document to be outputted. To determine the printer, the system first checks the settings for the purchasing group. If no printer has been maintained there, it checks the user parameter. If no printer has been specified there either, the system checks the fixed value for the user. If no printer has been specified, the system does not generate a message record.
Message determination activated
Adopt standard setting
In the standard system, the message determination facility is active. A message determination schema is supplied for and assigned to each purchasing document. If you wish to work with this standard setting, you need not make any changes in Customizing.
It is necessary that you maintain condition records for the desired message types:
- Choose Master data -> Messages -> <Purchasing document> -> Create or Change from the Purchasing menu.
- Enter the message type and choose the key combination. The latter determines the condition table in which the condition record is stored.
- Make the necessary entries.
- On the next screen, create the individual condition records.
- Via the menu options Goto -> Means of communication, enter the desired means of communication (e.g. EDI, or an output device such as a printer) for each message record.
- Save your data
Include new message type
If you wish to do this, you must
- Create the message type and define its fine-tuned control (e.g. whether the message type is to be used only for new printouts or only for change notices),
- Assign the message type to a schema
- Define the message determination
- Maintain condition records for the message type, as described above.
How is the printer determined for message output purposes?
The system checks whether a printer has been specified in the condition record.
If so, it is used.
If not, it checks the message type to see whether a print parameter has been set. If no parameter has been set, no message is generated.
If a parameter has been set, a printer is sought in accordance with this parameter. If a printer is found, it is used to output the message. If not, no message is generated.
Note:
You can change the printer when outputting messages (e.g. via the menu options Purchasing document> -> Messages -> Print/transmit). Select the desired message and choose Goto -> Message details -> Edit -> Means of communication.
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 |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19991126 |
| SAP Release Created in |
