There's no Replace option for export to Planning/Essbase. You should use Store Data anyway.
First, create your clear calc script and include the RUNTIMESUBVARS SET command to specify variables for period/year/scenario.
Then in FDMEE, add a "Before Data Load" calc script and specify parameters for period/year/scenario. See "Using Calculation Scripts" in the admin guide.
Ah, what about PBCS FDMEE? There's no calc script there?
Why are you trying to replace the data. The clean approach is to clear the data first and load using FDMEE.
that error is typically raised from Essbase when the fix has a member which does not exist:
HPLService] [loadData:550] END (com.essbase.api.base.EssException: Cannot calculate. Essbase Error(1200315): Error parsing formula for [FIX STATEMENT] (line 0): invalid object type)
Ah ok PBCS does have Replace, but you're probably running into the same drill through issue as non-PBCS FDMEE.
To answer your question, those other members you see in the FIX statement are automatically generated based on your mapping. I don't particularly agree with this design and we have raised this issue as a bug / enhancement request with Oracle. I've had it work just fine at some clients but when it doesn't, the workaround is to disable drill through in FDMEE and manually create the drill region in EAS; however, you don't have access to EAS with PBCS, so you may be out of luck.