SAP OCS_GET_CRT_QUEUE Function Module for
OCS_GET_CRT_QUEUE is a standard ocs get crt queue 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 get crt queue FM, simply by entering the name OCS_GET_CRT_QUEUE 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_GET_CRT_QUEUE 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_GET_CRT_QUEUE'".
EXPORTING
* IV_CURRENT_SYSTEM = 'X' "
* IV_ONLY_ACTIVE_ADDONS = 'X' "
IMPORTING
EV_OK = "
ES_BAD_PATCH = "Description of Patch that Makes Queue Inconsistent
ET_PATQ2 = "
TABLES
* ET_PATQ = "Line Structure for PAT_QTAB
ET_MISSING_PATCHES = "Line Type for PAT_MISS_TAB
* ET_QCALC_TRC = "
* IT_UPG_TARVERS = "
EXCEPTIONS
PATCH_FILE_ERROR = 1 BAD_PATCH = 2 INTERNAL_ERROR = 3
IMPORTING Parameters details for OCS_GET_CRT_QUEUE
IV_CURRENT_SYSTEM -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_ONLY_ACTIVE_ADDONS -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OCS_GET_CRT_QUEUE
EV_OK -
Data type: COptional: No
Call by Reference: Yes
ES_BAD_PATCH - Description of Patch that Makes Queue Inconsistent
Data type: BAD_PATCHOptional: No
Call by Reference: Yes
ET_PATQ2 -
Data type: TT_PAT_Q2Optional: No
Call by Reference: Yes
TABLES Parameters details for OCS_GET_CRT_QUEUE
ET_PATQ - Line Structure for PAT_QTAB
Data type: PAT_QOptional: Yes
Call by Reference: Yes
ET_MISSING_PATCHES - Line Type for PAT_MISS_TAB
Data type: PAT_MISSOptional: No
Call by Reference: No ( called with pass by value option)
ET_QCALC_TRC -
Data type: PAT_Q_TRCOptional: Yes
Call by Reference: Yes
IT_UPG_TARVERS -
Data type: SPAM_CVERSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
PATCH_FILE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BAD_PATCH -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OCS_GET_CRT_QUEUE 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_ev_ok | TYPE C, " | |||
| lt_et_patq | TYPE STANDARD TABLE OF PAT_Q, " | |||
| lv_patch_file_error | TYPE PAT_Q, " | |||
| lv_iv_current_system | TYPE C, " 'X' | |||
| lv_bad_patch | TYPE C, " | |||
| lv_es_bad_patch | TYPE BAD_PATCH, " | |||
| lt_et_missing_patches | TYPE STANDARD TABLE OF PAT_MISS, " | |||
| lv_iv_only_active_addons | TYPE C, " 'X' | |||
| lv_et_patq2 | TYPE TT_PAT_Q2, " | |||
| lt_et_qcalc_trc | TYPE STANDARD TABLE OF PAT_Q_TRC, " | |||
| lv_internal_error | TYPE PAT_Q_TRC, " | |||
| lt_it_upg_tarvers | TYPE STANDARD TABLE OF SPAM_CVERS. " |
|   CALL FUNCTION 'OCS_GET_CRT_QUEUE' " |
| EXPORTING | ||
| IV_CURRENT_SYSTEM | = lv_iv_current_system | |
| IV_ONLY_ACTIVE_ADDONS | = lv_iv_only_active_addons | |
| IMPORTING | ||
| EV_OK | = lv_ev_ok | |
| ES_BAD_PATCH | = lv_es_bad_patch | |
| ET_PATQ2 | = lv_et_patq2 | |
| TABLES | ||
| ET_PATQ | = lt_et_patq | |
| ET_MISSING_PATCHES | = lt_et_missing_patches | |
| ET_QCALC_TRC | = lt_et_qcalc_trc | |
| IT_UPG_TARVERS | = lt_it_upg_tarvers | |
| EXCEPTIONS | ||
| PATCH_FILE_ERROR = 1 | ||
| BAD_PATCH = 2 | ||
| INTERNAL_ERROR = 3 | ||
| . " OCS_GET_CRT_QUEUE | ||
ABAP code using 7.40 inline data declarations to call FM OCS_GET_CRT_QUEUE
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_current_system) | = 'X'. | |||
| DATA(ld_iv_only_active_addons) | = 'X'. | |||
Search for further information about these or an SAP related objects