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_CFMENUOLQBOQB4 | Define Document Types |
| Transaction Code | S_ALR_87004729 | IMG Activity: SIMG_CFMENUOLQBOQB4 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLQBOQB4 | Define document types |
| Customizing Activity | SIMG_CFMENUOLQBOQB4 | Define document types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLQBOQB4 |
In this step, you define the document types for the exchange of quality documents with vendors.
Standard settings
Two document types have been defined in the standard system for QM in Procurement:
- Q01 - quality assurance agreement with vendors (QAA)
(Stored in the info record for the material and vendor supply relationship) - Q02 - technical delivery terms (TDT)
(Stored in the material master)
The settings have been made so that
- The output function in procurement (for example, the purchase order printout) can process these documents. Therefore, in the standard system there are only SAPscript texts allowed for this document type.
- You can follow a procedure that complies with the rules for quality documents, for example, whether a new document version is required, if a released document has been changed.
You should check the controls for these document types, but not change them. You should also not define any additional document types for QM in procurement.
You can only change the settings relating to the document type, provided that this does not affect the output functions in Procurement. For example, you may want to define a different status sequence from the one contained in the standard system for these documents. To do this, you must temporarily remove the Customizing block on these document types.
Further notes
General Customizing of QM Documents
You can find more information about the document types used in the QM component in the Environment, Central Functions, Define Document Types section.
The complete Implementation Guide for the Document Management System is contained in the section Cross-Application Functions, Document Management System.
Purchase Order Printout
- If there are no valid TDTs or QAA and you ignore the warning messages that appear when the request for quotation and the purchase order is made, there is no reference to the TDTs or the QAA in the procurement output.
- If the valid TDTs or QAA contains a long text of less than 2 lines, the single line of text is not printed in the procurement output. You must therefore create another line by pressing 'Return'.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 3 | Nonrequired 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_CFMENUOLQBOQB4 | 0 | HLA0001806 | QM Control in Procurement |
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_TQ09 | V - View | SM30 | OLQB | Define document types for QM in Procurement | ||
| IMGDUMMY | D - Dummy object | OQBB | OLQU-D | Lock document type Customizing | ||
| IMGDUMMY | D - Dummy object | OQBC | OLQU-D1 | Unlock document type Customizing |
History
| Last changed by/on | SAP | 19990312 |
| SAP Release Created in |
