on 2010 Aug 17 9:26 PM
Hi All,
I have an issue, the data is coming from a flat file update DSO on monthly basis.
Say there is two field X(CHAR 6) and Y(CHAR 7), X loads data like aaaa, ahah,dest and Y loads data like 0034,8234,1209.
What happened is in some files(2 months back) say the data for X is loaded into Y bcoz the data been swapped in the file.
say field Y is loaded with data like aaaa, ahah,dest for some month say april 2010. Currently the field X alone is used in the report, now if you run the report for april there is no value in the field X bcoz the value is stored in field Y.
This is the situation, can anyone tell me how to solve?
Regards,
Anand
There are couple of options available:
1. Do selective deletion on DSO for the month of april, and correct the flat file and reload it.
2. Since its a DSO and mostly if it is overwrite just reload the correct april file, it will correct it self, but check all keyfigures should have overwrite.
hope this helps
thanks
syed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We cant do the reload here. Its kind of FI file, we are not allowed to do it. Is there any option to solve.
Ok let me ask you few things, Is it possible to add a new field in the DSO were data exist?
If yes, what is the step to do it? bcoz if yes i can write a routine to populate value for this new field from the existing two characteristics.
correct me if i am wrong. Also suggest me is there any other way to fix it.
Is there any way i can do it at query level?
Hi,
The best way is to do is relaod the file after selctive deletion.
If you want to add one more field to have values from both fields, this is not advised as it will restrict the future usage and requirements and for data load mistake we should not change the structure.
Still you want to do that then you may do this technically by adding one object to DSO (if it is an data filed, If it is a key field then when you will tarsprot the DSO it will fails to othere system and will ask for data deletion).
If it is data filed then ad that filed and create a self update rule from this DSO to this only (you may do that) In self update rule do the mapping for new field as needed.
I will still suggest the slective deletion and realod.
I hope it will help.
Thanks,
S
Hi Araj,
If you wish to add a characteristic to the DSO and you do not delete any existing one, then i think transport should be a success without deleting the data.
I have an idea which might just solve your problem. Create an identical DSO and transport it. In your transformation write a proper "Start/End" routine for populating the correct data in correct fields.
Pls note you can include an additional field if needed for correcting your data.Then after successful load to new DSO, move the data(full) to your original DSO.
Thanks,
VA
Edited by: Vishwa Anand on Aug 19, 2010 6:05 PM
User | Count |
---|---|
82 | |
12 | |
10 | |
10 | |
10 | |
9 | |
8 | |
7 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.