/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
In a stacked CompositeProvider (HCPR) scenario, where a H2 CompositeProvider consumes another H1 CompositeProvider, maintaining certain changes in the providers consumed by H1 will turn H1 inactive but not necessarily H2.
Read more...
Environment
- SAP NetWeaver 7.5
- SAP BW/4HANA 1.0, 2.0, 2021, 2023
Product
SAP BW/4HANA 1.0 ; SAP BW/4HANA 2.0 ; SAP BW/4HANA 2021 ; SAP BW/4HANA 2023 ; SAP NetWeaver 7.5
Keywords
"HCPR", "compositeprovider", "impact handling", "active", "inactive", "stacked", "This CompositeProvider can be added to another CompositeProvider", "reusable HCPR" , KBA , BW-MT-HCPR , CompositeProvider in BW Modeling Tools , BW4-ME-HCPR , Composite Provider , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)