Accounting DemoOrganizationalData.xml Rates

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Accounting DemoOrganizationalData.xml Rates

chris snow
In DemoOrganizationalData.xml, the rates are defined as global values:

    <RateAmount rateTypeId="STANDARD" rateCurrencyUomId="USD" periodTypeId="RATE_HOUR" workEffortId="_NA_" partyId="_NA_" emplPositionTypeId="_NA_" fromDate="2000-01-01 00:00:00.000" rateAmount="95.0"/>
    <RateAmount rateTypeId="DISCOUNTED" rateCurrencyUomId="USD" periodTypeId="RATE_HOUR" workEffortId="_NA_" partyId="_NA_" emplPositionTypeId="_NA_" fromDate="2000-01-01 00:00:00.000" rateAmount="55.0"/>
    <RateAmount rateTypeId="OVERTIME" rateCurrencyUomId="USD" periodTypeId="RATE_HOUR" workEffortId="_NA_" partyId="_NA_" emplPositionTypeId="_NA_" fromDate="2000-01-01 00:00:00.000" rateAmount="125.0"/>

In practice, does this fit most fee based organisations?  How would rates be modeled if different organisations within the company have different standard rates?  Would you simply add more rateAmount instances like the following with different partyId's and rateCurrencyUomId's?

    <RateAmount rateTypeId="STANDARD_HIGHER_US" rateCurrencyUomId="USD" periodTypeId="RATE_HOUR" workEffortId="_NA_" partyId="USORG" emplPositionTypeId="_NA_" fromDate="2000-01-01 00:00:00.000" rateAmount="150.0"/>
    <RateAmount rateTypeId="STANDARD_HIGHER_UK" rateCurrencyUomId="GBP" periodTypeId="RATE_HOUR" workEffortId="_NA_" partyId="UKORG" emplPositionTypeId="_NA_" fromDate="2000-01-01 00:00:00.000" rateAmount="75"/>

Many thanks in advance,

Chris