In Oracle Projects, user-defined cycles are used to specify when certain actions and processes take place. For example, billing cycles determine how often and on what dates a project is billed. Progress cycles determine when progress is to be entered for project tasks. Reporting cycles determine when new project status reports should be created and define the time period covered by each status report.
You must define cycles that fulfill your business needs, and assign cycles to each project. You can define and maintain as many cycles of each type as you need.
Note: A billing cycle code can optionally call a customized client extension to derive the next billing date.
In the Cycles window, specify the cycle name, type, value, effective dates, and a description of the cycle.
Save your work.
Name. Enter a unique, descriptive name for the cycle.
Type. Select the cycle type that you want to associate with the billing cycle. You can choose any predefined cycle type. The cycle types are shown in the following table:
| Billing Cycle Type | Description |
|---|---|
| Billing cycle days | The cycle is defined by the number of days that elapse between each automatic invoice generation date for a project. The entry you make under Value is the number of days in the cycle. |
| Date of the month | The cycle starts and ends on the same day of each calendar month. You enter the date under Value. Dates 29 through 31 are valid in some months only. For the months in which the date is invalid, Oracle Projects uses the last day of the month. |
| Last day of the month | The last day of each calendar month. |
| First day of the month | The first day of each calendar month. |
| 15th and month end | The 15th day and last day of each month. |
| Last weekday of the month | The last of a particular weekday in each calendar month. You enter the weekday under Value. |
| First weekday of the month | The first of a particular weekday in each calendar month. You enter the weekday under Value. |
| Project Completion | Completion date of the project. |
| Weekday each week | On the same day of each week. You enter the weekday under Value. |
| User defined | This type is used to indicate that the logic to derive the date has been coded in a cycle extension. You must customize the cycle extension to calculate the cycle that you require. |
Value. Enter the value that completes the information for the cycle type you entered. The following table shows the valid entries, depending on the cycle type:
| Value | Description |
|---|---|
| Integer | For the Bill Cycle Days type, enter an integer greater than or equal to zero. |
| Range 1 through 31 | For the Date of Month type, enter an integer in the range 1 through 31. |
| Monday through Sunday | For the Last Weekday of Month, First Weekday of Month, or Weekday Each Week type, select a weekday. Valid entries are Monday through Sunday. |
| User-Defined | For a user-defined cycle type, the Value can be anything meaningful for the client extension. Oracle Projects is seeded with three validated values (two date values and one day in the week value). You can specify two additional non-validated values. Weekdays are stored in the database as integers 1 to 7 for Monday to Sunday. |
Effective Dates. Enter the Effective Dates during which the cycle is valid.
Description. Enter a description for the cycle.
Other Sources
Billing Cycle Extension, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference