oracle time and labor – new rollback framework

8/18/2019 Oracle Time and Labor – New Rollback Framework

1/65

1© 2012 Oracle Corporation – Proprietary and Confidential

Day, Date, 2004

time p.m. ET

Teleconference Access:North America: xxxxInternational: xxxxPassword: Advisor

Wednesday July 25th, 2012

Morning :

3:00pm.GMT

7:00am. Pacific

8:00 am. Mountain

9:00 am. Central

10:00am. Eastern

MOS Doc ID: 1466868.1

Afternoon:

12:30 p.m. Pacific

1:30 p.m. Mountain

2:30 p.m. Central

3:30 p.m. Eastern

7:30 a.m. EDT

MOS Doc ID: 1466870.1

Teleconference Access:

North America: (877) 600-6701

For International Access please see Doc ID 1148600.1

Conference ids

Morning session: 90348239

Afternoon session 90349072

EBS HCM (HRMS) Community Advisor Webcasts:

For upcoming Community Advisor Webcasts please review:

‘Advisor Webcast Current Schedule (Doc ID 740966.1)’

To download a copy of this presentation please visit MyOracle

Support :

‘Advisor Webcast Archived Recordings (Doc ID 740964.1)’

Oracle Time and Labor – New Rollback Framework


2/65

OTL New Rollback Framework

25 July 2012


3/65


The following is intended to outline our general

product direction. It is intended for information

purposes only, and may not be incorporated into

any contract. It is not a commitment to deliver any

material, code, or functionality, and should not be

relied upon in making purchasing decision. The

development, release, and timing of any features

or functionality described for Oracle’s products

remains at the sole discretion of Oracle.

Safe Harbor Statement


4/65


Agenda

Welcome/Introduction

Prerequisite knowledge

Overview

New Programs

Setups & Demo

Troubleshooting

Useful References/My Oracle Support (MOS) Doc Ids

Q and A

Feedback


5/65


Pre-requisite Knowledge

Before you implement this functionality, you should have read the following articles:

• Oracle Time and Labor Implementation and User Guide, Release 12 [Note 1070930.1]

• Oracle Time and Labor Retrievals Troubleshooting Guide [Note 749174.1]

• Working knowledge of OTL – Payroll timecard lifecycle.


6/65


Overview

Before Rel 12.1.5, there was no functionally to Rollback a timecard from BEE

Batch back to HXC Timecard (Self Service or Timekeeper). Now thisfunctionality is available.

This webcast goes through Oracle Time and Labor new Rollback Framework

for Payroll application released in Oracle HRMS 12.1 RUP 5 (Patch

13418800)

This feature introduces four concurrent programs with flexible options to cater

to various business scenarios requiring a rollback of time transferred from

OTL to Payroll’s BEE interface.


7/657© 2012 Oracle Corporation – Proprietary and Confidential

New Programs

• OTL: Rollback Non OTLR Timecards

Rolls back a Non-OTLR Timecard from BEE Batch back to HXC (Self Service orTimekeeper)

• OTL: Rollback OTLR Timecards

Rolls back a OTLR Timecard from BEE Batch back to HXC (Self Service or Timekeeper)

• OTL: Rollback Batches from BEE

This program is the Rollback option for “Transfer to BEE” process. This is the rollback for

“Transfer to BEE” process. Rolls back a timecard from BEE Batch back to HXT (PUI

Timecard).

• OTL: Rollback Batches from BEE (Retro)

This program is the Rollback option for Transfer to BEE(Retro) process. The process is

equipped to rollback only Retro batches created from OTLR.



Demo

1st Program: OTL: Rollback Non-OTLR Timecards

Entered new Non-OTLR Timecard Starting 09-Jul-2012 to 15-Jul, 40 hrs

Navigation: Self Service Time > Create Timecard



Demo

Run “Transfer Time from OTL to BEE”

8-Jul-2012 to 16-Jul-2012

Retrieval Transaction Code: HMrollbackTest1

New Batch Reference: HMrollbackTest1

Navigation: OTL Application Developer > Submit Requests


10/65


Demo

BEE Batch showing status of “Unprocessed”. Navigation: OTL Application Developer > OTL Time Accounting > Mass Info eXchange: MIX


11/65


Demo

Now lets run “OTL: Rollback Non OTLR Batch” Process Navigation: OTL Application Developer > Submit Requests

Mode:

- Validate Only (simulation)

-Validate and Execute (Real

Rollback)

Rollback Mode:

- Rollback as per selection: The

process rolls back the latest

retrieval that happened for atimecard, as per the details

specified.

- Rollback All Details: When

selected, the process rolls back

all the details of the timecard ever

transferred to BEE.

Concurrent Request / Retrieval

Transaction Code / Batch Name

/ Batch Reference:

To select specific retrieval

process information.


12/65


Demo

Now lets run “OTL: Rollback Non OTLR Batch” Process Navigation: OTL Application Developer > Submit Requests

Dependent Batch Action:

Enabled only when Batch

Name/Batch Reference is

selected. (Dependent: Retro

batches).

Error Out: When a dependent

batch is encountered.

Process Dependent Batches:

Reverses dependent batch lines

Transferred Batch Action:

If batch was already transferred

to Element Entries.

-Error Out

- Create Reversal Batch

.


13/65


Demo

Process Output: Navigation: OTL Application Developer > View requests


14/65


Demo

What if the Batch was Transferred to Element Entries


15/65


Demo

BEE Batch Process > Validate

BEE Batch Process > Transfer.Navigation: OTL Application Developer > OTL Time Accounting > Mass Info eXchange: MIX


16/65


Demo

BEE Batch showing status of “Transferred”. Navigation: OTL Application Developer > OTL Time Accounting > Mass Info eXchange: MIX


17/65


Demo

Run OTL: Rollback Non OTLR TimecardsNavigation: OTL Application Developer > Submit Requests


18/65


Demo

Process Output showing the lines being reversed


19/65


Demo

2nd Program: OTL: Rollback OTLR Timecards

Entered new Timecard for an employee for period 9-Nov-2012 to 25-Nov, 27 hrs


Review Layout (showing OTLR explosion):


20/65


Demo

Run “Transfer Time from OTL to BEE” for this timecard. Batch Name: Fms19NovPyEpNavigation: OTL Application Developer > Submit Requests


21/65


Demo

Run “Validate for BEE” and “Transfer to BEE” for this timecard. Navigation: OTL Application Developer > Submit Requests


22/65


Demo

PUI Form showing Timecard status of “Transferred to BEE” Navigation: OTL Application Developer > OTL Time Accounting > Time Accounting > Entry/Validation/Approval


23/65


Demo

BEE Batch showing status of “Unprocessed”. We will rollback this batch from this stage. Navigation: OTL Application Developer > OTL Time Accounting > Mass Info eXchange: MIX


24/65


Demo

Now lets Rollback this Timecard. Run “OTL: Rollback OTLR Timecards” Navigation: OTL Application Developer > Submit requests

Parameter: Mode

o Validate Only : Runs the process in a Validate mode and displays all information about how theRollback would have processed. Does not actually execute the rollback.

o Validate and Execute : Runs the process in a complete mode, finishing the Rollback.


25/65


Demo


Parameter: Transferred Batch Action

What if the Batch was already transferred to Element Entries?o Error Out: When a transferred batch is encountered, the process errors out.

o Create Reversal Batch: A transferred batch line is reversed by creating negative entries for the

transferred lines


26/65


Demo


Parameter: Rollback Timecards To

o OTM: Rollback the timecard from BEE Batch back to the HXT version (PUI Timecard)o Time Store: Rollback the timecard from BEE Batch all the way back to HXC (Self Service of

Timekeeper version)

If chose “Time Store”, a new

parameter is enabled

“Action on Changes in OTM”:

When a manual update was doneon the PUI(HXT) timecard after

the transfer to BEE from

Entry/Validation/Approval form.

Error Out: If found manual update

then error out.

Delete Manual Changes in OTM:Delete any manual entry from

E/V/A screen off OTLR before

rolling back the changes to OTL

.


27/65


Demo

Final Parameters of “OTL: Rollback OTLR Timecards” Navigation: OTL Application Developer > Submit requests

According to the above, we are rolling back the timecard as follows:- Process the rollback, not just simulate

- For Payroll Vision HR Weekly and Time Period starting 19-Nov-2012

- If the Batch was already transferred to Element Entries, show an error and stop

- Rollback the Timecard all the way from BEE Batch back to HXC Version (SS).

- If the timecard was manually modified in PUI (Entry/Validation/Approval) form after it was

transferred to BEE then error out.


28/65


Demo

Process Output: Navigation: OTL Application Developer > View requests


29/65


Demo

Process Log also has some more deep information:Navigation: OTL Application Developer > View requests

D


30/65


Demo

Checking the Batch: “Unprocessed”, No lines: Navigation: OTL Application Developer > OTL Time Accounting > Mass Info eXchange: MIX

This batch header must be purged later by the user.


31/65


Demo

Checking PUI Timecard in E/V/A form: Not found.Navigation: OTL Application Developer > OTL Time Accounting > Time Accounting > Entry/Validation/Approval


32/65


Demo



33/65


Demo

New Scenario: Entered a new timecard from 26 Nov to 02 Dec 2012.

Transfer Time from OTL to BEE > Validate for BEE > Transfer to BEE

Transferred the Timecard to Element Entries (From BEE form: Process > Validate, Process > Transfer)

BEE Batch Status now: Transferred. PUI Timecard Status: Transferred to BEE.


34/65


Demo

Now Run Rollback OTLR Timecards with option “Create Reversal Batch”, back to TimeStore.


35/65


Demo

Process Output:

A reversal Batch was created!


36/65


Demo

Original Batch: same status, nothing changed. Expected.

New Reversal Batch: REV_469952_17477900. Status “Unprocessed”, Element Lines has negative

entries of all entries.

Checking PUI Timecard:

Not found. Expected!


37/65


Demo

3rd Program: OTL: Rollback Batches from BEE.

New scenario: Entered a new timecard from 31 Dec to 06 Jan 2012.



38/65


Demo

Transfer Time from OTL to BEE (Batch Name: Fms31DecPyEp) > Validate for BEE > Transfer to

BEE > then Transferred the Timecard further to Element Entries (From BEE form: Process >

Validate, Process > Transfer).

BEE Batch Status now: Transferred. HXT/PUI Timecard Status: Transferred to BEE.


39/65


Demo

Run OTL: Rollback Batches from BEE

Mode: Validate and Process

Starting Batch: Fms31DecPyEp_X_472943

Person: If you want to choose a specific person’s timecard(s) from the Batch.Transferred Batch Action: This parameter is available only if a person is selected. If a person

parameter is not selected, a batch is eligible for rollback only if it is in Unprocessed.

o Error Out: When a transferred batch is encountered, the process errors out.

o Create Reversal Batch: A transferred batch line is reversed by creating negative entries for the

transferred lines.

Trying without choosing a

person. Shouldn’t rollback

because Batch is

Transferred.


40/65


Demo

Process Output - Error:

That’s right. Because we didn’t specify a person, we can’t rollback a complete “Transferred” Batch.

Now lets choose a Person

in the Rollback BEE Batch

parameters:

Person: Class11_payemp,

Transferred Batch Action:

Create Reversal Batch

D


41/65


Demo

Process Output:

New batch got created to reverse the entries transferred to Element Entries. Reversal Batch name:

REV_472943_17478178. Let’s take a look on the Batch.

D


42/65


Demo

Reversal Batch: REV_472943_17478178

Reverses all timecard entries that were sent to Element Entries.

D


43/65


Demo

Checking the PUI Timecard. Status changed to Hold and it was linked to new Batch:

REP_472943_17478178.

D


44/65


Demo

Batch REP_472943_17478178 is in Unprocessed status with no lines if you want to rerun Validate

for BEE and Transfer to BEE again.

D


45/65


Demo

4th Program: OTL: Rollback Batches from BEE (Retro)

Let’s modify timecard (07-Jan-2013) from Self Service that was already transferred to BEE.

Changed 8hrs on Tuesday to 10

D


46/65


Demo

Run Transfer Time from OTL to BEE (Batch Name: Fms07Jan13V2)

Demo


47/65


Demo

Run Validate for BEE (Retro)

Demo


48/65


Demo

Transfer to BEE (Retro)

Demo


49/65


Demo

Checking the new Batch, new Batch created with the additional hours:

Demo


50/65


Demo

Checking PUI, Tuesday was modified to reflect the new hours:

Demo


51/65


Demo

Now lets Run OTL: Rollback Batches from BEE (Retro).

This should reverse the Transfer to BEE (Retro) that was just run, i.e. should reverse the additional

2 hours overtime.

Mode: Validate and Process

Starting Batch: Fms07Jan13V2_X_R476946

Demo


52/65


Demo

Process Output:

Demo


53/65


Demo

Checking Retro Batch, lines were deleted:

Demo


54/65


Demo

The process has reversed Transfer to BEE (Retro) process only. But does not reverse the change

itself in the timecard:


55/65


Demo


Demo


56/65


Demo

Lets Process > Validate, Process > Transfer for both Batches the original one and the Retro one so

we send them to Element Entries.

Original Batch “Transferred”:

And the Retro batch “Transferred”:

Demo


57/65


Demo

Now lets run OTL: Rollback Batches from BEE (Retro)

Demo


58/65


Demo

Process Output:

You cannot Rollback Retro Batch if it was already transferred to Element Entries. You must roll

it back from Element Entries first using “BEE Batch Process (Rollback)” using an HRMS

responsibility


59/65


“System does not have enough details to Rollback this timecard”: The timecard

being processed was created and transferred before the Rollback framework wasinstalled. At this point, the system does not have enough information about the timecardto execute an effective rollback.

“This timecard was transferred with OTLR rules YES at least once”: The timecardbeing processed was created and transferred at least once with OTLR option Yes andcannot be processed with this program.

“This timecard may be archived and cannot be processed”: The timecard beingprocessed is either partially or fully Archived using the Archive Data Set program andcannot be rolled back..

“Last Changes on this timecard were once rolled back. Rollback all details”: Thetimecard being processed is being requested to be rolled back with Rollback Mode

value Rollback as per selection. The latest retrieval on this timecard was once rolledback in this mode and hence this action is not permitted. This timecard can only berolled back by Rollback All Details mode.

Troubleshooting


60/65


“Batch –&BATCHNAME- has Transferred status and we are not rolling back

these”: The request was initiated with Transferred Batch action parameter set to Errorout. The batch currently encountered is in Transferred status in BEE and cannot beprocessed as per the parameters chosen.

“Batch -&BATCHNAME- is a dependent batch and we are not processingdependent batches”: The request was initiated with Dependent Batch Actionparameter set to Error out. The batch currently encountered is a dependent batch of the

batch requested to be rolled back. This action is not permitted as per the parameterschosen.

“There are manual entries in OTM”: The request was initiated with Action for Changesin OTM parameter entered as Error out, and the timecard is being rolled back to TimeStore. Until these manual entries in OTM are deleted, this action is not permitted

“This batch is Transferred and need to be rolled Back from EE first”: The processis initiated to rollback a batch which is in Transferred status in BEE. BEE BatchProcess(Rollback) needs to be initiated to rollback this batch to BEE first before thisprogram is run.

Troubleshooting

Useful References


61/65


Useful References

Doc ID 468700.1 - OTL: Rollback Framework for Payroll Retrieval Whitepaper

Doc ID 251402.1 - Which BEE Rollback process do I use to Rollback a Transferred BEE Batch?

Doc ID 749174.1 - Oracle Time and Labor Retrievals Troubleshooting Guide

Visit My Oracle Communities


62/65


Visit My Oracle Communities

Collaborate with a large network of your industry peers, support professionals, andOracle experts to exchange information, ask questions & get answers. Find out how yourpeers are using Oracle technologies and services to better meet their support and

business needs.

• Exchange Knowledge

• Resolve Issues

• Gain Expertise

Visi t the Payrol l Supp ort

Communi ty ! !

1. Log into My Oracle Support.

2. Select the Community tab

3. Select the Payroll –

EBS Community

4. Subscribe

HCM INSIDER News and Views


63/65

63

Oracle EBS HCM Support Newsletter 2012 (Docid)

Previous editions are available from the EBS HCM Newsletter Index, found in Docid 1325083.1

Next edition is scheduled for fall of 2012.

© 2012 Oracle Corporation – Proprietary and Confidential


64/65

64

Feedback


65/65

Please let us know how we are doing by providing the following:

1. Based on the webcast description, how did your learning experience compare towhat you expected when you began the webcast?

2. Would you recommend the recording for this webcast to your colleagues?

3. What topics specifically would you like to see covered in a future webcast?

4. If you have any additional questions or feedback from today’s webcast please

contact us via the following email addresses or post to the Payroll - EBS MOS

Community Thread:

• [email protected]

• [email protected]

Feedback

oracle time and labor – new rollback framework

Documents