SAP OCS_CREATE_COFILE Function Module for
OCS_CREATE_COFILE is a standard ocs create cofile 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 create cofile FM, simply by entering the name OCS_CREATE_COFILE 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_CREATE_COFILE 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_CREATE_COFILE'".
EXPORTING
PATCH = "
EXCEPTIONS
TP_INTERFACE_FAILURE = 1 TP_WARNING = 2 TP_ERROR = 3 TP_COMMAND = 4 TP_MISC = 5
IMPORTING Parameters details for OCS_CREATE_COFILE
PATCH -
Data type: PAT03-PATCHOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TP_INTERFACE_FAILURE -
Data type:Optional: No
Call by Reference: Yes
TP_WARNING -
Data type:Optional: No
Call by Reference: Yes
TP_ERROR -
Data type:Optional: No
Call by Reference: Yes
TP_COMMAND -
Data type:Optional: No
Call by Reference: Yes
TP_MISC -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OCS_CREATE_COFILE 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_patch | TYPE PAT03-PATCH, " | |||
| lv_tp_interface_failure | TYPE PAT03, " | |||
| lv_tp_warning | TYPE PAT03, " | |||
| lv_tp_error | TYPE PAT03, " | |||
| lv_tp_command | TYPE PAT03, " | |||
| lv_tp_misc | TYPE PAT03. " |
|   CALL FUNCTION 'OCS_CREATE_COFILE' " |
| EXPORTING | ||
| PATCH | = lv_patch | |
| EXCEPTIONS | ||
| TP_INTERFACE_FAILURE = 1 | ||
| TP_WARNING = 2 | ||
| TP_ERROR = 3 | ||
| TP_COMMAND = 4 | ||
| TP_MISC = 5 | ||
| . " OCS_CREATE_COFILE | ||
ABAP code using 7.40 inline data declarations to call FM OCS_CREATE_COFILE
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_patch). | ||||
Search for further information about these or an SAP related objects