SAP UPC_TRANSLATION_DATE_GET Function Module for Obtain Date for currency translation obtain

Search SAP Function Modules

UPC_TRANSLATION_DATE_GET is a standard upc translation date get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Obtain Date for currency translation obtain 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 translation date get FM, simply by entering the name UPC_TRANSLATION_DATE_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: UPC1
Program Name: SAPLUPC1
Main Program: SAPLUPC1
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPC_TRANSLATION_DATE_GET 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_TRANSLATION_DATE_GET'"Obtain Date for currency translation obtain
  EXPORTING
   I_AREA =  "Planning Area
   I_CHANM =  "
   I_CHAVLINT =  "
   I_TIMEREF =  "Time reference field for currency translation
   ITO_CHADEP =  "Values of Compound Characteristics

 IMPORTING
   E_DATE =  "Date and Time, Current (Application Server) Date

EXCEPTIONS
   CHANM_NOT_FOUND = 1    RFC_ERROR = 2    FAILED = 3 

.

IMPORTING Parameters details for UPC_TRANSLATION_DATE_GET

I_AREA - Planning Area

Data type: UPC_Y_AREA
Optional: No
Call by Reference: Yes

I_CHANM -

Data type: UPC_Y_CHANM
Optional: No
Call by Reference: Yes

I_CHAVLINT -

Data type: UPC_Y_CHAVLINT
Optional: No
Call by Reference: Yes

I_TIMEREF - Time reference field for currency translation

Data type: UPC_Y_TIMEREF
Optional: No
Call by Reference: Yes

ITO_CHADEP - Values of Compound Characteristics

Data type: UPC_YTO_CHADEP
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for UPC_TRANSLATION_DATE_GET

E_DATE - Date and Time, Current (Application Server) Date

Data type: SY-DATUM
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CHANM_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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)

Copy and paste ABAP code example for UPC_TRANSLATION_DATE_GET 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.

ABAP code using 7.40 inline data declarations to call FM UPC_TRANSLATION_DATE_GET

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