Re:Component Configuration in FPM

Question

Dear Experts,
In FPM component configuration,i have created one custom component configuration.in that,i have created two variants.The first variant (variant_1) i have created is like standard conponent configuration and another one (variant_2) is a custom develoment.Based on the user ,variant_1 and variant_2 has to call.But what the problem i am facing is when i try to call the variant_2 it is showing an error 'Variant_2 does not exist'.Do i need to store the variant_2 in some other table ? .Could you please help me out on this ?
Thanks & Regards,
R.Dhineshraj.

Answer 1

Hallo Chris,
I am not entirely sure about your problem. I have done some thing like this .See if it suits to your case.
Usually the FPM takes care of instanciating and attaching the shared
data component automatically. But in this case it is necessary to attach
it manually. The reason for this is that later within this method it is necessary
to access node data of the shared data component (e. g. node progress). By accessing data of the
shared data component, the WD runtime checks whether an instance of the
SD component already exists. The point is that in that point of time, the FPM
runtime did not create an instance and therefore the WD runtime creates an
instance of it. But at a later point of the time the FPM creates automatically
an instance of the SD and attaches is to the usage. Therefore two instances
of the SD would exist. This is why here an instance of the SD is created and
attached to the usage. Later the FPM will check wether and instance was already
created and attached to the usage and if yes will not create a second instance of it.
So we let the FPM do it, before the WD runtime does it. If you don't need access
to the SD compoment during startup-methods (such as WDDOINIT) you don't need to do this.
data lo_componentinterface type ref to if_wd_component_usage.
  lo_componentinterface = wd_this->wd_cpuse_usage_vh_persoon( ).
  call method wd_this->go_fpm->attach_component_to_usage
    exporting
      iv_component_name  = 'ZMOCK_IZRM_ZOEKEN'
      io_component_usage = lo_componentinterface.