SAP OCS_ADD_FULL_SUBCOMP_QUEUE Function Module for

Search SAP Function Modules

OCS_ADD_FULL_SUBCOMP_QUEUE is a standard ocs add full subcomp 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 add full subcomp queue FM, simply by entering the name OCS_ADD_FULL_SUBCOMP_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_ADD_FULL_SUBCOMP_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_ADD_FULL_SUBCOMP_QUEUE'"
  EXPORTING
*  IV_ONLY_INSTALLED_ADDON = ' ' "
*  IV_UNSORTED = ' ' "

 IMPORTING
   ES_BAD_PATCH =  "

CHANGING
   CT_PATQ =  "

TABLES
*  TT_TARLEVEL =  "
*  TT_QCALC_TRC =  "

EXCEPTIONS
   NO_VALID_QUEUE = 1    INTERACTIVE_ATTRIBUTE = 2    BAD_ATTRIBUTE = 3    UPGRADE_NOT_FINISHED = 4    PATCH_FILE_ERROR = 5    FFD_NEEDED = 6    INTERNAL_ERROR = 7 

.

IMPORTING Parameters details for OCS_ADD_FULL_SUBCOMP_QUEUE

IV_ONLY_INSTALLED_ADDON -

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_UNSORTED -

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for OCS_ADD_FULL_SUBCOMP_QUEUE

ES_BAD_PATCH -

Data type: BAD_PATCH
Optional: No
Call by Reference: Yes

CHANGING Parameters details for OCS_ADD_FULL_SUBCOMP_QUEUE

CT_PATQ -

Data type: TT_PAT_Q2
Optional: No
Call by Reference: Yes

TABLES Parameters details for OCS_ADD_FULL_SUBCOMP_QUEUE

TT_TARLEVEL -

Data type: SPAM_CVERS
Optional: Yes
Call by Reference: No ( called with pass by value option)

TT_QCALC_TRC -

Data type: PAT_Q_TRC
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_VALID_QUEUE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INTERACTIVE_ATTRIBUTE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

BAD_ATTRIBUTE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

UPGRADE_NOT_FINISHED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PATCH_FILE_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

FFD_NEEDED -

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_ADD_FULL_SUBCOMP_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.

ABAP code using 7.40 inline data declarations to call FM OCS_ADD_FULL_SUBCOMP_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.

Search for further information about these or an SAP related objects