Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-EIM-ESH (Application Component) NetWeaver Enterprise Search⤷
S_ESH_CUSTOMIZING (Package) Customizing
IMG Activity
| ID | MAPPINGRULES | Define Key-Mapping Rules |
| Transaction Code | S_BCE_68002444 | (empty) |
| Created on | 20090120 | |
| Customizing Attributes | MAPPINGRULES | Define Mapping Rules |
| Customizing Activity | MAPPINGRULES | Define Mapping Rules |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | MAPPINGRULES |
In order to use the long text search for BO legacy search object connectors with product version SAP_R/3_4.70, you have to perform the activities in this customizing activity.
To calculate long-text keys from object instance keys, you have to define key-mapping rules.
Example
You can define companies (key=LIFNR BUKRS) for vendors (key=LIFNR). The long-text key is a combination of LIFNR and BUKRS. A long-text key could look as follows: 000010000 4567.
To enable the search for the vendor long-text, you need to create two key-mapping parts for both fields of the object instance key. For the first part, set Rule Part =1 and for the second part, Rule Part =2.
Requirements
Standard settings
Recommendation
Activities
Choose New Entries and create new key-mapping rules for the attributes of the required node in a search object connector template for which you want to use the long-text search.
Specify the following parameters:
- Software Comp.: Specify the software component of the search object connector template, for example
SAP_R/3_4.70. You can find the value in the template modeler. - Model: In earlier releases, this entry was used as a characteristic for software components. However, you must enter the value
STANDARDfor compatibility reasons. - Object Type: Specify the object type, for example
CUSTOMER. The object type is the data model of a business object for the search. Together with the software component, the object type forms the search object connector template. You can find the value in the template modeler. - Node Name: Specify the name of the node for which you want to define the key-mapping rule. In most cases, you specify the root node here. You can find the value in the template modeler.
- Rule Part: In this field, specify the position of this element in the rule. If it is in the first position or a single value, enter 1. If it is in the second position, enter 2.
The key-mapping rule comprises the following parameters:
- Rule Term: Specify the content of the rule. In most cases, this is the ID of the required attribute in the selected node, for example
MATNR. However, you can also use a constant, for example '+' or '&'. If the object type consists of more than one element, you must define a separate key-mapping rule for each element and specify the sequence in the Rule Part field. - Is Field: Select this field if the rule part is a node field. If you are using a constant for this rule, do not select the field.
Further notes
Business Attributes
| ASAP Roadmap ID | 262 | Technical and Graphical Settings |
| 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 | MAPPINGRULES | 0 | B200003488 | NetWeaver Enterprise Search |
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_ESH_KEYM_RULES | V - View | SM30 |
History
| Last changed by/on | SAP | 20090122 |
| SAP Release Created in | 720 |
