Entity Resolution for Warehouse Objects

Warehouse Objects use entity resolution logic that is similar to the logic used by Reference and Entity Objects, but simplified.

The lookup used (eagle/star/pan-qentityxreference.htm) contains important elements around the code to implement the entity resolution logic:

Only 1 identifier can be used.

Class Code is not used for resolution.

There are 2 methods to specify the Entity Id element for Warehouse objects:

by Entity Xref Identifiers and
directly in entityId element of incoming EagleML message

Additional Details Around Resolving Entity Directly in entityId Element of Incoming EagleML Message

1. If the elements Xref Account Id and Xref Account Id Type are present in the incoming EagleML message:

In this case the value of Entity Id element is defined in the lookup by input parameters Xref Account Id (mapped Into RULESDBO.ENTITY_XREFERENCE.XREF_ACCOUNT_ID) and Xref Account Id Type (mapped Into RULESDBO.ENTITY_XREFERENCE.XREF_ACCOUNT_ID_TYPE).

The resulting value (mapped from the RULESDBO.ENTITY_XREFERENCE.ENTITY_ID) will be mapped into HOLDINGDBO.POSITION.ENTITY_ID database field.

An example of Entity Xreference Identifiers in the incoming message:

<EagleML>
        <header>
           ...
        </header>
        <warehouseTransaction>
                <header>
                   ...
                </header>
                <warehousePosition>
                         ...
                        <xrefAccountId>X</xrefAccountId>
                        <xrefAccountIdType>X</xrefAccountIdType>
                         ...
                </warehousePosition>
        </warehouseTransaction>
</EagleML>

2. If the Xref Account Id and Xref Account Id Type are not present in the incoming EagleML message:

The element Entity Id should not be null. The mapping into HOLDINGDBO.POSITION.ENTITY_ID database field will be direct.

Entity Identifiers can be found in the ‘Entity Common Id Model’ XSD Group. Refer to the Entity Common Id Model mapping for more details.