Warning message in RSA6

Question

Hello Experts,
In rsa6 when I transport the Data source, iam facing the below message.... ignored the warning transported and replicated in BI system but its not reflected in BI system...help me out.
The even-numbered length of the DEC field D_UNITS can lead to problems
Message no. R8569
Diagnosis
You want to use the field D_UNITS in the extract structure for DataSource 0CFM_DELTA_POSITIONS. This field has a field of type 'DEC' (or 'CURR' or 'QUAN') with an even number of characters.
This can create problems since the length resulting from calculations in ABAP (for example, in extractors or Customer Exits for extraction) is too large to be inserted in the database later (PSA in BW), causing a short dump.
Procedure
This warning is only relevant when the maximum length of this field is exceeded during extraction, for example when the field is expanded in the Customer Exit through a calculation.
More information and a remedy can be found in SAP Note 641744.

Answer 1

Hi KV........
Hav u checked the correct Application component after Replication..........is it popping any error message...........After replication u hav to activate the Transfer rules using the program : RS_TRANSTRU_ACTIVATE_ALL ...........Warning cannot be the reason........as per my understanding........First go to RSA1 >> go to source system >> Right click on the desired source system >> Display datasource tree >> then go to the correct Application Component >> Then right click >> Replicate metadata........
Hav u checked the SAP Note 641744..........given in the Error message.......For ur reference.......
Symptom
The following symptoms can occur:
1a: When you transfer a DataSource from the Business Content, a warning is displayed, stating that the even numbered length of the DEC field <Fieldname> can cause problems (message: R8 569).
1b: When you generate DataSources using transaction RSO2, the warning R8 569 is issued.
2: When you load extracted data to the PSA, a short dump 'DBIF_RSQL_SQL_ERROR' is generated. (In this case, the above message appears if the DataSource is checked in the source system in transaction RSA6.)
Other terms
OLTP, extractor, data extraction, DataSource, service API, SAPI, S-API
R8569, ORA1438,
Reason and Prerequisites
The DataSource contains fields of the 'DEC' DDIC type (also:'CURR' or 'QUAN') with an exact-number-of-places.
You should only expect problems if calculations are made with the above field types using the value read by the database.
Example:
The value '9999' is read by the database from a DEC field of length 4.
At runtime, this is treated as an internal ABAP type 'P' (length 3) that can, however, have the maximum value '99999'.If the read value is now increased by an arithmetic operation - for example, by adding '1' - the resulting value '10000' cannot be written to the PSA that was also generated on the basis of the DEC field of the extract structure with a length of 4.
Result: A short dump 'DBIF_RSQL_SQL_ERROR', 'CX_SY_OPEN_SQL_DB', is issued when you write to the PSA in BW using the INSERT_ODS routine.
Solution
If the field is not manipulated in the customer exit or elsewhere, no processing is required.
If you change the field, the following possible solutions are available:
You can make sure that the number of the characters does not increase after the manipulation.
If you can change the extract structure of the DataSource without affecting other scenarios (for example, if it was generated in transaction RSO2), you can increase the length of the DEC field (or CURR, QUAN) there to the next odd character (in the example above: from DEC 4 on DEC 5).
If neither of these solutions are possible, you can use a customer append that contains a relevant DEC field (or CURR, QUAN) with the next highest odd length. This can be used for the result of the calculations. This means that you do not have to manipulate the previous field.
Regards,
Debjani.........