SAP FOPC_CASE_CONVERT_TS_TO_LOCAL Function Module for
FOPC_CASE_CONVERT_TS_TO_LOCAL is a standard fopc case convert ts to local 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 fopc case convert ts to local FM, simply by entering the name FOPC_CASE_CONVERT_TS_TO_LOCAL into the relevant SAP transaction such as SE37 or SE38.
Function Group: FOPC_CASE_SERVICE
Program Name: SAPLFOPC_CASE_SERVICE
Main Program: SAPLFOPC_CASE_SERVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FOPC_CASE_CONVERT_TS_TO_LOCAL 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 'FOPC_CASE_CONVERT_TS_TO_LOCAL'".
EXPORTING
* I_TIME_ZONE = SY-ZONLO "Time Zone of Current User
CHANGING
CS_CASE_ATTR = "Case Attribute
IMPORTING Parameters details for FOPC_CASE_CONVERT_TS_TO_LOCAL
I_TIME_ZONE - Time Zone of Current User
Data type: SY-ZONLODefault: SY-ZONLO
Optional: No
Call by Reference: Yes
CHANGING Parameters details for FOPC_CASE_CONVERT_TS_TO_LOCAL
CS_CASE_ATTR - Case Attribute
Data type: SCMG_T_CASE_ATTROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FOPC_CASE_CONVERT_TS_TO_LOCAL 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_i_time_zone | TYPE SY-ZONLO, " SY-ZONLO | |||
| lv_cs_case_attr | TYPE SCMG_T_CASE_ATTR. " |
|   CALL FUNCTION 'FOPC_CASE_CONVERT_TS_TO_LOCAL' " |
| EXPORTING | ||
| I_TIME_ZONE | = lv_i_time_zone | |
| CHANGING | ||
| CS_CASE_ATTR | = lv_cs_case_attr | |
| . " FOPC_CASE_CONVERT_TS_TO_LOCAL | ||
ABAP code using 7.40 inline data declarations to call FM FOPC_CASE_CONVERT_TS_TO_LOCAL
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 ZONLO FROM SY INTO @DATA(ld_i_time_zone). | ||||
| DATA(ld_i_time_zone) | = SY-ZONLO. | |||
Search for further information about these or an SAP related objects