RSDD_TIP_LOGI - Logical Indexes as Transactional Providers

The following messages are stored in message class RSDD_TIP_LOGI: Logical Indexes as Transactional Providers.
It is part of development package RSDD_LTIP_IPROV in software component BW-BEX-OT. This development package consists of objects that can be grouped under "InfoProvider Wrapping of TREX Olap Indexes".
Message Nr
Message Text
001&1 &2 &3 &4
002Could not be read index catalog: &1
101Analytic index &1 created
102Analytic index &1 saved
104The InfoArea in the analytic index has not been defined
105InfoArea &1 does not exist
106The analytic index does not contain any view attributes
107Attribute &1 is used more than once in the analytic index
108InfoObject &1 is assigned to more than one attribute
109InfoObject &1 does not exist actively
110Dimension &1 has key figure &2 assigned to it
111Dimension name '&1' is invalid
112InfoObject &2 assigned to key figure &1 is not of type key figure
113No key figures defined
114The analytic index is not well defined. Check the definition.
115Key figure &1 has been assigned to invalid unit &2
116Unit &2 of key figure &1 is not assigned to an InfoObject
117InfoObject &2 referenced by key figure &1 is not a unit
118InfoObject &1 does not exist
119Transformation &2 used by attribute &1 does not exist
120Analytic index &1 is correct
121Component &3 of InfoObject &2 is not assigned
122Key not allowed (loading behaviour of facts is insert-only)
123No key defined (loading behaviour of facts is key-based)
124The analytic index does not contain any key attributes
125Enter an attribute name
126Key figure name '&1' is invalid
127Unit &1 (dim: &3) for key fig. &2 has not been selected with a reference
128Unit &1 for key figure &2 is missing in the dimensions
129The InfoObject name for key figure &1 must not be empty
130Attribute name '&1' of characteristic &2 is being used more than once
131Name '&2.&1' has more than 64 characters
132InfoObject &3, which is assigned to &2.&1, is used more than once
133InfoObject &3, which is assigned to &2.&1, does not exist
134The InfoObject name of dimension &1 must not be empty
135Numeric attribute '&1' cannot be a nav. attribute of '&2'
136Dimension name '&1' cannot have more than &2 characters
137Attribute name '&1' in dimension '&2' is invalid
138Component &3 of InfoObject &2 is assigned more than once
200Activation started for analytic index &1 (destination: &2)
201Analytic index &1 activated (destination: &2)
202Could not activate analytic index &1 (destination: &2)
203Analytic index '&1' is currently locked by user '&2' (dest. &3)
204Analytic index '&1' is locked (destination &2)
210No BWA destinations found
211Single-character ID &2 (destination &1) is not unique
212Single-character ID &1 is ignored with the default BWA
213DB object created for &1
494Analytic index &1 could not be deleted
495Analytic index &1 deleted
521Data deleted from the analytic index
600Error in BWA: &1 (Return code = &2)
601Inconsistency: Logical TREX index not found
602Inconsistency: Metadata not found for analytic index
689Dimension &1 contains an attribute with the same name
690Dimension &1 is given a nameless attribute
Privacy Policy