Entity of an Open For Business Project Component
None
Copyright 2001-2009 The Apache Software Foundation
None
1.0
Wether members of the list should be contacted only once.
This view entity models the following options:
- SegmentGroupRole(SGR) -> SegmentGroupRole(SGRTO)
- SegmentGroupRole(SGR) -> SegmentGroupRole(SGRTO) -> PartyRelationship(PRSGR)
- SegmentGroupRole(SGR) -> SegmentGroupClassification(SGC) -> PartyClassification(PC)
- SegmentGroupRole(SGR) -> SegmentGroupClassification(SGC) -> PartyClassification(PC) -> PartyRelationship(PRPC)
Typical fields to constrain:
- partyId of User -> sgrPartyId (SGR)
- partyId of Customer -> sgrToPartyId (SGRTO) AND prSgrPartyIdTo (PRSGR) AND pcPartyId (PC) AND prPcPartyIdTo (PRPC)
NOTE: these 4 partyIds represent the 4 options for entity relationship paths listed above
NOTE: because not all of these will exist, each needs to be the given partyId(s) OR null
- roleTypeId of User -> sgrRoleTypeId (SGR) - ex: SALES_REP, MANAGER, etc
- roleTypeId of Customer -> sgrToRoleTypeId (SGRTO)
NOTE: because not all of these will exist, each needs to be the given roleTypeId(s) OR null
- roleTypeId of _Employer_ in Employee/Employer relationship -> prSgrRoleTypeIdFrom (PRSGR) AND prPcRoleTypeIdFrom (PRPC) - INTERNAL_ORGANIZATIO
NOTE: constraining these fields is optional as the EMPLOYEE roleTypeIdTo is often sufficient
NOTE: because not all of these will exist, each needs to be the given partyId(s) OR null
- roleTypeId of _Employee_ in Employee/Employer relationship -> prSgrRoleTypeIdTo (PRSGR) AND prPcRoleTypeIdTo (PRPC) - EMPLOYEE
NOTE: because not all of these will exist, each needs to be the given partyId(s) OR null
- partyRelationshipTypeId in Employee/Employer relationship -> prSgrPartyRelationshipTypeId (PRSGR) AND prPcPartyRelationshipTypeId (PRPC)
NOTE: because not all of these will exist, each needs to be the given partyId(s) OR null