5.2.1.3 Application Preferences
Application Preferences UI allow Administrators and End Users to establish default values, manage other Core Application Parameters that affect the way Business Rules are created and the way Engine Processes are run.
To update the Funds Transfer Pricing Application Preferences:
- Navigate to Maintenance and select Preferences.
- Click Application tab.
Figure 5-17 Processing - Cash Flow General section of Application Preference
- Enter the following values in Application tab as described in the
table:
Fields Description Debugging Level The debugging output level determines the amount of SQL that will be written to the processing log. There are eight levels available:
- Trace: Designates finer-grained informational events than the DEBUG.
- All: All levels including custom levels.
- Error: Designates error events that might still allow the application to continue running.
- Information: Designates informational messages that highlight the progress of the application at coarse-grained level.
- Debug: Designates fine-grained informational events that are most useful to debug an application.
- Fatal: Designates very severe error events that will presumably lead the application to abort.
- Warning: Designates informational messages that highlight the progress of the application at coarse-grained level.
- Off: The highest possible rank and is intended to turn off logging.
Note: A log request of level p in a logger with level q is enabled if p >= q. This rule is at the heart of log4j. It assumes that levels are ordered. For the standard levels, we have ALL < DEBUG < INFO < WARN < ERROR < FATAL < OFF.
View Logs Level This shows the severity of the information telling you how important a given log message is. This shows the View level of the Log. There are three levels available:
- Information: Designates informational messages that highlight the progress of the application at coarse-grained level.
- Debug: Designates fine-grained informational events that are most useful to debug an application.
- Off: The highest possible rank and is intended to turn off logging.
Figure 5-18 Processing - Cash Flow Process section of Application Preference
Fields Description Cash Flow Process Batch Size Number of Account or Instruments that must be processed in a single batch. This is used by Cash Flow Engine for performance tuning.
Default Value of 1000 is seeded by the service, and you can modify it as needed
Cash Flow Process Parallel Requests Number of Parallel batches executed by each executor. This is a performance tunning parameter for Cash Flow Engine Cloud Service.
Default Value of 2 is seeded by the service, and you can modify it as needed
Cash Flow Process Parallel Threads Number of threads created by the executor for each batch. This is a performance tunning parameter for Cash Flow Engine Cloud Service. This defines how much memory can be used by the different components of the process such as the stack, data and text segments.
Default Value of 5 is seeded by the service, and you can modify it as needed
Cash Flow Process Flush Batch Size
Number of records that gets saved or updated in a batch during Cash Flow Process execution. This is used by Cash Flow Engine for performance tuning.
Default Value of 500 is seeded by the service, and you can modify it as needed
Figure 5-19 Processing - Cash Flow Edits section of Application Preference
Fields Description Cash Flow Edits Batch Size
Number of Account or Instruments that must be processed in a single batch. This is used by Cash Flow Edits Engine for performance tuning.
Default Value of 1000 is seeded by the service, and you can modify it as needed
Cash Flow Edits Flush Batch Size
Number of records that gets saved or updated in a batch during Cash Flow Process execution. This is used by Cash Flow Engine for performance tuning.
Default Value of 500 is seeded by the service, and you can modify it as needed
Figure 5-20 Dimensions and Hierarchies
Fields Description Default Dimension
Transfer Pricing requires users to declare one of the “Product” dimensions as the TP Product dimension. The model is seeded with three possible selections:- Product
- Common COA
- GL Account
Users can also add any placeholder dimension as product dimensions, which would also appear in the above list. Transfer Pricing business rules are based on the Product dimension selected here. The suggested default is the “Product” dimension
Default Hierarchy The list of values for the Default Product Hierarchy is based on the Default Product Dimension selection. The hierarchy selected here will be the default hierarchy selection in all business rules that support node-level assumptions. This selection acts as the starting value for convenience only and users can change at their discretion within each business rule. - Turn-on the Is Editable status.
- Click Save to confirm the changes.