SAP ABAP IMG Activity REFXV_TIVCASHSTRLOC (Define Search Strategy for Deriving Hierarchical Location)

Hierarchy

☛ EA-FIN (Software Component) EA-FIN
   ⤷ RE-FX (Application Component) Flexible Real Estate Management
     ⤷ RE_CA_SH (Package) RE: Search Help

IMG Activity

ID	REFXV_TIVCASHSTRLOC	Define Search Strategy for Deriving Hierarchical Location
Transaction Code	S_XEN_65000024	(empty)
Created on	20050715
Customizing Attributes	REFXV_TIVCASHSTRLOC	Define Search Strategy for Deriving Hierarchical Location
Customizing Activity	REFXV_TIVCASHSTRLOC	Define Search Strategy for Deriving Hierarchical Location

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	REFXV_TIVCASHSTRLOC

Use

You can use a search strategy so that an appropriate hierarchical location can be proposed for a given parcel (or piece of land).
Search strategies use search methods, which specify how the hierarchical location is determined from the object data.
In order for the system to be able to determine a default value or possible search help value for the hierarchical location of the parcel, exactly one search strategy must be active for the LOCHIER search field.

Requirements

Standard settings

Activities

Define the search strategy for the LOCHIER search field as follows.

Set the Active indicator for the search system you want the system to use. (All other search strategies are then superfluous and can be deleted. It is only possible in the test phase to define one search strategy for each search method being tested.)

Enter a name for the search strategy.

Specify how the search takes place:

• Name
  Text of search strategy (informational only)
• Search Method
  This is a method that is predefined in the system. The method describes how the search is performed. The way the system processes the values for the search strategy depends on the method you select here. Choose a method using the input help.
• Active?
  You can only use search strategies. For example, if you copied the search strategies from standard Customizing, then set the Active? indicator for those that you want to actually use in your system.
• Other Values
  Set this indicator, if you also want the standard search help to be available. The system then displays a Further Values row, in addition to the values returned by the search strategy. From there you can navigate to the standard search help.

Only one search method, LOCHIER, is predefined in the system for the hierarchical location. You can activate it by copying the sample code in the BADI_RECA_SEARCH_METHOD BAdI:

LOCHIER: Derive hierarchical location from already existing hierarchical location.

This search method assumes that the texts of the hierarchical locations in the different location structures do not differ. For a hierarchical location being derived, the system therefore checks if a hierarchical location was already entered (and if so, which one) and if there is a corresponding hierarchical location with the same text in the other location structures. If there are hierarchical locations that meet these criteria, then the system proposes them.

To be able to use this search method (that is delivered with the system), you have to copy the sample coding of the implementing class CL_EXM_IM_RECA_SEARCH_METHOD of enhancement spot BADI_RE_CA_SH to a customer class. Then you must activate this customer implementation.

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	REFXV_TIVCASHSTRLOC	0	AEN0000002	Land Use Management

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_TIVCASHSTRATSY	V - View	SM30		☐	☐

History

Last changed by/on	SAP	20050715
SAP Release Created in	600