Hierarchy

⤷

⤷

IMG Activity
ID | COCF_KNOWL_PROV | Set Up Storage of Shift Reports and Full-Text Search |
Transaction Code | S_PRN_53000669 | (empty) |
Created on | 20070228 | |
Customizing Attributes | COCF_KNOWL_PROV | Set Up Storage of Shift Reports and Full-Text Search |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | COCF_KNOWL_PROV |
Use
This IMG activity outlines how you have to proceed to be able to store shift reports and activate the full-text search.
The system uses the Knowledge Provider for the purpose of storing shift reports.
Requirements
You have installed a search engine (such as TREX).
Standard settings
Activities
- You activate the storage of shift reports in the Knowledge Provider in the IMG activity Define Repository for Shift Reports. Here you must extend the existing category COCF_SR by adding the repository. The repository is the actual physical storage location for the PDF documents.
- You activate the full-text search facility. You must specify an RFC connection for the previously installed search engine, in the IMG activity Define RFC Destination for Full-Text Search.
- You must then declare this RFC connection as the search server in the IMG activity Define Search Server Relation .
- In the IMG activity Define Full-Text Indexing, you release full-text indexing for the shift reports by setting the Index Releaseindicator for the document area COCF_SR. As a result, a full-text index is generated for all shift reports. In the transaction List Shift Reports (SHR4), you can then use the full-text search by entering a keyword on the initial screen. The system then searches for the shift report using the specified keyword.
If you do not set the Index Release indicator, the field for entering keywords in transaction SHR4 is grayed out.
Note
If you have problems with the full-text search, you can use transaction SKPR07. Here you must enter the document class COCF_SR_PH for the shift reports. Then you can restart any hanging indexing runs or reindex all documents if the search engine has lost the index. The use of transaction SKPR07 is only necessary in exceptional cases, however, because the system executes the indexing runs automatically when a shift report is saved.
If the full-text search fails to find anything although the shift reports sought exist, you must follow the instructions in SAP Note 685521 and then reindex all documents using the transaction SKPR07 (as described above).
Example
Business Attributes
ASAP Roadmap ID | 105 | Define functions and processes |
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 | COCF_KNOWL_PROV | 0 | HLA0006433 O HLA0009533 |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20080502 |
SAP Release Created in | 700 |