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 | OLQN-OQNFB | Define Report Type |
| Transaction Code | S_ALR_87004372 | IMG Activity: OLQN-OQNFB |
| Created on | 19981222 | |
| Customizing Attributes | OLQN-OQNFB | Define report type |
| Customizing Activity | OLQN-OQNFB | Define Report Type |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OLQN-OQNFB |
In this step, you define the report types for defects recording.
The report type restricts the size and contents of the defect data records. In the report type, you link a confirmation profile to a catalog profile. You use the confirmation profile to define the catalogs and defects for defects recording and the catalog profile to define code groups.
Since the notification type is defined using the inspection type, you need the report type to make finer distinctions between defect data. You can define report types for different purposes and according to various criteria, to suit your requirements. We recommend the following:
Recommendation
- Defects Recording
Usually, each department that records defects needs its own recording forms. For example, the department that carries out visual inspections can only make a note of the defect type and defect location, while a department that makes defect analyses and carries out repairs also records the defect cause, the defect valuation and activities. You can use the report type to provide each recording center with the appropriate form for recording defects.
You can assign specific report types to work centers or users. In addition, you can stipulate a suitable report type for each center in an internal memo. - Defect Analysis
The definition of the report type depends on the evaluations that are needed for the defect data, since the report type is a criterion (like the notification type) for summarizing and analyzing defect data in the QM Information System. The report type provides another option for differentiating defect data for evaluation purposes.
Activities
- Determine which criteria is to be used to define the report categories and which report categories are needed. Define the report categories by assigning a catalog profile and a confirmation profile to each report category; this permits the report category to be determined automatically.
- If you define report categories on the basis of the inspecting work center, and if you use inspection plans containing specified work centers, you can assign the report categories to the respective work centers.
The table allows generic entries in the plant and work center fields. Note: Also define a report category for plant '*' and work center '*', so that the system can find a valid report type when defect data is created automatically. - Determine whether you want:
- The system to propose report categories in the user master record
(User parameter QFE = report type key) - The user to be able to change a report type that is automatically found by the system
(User parameter QF1 = X)If necessary, set the user parameters accordingly.
- Determine whether inspection results are to be transferred from subsystems and if defect records are to be generated automatically if characteristic results are rejected. If necessary, you must uniquely specify a report type for the relevant work center.
Further notes for Finding the Report Type
You can assign a report type to the work center master record and define a report type in the user master record. When a defect record is created, the system searches for the report type in the following sequence:
- Work Center
Note: Generic entries for the work center are allowed in the assignment of report types to work centers. When you record defects for an operation or inspection characteristic, the system automatically selects the most suitable report type that has been assigned. If this assignment is not clear, and the system cannot find a report type the user must choose one of the report types.
If the control key for the inspection characteristic stipulates that defect records are to be generated automatically, but there is no work center entered in the operation, the system chooses the report type that is stored under plant '*' and work center '*'. - User Master Record
Note: To store a report type in the user master, use the user parameter 'QFE' and assign the appropriate report type to this parameter as a value.
When users record defects manually in the results recording function or make the usage decision, if you want to allow them to choose a report type other than the one found by the system, use the user parameter 'QF1' and assign the value 'X' to it.
You can use transaction 'QF01' to choose any report type when recording defects for the inspection lot, without having to set the user parameter QF1.
However, if report types have been defined for the work center, the system only allows you to select one of these types when recording defects for the operation or inspection characteristic manually.
Further notes for Finding the Catalog Profile
You can define a catalog profile in the following objects:
- Material master record (or master record for equipment or functional location)
- Notification type
- Report type
In the report type, you can define the object from which the catalog profile is to be taken. The system then searches for a catalog profile in the sequence already mentioned, provided that the material and notification type fields have been checked in the report type and an entry has been made in the catalog profile field. If the system cannot determine a catalog profile, it issues an error message when a defect record is created.
Note: In contrast, you can create a quality notification without having assigned a catalog profile to the notification type. In such a case, there are only text fields and no catalog fields for the individual notification elements (such as, subject, defect type, defect location, defect cause, activity).
Further notes for Dependent Characteristic Specifications
In the inspection characteristic, if you define code groups or selected sets from catalogs that are contained in the notification type assigned to the report type, these code groups and sets provide the values when you record defects for the inspection characteristic. Although the code groups in the catalog profile are not taken into account, the confirmation profile still applies.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional 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 | OLQN-OQNFB | 0 | HLA0006218 A HLA0001809 |
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_TQ86 | V - View | SM30 | 9999999999 | Define Defect Report Type | ||
| V_TQ86A | V - View | SM30 | 9999999999 | Assign Report Type to the Work Center |
History
| Last changed by/on | SAP | 19990503 |
| SAP Release Created in |
