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

Function OCS_CHECK_COMPONENT_PATCH 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_CHECK_COMPONENT_PATCH'".
EXPORTING
IV_PATCH = "Support Package Name
TABLES
ET_PATQ = "Line Structure for PAT_QTAB
ET_MISSING_PATCHES = "Line Type for PAT_MISS_TAB
EXCEPTIONS
PATCH_NOT_OK = 1 MISSING_PATCHES = 2
IMPORTING Parameters details for OCS_CHECK_COMPONENT_PATCH
IV_PATCH - Support Package Name
Data type: PAT03-PATCHOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OCS_CHECK_COMPONENT_PATCH
ET_PATQ - Line Structure for PAT_QTAB
Data type: PAT_QOptional: No
Call by Reference: Yes
ET_MISSING_PATCHES - Line Type for PAT_MISS_TAB
Data type: PAT_MISSOptional: No
Call by Reference: Yes
EXCEPTIONS details
PATCH_NOT_OK -
Data type:Optional: No
Call by Reference: Yes
MISSING_PATCHES -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OCS_CHECK_COMPONENT_PATCH 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: | ||||
| lt_et_patq | TYPE STANDARD TABLE OF PAT_Q, " | |||
| lv_iv_patch | TYPE PAT03-PATCH, " | |||
| lv_patch_not_ok | TYPE PAT03, " | |||
| lv_missing_patches | TYPE PAT03, " | |||
| lt_et_missing_patches | TYPE STANDARD TABLE OF PAT_MISS. " |
|   CALL FUNCTION 'OCS_CHECK_COMPONENT_PATCH' " |
| EXPORTING | ||
| IV_PATCH | = lv_iv_patch | |
| TABLES | ||
| ET_PATQ | = lt_et_patq | |
| ET_MISSING_PATCHES | = lt_et_missing_patches | |
| EXCEPTIONS | ||
| PATCH_NOT_OK = 1 | ||
| MISSING_PATCHES = 2 | ||
| . " OCS_CHECK_COMPONENT_PATCH | ||
ABAP code using 7.40 inline data declarations to call FM OCS_CHECK_COMPONENT_PATCH
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.| "SELECT single PATCH FROM PAT03 INTO @DATA(ld_iv_patch). | ||||
Search for further information about these or an SAP related objects