Different handling of SAP D34R / DF34_RAW datatype in Fivetran
Answered
A discrepancy has been identified in the way fields based on the SAP D34R / DF34_RAW datatype are extracted and stored by Fivetran compared with AecorSoft.
Instead of exposing the decoded decimal value, Fivetran appears to preserve the underlying 16-byte binary representation.
For the same source record:
- AecorSoft represents the value as 0.
- Fivetran stores the value as BINARY(16)
- Fivetran value is displayed as gAAAAAAAAAAAAAAAAAAAAA==.
- The underlying binary value in hexadecimal representation is 80000000000000000000000000000000. – Will not be an equal to 0
all columns which most likely will be affected due to D34R type.
- BSAD: HIST_TAX_FACTOR, HIST_TAX_FACTOR1, HIST_TAX_FACTOR2, HIST_TAX_FACTOR3
- BSAD_BCK: HIST_TAX_FACTOR, HIST_TAX_FACTOR1, HIST_TAX_FACTOR2, HIST_TAX_FACTOR3
- BSAK: HIST_TAX_FACTOR, HIST_TAX_FACTOR1, HIST_TAX_FACTOR2, HIST_TAX_FACTOR3
- BSAK_BCK: HIST_TAX_FACTOR, HIST_TAX_FACTOR1, HIST_TAX_FACTOR2, HIST_TAX_FACTOR3
- BSEG: HIST_TAX_FACTOR, HIST_TAX_FACTOR1, HIST_TAX_FACTOR2, HIST_TAX_FACTOR3
- BSID: HIST_TAX_FACTOR, HIST_TAX_FACTOR1, HIST_TAX_FACTOR2, HIST_TAX_FACTOR3
- BSIK: HIST_TAX_FACTOR, HIST_TAX_FACTOR1, HIST_TAX_FACTOR2, HIST_TAX_FACTOR3
- REGUP: HIST_TAX_FACTOR, HIST_TAX_FACTOR1, HIST_TAX_FACTOR2, HIST_TAX_FACTOR3
- IBSYMBOL: ATDECV, ATDECB
- TRDT_FLOW: FLOWFACTOR, BASEFACTOR
- TRST_CLASFLO: FLOWFACTOR, BASEFACTOR, ISSUED_NOMINAL_FRACTION, FACE_FACTOR_CURRENT, FACE_FACTOR_PREVIOUS, PRICEINDEX_FACTOR
- VDBEPI: FLOWFACTOR, BASEFACTOR
- VTBFHAPO: FLOWFACTOR, BASEFACTOR
- VTBFINKO: INDEX_BASE_VALUE
- VZZKOPO: FACE_FACTOR_CURRENT, INDEX_BASE_VALUE
-
Hi Przemyslaw,
Thank you for this feature request. We are investigating how we can improve the representation of these special numeric types in Fivetran's destinations. I will report back here once we have more clarity.
Best regards,
Edwin
Please sign in to leave a comment.
Comments
1 comment