Hierarchy
⤷ QM-IM-SM (Application Component) Sample Management
⤷ QPR (Package) QM sample management
IMG Activity
ID | QPRE_CREATE_EXT_SAMP | BAdI: Creation of Samples for Externally Triggered Inspection |
Transaction Code | S_PCO_36000129 | (empty) |
Created on | 20050428 | |
Customizing Attributes | QPRE_CREATE_EXT_SAMP | BAdI: Creation of Samples for Externally Triggered Inspection |
Customizing Activity | QPRE_CREATE_EXT_SAMP | BAdI: Creation of Samples for Externally Triggered Inspection |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | QPRE_CREATE_EXT_SAMP |
Use
This Business Add-In (BAdI) is used in the Quality Inspection (QM-IM) component.
When creating inspection lots, you can use this BAdI to create additional physical samples, and to explicitly assign the associated inspection point to the work centers for an inspection operation in the inspection plan.
The BAdI is called in the function module QPRE_PREPARE_ALL_PHYS_SAMPLES.
Standard settings
In the standard, this BAdI is active for the origin 17 (external inspection). If you activate this BAdI without making any changes to it, externally created samples will be represented as physical samples in quality management (QM) in the ERP system, and, if planned, assigned to a specific work center.
The BAdI is filter-dependent. Create implementations for the required origins. If required, you can use the implementation for the origin 17 as a template.
This BAdI is not designed for multiple uses.
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
Example
To display sample coding, choose Goto -> Sample Code -> Display.
See also
Methods
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
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 | QPRE_CREATE_EXT_SAMP | 0 | HLA0100686 | Sample Management |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20050428 |
SAP Release Created in | 600 |