Ansicht
Dokumentation
MAPPINGRULES - Define Key-Mapping Rules
General Data in Customer Master Vendor Master (General Section)This documentation is copyright by SAP AG.
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.
You can define companies (key=LIFNR BUKRS) for vendors (key=LIFNR). The long-text key is a combination of LIFNRand 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.
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 STANDARD for 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.
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.
Length: 3270 Date: 20240523 Time: 212441 sap01-206 ( 58 ms )