SAP OCS_READ_ADDON_INSTALLATIONS Function Module for









OCS_READ_ADDON_INSTALLATIONS is a standard ocs read addon installations 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 read addon installations FM, simply by entering the name OCS_READ_ADDON_INSTALLATIONS 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_READ_ADDON_INSTALLATIONS 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_READ_ADDON_INSTALLATIONS'"
TABLES
ET_PACKLIST = "

EXCEPTIONS
NO_PACKAGES = 1 INTERNAL_ERROR = 2
.



TABLES Parameters details for OCS_READ_ADDON_INSTALLATIONS

ET_PACKLIST -

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

EXCEPTIONS details

NO_PACKAGES -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OCS_READ_ADDON_INSTALLATIONS 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_packlist  TYPE STANDARD TABLE OF PAT03, "   
lv_no_packages  TYPE PAT03, "   
lv_internal_error  TYPE PAT03. "   

  CALL FUNCTION 'OCS_READ_ADDON_INSTALLATIONS'  "
    TABLES
         ET_PACKLIST = lt_et_packlist
    EXCEPTIONS
        NO_PACKAGES = 1
        INTERNAL_ERROR = 2
. " OCS_READ_ADDON_INSTALLATIONS




ABAP code using 7.40 inline data declarations to call FM OCS_READ_ADDON_INSTALLATIONS

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!