Recommendations and Best Practices
The following table outlines the recommended size for multiple elements, such as Activity Sheets and Business Processes (BPs), within the system. It also describes the consequences of exceeding the recommended sizes and provides additional best-practice guidelines for some situations.
Element | Maximum Size | Potential Result of Exceeding the Maximum Size |
|---|---|---|
Activity Sheet — Manual | 10,000 | If the maximum number of activities is exceeded, it impacts the speed at which the system displays the Activity Sheet. |
Activity Sheet — System | 50,000 | If the maximum number of activities is exceeded, it impacts the speed at which the system displays the Activity Sheet. Note: Because the System Activity Sheet is read-only, the system supports a larger number of activities than the Manual Activity Sheet does. |
BP — Cost Type — Base Commit — General Spends | 3,000 | If the number of line items is exceeded, the time required to update all relevant parts of the system might be extensive and, in certain conditions, the update might fail. |
BP — Cost Type — Base Commit — Payment Application | 2,000 | If the number of line items is exceeded, the time required to update all relevant parts of the system might be extensive and, in certain conditions, the update might fail. |
BP — Cost Type - Base Commit — Summary Payment Application | 2,000 | If the number of line items is exceeded, the time required to update all relevant parts of the system might be extensive and, in certain conditions, the update might fail. Best Practice: If there is only one costed line item per summary, Oracle recommends using the Payment Application BP instead of the Summary Payment Application BP. |
BP — Forms — Number of Auto-Creates on line items | 5 | Assuming that the maximum number of line items is used, exceeding the maximum size might require an extensive amount of time to update the system. |
BP — Forms — Number of Reverse Auto-Populates (RAPs) to unique BPs on line items | 10 | Assuming that the maximum number of line items is used, exceeding the maximum size might require an extensive amount of time to update the system. |
BP — Number of QBTs | 5 | The system limits the number of query-based tabs (QBTs) in a BP to 15. Best Practice: Oracle recommends that you create 5 or fewer QBTs. |
BP — Number of summary elements (QBT) | 50 | Oracle recommends that you use 50 or fewer summary data elements (DEs). |
BP — Generic Cost type using CBS codes or BP — Line Item type | 10,000 | If the number of line items is exceeded, the time required to update all relevant parts of the system might be extensive. |
Cash Flow | 1,000 | The number of CBS codes and columns determines the performance of the cash flow worksheet. Best Practice: Oracle recommends that you use 1,000 or fewer cost codes by 5 years for a monthly time scale (that is, with 60 or more columns as the size of the cash flow worksheet). Exceeding these maximum sizes might require an extensive amount of time to update the system. |
Cost Sheet — number of CBS codes | 10,000 | The number of cost breakdown structure (CBS) codes and columns determines the performance of the cost sheet. Oracle recommends that you use 10,000 CBS codes by 50 columns as the maximum size of the cost sheet. Exceeding these maximum sizes might require an extensive amount of time to update the system. |
Cost Sheet — number of columns | 50 | See the preceding entry, Cost Sheet — number of CBS codes. Best Practice: Based on a combination of BP records and their Status, the system supports up to 1,000 BP data sources. |
Custom Reports — Data Views |
| Best Practice: Although a size cannot be provided, Oracle recommends that you run a SQL statement Explain Plan in the environment where the reports will be run to ensure that the SQL query created is as efficient as possible. |
Document Manager — Files for Tree View | 20,000 | Avoid exceeding the maximum number of files across all folders in Tree View. Best Practice: If you anticipate exceeding the maximum number of documents, Oracle recommends that you use Flat View instead of Tree View. |
Fund Sheet — number of columns | 50 | See the following entry, Fund Sheet — number of FBS codes. |
Fund Sheet — number of FBS codes | 1,000 | The number of fund breakdown structure (FBS) codes and columns determines the performance of the fund sheet. Oracle recommends that you use 1,000 fund codes by 50 columns as a size of the fund sheet. Exceeding these maximum sizes might require an extensive amount of time to update the system. |
Integration: Add Assignees to Workflow BP Records REST API | In the array of an API Request, specify a maximum of 1000 records and 10 assignees. |
|
Integration |
| Oracle develops new web services using representational state transfer (RESTful) web services. Best Practice: Simple Object Access Protocol (SOAP) was deprecated in version 23.10. Oracle recommends that new integrations use RESTful (REST) web services and that existing customers migrate SOAP integrations to REST. |
Payment Application Records or Summary Payment Application Records | 500 | If you are importing payment line items in Payment Applications or Summary Payment Applications through a Microsoft Excel or CSV file for the Schedule of Values (SOV) sheet, ensure that each payment record is limited to batches of 500 or fewer rows. Exceeding the maximum number of rows might require an extensive amount of time to process all line items. Best Practice: For payment records with 2,000 or more SOV line items, Oracle recommends that you complete the process using multiple payment records, each of which contains 500 or fewer rows, including summary and costed line items, in the payment grid. |
Schedule Manager |
| See the preceding entries, Activity Sheet — Manual and Activity Sheet — System. Best Practice: The Schedule Manager was deprecated in version 23.5. Oracle recommends that new customers use the Activity Sheets and that existing customers transition to the Activity Sheet from the Schedule Manager. |
Schedule of Values (SOV) | 3,000 | The size is based on the recommendations for the Base Commits described earlier and takes the additional line items added through Change Commit into account. |
WBS Sheet — number of columns | 50 | See the following entry, WBS Sheet — number of WBS codes. |
WBS Sheet — number of WBS codes | 3,000 | The number of work breakdown structure (WBS) codes and columns determines the performance of the WBS sheet. Oracle recommends that you use 1,000 WBS codes by 50 columns as a size of the WBS sheet. Exceeding these maximum sizes might require an extensive amount of time to update the system. |
Last Published Wednesday, September 3, 2025