SAP FOPC_GET_NOTE_TEXT Function Module for
FOPC_GET_NOTE_TEXT is a standard fopc get note text SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for fopc get note text FM, simply by entering the name FOPC_GET_NOTE_TEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FOPC_CASE_SERVICE
Program Name: SAPLFOPC_CASE_SERVICE
Main Program: SAPLFOPC_CASE_SERVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function FOPC_GET_NOTE_TEXT pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'FOPC_GET_NOTE_TEXT'".
EXPORTING
IM_GUID = "Technical Key of Case (Case GUID)
IM_MODEL_ID = "Model ID of the Note in the Back End Record
IMPORTING
EX_CONTENT = "Note Contents
EXCEPTIONS
CX_FOPC_CASE = 1
IMPORTING Parameters details for FOPC_GET_NOTE_TEXT
IM_GUID - Technical Key of Case (Case GUID)
Data type: SCMG_CASE_GUIDOptional: No
Call by Reference: Yes
IM_MODEL_ID - Model ID of the Note in the Back End Record
Data type: STRINGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FOPC_GET_NOTE_TEXT
EX_CONTENT - Note Contents
Data type: STRINGOptional: No
Call by Reference: Yes
EXCEPTIONS details
CX_FOPC_CASE - SOA: Case
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FOPC_GET_NOTE_TEXT Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.DATA: | ||||
lv_im_guid | TYPE SCMG_CASE_GUID, " | |||
lv_ex_content | TYPE STRING, " | |||
lv_cx_fopc_case | TYPE STRING, " | |||
lv_im_model_id | TYPE STRING. " |
  CALL FUNCTION 'FOPC_GET_NOTE_TEXT' " |
EXPORTING | ||
IM_GUID | = lv_im_guid | |
IM_MODEL_ID | = lv_im_model_id | |
IMPORTING | ||
EX_CONTENT | = lv_ex_content | |
EXCEPTIONS | ||
CX_FOPC_CASE = 1 | ||
. " FOPC_GET_NOTE_TEXT |
ABAP code using 7.40 inline data declarations to call FM FOPC_GET_NOTE_TEXT
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects