Block 1-> Change address groups for connection objects and PoDs

With this action it is possible to set own addressgroups for connection objects and point of deliveries. This is particularly important for technical object address searches. Now it possible to get better results- e.g. if somebody searches for CITY = ‘Examplevillage’, that the search now finds only connection objects OR(!) PoDs.

In former releases it finds connection objects AND PoDs. It is also possible to run or switch back to the old mode.

Execution of this block: recommended

Runtime of this block: medium.

Block 2-> Fill index table ECRM_ISU_TO_IDX for a better search performance

Individual object, IBase components and their sets are stored in many different tables. The main key of the object is defined in the new index table. This results in a better search performance for these obejcts.

Execution of this block: recommended

Runtime of this block: High

Block 3-> Deactivate index table ECRM_ISU_TO_IDX (for migration, for example)

Sometimes it makes sense to switch off the index, for example, during migration from IS-U, or when performance deteriorates during mass creation of technical objects.

We recommend execution of this block for mass processing of technical objects.

Runtime of this block: Very low

Block 4-> Fill field IN_GUID of table IBIN (only for migration from older releases)

For a better selection of IBase data in the new searches, it is obligate to have the component GUID in a RAW 16 format. This was not possible in older releases.

Execution of this block: obligatory if the fields are empty in table IBIN

Runtime of this block: Low

Block 5-> Create CRM GUIDs for premises (necessary for using WebClient UI)

Appendix

BADI ECRM_ISU_UTILITY_UIS was created primarily for the GUI interfaces. You can also use method CHECK_DATA_BEFORE_SAVE to make checks before saving.