Solution : https://service.sap.com/sap/support/notes/460652 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues with key figures in BW, specifically with data types 'DEC', 'CURR', or 'QUAN' that have a fixed length and decimal places which may be insufficient, leading to errors like DB2’s SQLCODE -802—decimal overflow—and similarly in other databases such as MaxDB and MSSQL. Solutions include altering InfoObject characteristics to FLOAT for dynamic length and decimal precision (BW 3.0 SP5 onward) and using custom domains ensuring compatibility with the key figure’s designated data type without modifying posted data. For BW versions prior to 3.0, domain adjustments need to be reaffirmed post any transport or activation.
Key words :
position dsnt418i sqlstate = 22003 sqlstate return code dsnt415i sqler key figures, log bzy=> unexpected return code 4 calling dbacds [dbacds#2 @ 1471] [dbacds 1471 ], converting column overflows integer datatype, fet> numeric output parameter overflow, ##y4p143698d2u00000056080000009238044338 col 6 dbstatus_e_unavailablec dbslexeread - error 27, error => number -> bcd conversion failed, 3 decimal places solution correction option 1, ##y4p143698d2u00000056080000009238044338 col 5 dbstatus_e_unavailablec copy2output, varnum->bcd conversion [dboci, error => invalid varnum number
Related Notes :
| 1643252 | Kennzahlaktivierung bricht ggf. ab |
| 1592764 | MDX: Precision when displaying formatted value |
| 1576540 | New Key Figure Classes R0_LDECAD and R0_LDECNAD |
| 1557321 | Numeric Overflow during standard BW processes |
| 1300350 | DBSTATUS_E_UNAVAILABLE |
| 928365 | BIA index with InfoCubes with key figures of type "FLOAT" |
| 871494 | Length of amount key figures in the Reporting BW system |
| 579342 | Changing key figures that are used in InfoProviders |
| 568768 | Analysis of SQL Errors causing Shortdumps or Error messages |