Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
QM-PT-IP (Application Component) Inspection Planning⤷
QPMS (Package) QM: Planning for Multiple Specifications
IMG Activity
| ID | 0LQS_MS_T | Define Object Types for Multiple Specifications |
| Transaction Code | S_AC0_52000461 | (empty) |
| Created on | 20050203 | |
| Customizing Attributes | 0LQS_MS_T | Define Object Types for Multiple Specifications |
| Customizing Activity | 0LQS_MS_T | Define Object Types for Multiple Specifications |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | 0LQS_MS_T |
Use
In this IMG activity, you define the object types for multiple specifications. You can define, for example, whether the object in question is a pharmacopoeia, country, or customer.
The object type controls the transfer of a batches suitability for an object based on multiple specifications. You must assign a control key to the object type. This control key determines whether the batch classification is to be performed based on the customer, country, or general object.
The control is technically implemented via a field name. This field name also allows you to use custom objects for classification.
If you want to store the suitability of a batch for a multiple specification object, you must specify class characteristics in the table of object types. For each object type, you can specify a characteristic with the description Suitable For and a characteristic with the description Not Suitable For. Whether you need a characteristic with a positive valuation or a characteristic with a negative valuation depends on the type of batch search you plan to use:
If you want to search using the question "Is the batch suitable for...?", you just need characteristics with positive valuations.
If you also want to search with the question "Is the batch unsuitable for...?", characteristics with negative valuations are also required.
You define the suitability of a batch for a multiple specification object when making the usage decision. The system determines a proposed value for each object based on the multiple specification. The user can accept or change this proposed value as required. This value is transferred to the corresponding class characteristic for the batch class when you save the usage decision.
Requirements
You have defined batch classes and class characteristics.
For more information about processing class characteristics, see:
SAP Library -> SAP ERP Central Component -> Cross-Application Components -> Classification System -> Characteristics
Standard settings
The following three object types are supplied with the standard system:
- Customer
- Country
- Pharmacopoeia
Activities
- Define which object types require multiple specifications.
- Define whether the suitability of batches is to be determined based on multiple specifications and transferred to batch classification.
- If required, define the class characteristics for each object type that describe whether a product is suitable or not suitable.
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| 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 | 0LQS_MS_T | 0 | HLA0006200 | Basic Data |
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_TQMS1 | V - View | SM30 |
History
| Last changed by/on | SAP | 20050207 |
| SAP Release Created in | 600 |
