This includes handling data presented to Virtual Trader in the form of files and spreadsheets, but also includes facilities for collected transactions directly out of Oracle EBS. There are various methods of collecting these transactions including concurrent processes, subscription services or Oracle trigger technology.
In contrast to the usual approach of providing a number of predefined options for the transactions collected for processing, Virtual Trader can be configured to collect and process any transaction whether it originated from within the host Oracle EBS application or a remote system.
Where timing is critical, as with shipping documentation for example, Virtual Trader can be operated in a ‘real time’ mode to process transactions on-demand.
This flexible facility provides a method of collecting transactions directly out of any table within the Oracle database. The facility collects transactions not already collected on each run.
This allows almost any transaction to be targeted for collection and processing by Virtual Trader, rather than a limited list of predefined options.
There are a number of predefined interfaces for Virtual Trader that relate to commonly used transaction types. A General Interface is provided to handle other types of transactions for which a specific interface is not provided directly.
The definition of this interface can be configured to match specific client requirements.
Where incoming transactions cannot be directly interfaced into an Oracle Table, transactional data can be loaded to Virtual Trader from a fat file.
The file can be a delimited file, or can be a fixed format file often used in mainframe applications. Virtual Trader can handle multiple record type definitions within the file.
Supports the loading of spreadsheets directly from the users desktop to interfaces in Virtual Trader.
This feature is not restricted to pre-defined spreadsheet layouts. A simple spreadsheet mapping facility allows client specific spreadsheet layout to also be accommodated.
Multiple spreadsheet definitions can also be handled.
Further more, this feature is not restricted to just accounting journals. This has been used to import stock options, payroll cross charges, cash funding schemes etc.
An alternative to collecting source transactions into Virtual Trader through ‘concurrent jobs’ is to use Oracle database triggers. This allows source transactions to be collected as they happen within the host Oracle application.
This is particularly useful when needing to collect transactions from on-line activity within Oracle EBS.
SLA Capture (Oracle Service Subscription)
There are a number of standard processes within Oracle EBS to which a client may ‘subscribe’. At these points within the process, Oracle passes control to the ‘subscriber’ where custom processing can be performed.
This is particularly true of accounting transactions passing through Sub Ledger Accounting but not yet imported to GL. This Service Subscription allows Virtual Trader to intervene with additional functionality or accounting.
For specialized requirements where timing is critical, Virtual Trader provides real time processing. This accommodates the need for on-line services to call the Virtual Trader Real-time Engine to provide processing results.
This facility has most typically been used for handling requirements around shipping and customs documentation.