Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
QI (Package) QM IMG and area menu
IMG Activity
| ID | SIMG_CFMENUOLQWOQL1 | Maintain Inspection Types |
| Transaction Code | S_ALR_87005374 | IMG Activity: SIMG_CFMENUOLQWOQL1 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLQWOQL1 | Maintain inspection types |
| Customizing Activity | SIMG_CFMENUOLQWOQL1 | Maintain inspection types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLQWOQL1 |
In this step, you maintain the inspection types and the controls associated with the inspection type.
Using the online documentation, first familiarize yourself with the meaning of the individual fields in this table!
Requirements
Depending on the functions and control options you want to use, you must make sure the following conditions are met before you can maintain the table:
- Catalog 3 for usage decisions and the associated selected sets have been created at the plant level.
- Status profiles for inspection lots have been defined.
- Order types for appraisal costs have been defined.
- Quality notification types have been defined.
- Task list usages have been defined.
- Control keys for inspection operations have been defined.
- Sample types for sample management have been defined.
Standard settings
The table has the delivery class G. The following name range is reserved for the user:
- Inspection type 9*, A*, ... , Z*
Activities
- Define the eight-character keys and the short texts for each inspection type that you want to use.
Note that you are only allowed to use each inspection type for one inspection lot origin. - Determine which control fields are relevant for each inspection type.
Define the contents of the controlling fields for each inspection type. If necessary, you must make sure the conditions mentioned above have been met.
Further notes
The default values in the material specification take effect, if inspections are planned exclusively with a material specification and there is no inspection plan. For these inspection lots, the system creates an inspection operation using these specifications (operation number, control key and text for the operation).
Note: If there is an inspection plan, the system assigns the inspection characteristics from the material specification to the last operation in the plan, providing that these characteristics are not already contained in this plan.
If the inspection characteristics contained in the material specification are identical to those in the plan, and if the default values for these inspection characteristics in the material specification differ from those in this plan, the system uses the specifications from the material specification and ignores the default values in the inspection plan.
If inspection characteristics are linked to class characteristics, the system takes the specifications from these class characteristics and ignores the specifications in the inspection characteristics.
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_CFMENUOLQWOQL1 | 0 | HLA0006211 | Inspection Lot Creation |
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 |
| V_TQ30 | V - View | SM30 | 9999999999 | Define inspection types |
History
| Last changed by/on | SAP | 19990212 |
| SAP Release Created in |
