Definition Type: ComplexType
Name: BeneficiaryType
Namespace: http://www.hr-xml.org/3
Containing Schema: Components.xsd
Abstract
Documentation:
Beneficiary. Details Contains a collection of data about a person or organization designated as the receiver of some allocation of account proceeds in the event of the account holder's death. Note that BeneficiaryPerson and BeneficiaryOrganization are optional elements appearing in sequence. xsd:choice is not used for tool compatibility reasons. However, proper use is to use one or the other, but not both when a single BeneficiaryDetails instance.
Collapse XSD Schema Diagram:
Drilldown into UserArea in schema fields_xsd Drilldown into BenefitAmountDesignation in schema components_xsd Drilldown into BeneficiaryOrganization in schema components_xsd Drilldown into BeneficiaryPerson in schema components_xsd Drilldown into BeneficiaryTypeCode in schema fields_xsd Drilldown into PrecedenceCode in schema fields_xsd Drilldown into BeneficiaryID in schema fields_xsd Drilldown into PlanID in schema fields_xsd Drilldown into validTo in schema fields_xsd Drilldown into validFrom in schema fields_xsd Drilldown into EffectiveDateAttributeGroup in schema fields_xsdXSD Diagram of BeneficiaryType in schema components_xsd (HR-XML - Human Resources XML)
Collapse XSD Schema Code:
<xsd:complexType name="BeneficiaryType">
    <xsd:annotation>
        <xsd:documentation source="http://www.hr-xml.org" xml:lang="en">
            <ccts:DictionaryEntryName xmlns:ccts="urn:un:unece:uncefact:documentation:1.1">Beneficiary. Details</ccts:DictionaryEntryName>
            <ccts:DefinitionText xmlns:ccts="urn:un:unece:uncefact:documentation:1.1">Contains a collection of data about 
a person or organization designated as the receiver of some allocation of account proceeds in the event of the account holder's death.</ccts:DefinitionText>
            <ccts:UsageRule xmlns:ccts="urn:un:unece:uncefact:documentation:1.1">Note that 	BeneficiaryPerson and BeneficiaryOrganization are optional elements appearing in sequence. xsd:choice is not used for tool compatibility reasons. However, proper use is to use one or the other, but not both when a single BeneficiaryDetails instance.</ccts:UsageRule>
        </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
        <xsd:element ref="PlanID" minOccurs="0" />
        <xsd:element ref="BeneficiaryID" minOccurs="0" />
        <xsd:element ref="PrecedenceCode" minOccurs="0" />
        <xsd:element ref="BeneficiaryTypeCode" minOccurs="0" />
        <xsd:element ref="BeneficiaryPerson" minOccurs="0" />
        <xsd:element ref="BeneficiaryOrganization" minOccurs="0" />
        <xsd:element ref="BenefitAmountDesignation" minOccurs="0" />
        <xsd:element ref="UserArea" minOccurs="0" />
    </xsd:sequence>
    <xsd:attributeGroup ref="EffectiveDateAttributeGroup" />
</xsd:complexType>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
PlanID nsA:PlanID 0 (1)
BeneficiaryID nsA:BeneficiaryID 0 (1)
PrecedenceCode nsA:PrecedenceCode 0 (1)
BeneficiaryTypeCode nsA:BeneficiaryTypeCode 0 (1)
BeneficiaryPerson nsA:BeneficiaryPerson 0 (1)
BeneficiaryOrganization nsA:BeneficiaryOrganization 0 (1)
BenefitAmountDesignation nsA:BenefitAmountDesignation 0 (1)
UserArea nsA:UserArea 0 (1)
Collapse Child Attributes:
Name Type Default Value Use
validFrom nsA:validFrom Optional
validTo nsA:validTo Optional
Collapse Derivation Tree:
Collapse References:
nsA:Beneficiary