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 | OLQZ-VH | Define Data Origin |
| Transaction Code | S_ALR_87005346 | IMG Activity: OLQZ-VH |
| Created on | 19981222 | |
| Customizing Attributes | OLQZ-VH | Define data origin |
| Customizing Activity | OLQZ-VH | Define data origin |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OLQZ-VH |
In this step, you define data origins for certificates.
If you are using certificate types which contain value information for inspection characteristics or class characteristics, the values can have the following origin:
- Default values for characteristics
- From master inspection characteristics
- From batch specifications
- Results for characteristics
- From result records for the inspection lot or partial lot
- From batches
You can define sources for language-specific characteristic short texts irrespective of the origin of the value specifications:
- Characteristics from a certificate profile
If no text is found here, the system accesses further master records:
- Master inspection characteristics
- Class characteristics
If the results are loaded from inspection lots or partial lots, you must specify strategies for the skip procedure when maintaining the certificate profiles.
If the results for inspection points or samples were loaded, the mean values and original values for the last inspection point or last sample (or for all inspection points or samples in an inspection lot) can be included in the certificate.
You can define keys for all of the listed data origins in the system and assign function modules for data retrieval to these keys.
In certain circumstances you need to include differing materials in certificates, for example, if the same material is sold in different forms, but the properties of the material remain the same.
To avoid incorrect assignments of data origins, you define allowed combinations of data origins for characteristic specifications and characteristic values. You can also define that specifications and values must come from the same source.
Standard settings
The system already contains predefined keys and function modules for the data origins.
Proposals are also implemented in case of a skip.
Recommendation
- Use the data origins set in the system. Consult an expert if you want to implement your own data origins.
- Do not change the function modules implemented in the standard system. Create your own function modules, if necessary. Use the available function modules as copy models, for the interfaces in particular.
Activities
You can use the online documentation for the table fields and function modules to determine from where the system retrieves the characteristic data in the standard system. It is only necessary to define your own origins and function modules if this manner of retrieval is not acceptable. In doing so, consider the following origins:
- Origin of the default values
- Origin of the short texts
- Origin of the result values
- Alternative strategy in case of a skip
- Allowed combinations of default origins and characteristic values
The report RQCFTQ65 determines the usual combinations using the characteristic data in the existing certificate profiles and makes entries in the table.
Further notes
You can specify which inspection characteristic results are used for data retrieval. In the standard system, these are all of the valuated characteristics. In the chapter Quality Inspection/Results Recording, you will find more detailed information under filter for inspection characteristics. The table entry QC00 is responsible for retrieval of the certificate data.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional 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 | OLQZ-VH | 0 | HLA0006216 | Basic Data for Certificates |
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_TQ61 | V - View | SM30 | 9999999999 | Origin of characteristíc values | ||
| V_TQ62 | V - View | SM30 | 9999999999 | Output strategy when inspection characteristics are skipped | ||
| V_TQ63 | V - View | SM30 | 9999999999 | Origin of characteristic specifications | ||
| V_TQ64 | V - View | SM30 | 9999999999 | Origin of characteristic texts | ||
| V_TQ65 | V - View | SM30 | 0000000000 | Allowed combination of specification and value origins |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
