Oh, bugger.
Friday 13th was a good day, by standards. Saturday 14th rocked quite severely, and even Sunday 15th wasn't a bad dau (despite the ye gods o'clock start). Suppose I shouldn't be surprised that the crapness has waited till Monday 16th!
I've been helping IWasLike settle into PutUpon's role. It's not easy. She's been thrown into a totally different job with almost no training, and the end users have been spoiled by PutUpon's old trick of turning requests around in short order. One of them was almost affronted when I explained that our SLa includes a two working day lead time! Anyway, I've been helping her and trying to sort my own stuff out (and the 42 product codes that I received on Friday? I'd just about finished printing them out, when more started to arrive! Another 12, and counting...) Then I had to make a correction for one of the site munchkins - part my fault, part his. This involved doing the same thing twice - once in the live manufacturing system, and once in the budget version (used to make sure that we can make more in the next financial year). When I came to enrol the manufacturing version of the new products, guess what I forgot to check..?
I set up 42 resources, warehouse balance records and unit of measure conversions in the wrong database! If I'd had one to hand, I would have smashed myself upside the head with a clue stick!
The first two name who came to hand weren't in (then I remembered that they're at the new site, as Orable was supposed to go live at the start of this month, and was put back to next month when they worked out what else it can't do), so I called the third. He said that there is a way to copy the information back, but the bare bones of the records must already exist at their destination for it to work. Cue me entering data like a bastard. He tried one resource to see if it would work - it did! Then he told me what access I needed to do it (and one of the things I like about my job is the ability to amend ,y own system access). I submitted the first few jobs, and went to get lunch. When I checked, the jobs were sitting on the job queue. Not good, I thought, but not a lot that I can do about it. Then I got a call from the mainframe support people - the jobs were all going to fail. It was at this point that I started to despair. After some system prodding, it turned out that I'd misheard a vital piece of information. I could only use the cross-entity copy facility from the live version, even though the data I was copying were in the budget one... Cue frantic submissions of yet more jobs...
They have now all run, over-written the defaults with the correct information and are generally hunky-dory. *Breathes sigh of relief*
ION, happy birthday dragool! Welcome to the third trip around the Chinese zodiac! (I did get you a card, but I'm not sure if the address I've got is still correct.)
I've been helping IWasLike settle into PutUpon's role. It's not easy. She's been thrown into a totally different job with almost no training, and the end users have been spoiled by PutUpon's old trick of turning requests around in short order. One of them was almost affronted when I explained that our SLa includes a two working day lead time! Anyway, I've been helping her and trying to sort my own stuff out (and the 42 product codes that I received on Friday? I'd just about finished printing them out, when more started to arrive! Another 12, and counting...) Then I had to make a correction for one of the site munchkins - part my fault, part his. This involved doing the same thing twice - once in the live manufacturing system, and once in the budget version (used to make sure that we can make more in the next financial year). When I came to enrol the manufacturing version of the new products, guess what I forgot to check..?
I set up 42 resources, warehouse balance records and unit of measure conversions in the wrong database! If I'd had one to hand, I would have smashed myself upside the head with a clue stick!
The first two name who came to hand weren't in (then I remembered that they're at the new site, as Orable was supposed to go live at the start of this month, and was put back to next month when they worked out what else it can't do), so I called the third. He said that there is a way to copy the information back, but the bare bones of the records must already exist at their destination for it to work. Cue me entering data like a bastard. He tried one resource to see if it would work - it did! Then he told me what access I needed to do it (and one of the things I like about my job is the ability to amend ,y own system access). I submitted the first few jobs, and went to get lunch. When I checked, the jobs were sitting on the job queue. Not good, I thought, but not a lot that I can do about it. Then I got a call from the mainframe support people - the jobs were all going to fail. It was at this point that I started to despair. After some system prodding, it turned out that I'd misheard a vital piece of information. I could only use the cross-entity copy facility from the live version, even though the data I was copying were in the budget one... Cue frantic submissions of yet more jobs...
They have now all run, over-written the defaults with the correct information and are generally hunky-dory. *Breathes sigh of relief*
ION, happy birthday dragool! Welcome to the third trip around the Chinese zodiac! (I did get you a card, but I'm not sure if the address I've got is still correct.)