Hello everybody,

the possibility how to integrate documentation objects from SE61 into an FPM application via the explanation control is well-known.

Within transaction SE61 you create a document object and refer later to it within your OVP floorplan configuration (see below screenshots, click on them to enlarge).

Explanation.png

SE61.png

However  the explanation is only visible if the quick help is being activated via right-mouse click:

Quick_Help.PNG

Having a longer text within your FPM application which should be there from quite the beginning of the application runtime, can be achieved by the following way:

The idea is to use the text maintained via SE61 within other parts of your FPM application, e.g. within the Form UIBB. It would be a good idea doing this e.g. via the Formatted Text View.

Within this UI element of the form configuration you just can edit a normal text, but not a document object from SE61. Furthermore within the configuration layer you are limited to 255 characters due to translation reasons.

This is why there is a possibility to programmatically give the information via feeder class which document object from SE61 should be taken – either for the Formatted Text View or Formatted Text Edit.

Therefore you need the following coding snippet:

 
DATA docu_utility TYPE REF TO cl_wdr_docu_utility.
 
DATA lv_text_xml  TYPE string.

  docu_utility = cl_wdr_docu_utility=>get_instance( ).
  lv_text_xml
= docu_utility->get_general_docu_as_fmt_text(
                     

                    object = `FPM_CBA_FR` ” your document object from se61
                    langu 
= sylangu ).

This coding converts the document object to a SAP Script Text.

GET_DATA.png

This text now you just have to assign to the correct field component of CS_DATA within GET_DATA of your feeder class and the documentation should be now displayed properly on the FPM application. For beautification reasons you can also remove the label from the Formatted Text View via the form configuration.

To report this post you need to login first.

6 Comments

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

  1. Nilay Patel

    Very helpful. Thanks..

    Just to add, those who want non-HTML We text, they can use this method call instead

    “lcl_docu_utility->get_general_docu_as_wad_text”

    (0) 

Leave a Reply