Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MB0C (Package) Customizing R/3 inventory management
IMG Activity
| ID | SIMG_CFMENUOLMBM708 | Maintain Output Determination Procedures |
| Transaction Code | S_ALR_87000149 | IMG Activity: SIMG_CFMENUOLMBM708 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLMBM708 | Maintain Message Schema |
| Customizing Activity | SIMG_CFMENUOLMBM708 | Maintain Output Determination Procedures |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLMBM708 |
An output determination procedure groups together all output types of an application. For Inventory Management, output determination procedure ME0001 is predefined.
In the output determination procedure, you can enter a requirement for individual output types that must be fulfilled for the output to be created.
Example:
A mail for the order price quantity variance is only sent if there is actually a variance in the order price quantity. This check is stored in requirement 172.
Default settings
The standard output types are already assigned to procedure ME0001.
SAP Recommendation
SAP recommends that you accept the settings defined in the standard system. In this case, no action is required on your part.
Activities
Select Material document -> Output procedures to check whether all output types are assigned to procedure ME0001.
Please note that the following output types need a requirement:
- MLGR (GR notification) -> 171
- MLMD (GR quantity variance) -> 172
- MLUD (GR underdelivery) -> 174
- WE03 (GR slip vers 3) -> 173
- WEE3 (GR label vers. 3) -> 173
- WE03 (GR slip vers. 3) -> 173
- WA03 (GI slip vers. 3) -> 173
- WLB3 (GI slip SC vers. 3) -> 173
Note
In the standard version, a GR message (message type MLGR or MLUD) is issued for each material document item. If you only want to send one mail for each material document, you must define a new condition (beginning with 9xx) that groups together the source texts of conditions 171 and 173. In this case, only the item data of the first item (for example, purchase order number) is available for the text variables.
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 | SIMG_CFMENUOLMBM708 | 0 | HLA0006045 O HLA0006047 O HLA0006048 |
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_T683_XX_MB | C - View cluster | SM34 | 0000000008 | Conditions: Procedure | ||
| VOFM | T - Individual transaction object | VOFM | 0000000005 | Configuration for Reqs, Formulae |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
