** TEAM FPM ** – How to integrate longer texts into your FPM application?
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).
However the explanation is only visible if the quick help is being activated via right-mouse click:
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:
* Replacing the current text with a SE61 document object
DATA lv_header TYPE thead.
DATA lv_lines TYPE tlinetab.
CALL FUNCTION ‘DOCU_GET’
id = ‘TX’ ” doku_id
langu = sy–langu
object = ‘FPM_CBA_FR’ ” your document object from se61
head = lv_header
line = lv_lines
no_docu_on_screen = 1
no_docu_self_def = 2
no_docu_temp = 3
ret_code = 4
OTHERS = 5.
sapscript_head = lv_header
sapscript_lines = lv_lines )->m_xml_text.
This coding converts the document object to a SAP Script Text.
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.
At the end the documentation object within the application could look like this…