A) Stages in Payroll retrieval � Non OTLR

Adjustments / Corrections --------------------------Transfer time from OTL to BEE

The same process transfers new and adjusted timecards from OTL to BEE. However, the adjustments are not transferred as is. When a timecard is adjusted in some way, the next process picks up the timecard in the latest shape and creates a batch in BEE as the latest and most valid entry. The earlier batch that was transferred in the first place is negated with a retro batch created automatically.

Eg.� User creates timecard with 40 hrs for the week.� Xfer time from OTL to BEE creates a batch for 40 hrs for the week.� User adjusts the timecard to have 45 hrs for the week.� Xfer time from OTL to BEE creates two batches now. One for 45 hrs for the week, which shows the latest data, and a retro batch for -40 hours to reverse the 40 hours processed earlier.

B) Stages in Payroll Retrieval � OTLR

Explosion---------The time data is moved to OTLR module, where it goes thru an Explosion process which logically manipulates time entered according to rules set up for the employee(s). The data thus created and exploded in OTLR module is viewable thru the Entry/Validation/Approval Screen.

BEE Validate/transfer---------------------Unless a batch in OTLR is validated without errors ( with or without warnings), it cannot be transferred to BEE.Batches are created with source as �OTM� in BEE.

Adjustments / corrections.--------------Adjustments to timecards already created or Retro timecards go to OTLR module in the same route as normal timecards. However, the original batches in which timecards are created and transferred to BEE are not modified for retro adjustments. The changes to timecards are created as a fresh retro batch, which only include the adjustments.

C) Rollback options prior to R12.1.5

BEE Batch Process (Rollback)------------------------------This program can be used to Rollback any batch from Element Entry back to BEE. Batches rolled back thus come back to BEE in status Unprocessed and can be trans

ferred again to Element Entry with or without changes.

Rollback BEE--------------This program owned by Time and Labor can be used to Rollback OTLR (batch source: OTM) from BEE back to OTLR module. Process only considers batches which are in BEE with status UnProcessed and does not consider any retro batches. The process only works to rollback a normal batch back to OTLR without any retro changes.

Gaps in the existing flow--------------------------

The following simple cases require a more flexible option to rollback time.

� A batch having Non OTLR timecards moved to Element entry can only be rolled back as much as BEE thru the Application. If the rollback had to be done to pick up corrected time or to fix some issue with the process, rerunning Xfer time from OTL to BEE does not move the time again to BEE. The only way out here is to have the timecards updated again and move time to BEE again as two batches ( Changed batch, retro batch for earlier batch) and then process only the Changed batch. This clearly is not the expectation from a complete rollback option.

� An OTLR timecard having one or more retro changes thru retro batches cannot be rolled back thru the application at all because Rollback BEE process does not rollback retro batches or batches having further retro changes

� An OTLR timecard can never be rolled back to OTL from OTLR module. This poses a big problem if the rollback is required because of wrong setup in OTLR rules evaluation.

� A few hundred timecards included in one single batch requiring a rollback would mean all of the timecards being touched again, which makes it difficult for self service users.

� Setups blocking update of a timecard once approved have a deadlock if for some reason the timecards have an issue in BEE and need to be rolled back.