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_CMMENUOLMBNAKT | Maintain Condition Tables |
| Transaction Code | S_ALR_87000166 | IMG Activity: SIMG_CMMENUOLMBNAKT |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CMMENUOLMBNAKT | Maintain Condition Tables |
| Customizing Activity | SIMG_CMMENUOLMBNAKT | Maintain Condition Tables |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CMMENUOLMBNAKT |
All fields that represent a condition for creating output are defined in a condition table.
In menu option "Maintain condition tables", you can check the condition tables that are defined for output determination in Inventory Management. Please note that you check only the structure of the table here. You define the table entries by creating conditions.
Example
In the standard system, the creation of goods receipt/issue slips (also referred to as goods accompanying slips) depends on the following fields:
- transaction type (derived from the transaction)
- version (derived from the transaction)
- print indicator (derived from the movement type)
These fields are defined in condition table 072.
For label printout, the label type and label form from the material master record ("Storage" view) are also relevant. All fields for label printout are defined in condition table 070.
Default settings
The following condition tables are defined in the standard SAP R/3 System:
- 070 label printout
- 071 MAIL messages at time of goods receipt
- 072 GR/GI slips
- 073 GR/GI slips for materials provided to subcontractors
- 074 MAIL messages for missing parts
- 075 kanbans at time of goods receipt
SAP Recommendation
You should not change the condition tables contained in the SAP standard version.
It is not usually necessary to create your own condition tables. It is not useful to create condition tables with the following fields:
- User, plant, storage location
This data is used for printer determination and is already contained in the printer determination table. - Movement type
The movement type is already indirectly contained in the condition tables via the print indicator. If you need a different control for particular movement types, define new print indicators and assign them to the relevant movement types.
Actions
Simply select Material document -> Condition tables -> Display to check whether condition tables 070 to 075 exist.
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_CMMENUOLMBNAKT | 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 |
| IMGDUMMY | D - Dummy object | M703 | 1 | Output: Create Conditions Table | ||
| IMGDUMMY | D - Dummy object | M704 | 2 | Messages: Change Condition Table | ||
| IMGDUMMY | D - Dummy object | M705 | 3 | Output: Display Conditions Table |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
