SAP ABAP Message Class RS_HCPR_MODEL (Messages related to the HANA Composite Provider Backend)
Basic Data
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷
BW-WHM-MTD (Application Component) Metadata (Repository)
⤷
RSO_HCPR_MODEL (Package) BW: Backend Model for HANA Composite Provider
⤷
⤷
Attributes
| Message class | RS_HCPR_MODEL | |
| Short Description | Messages related to the HANA Composite Provider Backend | |
| Changed On | 20140121 | |
| Last Changed At | 103036 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | The input XML does not contain any model information | The short text describes the object sufficiently | ||
| 2 | Required XML attribute '&1' not found in element '&2' | The short text describes the object sufficiently | ||
| 3 | Could not perform CompositeProvider deserialization | The short text describes the object sufficiently | ||
| 4 | Could not perform CompositeProvider serialization | The short text describes the object sufficiently | ||
| 5 | The model has no name | The short text describes the object sufficiently | ||
| 6 | The CompositeProvider claims to be &1 but model content refers to &2 | Space: object requires documentation | ||
| 7 | The model must be of type &1 but has currently no type | The short text describes the object sufficiently | ||
| 8 | The model must be of type &1 but has currently type &2 | The short text describes the object sufficiently | ||
| 9 | The model for CompositeProvider &1 has no default view node | Space: object requires documentation | ||
| 10 | CompositeProvider &1 is consistent | The short text describes the object sufficiently | ||
| 11 | Field '&1' is not compatible with a BW InfoObject | Space: object requires documentation | ||
| 12 | Compounding parent &1 of navigation attribute &2 is not active | Space: object requires documentation | ||
| 13 | Name must not be empty | The short text describes the object sufficiently | ||
| 14 | Name '&1' contains invalid character '&2' at position &3 | The short text describes the object sufficiently | ||
| 15 | Name '&1' must not contain a substring '__' | The short text describes the object sufficiently | ||
| 16 | Length of name '&1' exceeds &2 characters | The short text describes the object sufficiently | ||
| 17 | Field name '&1' is not unique | The short text describes the object sufficiently | ||
| 18 | InfoObject '&1' does not exist | The short text describes the object sufficiently | ||
| 19 | Global name '&1' not unique (used by fields '&2' and '&3') | The short text describes the object sufficiently | ||
| 20 | Field '&1' cannot be used as a currency/unit field for '&2' | The short text describes the object sufficiently | ||
| 21 | Value '&1' is not valid for characteristic '&2' | The short text describes the object sufficiently | ||
| 22 | No currency information for amount key figure '&1' | The short text describes the object sufficiently | ||
| 23 | No unit information for quantity key figure '&1' | The short text describes the object sufficiently | ||
| 24 | Invalid compounding parent given by field '&1' (InfoObject '&2') | The short text describes the object sufficiently | ||
| 25 | Compounding parent '&1' missing for field '&2' (InfoObject '&3') | The short text describes the object sufficiently | ||
| 26 | Missing input for '&1' | The short text describes the object sufficiently | ||
| 27 | View node name '&1' is not unique | The short text describes the object sufficiently | ||
| 28 | No target fields in view node '&1' | The short text describes the object sufficiently | ||
| 29 | Source field '&1' and target field '&2' do not have compatible data types | The short text describes the object sufficiently | ||
| 30 | Obsolete assigment: Target field '&1' does not exist | The short text describes the object sufficiently | ||
| 31 | Obsolete assigment: Source field '&1' does not exist | The short text describes the object sufficiently | ||
| 32 | No assigment to target field '&1' from input '&2' | The short text describes the object sufficiently | ||
| 33 | More than one assigment exists to target field '&1' | The short text describes the object sufficiently | ||
| 34 | No assigment to target field '&1' | The short text describes the object sufficiently | ||
| 35 | Type ('&2') of InfoProvider '&1' not supported | Space: object requires documentation | ||
| 36 | InfoProvider '&1' not allowed | Space: object requires documentation | ||
| 37 | InfoProvider '&1' of type '&2' not allowed (because joins exist) | The short text describes the object sufficiently | ||
| 38 | Semantically partitioned object '&1' not allowed (joins and unions exist) | The short text describes the object sufficiently | ||
| 39 | Maximum of one semantically partitioned object allowed (joins exist) | The short text describes the object sufficiently | ||
| 40 | Input view '&1' not allowed in union '&2' | Space: object requires documentation | ||
| 41 | Inner join '&1' must not contain outer joins | The short text describes the object sufficiently | ||
| 42 | InfoProvider &1 is not allowed in a join | The short text describes the object sufficiently | ||
| 43 | Cannot read near-line storage for PartProvider &1 | The short text describes the object sufficiently | ||
| 44 | Navigational attribute &1 is not part of PartProvider &2 | The short text describes the object sufficiently | ||
| 45 | Aggregation '&2' of key figure &1 is not allowed in combination with Join | The short text describes the object sufficiently |
History
| Last changed on/by | 20140121 | SAP | |
| SAP Release Created in | 740 |