SAP OCS_EXTRACT_NOTE_BLOCK Function Module for
OCS_EXTRACT_NOTE_BLOCK is a standard ocs extract note block 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 ocs extract note block FM, simply by entering the name OCS_EXTRACT_NOTE_BLOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: OCS_CORE
Program Name: SAPLOCS_CORE
Main Program: SAPLOCS_CORE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OCS_EXTRACT_NOTE_BLOCK 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 'OCS_EXTRACT_NOTE_BLOCK'".
EXPORTING
IV_PACKAGE = "
* IV_FORCE = ' ' "
EXCEPTIONS
PATCH_FILE_ERROR = 1 UNKNOWN_BLOCK = 2
IMPORTING Parameters details for OCS_EXTRACT_NOTE_BLOCK
IV_PACKAGE -
Data type: PATCHOptional: No
Call by Reference: Yes
IV_FORCE -
Data type: OAXDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
PATCH_FILE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_BLOCK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OCS_EXTRACT_NOTE_BLOCK 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_iv_package | TYPE PATCH, " | |||
| lv_patch_file_error | TYPE PATCH, " | |||
| lv_iv_force | TYPE OAX, " SPACE | |||
| lv_unknown_block | TYPE OAX. " |
|   CALL FUNCTION 'OCS_EXTRACT_NOTE_BLOCK' " |
| EXPORTING | ||
| IV_PACKAGE | = lv_iv_package | |
| IV_FORCE | = lv_iv_force | |
| EXCEPTIONS | ||
| PATCH_FILE_ERROR = 1 | ||
| UNKNOWN_BLOCK = 2 | ||
| . " OCS_EXTRACT_NOTE_BLOCK | ||
ABAP code using 7.40 inline data declarations to call FM OCS_EXTRACT_NOTE_BLOCK
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.| DATA(ld_iv_force) | = ' '. | |||
Search for further information about these or an SAP related objects