BPC 10 Virtual Provider - is the technical name constant when modified or transported?
I have seen a whitepaper from SAP that suggests the virtual provider generated when 'Use as a source of data for External Applications' is checked has a technical name that "may change in the target system" unless parameter ENABLE_FIXED_CUBENAME is switched on (which has it's own problems with changing and transporting models). The white paper can be found via this link -
However when we generated a virtual provider in our system, and then changed the model several times, we found the virtual provider technical name didn't change (as we had hoped). As I am working in a demo environment and don't have a BPC 10 that has been transported to a subsequent environment (Test/Prod), can we have your experience in transporting and changing models where a virtual provider has been generated and the effect on the technical name. As you would have guessed we are hoping to use the virtual provider to transfer data out of the BPC cube.
Note 1689814 explain parameter ENABLE_FIXED_CUBENAME in details that it will prevent cube from techname being changed on DEV. Since techname of multiprovider and virtualprovider are based on the techname of mode/cube when they are generated, so such technames will also keep consistant, right?
The important thing is to set this parameter to all DEV, QAS, PRD. and pay attention to whether the transport request contains transport the value of this parameter.