...
| Info |
|---|
|
| 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 ObjectsLoading to DB (inbound) – all EagleML objects EXCEPT Accounting.
Extracting from DB (outbound) – the following objects:
...
| Info |
|---|
|
| 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 TablesYou 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 |
|---|
|
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 FieldsThe EFFECTIVE_DATE DATE, ENTITY_ID CHAR(8), and SRC_INTFC_INST NUMBER fields (data type in bold) are required for the following extension tables:
...