cancel
Showing results for 
Search instead for 
Did you mean: 

Wiring Model between more than 2 UIBB

Former Member
0 Kudos

What is best way to create connection between multiple UIBB ,e,g 2 set of Form,list ,i.e over all 3 UIBB. Is static attribute better way .

Accepted Solutions (1)

Accepted Solutions (1)

jens_boeckenhauer
Active Participant
0 Kudos

Hi,

Wiring is only recommended if you are working with generic feeder classes or at least with a significant reuse potential of your feeder classes. For individual applications it is easier to use event parameters or central instances (e.g. a singleton) for the implementation of data flows between UIBBs.

Best regards

Jens

Former Member
0 Kudos

Hi Jens,

Thanks for reply .

I have  requirement, which is developed using Feeder class . FPM application is OIF_Tabbed based . In one tab , there are 3 FORM_UIBB and one LIST_UIBB . Means over all 4 UIBB ,and all are implemented using Feeder class .

Now , I need data across are 4 UIBB .I am planning to use "Static Attributes" in all 4 feeder classes , to have data available across user session .

However , I checked in below link , we can use "Event based approach" as well . Wiring,I understand ,might not be that helpful for my case .

Can you please tell ,which is more better way of doing,since I am new to FPM

jens_boeckenhauer
Active Participant
0 Kudos

Hi Deepa,

the shared data component is not suitable if you use GUIBBs i.e. feeder classes. The event based approach is fine but you need to take into account that UIBBs can miss events if they are not processed: For instance, when a UIBB is on a different page or on a hidden tab of the Tabbed UIBB, then its event loop methods are not processed. Using static attributes is maybe not the most beautiful approach ever, but for simple use cases it is absolutely fine. A singleton is also fine.

But by the way: Static attributes do not hold data across ABAP sessions.

Best regards

Jens

Former Member
0 Kudos

Thank you Jens for answer .

But , I am still not clear, which approach should be followed for my case ..can you please suggest something.

jens_boeckenhauer
Active Participant
0 Kudos

Go for the singleton which can be accessed from each individual feeder class.

Regards, Jens

Former Member
0 Kudos

Hi Jens

Thank you again for reply .

My understanding :

  1. We can create one singleton class ,which can multiple Public attribute .i.e in one FPM application ,if i have Header, Item,Detail ( 3 UIBB and respective feeder class ) . I can create 3 or what ever , is needed number of Instance attributes in singleton class .
  2. Based on requirement all "Instance attributes of singleton class" can be accessed by all three feeder classes through "GET Instance" and our final business logic can trigger .

Please correct me,,

jens_boeckenhauer
Active Participant
0 Kudos

Hi Deepa,

yes, you can do like this.

Regards, Jens

Former Member
0 Kudos

Thank you Jens

Answers (0)