Incoming Service Operations from the TCD Server to the PeopleSoft Server

The following are incoming service operations from the TCD server to the PeopleSoft server, and online pages to check for errors and reported time:

  • Service Operations and Queue

    The two service operations for incoming messages are: ELAPSED_TIME_ADD (Elapsed Time Interface message) and PUNCHED_TIME_ADD (Punched Time Interface message).

    The queues for these two messages are: ELAPSED_TIME (Elapsed Time queue) and PUNCHED_TIME (Punched Time queue).

    The handler of the service operations triggers the TL_ST_LOADER Application Engine process that inserts rows into the Reported Time Tables. TL_ST_LOADER also initiates the Validation process for the validations defined on the TL Installation page.

  • TCD Error Queue

    This page is located in Set Up HCM, System Administration, Utilities, Analyze Time and Labor, Review TCD Errors. Using TCD Error Queue, you can check any errors for the Publishing Node you are using. If there are no errors found for the node, you can see the time in the reporting pages.

    See Understanding TCDs.

  • Report Time

    This page is located in Manager Self-Service, Time management, Report Time, Timesheet. This page displays the list of employees using the Find feature on the grid. Select Timesheet and then click on Name which opens with the current date as the start of the week. you can change the Week begin date and click Refresh Date.

See Reporting Time.

Alternate Service Operation Handler and Process for PUNCHED_TIME_ADD Messages

The default service operation handler for PUNCHED_TIME_ADD triggers the TL_ST_LOADER process to insert the content of an incoming message into reported time. Oracle delivers the PUNCH_ADD_DAEMON service operation handler, and the TL_ST_LD_DMN Application Engine process, which provide the following advantages over the default handler and process:

  • You can configure a limit to the size of each batch of messages the system processes.

  • The transactions for a given employee are kept within a single job. The system does not allow splitting employee transactions across multiple concurrent processes.

The PUNCH_ADD_DAEMON handler places the contents of incoming message into a staging table (TL_ST_PCHTIME). The handler does not automatically trigger the TL_ST_LD_DMN process. You must specify a repetitive schedule for the STDAEMON job to look for and process new transactions in the staging table. There is no direct tie between incoming message and each recurrence of the STDAEMON job, so the content of each message may be split between multiple jobs. However the process prevents splitting transactions for a given employee across multiple concurrent processes.

The TL_ST_LD_DMN process enables you to configure the maximum size of each batch of messages by setting the Max Punches in a Batch value on the Time and Labor Installation page. The default batch size is 2,000 transactions. The Max Punches in a Batch field is only visible after you activate the PUNCH_ADD_DAEMON handler.

In order to use the PUNCH_ADD_DAEMON handler, and the TL_ST_LD_DMN process, you must perform the following steps:

  1. Activate the PUNCH_ADD_DAEMON handler on the Handlers page (IB_SERVICEHDLR)

  2. Define the batch size for the TL_ST_LD_DMN process on the Time and Labor Installation page.

  3. Define, or modify, a recurrence pattern for the STDAEMON job on the Recurrence Definition page.

  4. Schedule the STDAEMON job on the Schedule JobSet Definition page.

    To initiate the first occurrence of the job, set the status to Active. The process has a built-in clean-up of the process monitor queue. This clean-up assumes that the Run Control ID used for the process is "TCD".