About the Warehouse Close Lot Inbound Interface

Overview

The Warehouse Close Lot inbound interface is designed to load and update data in the TRADESDBO.DISPOSAL_LOTS database table.
The format of incoming message: EagleML (WarehouseCloseLot complex type).

Stream Logic

EagleML Processing Sequence

Warehouse Close Lot is loaded into DB via eagle_ml-2-0_default_in_xml_warehouse_preproc in two steps:

XSLT transformation. XSLT rule 'eagle_default/in/xml/xslt/wrh_egl_gen_interface3.xsl' is used.
Loading data into the database. The 'eagle_default/in/xml/xml-warehouse_v2.xml' rule is used.

To load or update data in Warehouse Close Lot database tables send an EagleML message into the eagle_ml-2-0_default_in_xml_warehouse_preproc stream.

Refer to the data Map Table for Warehouse Close Lot object.

CSV Processing Sequence

Warehouse Close Lot is loaded to DB with the following streams:

eagle_default_in_csv_warehouse - this is PRF stream which consist of two steps transform and load
eagle_default_in_csv_warehouse_t - transformation CSV to EagleML
- close_lot.xml rule
eagle_ml-2-0_default_in_xml_warehouse_preproc
- XSLT transformation. XSLT rule 'eagle_default/in/xml/xslt/wrh_egl_gen_interface3.xsl' is used.
- Loading data into the database. The 'eagle_default/in/xml/xml-warehouse_v2.xml' rule is used

To load or update data in Warehouse Close Lot tables, send your CSV message to the eagle_default_in_csv_warehouse stream.

Required Elements

The following elements are required in the EagleML message: Effective Date, Entity Id (or Entity Identifiers), Source Name, Lot Number, identifiers to resolve Security Alias.

Effective Date: warehouseTransaction/warehouseCloseLot/effectiveDate – mapped to TRADESDBO.DISPOSAL_LOTS.EFFECTIVE_DATE
Entity Id: warehouseTransaction/warehouseCloseLot/entityId (or warehouseTransaction/warehouseCloseLot/xrefAccountId and warehouseTransaction/warehouseCloseLot/xrefAccountIdType) – mapped to TRADESDBO.DISPOSAL_LOTS.ENTITY_ID
Source Name: warehouseTransaction/warehouseCloseLot/sourceName
Number of Lots: warehouseTransaction/warehouseCloseLot/numberofLots – mapped to TRADESDBO.DISPOSAL_LOTS.NBR_OF_LOTS
Master Ticket Number: warehouseTransaction/warehouseCloseLot/masterTicketNumber – mapped to TRADESDBO.DISPOSAL_LOTS.MASTER_TICKET_NUMBER
Security Identifiers: to resolve the Security Alias (see the section 'Security Resolution Logic'), Security Alias mapped to TRADESDBO.DISPOSAL_LOTS.SECURITY_ALIAS

Relationship to DB Table TRADESDBO.TRADE, Element Trade Id

For successful loading data into DB table TRADESDBO.DISPOSAL_LOT, the record containing the following elements should exist in the DB table TRADESDBO.TRADE:

Security Alias + Source Name + Entity Id + Master Ticket Number

The set of elements above are mapped into lookup for resolving Trade Id:

SELECT trade_id
INTO L_trade_id
FROM TRADE
WHERE security_alias = L_security_alias
AND src_intfc_inst = L_src_intfc_inst
AND entity_id = in_entity_id
AND effective_date = TO_DATE(in_effective_date,'YYYYMMDD')
AND master_ticket_number = in_master_ticket_number;

Security Alias: mapped to TRADESDBO.TRADE.SECURITY_ALIAS
Source Name: the field Src Intfc Inst resolved by Source Name, mapped to TRADESDBO.TRADE.SRC_INTFC_INST
Entity Id: mapped to TRADESDBO.TRADE.ENTITY_ID
Master Ticket Number: mapped to TRADESDBO.TRADE.MASTER_TICKET_NUMBER

The loading will complete with an error if the record with specified elements in incoming message above is not present in Trade DB table. You have to load a Warehouse Trade record first.

Security Resolution Logic

<securityAlias> should not be specified in the incoming EagleML message. Refer to Security Resolution for Warehouse Objects

Entity Resolution Logic

Refer to Entity Resolution for Warehouse Objects

Modes of Data Loading

The Warehouse Close Lot inbound interface has two modes for loading data into DB.
Batch Mode
UPSERT mode