Warning Status in Loading BW data to BPC

[Former Member]

Hi,

The client ask us to test the new QA server environment. Part of the testing is to load data from BW Cube. When we do that the status is "Warning" and there are rejected records on the package. We checked the transformation file and it is identical to the PROD server. Another thing the loading of BW data to the DEV also produce "Warning" message. In the Prod server the loading is successful but the task at hand is to test the new environment in Q for back up purposes.

I attached a screenshot for the result of the package of Q server (Error 3 and Error 4) and Dev serv (Dev1 and Dev2). And i attached the transformation file for PROD and Q (Compare 1). Any feedback will be much appreciated.

Regards,

[damovand]

Hello,

Do you have exactly the same data in the BW cube that you load in QA and Dev? If the data that you are loading is not the same then that could explain the differences in the result.

Best Regards,

Leila Lappin

[Former Member]

Hi Vadim,

Apologies for that. Here are the screenshot

Result of Q server

Result of Q server pt 2

Dev server

Dev server 2

Comparison of transformation file of Q server and Prod server (right)

Regards,

[former_member186338]

Rejected records and Rejected Data screenshots, please!

[former_member186338]

First of all - it's a bad idea to use "Insert File" instead of correct "Insert Image". It's hard to read the question, please correct.

P.S. And please accept correct answer for your previous question!

[Former Member]

Hi Peter,

Yes I did validate the transformation file and no errors came up. The thing is this transformation file in the Q server is identical to the one in the PROD server (screenshot Compare1) except in the PROD the data load is successful.

[SeerOfSig]

If you re-validate the transformation and conversion files again with the data that is giving the warning do you get any errors? Often the diagnostics produced by the validation process will point to the incorrect data or data that cannot be mapped due to string size.