Hierarchy
⤷ BW-WHM-DST (Application Component) Data Staging
⤷ RSSM (Package) BW: General monitoring and scheduling
Basic Data
Data Element | RSCHAVL_CHECK |
Short Description | Consistency check for characteristic values |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1 | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Cons chck |
Medium | 20 | Consistency check |
Long | 40 | Consistency check for char. values |
Heading | 10 | Cons Chck |
Documentation
Definition
During the Consistency Check for Characteristic Values, the characteristic values are checked for:
- Use of lowercase characters
- Use of special characters
- Plausibility of date fields
- Plausibility of time fields
- Use of character values in fields with data type NUMC and
- Correct observance of the ALPHA conversion routine
.
With InfoObjects of type characteristic, lowercase letters are not allowed as values. In InfoObject maintenance, you can set the Lowercase indicator and allow lowercase. You can only do this if the characteristic is used exclusively as a display attribute. If you do not set this indicator, the system runs the consistency check.
Special characters are not allowed in characteristic values either. This is because special characters in the country-specific character sets can be stored in different positions in the ASCII table. This could lead to them being displayed incorrectly after they have been transferred from the source system. In the maintain permitted extra characters activity in BW you can specify that special characters are valid. See also Permitted Characters.
The entries in the date and time fields must be plausible. For example, the values 199913 or 121999 are not valid for characteristic 0CALMONTH (calendar year/month). Plausible values fort his characteristic are values YYYYMM, where the year is a value greater that 1000 and the month is a value between 01 and 12 (Y = year, M = month).
Fields of data type NUMC can only contain numbers.
Correct observance of the ALPHA conversion routine means that internal numbers have leading zeros.
Unless you explicitly allow the use of lowercase or special characters, an error occurs when you update the data into the InfoCube or master data table of the InfoObject. The system cannot post the data package.
Use
If you select the Consistency Check for Characteristic Values indicator when you schedule an InfoPackage in the scheduler, the system performs a check when it updates the InfoPackage after the data has been read from the PSA or IDoc. Incorrect values are displayed in the monitor. After the errors have been corrected, the data package can be updated again.
If you are updating data from the PSA, you can set the indicator to Scheduler for Updating the Request if an error occurs when you update data into the InfoCube.
During the test phase, you should always select this indicator if you are updating new data or non SAP data. Once you are sure that the quality of the data is ok (you have performed several data imports and have not found incorrect values), switch off this indicator again because using this function has a negative impact on system performance when you load data.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in |