Versions Compared

Old Version 10

changes.mady.by.user Pamela Totas

Saved on

compared with

New Version 11

changes.mady.by.user Pamela Totas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Version published after converting to the new editor

You can extend EagleML by using the IWS XPanels functionality. This article describes the requirements your environment must meet to use EagleML extensions, including the list of supported EagleML objects and required database tables with required fields. You will also find an example of how to create an extension via the XPanels application and load this extension via a Transform & Load solution. Use the same approach to create extensions and Transform & Load solutions for other objects.

On this page

Table of Contents
maxLevel2
printablefalse


Info
iconfalse
The EagleML Extension feature is only used to add fields into new tables. Existing tables should never be modified.

Anchor
Supported_EagleML_Objects
Supported_EagleML_Objects
Supported EagleML Objects

Loading to DB (inbound) – all EagleML objects EXCEPT Accounting.
Extracting from DB (outbound) – the following objects:

  • Warehouse Trade
  • Generic SMF
  • Generic SMF (history mode)
  • SMF Identifiers
  • SMF Identifiers (history mode)
  • Issuer Organization
  • Issuer Relationship
  • Rating
  • Generic Issue Analytics
  • Client
  • Schedule
  • Time Series
Info
iconfalse
While the above objects are supported, only SMF has been heavily used to date. The other objects have undergone basic unit testing and therefore there could be a chance of some minor issues. If you do encounter any, Eagle will address in a timely fashion.

Anchor
Required_Database_Tables
Required_Database_Tables
Required Database Tables

You must first create extension database tables with the required fields as listed below and grant the rights to apply SELECT, INSERT, UPDATE and DELETE commands in these tables to the ESTAR user. You will need to create two database tables to load your extension. 
The following sample script allows you to create two extension tables.

Code Block
languagesql
create table ESTAR.TEMP_WRHS_EXT
(
EFFECTIVE_DATE DATE,
ENTITY_ID CHAR(8),
SRC_INTFC_INST NUMBER,
PARAM1 VARCHAR2(500),
PARAM2 NUMBER,
PARAM3 DATE
); 

create table ESTAR.TEMP_TRADE_EXT
(
TRADE_ID NUMBER,
PARAM1 VARCHAR2(500),
PARAM2 NUMBER,
PARAM3 DATE
);
grant select, insert, update, delete on ESTAR.TEMP_WRHS_EXT to ESTAR;
grant select, insert, update, delete on ESTAR.TEMP_TRADE_EXT to ESTAR;

Anchor
Required_Fields
Required_Fields
Required Fields

  • EFFECTIVE_DATE - DATE, 
  • ENTITY_ID - CHAR(8),
  • SRC_INTFC_INST - NUMBER
  • SECURITY_ALIAS - NUMBER
  • LONG_SHORT_IND - CHAR(1)

are the fields (data type in bold) required for the following extension tables:

  • WarehouseTrade
  • WarehouseCloseLot
  • WarehouseCashActivity
  • WarehouseOpenLot
  • WarehousePosition
  • WarehouseNAV
  • WarehouseCashFlowProjection
  • WarehouseGLBalances
  • WarehousePerformance

TRADE_ID - NUMBER field is required for the WarehouseBrokerTradeQuote extension table.