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 | OLQW-EV | Define Parameters for Input Processing |
| Transaction Code | S_AL0_96000348 | (empty) |
| Created on | 20011106 | |
| Customizing Attributes | OLQW-EV | Define Parameters for Input Processing |
| Customizing Activity | OLQW-EV | Define Parameters for Input Processing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OLQW-EV |
Use
In this step, you define the key fields and the parameter values for input processing. A filter value of an implementation of the Business Add-In QM_INPUT_PROCEDURE is assigned to every key input-processing field.
Requirements
If you want to use one of the implementations delivered by SAP, select the relevant implementation using the F4 help for the "BADI Filter Value" field.
If you want to use your own logic for the input processing of quantitative measured values, you must first create an active customer implementation with a filter value in the Business Add-Ins structure in Customizing, or using transaction SE19. You can find additional information under Business Add-In for Input Processing.
Standard settings
If you have activated the input processing control indicator for a characteristic, you can access the implementations delivered by SAP in the PLM Addon package:
QM_INPPROC_100 Output like Input (Decimal Places)
and
QM_INPPROC_200 Output According to Significant Characters
The first implementation uses the "input like output" process to clarify the principle behind input processing.
The second implementation shows you how the output of significant characters can be changed using input processing.
These implementations can be used as templates to help you to represent your own input processing procedures for quantitive measured values.
Activities
1. If you are using the SAP implementation "Output According to Significant Characters", you define the number of significant characters using parameter 1 on the detail screen.
2. If you have created a customer-specific, active implementation with a filter value, you define a key for input processing in the customernamespace (A* ... Z*, 9*) and assign a suitable short text to it. Then enter the relevant filter value in the Procedure column. If your customer-specific implementation works using parameters, you maintain the values of these parameters on the detail screen.
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 3 | Nonrequired 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 | OLQW-EV | 0 | HLA0006201 | Inspection Planning |
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_TQ71 | V - View | SM30 | 9999999999 |
History
| Last changed by/on | SAP | 20011106 |
| SAP Release Created in | 470 |
