- Product Functionality
As Virtual Trader is a flexible ‘Structured Solution’, it can evolve quickly, without impacting business areas that do not change. The control of the business logic held within Virtual Trader is aimed at the business community, rather than IT.
These features significantly reduce the total cost of ownership and risk over the traditional route of customization.
Source & Target Definitions
The sources from which originating transactions are captured, and the targets to which the resulting outbound transactions are sent are configurable.
Oracle sources and targets are provided as standard, but the configurability of the product allows multiple instances to be accommodated, and non Oracle applications and customizations to be incorporated.
The Virtual Trader solution supports the application of business rules based on the nature of trading relationships, rather than specific company-to-company definitions.
New acquisitions can be quickly defined by the existing business rules through their addition to an appropriate trading relationship type.
This can often reduce setup and maintenance costs for large organizations.
Outbound Transaction Mapping
Virtual Trader natively supports mapping with common Oracle interfaces such as General Ledger, Payables & Receivables etc., but allows mapping to any available interface.
Virtual Trader supports this mapping across instances, mapping to interfaces of non-Oracle applications and customizations.
Virtual Trader also facilitates directly driving published API functionalities within Oracle EBS for real time Oracle updates.
Most implementations need to reference one or more custom lookups associated with the clients business.
Where these exist, Virtual Trader can reference original data.
Were they do not exist; a client specific form can be configured through the Custom Lookups functionality within Virtual Trader.
Custom Events, Utilities & Messaging
Where the existing business rules cannot accommodate specific business logic, Virtual Trader provides a series of User Exits (Custom Events) and Utilities that can provide advanced features or even PL/SQL procedures where necessary.
Any business logic or validation incorporated in this way can be associated with user-defined messages.
These Custom Events and Utilities are contained within the product and automatically migrated with all the other components of the product through the Virtual Trader Snapshot functionality.
All functionality within Virtual Trader that touches Oracle does so through ‘Views’. This approach provides a protective layer between Virtual Trader and the architecture of the underlying system.
These ‘Views’ are part of Virtual Traders client layer and can be modified to change the relationship to Oracle where necessary. New definitions can be added to work with multiple instances or even non-Oracle applications.