Information Sheet on Transferring QM Inspection Methods
A. Object Profile
Object Name and Identification
Name of application object |
Inspection method |
Name of business object (BOR object) |
QMTB |
DX Workbench object and possibly subobject number(s) (DX Workbench <= 4.5) |
- |
Change document object supported? |
No |
Long text object |
Yes |
Category of data |
Master data |
Numbering |
External |
SAP field for the legacy number available? |
No |
Transactions
Create |
QS31 |
||
Change |
QS33 |
||
Display |
QS34 |
||
Delete |
QS35 |
Other Programs
Reports for post load verification and analyzing of data transferred |
General stock list (QS38) |
Mass delete program function? |
No |
Change program available? Mass maintenance tool applicable? |
No |
Tables/Databases
Main tables |
QMTB (Inspection method master) QMTT (short texts for inspection method) STXH (long texts for inspection method) STXL (long texts for inspection method) |
Main logical databases |
QMTB: In logical database PGQ QMTT: In logical databases PGQ and QTQ |
Tablespace |
- |
Customizing
Customizing activities that affect data transfer |
- |
Time and Sequence
Time for the transfer |
Any time for data transfer |
Dependencies on other data |
If the inspection method is classified and the classification should be copied to the SAP system, the classes must already be available in the SAP system before the inspection methods are posted. The same applies to assigned documents. |
SAP Notes
SAP note no., version no. |
None |
B. BI / DI Information
BI / DI data transfer program |
- |
Special notes and constraints |
- |
User exits or BAdis available? |
- |
Program for generating test data |
- |
Append structures |
- |
Z-structures |
- |
NODATA character |
- |
RESET character |
- |
C. BAPI Information
Required authorization? |
Q_STA_QMTB, Q_MASTER D |
Business object method |
SaveReplica |
Message type |
QSMT |
IDoc type |
QSMT01 |
Workflow for error handling |
No |
Which attributes are covered? Are all necessary parameters included? If not, which ones are not included? |
All attributes (see QMTB, QMTT) All the required parameters are included. |
Are the created objects rendered in a message within the standard parameter RETURN? * |
No |
Test run flag (for details see *) |
No |
Mass update possible? |
Yes Yes |
Is the BAPI extensible? - Parameter extensionIn/extensionOut? - User exits or BAdis available? |
Yes |
Program for generating test data? |
RBDSEQSMT |
Special notes for parallel runs |
No restrictions |
Special notes and constraints |
The IDoc does not have a hierarchical structure. The IDoc interface was automatically created using ALE-BAPI generation. |
* See the guide 'BAPI Development for Mass Data Transfer'.
D. EDI Information
Message type |
- |
IDoc type |
- |
X12 message type |
- |
Edifact message type |
- |
Output type used? |
- |
Workflow for error handling |
- |
Processing program |
- |
Special notes and constraints |
- |