CT tells me that you have to make sure that the Balance Initialization elements have to be 'Linked to all payrolls' with an effective_start_date of '01-Jan-0001' is this till the case? The Business Group here has been set up from '01-Jan-1951'. . .CT have you got the script which sets the effective_start_date? . .Sorry to post a work-related question on the board Fish did it last week and it brought the whole thing down!

CB . .The BG from-date makes no odds mate the table isn't date-tracked anyway. I'm looking into where I put that script for you. . .CT

Don't forget the 'Commit'

Choose a reply from.... . .a). I've already checked that the commit statement is at the end . .b) F*** you and all who sail in you

.. Colin .. are you running it correctly ?

You Don't need a script anymore you can do it in the app

Hello young man long time no see etc? . .Hmm I'm not convinced. You can change your effective date to 01-JAN-0001 within the app and I'm pretty sure that elements do take on that effective start date. However unless something has been fixed real recent-like the links and link input values still get created with a date of 01-JAN-1901. . .Perfickly happy to be proved wrong only please write your evidence on the back of a blank cheque. Obviously you'll need to sign the front of it or I won't believe it was sent by you... :twisted:

OK will try doing it through the App. . .And Nic what do you mean "are you running it correctly ?" - what you trying to say about ex-Practice Managers/ex-HRMS Techie Gurus?

Hi Clive....what are you upto at the moment DWP ??

You mean the well-known administrator of works and pensions based somewhere in the North East? Nah mate I got out of there a week or so ago. Just running the clock down...

It was possible via the App to set the effective_start_date on the element links to 1st Jan 0001.

Pheeeeeeeewww!!!!

Still couldn't load my balances 'cos some Oracle consultant (known for wearing white socks and vomitting) didn't tell me before I started that balances won't load after you have run Batch Element Entries and that Terminations should be run last. Luckily Oracle have now got rid of him (not before time) and to be honest if he ever pitches up on this notice board we had all better watch out. I've had the misfortune to work with the bloke for years and I've been trying my damnest to teach him everything I know about Oracle HRMS but it obviously didn't sink in - or maybe he wasn't COMMITed enough. .I'm rambling now because it's the last afternoon before the Bank Holiday weekend and me dataload has ground to a halt so there's nowt alot else to do apart from drink tea and slag others off (with those attributes I should be a Practice Manager!).

You need a decent if expensive contractor to work with you. 8)

I don't know any - do you?

At least I didn't sit and wait for 20 minutes for a SQL query to return results only to realise it had been entered in a Notepad session by mistake.... oh hang on... yes I did actually. Damn. . .*bites knuckles in rage*

You can just delete the Payroll action and the Assignment actions for a mix batch as it has not effect. . .As for the terminations ...sorry you have to reverse those . .Assuming you use MIX batches for elements the order of the Load is now changed....it used to be Elements Balances is it now the reverse. There is no problem if you use the API for the element load

Are you suggesting deleting directly from the tables? . .Away we go!!!!!!!!!!!!!

Yes I have done this at two sites it seems to have no impact. . .It is obviously better if you can schedule the Migration appropriately. . .But you can get out jail. . .Does anyone know why MIX now creates Payroll actions and assignment actions ?? It only creates entries in these two tables and not the run results or run result values. . .You could also roll back the MIX batches if they are still there and re-apply after loading the balances

Are they the two sites that you had to leg it from? . .I think it creates the Payroll and Assignment actions so that you can roll back the batches via the standard rollback under Concurrent Manager.

Mr. Brookes that is a scurrulous accusation As far as I am aware I have never 'HAD' to leg it from a site........Although I may have wanted to on many occasions !! . .As for the rollback process MIX has its own rollback process

Thought I'd reopen this one. I've got a question re: post balance initialisation. . .We have a calendar monthly payroll and balances have been initialised as at 29-Apr-2004. So far fine and dandy. Viewing the expected results is another matter. Bear in mind no payroll processes have yet been run. . .We are viewing the balances through the balances form in the Others button on the assignment. If we datetrack to 1st April 2005 (First month of the new tax year) we can still see all the YTD balances. If we datetrack to 6th April all the ASG dimensions revert to nil but we can still see the PER_TD_YTD balance value. If we datetrack to 30th April all the dimensions revert to nil. Should I not expect them to all be nil from 1st April or am I missing something here?

Think I might have solved this one. It appears to be a "view" thing on the form. Arguably it could be said that 1st April is still in the old tax year and therefore the form retrieves the balances accordingly. No problem with that. Looks like a slight buggette in the view for the PER_TD_YTD; it reverts to nil at 7th April and not the 6th.

Finally Degsy has read the updated Balances Load document made a few minor changes and I have now posted onto the Download-able bit (technical term). .Thanks go to Steve Rose for the original 1976 version which I used as the basis for this rewrite! Obviously had to take out all references to backslash.