SAP PTCOR_UIA_TIME_ACCOUNTS Function Module for
PTCOR_UIA_TIME_ACCOUNTS is a standard ptcor uia time accounts 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 ptcor uia time accounts FM, simply by entering the name PTCOR_UIA_TIME_ACCOUNTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: PT_COR_REQUEST_UIA
Program Name: SAPLPT_COR_REQUEST_UIA
Main Program: SAPLPT_COR_REQUEST_UIA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function PTCOR_UIA_TIME_ACCOUNTS 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 'PTCOR_UIA_TIME_ACCOUNTS'".
EXPORTING
IM_COMMAND = "Correction Scenario: UI Command
IM_PERNR = "Personnel Number
IM_MODUS = "Mode of Web Application
* IM_DEBUG = "Boolean Variable (X=True, -=False, Space=Unknown)
IMPORTING
EX_LASTRUN_DATE = "Date in CHAR format
EX_LASTRUN_TIME = "Time in CHAR Format
TABLES
EX_MESSAGES = "Clock-In/Out Corrections: UIA Message Table
EX_COMMANDS = "
EX_ACCOUNTS = "Time Balances (Correction Scenario)
IMPORTING Parameters details for PTCOR_UIA_TIME_ACCOUNTS
IM_COMMAND - Correction Scenario: UI Command
Data type: PTREQ_COMMANDOptional: No
Call by Reference: No ( called with pass by value option)
IM_PERNR - Personnel Number
Data type: P_PERNROptional: No
Call by Reference: No ( called with pass by value option)
IM_MODUS - Mode of Web Application
Data type: PT_REQ_MODEOptional: No
Call by Reference: No ( called with pass by value option)
IM_DEBUG - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PTCOR_UIA_TIME_ACCOUNTS
EX_LASTRUN_DATE - Date in CHAR format
Data type: DATEOptional: No
Call by Reference: No ( called with pass by value option)
EX_LASTRUN_TIME - Time in CHAR Format
Data type: TIMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PTCOR_UIA_TIME_ACCOUNTS
EX_MESSAGES - Clock-In/Out Corrections: UIA Message Table
Data type: PTCOR_UIA_MESSAGE_TABOptional: No
Call by Reference: Yes
EX_COMMANDS -
Data type: PTCOR_UIA_COMMAND_TABOptional: No
Call by Reference: Yes
EX_ACCOUNTS - Time Balances (Correction Scenario)
Data type: PTCOR_UIA_BALANCE_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PTCOR_UIA_TIME_ACCOUNTS 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_im_command | TYPE PTREQ_COMMAND, " | |||
| lt_ex_messages | TYPE STANDARD TABLE OF PTCOR_UIA_MESSAGE_TAB, " | |||
| lv_ex_lastrun_date | TYPE DATE, " | |||
| lv_im_pernr | TYPE P_PERNR, " | |||
| lt_ex_commands | TYPE STANDARD TABLE OF PTCOR_UIA_COMMAND_TAB, " | |||
| lv_ex_lastrun_time | TYPE TIME, " | |||
| lv_im_modus | TYPE PT_REQ_MODE, " | |||
| lt_ex_accounts | TYPE STANDARD TABLE OF PTCOR_UIA_BALANCE_TAB, " | |||
| lv_im_debug | TYPE BOOLEAN. " |
|   CALL FUNCTION 'PTCOR_UIA_TIME_ACCOUNTS' " |
| EXPORTING | ||
| IM_COMMAND | = lv_im_command | |
| IM_PERNR | = lv_im_pernr | |
| IM_MODUS | = lv_im_modus | |
| IM_DEBUG | = lv_im_debug | |
| IMPORTING | ||
| EX_LASTRUN_DATE | = lv_ex_lastrun_date | |
| EX_LASTRUN_TIME | = lv_ex_lastrun_time | |
| TABLES | ||
| EX_MESSAGES | = lt_ex_messages | |
| EX_COMMANDS | = lt_ex_commands | |
| EX_ACCOUNTS | = lt_ex_accounts | |
| . " PTCOR_UIA_TIME_ACCOUNTS | ||
ABAP code using 7.40 inline data declarations to call FM PTCOR_UIA_TIME_ACCOUNTS
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