SAP UPC_BW_TIME_SHIFT Function Module for Time incrementor
UPC_BW_TIME_SHIFT is a standard upc bw time shift SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Time incrementor 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 upc bw time shift FM, simply by entering the name UPC_BW_TIME_SHIFT into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPCBW
Program Name: SAPLUPCBW
Main Program: SAPLUPCBW
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPC_BW_TIME_SHIFT 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 'UPC_BW_TIME_SHIFT'"Time incrementor.
EXPORTING
I_AREA = "Planning Area
I_CHANM = "
I_CHAVLINT = "
ITO_CHADEP = "Values of Compound Characteristics
I_SHIFT = "
IMPORTING
E_CHAVLINT = "Field for any characteristic value
EXCEPTIONS
RFC_ERROR = 1 FAILED = 2 OUT_OF_RANGE = 3
IMPORTING Parameters details for UPC_BW_TIME_SHIFT
I_AREA - Planning Area
Data type: UPC_Y_AREAOptional: No
Call by Reference: Yes
I_CHANM -
Data type: UPC_Y_CHANMOptional: No
Call by Reference: Yes
I_CHAVLINT -
Data type: UPC_Y_CHAVLINTOptional: No
Call by Reference: Yes
ITO_CHADEP - Values of Compound Characteristics
Data type: UPC_YTO_CHADEPOptional: No
Call by Reference: Yes
I_SHIFT -
Data type: IOptional: No
Call by Reference: Yes
EXPORTING Parameters details for UPC_BW_TIME_SHIFT
E_CHAVLINT - Field for any characteristic value
Data type: UPC_Y_CHAVLINTOptional: No
Call by Reference: Yes
EXCEPTIONS details
RFC_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OUT_OF_RANGE - Shift not allowed
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UPC_BW_TIME_SHIFT 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_area | TYPE UPC_Y_AREA, " | |||
| lv_rfc_error | TYPE UPC_Y_AREA, " | |||
| lv_e_chavlint | TYPE UPC_Y_CHAVLINT, " | |||
| lv_failed | TYPE UPC_Y_CHAVLINT, " | |||
| lv_i_chanm | TYPE UPC_Y_CHANM, " | |||
| lv_i_chavlint | TYPE UPC_Y_CHAVLINT, " | |||
| lv_out_of_range | TYPE UPC_Y_CHAVLINT, " | |||
| lv_ito_chadep | TYPE UPC_YTO_CHADEP, " | |||
| lv_i_shift | TYPE I. " |
|   CALL FUNCTION 'UPC_BW_TIME_SHIFT' "Time incrementor |
| EXPORTING | ||
| I_AREA | = lv_i_area | |
| I_CHANM | = lv_i_chanm | |
| I_CHAVLINT | = lv_i_chavlint | |
| ITO_CHADEP | = lv_ito_chadep | |
| I_SHIFT | = lv_i_shift | |
| IMPORTING | ||
| E_CHAVLINT | = lv_e_chavlint | |
| EXCEPTIONS | ||
| RFC_ERROR = 1 | ||
| FAILED = 2 | ||
| OUT_OF_RANGE = 3 | ||
| . " UPC_BW_TIME_SHIFT | ||
ABAP code using 7.40 inline data declarations to call FM UPC_BW_TIME_SHIFT
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