The Floorplan Manager BOPF Integration (FBI) provides a configurable integration of FPM applications and business objects modeled with the Business Object Processing Framework (BOPF). Through this integration, the exchange of data between FPM applications and business objects is made possible.

In business workflows, there is usually a need to navigate between different FPM applications while passing application parameters in the process in order to meet certain business requirements.

In a previous article Parameterless navigation between FPM applications with FBI, the concept of navigation between different FPM applications and how to achieve such a simple navigation was explained. As a result, this article will mainly be an extension of the concepts already introduced and will concretely address the question of how parameters can be passed between FPM applications during a simple navigation. Subsequently, two practical scenarios will be presented where parameters are passed during navigation.

Parameter types

Two types of parameters (static and dynamic) can be passed on from the source FPM application to the destination FPM application during a navigation.

Static parameters are parameters whose values are known before the navigation takes place and don’t change at application runtime. Dynamic parameters are parameters whose values are not known before the navigation takes place and can be assigned at application runtime. Static parameters can be configured in the launch pad role and in custom non-BOPF UI actions of FBI views while dynamic parameters can be configured in custom non-BOPF UI actions of FBI views. The screenshots of the launch pad role and the FBI view below show how to configure static and dynamic parameters for the destination FPM application.

/wp-content/uploads/2014/03/launchpad_417328.png

/wp-content/uploads/2014/03/fbi_view_417362.png

Practical scenarios

For the following practical scenarios, two FPM applications (A and B) which will be used as source and destination application are shown in the screenshots below. The FPM application B consists of an Initial screen and a Main screen and allows viewing of customer details based on a valid customer ID value input.

/wp-content/uploads/2014/03/app_b_417363.png

The FPM application A shown in the screenshot below consists of a Main Screen with a search field and a display table (list) in which all customers meeting a certain search criterion are displayed.

/wp-content/uploads/2014/03/app_a_417364.png

Scenario 1

In the example scenario shown in the screenshot below, the goal is to navigate from the customer search screen in application A to the customer details view in application B by clicking on a valid customer ID.

/wp-content/uploads/2014/03/scen_1_417365.png

In order to achieve this, the customer ID from application A has to be passed as a dynamic parameter to application B while skipping the Initial screen of application B, as shown above. The initial screen can be skipped by setting the static parameter SKIP_INITIAL_SCREEN=X. Both parameters can be configured in the Action Paramters tab of the non-BOPF custom UI action, as can be seen in the screenshot below. The static parameter can also be configured in the launch pad role, as already mentioned above.

/wp-content/uploads/2014/03/scen_1_param_417366.png

Scenario 2

In the example scenario shown in the screenshot below, the goal is to create a new instance of a customer in  application B by clicking the New button in application A.

/wp-content/uploads/2014/03/scen_2_417367.png

In order to achieve this the static parameter CHANGE_MODE=C has to be passed during a navigation from application A to application B. This parameter can be configured in the Action Paramters tab of the non-BOPF custom UI action,as shown in the screenshot below or in the launch pad role, as already mentioned above.

/wp-content/uploads/2014/03/scen_2_param_417368.png

As has been illustrated, navigating between different FPM applications while passing parameters in the process can easily be realised using FPM launch pad roles configured in custom UI actions of FBI views.

In case of any questions or comments, we will like to hear about them. Also, if you solved this problem using another approach, we will be pleased to hear about it.

This article is a translated version of the article FPM Navigation: Parameterübergabe mit FBI (in German). You can also find other related articles to BOPF and FBI (in German) on our blog  Erlebe Software – Individuelle SAP Software.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Arunkumar Subramanian

    Hi Eugene Mbanya,

    It was very useful post. We tried to implement the same as we are using FBI. My target application is getting called. But the value is not set in the initial page.

    In my FBI view, i have passed the parameter as MATNR and value as (MATNR). Hence I get in the initial page as (MATNR) instead of the actual value. Do i need to pass the value explicitly??

    Thank you

    Regards

    Arun

    (0) 
    1. Eugene Mbanya Post author

      Hello Arun,

      Thank you for your question.

      The configuration of your FBI view is correct. Could you send me some screenshots per mail to help me better understand your problem/results?

      Best regards,

      Eugene

      (0) 

Leave a Reply