Below are the couple of root causes identified and resolution:
Root cause 1: pr_data_pipeline_configuration table may not be properly populated and/or DADT of Data-Pipeline-Configuration may not be updated.
Resolution: If upgarade happened from 4.1 to 4.2 or later, check whether pr_data_pipeline_configuration table exists and entries are present in it. Also check DADT for the class Data-Pipeline-Configuration is updated to point to pr_data_pipeline_configuration table.
Root cause 2: D_pxApplicationsWithPipelinedata page in the clipboard for which pxResults page is classless,This can be because DSS "datapage/newgenpages" is set to false
Resolution: Private edit the data transformpzGetApplicationsWithPipelinesand declare Primary.pxResults in Pages & Classes with class name as "Pipeline-Build-Status". And Launch the Deployment Manager again.Fix has been provided in Deployment Manager 4.3.2