on 05-09-2011 5:32 AM
Hi All,
I have two remote systems R1 and R2, I am modelling a scnrio for materail master.
I have replaced all my qualified tables with tuples.
Main table
matNo Unit length width desc
mat01 BUn 10 20 TESTMAT - R1
mat02 BUn 15 30 TESTMAT - R2
Tuple
BUn Nr Dr AUn length width
EA 1 2 BX 10 20 - R1
EA 1 2 CT 10 20 - R1
EA 1 2 CR 10 20 - R2
EA 1 2 BAG 10 20 - R2
EA 1 2 BT 10 20 - R2
EA 1 2 CT 10 20 - R2
can a tuple have a remote key, i dont see any option, how can i check the with edit key mappings?
then how can i model this scnrio.......should i take this in a qualified table...... pls suggest me.
thnx,
ve
Hi Veena,
Tuples is just a data type but not a table. So it will not have the remote keys.
When you are accessing the main table records, even if you have a qualified lookup, we cannot see the remote key value of the qualified table.
So I do not see any reason for going back to the qualified table.
Kindly let me know the reason you need a remote key for a tuple.
Regards,
Sravan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
sravan, thanks for the reply
So, when I want to syndicate my data to remote systems, how will my data in tuples be segregated
mat01 BUn 10 20 TESTMAT - R1
EA 1 2 BX 10 20 - R1
EA 1 2 CT 10 20 - R1
mat02 BUn 15 30 TESTMAT - R2
EA 1 2 CR 10 20 - R2
EA 1 2 BAG 10 20 - R2
EA 1 2 BT 10 20 - R2
EA 1 2 CT 10 20 - R2
lets say I merge my above records, then I have a single record with ref to remote systems R1, R2.
mat02 BUn 15 30 TESTMAT - R2/R1
EA 1 2 BX 10 20 - R1
EA 1 2 CT 10 20 - R1
EA 1 2 CR 10 20 - R2
EA 1 2 BAG 10 20 - R2
EA 1 2 BT 10 20 - R2
EA 1 2 CT 10 20 - R2
So, How will my syndicaion work if I dont give a remote key for the data in tuple,
Is tuple right option for me or should I got with qualified table.
pls suggest.
rgards,
ve
Hi Veena,
When we merge two records from different remote systems, the same data is expected to be sent across all the remote systems.
In your case the material from R1 and R2 is now finalized as
mat02 BUn 15 30 TESTMAT - R2/R1
EA 1 2 BX 10 20 - R1
EA 1 2 CT 10 20 - R1
EA 1 2 CR 10 20 - R2
EA 1 2 BAG 10 20 - R2
EA 1 2 BT 10 20 - R2
EA 1 2 CT 10 20 - R2
So this record will as it is go to the 2 remote systems.
It is the same with the qualified table as well.
When the main table record from 2 different remote systems are merged, as it (merged record) will have reference to both the remote systems, Syndicator will send the same data to both the systems.
Irrespective of it being a tuple or qualified, we syndicate the main table records with the remote key of Material Number.
Regards,
Sravan
Hi sravan, thanks for explaining ....... still some doubt
mat02 BUn 15 30 TESTMAT - R2/R1
EA 1 2 BX 10 20 - R1
EA 1 2 CT 10 20 - R1
EA 1 2 CR 10 20 - R2
EA 1 2 BAG 10 20 - R2
EA 1 2 BT 10 20 - R2
EA 1 2 CT 10 20 - R2
So if this record goes to both the 2 remote systems, how will my remote sysem know the relevent records for remote system R1, should I include an new coloumn in my Tuple/Qualified to identfy my remote system.
If yes, then what is the use of the remote key option for the qualified table.
pls explain
thanks,
ve
Hi Veena,
Small correction from my end.
In case of qualified table, when 2 records from different remote systems are merged,
then based on the mapping we can decide whether all the qualified links or the relevant links should be sent to the remote system.
Mapping the remote key will send only the relevant qualified links to the remote system and not mapping the remote key will send all the qualified links.
This option is not available for tuple as it does not have any remote keys.
So if you want to send only relevant links to the remote system, then better use qualified table in your case.
Regards,
Sravan
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.