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

Function OCS_UPLOAD 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_UPLOAD'".
EXPORTING
* FILE_EXTENSION = GC_EXTENSION_PAT "
* EPS_DIR = ' ' "Directory Name
TABLES
PATCH_LIST = "
EXCEPTIONS
NOTHING_TO_UPLOAD = 1 FAILURE = 2
IMPORTING Parameters details for OCS_UPLOAD
FILE_EXTENSION -
Data type: TEPSIN-EPSPCLEXTDefault: GC_EXTENSION_PAT
Optional: Yes
Call by Reference: No ( called with pass by value option)
EPS_DIR - Directory Name
Data type: EPSF-EPSDIRNAMDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OCS_UPLOAD
PATCH_LIST -
Data type: PAT_UPLOADOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOTHING_TO_UPLOAD -
Data type:Optional: No
Call by Reference: Yes
FAILURE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OCS_UPLOAD 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_patch_list | TYPE STANDARD TABLE OF PAT_UPLOAD, " | |||
| lv_file_extension | TYPE TEPSIN-EPSPCLEXT, " GC_EXTENSION_PAT | |||
| lv_nothing_to_upload | TYPE TEPSIN, " | |||
| lv_eps_dir | TYPE EPSF-EPSDIRNAM, " SPACE | |||
| lv_failure | TYPE EPSF. " |
|   CALL FUNCTION 'OCS_UPLOAD' " |
| EXPORTING | ||
| FILE_EXTENSION | = lv_file_extension | |
| EPS_DIR | = lv_eps_dir | |
| TABLES | ||
| PATCH_LIST | = lt_patch_list | |
| EXCEPTIONS | ||
| NOTHING_TO_UPLOAD = 1 | ||
| FAILURE = 2 | ||
| . " OCS_UPLOAD | ||
ABAP code using 7.40 inline data declarations to call FM OCS_UPLOAD
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 EPSPCLEXT FROM TEPSIN INTO @DATA(ld_file_extension). | ||||
| DATA(ld_file_extension) | = GC_EXTENSION_PAT. | |||
| "SELECT single EPSDIRNAM FROM EPSF INTO @DATA(ld_eps_dir). | ||||
| DATA(ld_eps_dir) | = ' '. | |||
Search for further information about these or an SAP related objects