Show TOC

Background documentationExcursus: Changing settypes and attributes Locate this document in the navigation structure

Activities

Adding, changing or deleting attributes in existing settypes

  • At this point, you do not need to do anything else because the set type DDIC structure is directly included in the CI include; the fields are available on all levels

  • Caution: Changing attributes can cause problems, particularly if the set type tables contain entries

Adding, Changing or Deleting Set Types

  • See note 1060547 for CRM 5.1 and for CRM 5.2 up to SP01

  • Add set types: Restart the report for generating the include CI_POD In addition, the new set types are attached to the end of the structure with a new suffix; the other includes remain unchanged.

  • Changing: Do not change the set types manually.

  • Delete: Execute the report again. The include is deleted from the structure; the other includes remain unchanged. The suffix of the deleted set type can be used for a new set type.

Time periods for IObjects set types (since CRM 5.1 SP 4)

As of support package four of CRM 5.1, it is possible to manage timeslices in the set types of an individual object (service industry version). This means to make it possible to change field values with a kind of “activation date”, in the future as well as in the past.

To activate the time dependency of a set type, choose the setup report ECRM_ISU_TO_DIV_SETUP and the choose the Execute button as shown in the following figure.

Note Note

Technical Background

If you mark a set type as time dependent and choose the Apply Changes button in the popup, the system replaces the generated SAVE function of the set type with a generic SAVE function. Accordingly, it is also possilbe to deselect the indicator and reactivate the generic function. However, in this case, changes will be lost in the future as the generated function always uses the current date as the start date and 31/12/9999 as the end date if the set type is changed. The time dependency of the set types is independent from the service type; however, its use is only optional for every service type. To use the timeslices, use the view configuration tool to set the ‘VALID_FROM’ and/or ‘VALID_TO’ fields to the technical data detail view. These two fields are always generated when the set type is created. However, they are only valid for the fields of one set type.

EXAMPLE: Example: Set type ‘ZETC_T1’ used in service type ‘T1’ and ‘UG’:

  • Attribute ‘ZZ0010’ -> ZETC_OBU_ID

  • Set type structure ZETC_V1_MV includes fields ‘VALID_FROM’and ‘VALID_TO’

  • Set type name in structure CI_POD = ‘.INCLU-A2_’

  • Name of valid fields in the view configuration: //SERVICEOBJECT/STRUCT.VALID_TOA2_ and //SERVICEOBJECT/STRUCT.VALID_FROM2_

Exception: Standard set type ISU_POD which is always allocated automatically. If you want to make field EXT_UI, for example, time-dependet, use fields PD_VALID_FROM and/or PD_VALID_TO .

End of the note.
Detailed handling of the time periods - examples

Changes in the future (standard case)

Existing timeslice: 19.02.2004 14:10:42 - 31.12.9999 23:59:59

New value in the future

Entry from UI timestamp fields

PD_VALID_FROM COMT_VALID_FROM 21.12.2007

PD_VALID_TO COMT_VALID_TO empty

Leads to the following new timeslice in the tables:

ISU_PODH

19.02.2004 14:10:42 - 20.12.2007 23:59:59

ISU_POD 21.12.2007 00:00:00 - 31.12.9999 23:59:59

Existing timeslice: 19.02.2004 14:10:42 - 31.12.9999 23:59:59

New timeslice insert

Entry from UI timestamp fields

PD_VALID_FROM COMT_VALID_FROM 21.12.2007

PD_VALID_TO COMT_VALID_TO 23.12.2007

Leads to the following new timeslice in the tables:

ISU_PODH

19.02.2004 14:10:42 - 20.12.2007 23:59:59

21.12.2007 00:00:00 - 22.12.2007 23:59:59

ISU_POD 23.12.2007 00:00:00 - 31.12.9999 23:59:59

Existing timeslice: 19.02.2004 14:10:42 - 31.12.9999 23:59:59

New value in the past (mainly toll collection)

Entry from UI time stamp fields

PD_VALID_FROM COMT_VALID_FROM 30.06.2006 12:00

PD_VALID_TO COMT_VALID_TO

Leads to the following new timeslice in the tables:

ISU_PODH

19.02.2004 14:10:42 - 30.06.2006 11:59:59

ISU_POD

30.06.2006 12:00:00 - 31.12.9999 23:59:59

ISU_PODH

19.02.2004 14:10:42 - 20.12.2007 23:59:59

21.12.2007 00:00:00 - 29.12.2007 23:59:59

ISU_POD

30.12.2007 00:00:00 - 31.12.9999 23:59:59

Changing an attribute with existing changes

Entry from UI time stamp fields

PD_VALID_FROM COMT_VALID_FROM 21.12.2007

PD_VALID_TO COMT_VALID_TO

  • Insert not possible (check)

  • Cancellation of 30.12.2007 00:00:00 - 31.12.9999 23:59:59

Leads to the following new time slice in the tables:

ISU_PODH

19.02.2004 14:10:42 - 20.12.2007 23:59:59

21.12.2007 00:00:00 - 24.12.2007 23:59:59

ISU_POD

25.12.2007 00:00:00 - 31.12.9999 23:59:59