|
Re: Update Script - Failed to parse sql- Please help
Posted: 22 Feb 10 9:51 AM
|
Now, looking at this from a completely different perspective:
If your Account Extension Table (C_ACCOUNT_EXT) has a One to One Relationship to the Account table, why would you add a SECCODEID column to it (and name it SECCODEID)?
I am not saying that it isn't ok to add multiple Relationships to Owners (e.g. Owner = Sales Team, and Implementation = Implementation Team), however if that was the case I wouldn't call it SECCODEID.
The fact is that (again, if the relationship is one to one) that the C_ACCOUNT_EXT table carries the security from the ACCOUNT record, so by having this column it causes problems with synchronization if it is not properly updated.
For instance, If I change the Owner of the Account using Territory Realingment, but fail to follow it up with an Update script for the Extension table, the Remote reps that receive this records on their database would not have visibility to them. Their screens would load partial data, and they may even receive errors regardign PK violations when trying to update these records.
Now, if the data on the Extension table is indeed to be kept away from certain users, then this approach "may" be ok, but you have to make sure to always use LEFT joins to avoid issues on Detail views, and/or properly maintain Teams and Ownership when reassignig records.
|
|
|