Virtual Trader


	Shared Service Centres


	Inter-Company


	Customised Accounting


	Systems Integrator

Systems Integrator

Download PDF)

For many organisations, operating multiple systems is a business reality due to acquisition, ‘best of breed’ or geographic location. This can result in complex business logic being ‘locked’ away in interfaces, and restrict the evolution of new business processes and work flows.
Using Virtual Trader to drive these interfaces provides a unified approach to systems integration. Interface logic is represented as business rules, maintained on-line by the business community in the same place and in a common format. This single repository of business rules provides a more robust, responsive and cost effective solution to an ever evolving organisation.

Although many systems provide ‘open’ interfaces, the programs developed by the client to populate them often result in complex logic to represent the various business requirements. Economics usually dictate that these are ‘hard coded’ facilities often with little uniformity of approach across interfaces and limited scope for modification, expansion or upgrade of ERP or boundary systems.
This results in poor visibility of the business rules embedded within these interfaces for the business owners. Maintenance of these interface requires both business and development staff and extensive end to end regression testing.
Virtual Trader’s Transaction Engine is a generic approach to driving interfaces. The business logic required by any interface is represented directly as rules maintained within Virtual Trader by the business community. This secures a continuity of approach for business rules across different interfaces, ensures visibility and promotes ease of use.
Each business scenario is represented within Virtual Trader by discrete re-usable groups of rules. This rule integrity promotes discrete change control management, significantly reducing the process life cycle and cost from definition to implementation. formats.

THE SYSTEM

VIRTUAL TRADER WILL

Virtual Trader is hosted within an Oracle Application environment. It can be co-resident with your Oracle Application or operate as a stand alone system.
Virtual Trader retains a crucial independence from the systems it integrates by ‘talking’ to each application it reads from or writes to through Dynamic Interfaces. These present the data from all transactions to be processed in a generic format. Version impact is confined to the Dynamic Interfaces, making the definition and processing of business rules largely independent of the source application and its version.
Dynamic Interfaces allow Virtual Trader to process transactions across various systems, applications, versions. As it is ‘instance aware’ it can also process and route transactions across multiple instances and platforms. Dynamic Interface plug-ins can be created and maintained by the client in order to adapt and evolve new solution areas.
Virtual Trader can route transactions from the same source to multiple destinations in a synchronous manner. These can be different work spaces, regional instances, different systems or versions or even different platforms.

	•	Integrate transaction processing between legacy or boundary systems and ERP suites.
	•	Integrate across different system platforms connected by database links.
	•	Integrate transaction processing across multiple instances or versions of ERP suite or different ERP systems.
	•	Maintain corporate systems directly or in parallel with local or operational systems. Transaction routing can be selective, summarised or consolidated.
	•	Control the routing of transactions between modules or systems using rule based ownership logic.
	•	Route transactions between multi-company work spaces and company specific facilities, often used in supporting shared service centre operations.
	•	Enable the business community to define and maintain the business logic needed within system interfaces in a common format.
	•	Provide a single repository for holding and viewing the rules that control the business.
	•	Eliminate the risk of ‘hard coded’ interface solutions.
	•	Reduce version dependency of system interfaces, and subsequent upgrade timescales and costs.
	•	Enable direct changes to business logic by the business community.
	•	Limit the scale of regression testing through the use of modular rule architecture.
	•	Reduce the design to implementation timescales and costs of evolving new business scenarios.