1.2.2 Non-Functional Features

Plato Batch Framework Adoption

Oracle Banking Supply Chain Finance has adopted the Plato Batch framework for supported scheduled and bulk-processing activities, including future-dated disbursements, auto-debit processing, invoice and purchase order acceptance, finance retries, reconciliation, and refunds. Batch execution can be configured using parameters such as commit frequency, stream size, and skip policy.

The framework is also used for applicable End-of-Day processes, including Stale Invoice, Overdue Invoice, Non-Performing Asset, Product Expiry, Program Expiry, Limit Structure Refresh, Limit Structure Expiry, Pre-EOD, Outstanding Transactions, Modify Contract, Batch Charges, Purchase Order Charges, and Alerts.

Plato Archival Adoption for Non-Business Tables

The Plato Archival framework has been adopted for configurable archiving and purging of non-business tables, including logging, audit, and event-log data, within the Supply Chain Finance domain. The adoption uses plato-archival-core to manage historical non-business data and support system performance and data-retention requirements.

Plato Field Configuration

A new service is introduced to provide the capability to make user interface extensible. This includes the ability to hide/show fields, enable/disable switches, set default values, or make non-mandatory fields as mandatory.

New Business Process Maintenance Adoption

The enhanced Business Process Maintenance interface has been adopted for creating and maintaining domain-specific workflows using the supported Domain-Specific Language (DSL).

Shared Filter Service Adoption

The Shared Filter Service has been adopted to provide standardized filtering across applicable Supply Chain Finance screens and services.

Common End-of-Day Processing Adoption

The Common End-of-Day framework has been adopted to support standardized orchestration and execution of applicable Supply Chain Finance End-of-Day processes.

Plato Rule and Configuration Screens with Maker-Checker

The Plato Rule and Configuration screens have been enhanced to support maker-checker processing for rule creation and modification. Changes are submitted through an approval workflow before becoming effective, and Supply Chain Finance has adopted the enhanced rule service to support this lifecycle.

Product Version and Environment Name Display

The product release version and configured environment name are displayed in the user interface and application logs, improving deployment identification, traceability, and operational troubleshooting.