The feature was introduced in patch level vt272gen008

For Virtual Trader to process a record, it needs to know that a business event has happened. We traditionally have used database triggers, concurrent programs, forms personalisation and custom programs to provide these feeds. Now there is another way to capture records from Oracle's base tables and Oracle provides the solution.

Oracle Alerts are often used to send email notifications to staff that a particular criteria has happened in the database. For example, a item many not have been costed or an order date can not be meet. But Oracle Alerts are more powerful than that. They can also perform PL/SQL insert and update commands.

In patch vt272gen012 we will provide a database function call that can be added to an Oracle Alert. This feature makes an entry into a new table in Virtual Trader called 'cp_interface_queue' containing the 'table name' and 'rowid' of the source table. From here Virtual Trader uses a 'Queue Definition' to figure out key data elements and makes an entry into the appropriate Virtual Trader interface.

It's like having a database trigger, without having a database trigger and is ideal for moderate volumes of data inserts or updates on base tables (not interfaces).

If you would like to know more, please contact us.

- Keith

For those of our customers that capture records based on a trigger on the GL_INTERFACE, this method will no longer be available in all cased. Instead we have worked we some of our customers and Oracle to develop a new method of capturing journals via the Oracle Business Events. A patch will soon be available to all customers that want to use this method.

We have developed a public database package that can be used by the Oracle Business Events. The package is called xxcp_business_event.obe_gl_start_import_r12,  which is used as a subscription to the event. The code looks at records being passed to the GL and if required makes a copy of the record into cp_gl_interface. When VT runs it creates new records into the GL_INTERFACE table and they are imported in the original way.

If you have any questions about this new method, please contact us.

We have been busy over the last six months creating VT272. We have included a lot of features that our clients have asked for and made some areas of the product simpler to configure and support.

VT272 includes new features like Pricing ladders, simpler Pricing Methods, Common Assignment, Formula Sets, Snapshot compare, Pass Through Rules, additional security and many other new features that will make configurations easlier.

If you are running a version of VT that is earlier than VT271 then you don't need to take all of the patches between your existing version and vt271. Our support team are happy to provide scripts that will let you skip those major patch releases.

We hope you enjoy this release.

- Keith

The new feature translates the SQL block and the Dynamic Attribute Sets. In the case of the Dynamic Attribute Sets we have provided a list of values with the available Bind Variables and Dynamic Attributes so that they are quickly to hand and reduce typing errors.

I hope you like this new feature.

- Keith

System designers have got around this problem by embedding the ownership logic in the Assignment Dynamic Interfaces, but this quickly becomes hard to maintain and understand.

In VT272 we’ve introduced a new optional feature called Common Assignment in the Assignment Control form to work out a number of Tax Registrations before the Dynamic Interface fires for a processing Trading Set (or Leg).

Once the Tax Registrations have been worked out they can be used in the Assignment Dynamic Interfaces that follow, or directly in the Assignment Rules. This can eliminate the need for complex SQL and duplication. It makes the rules easier to understand and most importantly it keeps the business rules in your hands.

We hope you like this new feature.

- Keith