Functionality
Search function of the IS-U Data Finder as programming interface
Supported Object Types
The search for data objects in the following BOR object types issupported:
Name,,Object type (constant in include IEOBJTYP)
Customer,,co_objtype_bpartner
Contract account,,co_objtype_account
Contract,,co_objtype_econtract
Budget billing plan,,co_objtype_budbilplan
Installation,,co_objtype_instln
Premise,,co_objtype_premise
Connection object,,co_objtype_connobj
Device location,,co_objtype_devloc
Device,,co_objtype_device
Print document,,co_objtype_printdoc
SM order,,co_objtype_smorder
Search Algorithm
The hit list contains all the data records that have a foreign keyrelationship to an object selected by the search criteria. In the caseof multiple selections, a relationship to all selected objects mustexist.
Definition of the Hit List.
The set of supported object types and their foreign key relationships(see listing below) form a cycle-free graph, the search tree. Theobject type of the search object is the root of the search tree.
A partial hit list is then determined for each node (=object type). Itcontains all the data records that have a foreign key relationship tothe partial hit lists of all child nodes and which also meet theselection criteria for the node itself.
The hit list for a node is only filled when either a sufficiently exactselection (see below) for the node itself is available or when a childnode has a (non-blank) partial hit list. Otherwise, the partial hitlistremains blank. Child nodes with blank partial hit lists are ignoredduring the selection by foreign key relationship.
The hit list of the root node that is determined in this manner is thehit list of the entire search operation.
Search methods
The Data Finder analyzes the following foreign key relationships:
Customer,,- Contract account
Contract account,,- Contract
Contract account,,- Printed document
Contract,,- Installation
Installation,,- Device
Installation,,- Premise
Premise,,- Connection object
Budget billing plan,,- Contract
Device location,,- Connection object
Device location,,- Device
Connection object,,- SM order
Search Criteria
The search criteria are analyzed as follows for the indivdual objecttypes. The system differentiates between selective search criteria(which are used to determine a partial hit list) and non-selectivecriteria (which merely restrict a partial hit list).
Object type,,Selective criteria,,Non-selective criteria
Customer,,Name, address,,-
Contract account,,-,,Company code
Contract,,-,,CCode, division, date
Installation,,-,,Division, billing class, date
Device,,Serial number,,Division, date
Premise,,-,,House no.,floor.,apt. no.,...
Connection object,,Address,,-
Bud. bill. plan,,-,,Date
Device location,,-,,Location
Printed document,,-,,Posting date
SM order,,Corr. serv. notif.,,Order type, category, status
In addition, the key of the object type itself is supported as aselective search criteria for most object types. If no selectivecriteria are available for an object type, an E message is triggered.
Limiting the Hit List
To avoid performance problems in case of insufficiently narrowselection, a maximum partial hit list of 100 records is read duringeach database access. If the partial hit list is limited, then theoverall hit list may be incomplete, and a W message will be returned inthe RETURN structure.

Search Results
The hit list is available in table SEARCHRESULT. Each line has theformat of a persistent BOR object reference and can be processed withthe container macros. In many cases, however, the key of the dataobject (which is in field OBJKEY) will suffice.

Comments on the RETURN Parameter
The RETURN parameter returns exceptions that occurred with the functionmodules in the form of messages.
The following constellations are supported:
Situation,, ,,Message (type, no. msg. cl.)
Parameter OBJECTTYPE blank,, ,,E877(E9) (Termination)
Insufficient selection criteria,, ,,E203(E7) (Termination)
Parameter OBJECTTYPE not supported,, ,,E201(E7) (Termination)
Enter country for phone number,, ,,E205(E7) (Termination)
Undefined exception ISU_FINDER,, ,,E887(E9) (Termination)
Limited hit list,, ,,W202(E7) (Normal processing)

Example
You search for all installations in division "01" for customer "M.King" in "Crown Street 9".
OBJECTTYPE,,= 'INSTLN'.
SEARCHPARAMETERS-NAME1_FIR,,= 'M*'.
SEARCHPARAMETERS-NAME2_SUR,,= 'King'.
SEARCHPARAMETERS-STREET_CONN_OBJ,,= 'Crown Street'.
SEARCHPARAMETERS-HOUSE_NO_CONN_OBJ,,= '9'.
SEARCHPARAMETERS-DIVISION_INSTALLATION,,= '01'.
CALL FUNCTION 'BAPI_ISUFINDER_FINDOBJOFDATE '
....
The system initially searches for a customer named "M. King", of whichthree are found. It then searches all the contract accounts, and allthe contracts with division 01 for these contract accounts. Let us callthese contracts A, B, and C.
The system also selects all connection objects in "Crown Street 9", andall the premises for these connection objects, e.g. 21, 22.
The hit list for installations now includes all the installations thatbelong to both one of the contracts (A, B, or C) and toone of the premises (21 or 22)

Further information
Also see the documentation for function group EFND.