Varad
Let’s start on Issue in opening Notepad attachment using class CL_FITV_GOS=>GET_CONTENT. You have a GOS scratch pad connection in your business object (for this post let us expect your business object is BUS1001006 for example Material). You chose to utilize the class technique CL_FITV_GOS=>GET_CONTENT to peruse the substance of the connection and utilize the class strategy CL_WD_RUNTIME_SERVICES => ATTACH_FILE_TO_RESPONSE to open the document in the internet browser. Issue in opening Notepad attachment using class CL_FITV_GOS=>GET_CONTENT.
Calculator in SAP using New ABAP Syntax
Amazingly, when you open the notebook text record, it is shown void. Despite the fact that the scratch pad has text in it (see figure underneath).
However, the more intricate records like PDF, JPG opens accurately.
So what turned out badly?
Appears, SAP missed to put the rationale to peruse scratch pad information (which are joined straightforwardly utilizing t-code in the event that MM02 or OAER). We observed that the notebook which were connected utilizing the class technique SAVE, would open accurately with this class. Issue is just with scratch pad which were NOT stacked with the class strategy SAVE.
Troubleshooting inside the class technique cl_fitv_gos=>get_content uncovers that for scratch pad, the hexadecimal result isn’t populated (as displayed in above figure).
Main driver:
In the technique for the class, object kind of text document is ‘EXT’ however it isn’t taken care of accurately.
Work Around for this issue:
In the event that ev_content_hex is clear, utilize standard FM ‘SO_DOCUMENT_READ_API1’ to get the substance of the text record. Convert the text content to hexadecimal utilizing FM ‘SCMS_TEXT_TO_XSTRING’ and show it.
Suspicion: The class technique doesn’t work for scratch pad record provided that you transfer the notebook text document utilizing MM01/MM02 or OAER straightforwardly (not utilizing class CL_FITV_GOS=>SAVE).
YOU MAY BE INTERESTED IN
SAP ALE IDoc Configuration Steps: Streamlining Communication
