Issues with invalid characters or SID Generation

Symptom

BRAIN070, BRAIN060, BRAIN 290

Other terms

DSO, activation, invalid SID, not-allowed characters, ALL_CAPITAL

Reason and Prerequisites

You have successfully loaded a request to an ODS object. The data is in

the new data table. When you try to activate the request, you receive an error and the data is not updated in the active data table.

Not all characters are allowed in characteristic values of InfoObjects in BW. There is a predefined set of allowed characters. Please refer to the article "Permitted Characters in Characteristic Values", which is available in SAPNet on the SAP  Business Information Warehouse home page (BW) > Documentation >   Documentation Enhancements and OSS Note 173241 'Allowed characters in the BW System'. Additionally, SPACE symbol is allowed.

The system uses # character for all hexadecimal values, for which a code page does not know the appropriate character to use. This is the case for invalid characters, and hence, this sign may represent ANY invalid character in BW messages. Characters with hex codes from 00 to 1F are forbidden. These very characters cause most of problems during data loading. Remember that pressing the keys like TAB, ENTER, arrows, BACKSPACE creates these codes.

The symbols for the US Dollar ($), British Pound, Japanese Yen and the Euro are not allowed by default. The symbol for the US Dollar ($) is allowed in BW customizing. The other special currency indicators lead to errors in the system. You can enter these symbols in transaction RSKC to add them to the list of permitted characters.

The euro symbol is not supported in non-unicode systems. See the notes 447596, and 99422.

Solution

BRAIN060, BRAIN 290;

Value '...' (hex. '...') of characteristic ... contains invalid characters

First of all, make sure that the notes 1163736 and 1162968 are applied to ensure the error message identifies the incorrect characters.

1. If there are lowercase letters in the value, check if the InfoObject allows lower case in RSD1. If not, you must set the lowercase letters flag for the infoObject, or correct the data coming from the source system. This could be done with a TRANSLATE RESULT TO UPPER CASE statement in a routine in transfer rules (it could be done in a formula too).

2. Make sure that you have entered only ALL_CAPITAL in RSKC. If there are any additional characters entered, the system will not recognise ALL_CAPITAL.

ALL_CAPITAL option allows you to use all the characters that are capitals in the local language (the language in which the batch processes run).

BRAIN070;

No SID found for value '...' of characteristic ...

1. Check the SID table /BIC/S... for the characteristic. If there is no entry for the value '...' in the SID table, then you must create the master data, or correct the value loaded to the ODS object.

2.  If the value in the error message is padded with zeros and the value in the SID table is not (or vice versa), check the "Convers. Rout" field in RSD1.

- If the conversion routine is 'MATN1' or 'PRODU', make sure that the customising settings in BW are the same as in R/3 as per note 555675. You will have to reload the master data in this case as it is not possible to repair this in RSRV.

- If the value is 'ALPHA' see the note 559763. If you do not want to use either option from this note, the master data would have to be reloaded.

In General;

You can you can also switch off the "SIDs Generation upon Activation" flag to avoid these problems ("Bex Reporting" flag for 3.x systems).

If this flag is switched off, the SIDs will be generated when a query is run on the DSO at runtime. This is new in 700 systems.