SAP CRM_DATES_MODIFY_LOCAL_CONTEXT Function Module for Modify the timezone assigned to the reference object in local context
CRM_DATES_MODIFY_LOCAL_CONTEXT is a standard crm dates modify local context SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Modify the timezone assigned to the reference object in local context processing and below is the pattern details for this FM, 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 crm dates modify local context FM, simply by entering the name CRM_DATES_MODIFY_LOCAL_CONTEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_DATES_OW
Program Name: SAPLCRM_DATES_OW
Main Program: SAPLCRM_DATES_OW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_DATES_MODIFY_LOCAL_CONTEXT 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 'CRM_DATES_MODIFY_LOCAL_CONTEXT'"Modify the timezone assigned to the reference object in local context.
EXPORTING
IV_NAME_OBJECT = "Name of Reference Object
IV_TZONE = "Time Zone
IMPORTING Parameters details for CRM_DATES_MODIFY_LOCAL_CONTEXT
IV_NAME_OBJECT - Name of Reference Object
Data type: TIMENAOBJBOptional: No
Call by Reference: Yes
IV_TZONE - Time Zone
Data type: TIMEZONEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_DATES_MODIFY_LOCAL_CONTEXT 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_iv_name_object | TYPE TIMENAOBJB, " | |||
| lv_iv_tzone | TYPE TIMEZONE. " |
|   CALL FUNCTION 'CRM_DATES_MODIFY_LOCAL_CONTEXT' "Modify the timezone assigned to the reference object in local context |
| EXPORTING | ||
| IV_NAME_OBJECT | = lv_iv_name_object | |
| IV_TZONE | = lv_iv_tzone | |
| . " CRM_DATES_MODIFY_LOCAL_CONTEXT | ||
ABAP code using 7.40 inline data declarations to call FM CRM_DATES_MODIFY_LOCAL_CONTEXT
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