on 10-17-2011 10:44 AM
HI ALL,
We have 5 DSO'S from these 5 DSO'S data is going into one target DSO (DSO 6) and from this Target (DSO 6) Data is again loading into Info Object " Service contract".
DSO1---> DSO 6
DSO2---> DSO6
DSO3---> DSO6
DSO4---> DSO6
DSO5---> DSO6
After this from DSO6 ---> INFO OBJECT data is loading.
The problem here is some data is missingfrom DSO1and DSO 3 to the target DSO (DSO 6). when i observed the data is missing at master data Info object leval also but when i observed the data in source DSOs DSO1 and DSO3 data was there.
if i do REPAIR FULL LOAD the data is coming from the DSO1 to DSO6 and DSO3 to DSO6 after that DSO6 to Info object(Service contract) and later ATTR RUN and data is coming properly into infoobject and at report level also working fine.
the user is asking why its happenign like this so i did below analysis.
I did follwing analysis to find out why the data is not coming to data target (DSO 6 ) from DSO1 and DSO 3. to avoid this REPAIR FULL LOAD.
1. I have checked any common fields mapping there between DSOs. that is overwritting .But there are no commom fields mapping there.
2. In the process chain the data loading for all DSO's starting at same time in parallel but they are not completing at same time some fraction of second time gap there.
3 .I observed start routines. in the routine they are deleting some data based on flag in (DSO 3) and in (DSO 1) they are is code to check service contract as " NEW CONTRACT" based upon the data from DSO1, DSO2 and DSO3 active table " service conrtact start date and End Dates"
Can any body tell me what might be the reason for data is not coming to Target DSO (DSO6) and data is coming to target DSO when we do repair full load.
we need solution because always we can't load data by repair full load for single records. please help on this.
Hi,
I feel the data load sequence causes this mess. Instead of loading from all 5 DSO's in parallel, it's better to load one after the other. Put a validation as Successful while connecting all these 5 meta chains.
Regards,
Suman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
This data sequencing and time lag of data load .
As data increases data loading time increase proporationally.Your sequence might be correct but you have to make last load once other two loads are complete. May be you have to modify your process chain accordingly.
Thanks and regards
Kiran
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Looks like Data load sequence issue.
EX: -
While loading data from DSO1 to DSO6, if you are looking contract status detail from DSO2.
Now in this case,
if DSO2 is not loaded before start the data load from DSO1 to DSO6, code will not be able to find out the status detail of contract from DSO2. and that's why those data will get deleted..
But at the time of repair full, both DSO having data, so in repair full upload from DSO1 rto DSO6, code is able to find the status detail from DSO2. SO data will get loaded to DSO6.
SO whenever there is a look up, you need to take care of data load sequence. Otherwise you miss some records or some of the fields will updated with wrong information.
Please let me know if you have any doubt.
Regards,
Ashish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mostly it could be a load sequence issue.
Before concluding it is a load sequence issue, check -
1. If you have rules groups. If there are rule groups check the mapping in each rule group.
2.In transformation, If you have code in end routine and when the target is a DSO, next to end routines delete icon (garbage can) there is an icon similar to select fields, click on it, this will give info about the "Update of target fields".
Even when there are no mappings in transformation, if the option "all target fields(independent of active rules)" is selected, the target fields will be filled with blanks/zeros. So in your case check this setting in all transformations to DSO6 if there is end routine. It should be "only target fields with active rules".
Regards,
Raghu
Edited by: Raghu tej harish reddy on Oct 17, 2011 12:23 PM
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.