Page 1 of 1
rejection logic
Posted: Mon Feb 11, 2008 9:26 pm
by veera24
Actually i got to generate sequence ID'S.After that, i'll load d data into DB.So i ll generate the ID'S irrespective of the rejection.So i need to pull the ID'S again without generating again cos am supposed to maintain uniqueness.Is there any logic for single rejection run?and moreover am supposed to parameterise the hardcode values also..ll any one help me 4 this?...
Thanks in advance,
veera.
Posted: Mon Feb 11, 2008 10:23 pm
by ray.wurlod
The best advice is to write out what has to happen in each circumstance, in English (or your language of choice). This becomes the specification from which you can then develop your algorithms and, finally, your job design.
Re: rejection logic
Posted: Tue Feb 12, 2008 7:36 am
by chulett
veera24 wrote:Actually i got to generate sequence ID'S.After that, i'll load d data into DB.So i ll generate the ID'S irrespective of the rejection.So i need to pull the ID'S again without generating again cos am supposed to maintain uniqueness.Is there any logic for single rejection run?and moreover am supposed to parameterise the hardcode values also..ll any one help me 4 this?...
'single rejection run'? What 'hardcode values'?
I'm sorry, but I really have no idea what you are trying to accomplish or what exactly you need help with - other than load data with surrogate values. Can you try again please, rephrase this for us?