[ https://issues.apache.org/jira/browse/OFBIZ-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Smits updated OFBIZ-10905: --------------------------------- Description: Currently no service exists that creates CustomTimePeriod records on a scheduled basis. One could think of: * a yearly schedule that creates the next fiscal year period * a quarterly schedule that creates the next fiscal quartered period * a monthly schedule that creates the next fiscal month period Considerations regarding requirements: # Following requirements are to be considered static: ## the highest granularity regarding a custom time period is a year (parameter value = YEAR) # Following requirements are to be configured/set via SystemProperty records: ## the applicability based on data PeriodType records: currently we can derive/identify two categories: FISCAL and SALES; ## the highest period granularity is static and set to "YEAR" ## the lowest period granularity is configurable and set to "MONTH"; ## whether intermediate granularities (between lowest and highest) should be created for a given type (see 2.1) (intermediate indicator: "true"/"false" or "Y"/"N"). # A CustomTimePeriod is only to be created: ## when a PartyAcctgPreference record exists, and ## when the 'enableAccounting' field of that record has the value set to "Y" # Each lower granularity CustomTimePeriod record must reference higher granularity CustomTimePeriod record (Parent/Child principle). Based on requirement considerations stated above, following examples can be thought of: # with lowest granularity set to "MONTH" and intermediate indicator = "N" and type ="FISCAL: {code:java} <CustomTimePeriod customTimePeriodId="202000001" periodTypeId="FISCAL_MONTH" fromDate="2020-01-01 00:00:00.000" thruDate="2020-01-31 23:59:59.000" isClosed="N" periodNum="20200000" periodName="2020-JAN" organizationPartyId="Company" /> <CustomTimePeriod customTimePeriodId="202000002" periodTypeId="FISCAL_MONTH" fromDate="2020-01-02 00:00:00.000" thruDate="2020-02-29 23:59:59.000" isClosed="N" periodNum="20200000" periodName="2020-FEB" organizationPartyId="Company" /> {code} was: Currently no service exists that creates CustomTimePeriod records on a scheduled basis. One could think of: * a yearly schedule that creates the next fiscal year period * a quarterly schedule that creates the next fiscal quartered period * a monthly schedule that creates the next fiscal month period * etc. With each record referencing the appropriate parent, e.g.: * the fiscal month referencing the fiscal quarter * the fiscal quarter referencing the fiscal year * etc. > Have a service that runs periodically to generate CustomTimePeriod records > -------------------------------------------------------------------------- > > Key: OFBIZ-10905 > URL: https://issues.apache.org/jira/browse/OFBIZ-10905 > Project: OFBiz > Issue Type: Improvement > Components: accounting > Affects Versions: Release Branch 15.12, Release Branch 16.11, Release > Branch 18.12, Release Branch 17.12, Trunk > Reporter: Pierre Smits > Assignee: Pierre Smits > Priority: Major > Labels: CustomTimePeriod > > Currently no service exists that creates CustomTimePeriod records on a > scheduled basis. One could think of: > * a yearly schedule that creates the next fiscal year period > * a quarterly schedule that creates the next fiscal quartered period > * a monthly schedule that creates the next fiscal month period > Considerations regarding requirements: > # Following requirements are to be considered static: > ## the highest granularity regarding a custom time period is a year > (parameter value = YEAR) > # Following requirements are to be configured/set via SystemProperty records: > ## the applicability based on data PeriodType records: currently we can > derive/identify two categories: FISCAL and SALES; > ## the highest period granularity is static and set to "YEAR" > ## the lowest period granularity is configurable and set to "MONTH"; > ## whether intermediate granularities (between lowest and highest) should be > created for a given type (see 2.1) (intermediate indicator: "true"/"false" or > "Y"/"N"). > # A CustomTimePeriod is only to be created: > ## when a PartyAcctgPreference record exists, and > ## when the 'enableAccounting' field of that record has the value set to "Y" > # Each lower granularity CustomTimePeriod record must reference higher > granularity CustomTimePeriod record (Parent/Child principle). > Based on requirement considerations stated above, following examples can be > thought of: > # with lowest granularity set to "MONTH" and intermediate indicator = "N" > and type ="FISCAL: > {code:java} > <CustomTimePeriod customTimePeriodId="202000001" periodTypeId="FISCAL_MONTH" > fromDate="2020-01-01 00:00:00.000" thruDate="2020-01-31 23:59:59.000" > isClosed="N" periodNum="20200000" periodName="2020-JAN" > organizationPartyId="Company" /> > <CustomTimePeriod customTimePeriodId="202000002" periodTypeId="FISCAL_MONTH" > fromDate="2020-01-02 00:00:00.000" thruDate="2020-02-29 23:59:59.000" > isClosed="N" periodNum="20200000" periodName="2020-FEB" > organizationPartyId="Company" /> > {code} > -- This message was sent by Atlassian Jira (v8.3.4#803005)