Entity Accounting Periods - SP Mode of Data Loading

The SP mode is the mode of loading data using the stored procedure.

To use this mode, set the Accounting Validation Flag (entityTransaction/entityAccountingPeriods/accountingValidationFlag) to ‘Y’:

<accountingValidationFlag>Y</accountingValidationFlag>

In SP mode data, is only inserted into the ESTAR.ESTAR_ACCOUNTING_PERIODS DB table (Open Accounting Period). 

The SP mode does not support updating data.

Inserting Data in SP mode

The following conditions are required to insert a new record:

• The record with the set of elements Entity Id (DB field PORTFOLIO_ACCT) + Accounting Basis (DB field ACCT_BASIS) + Start Date (DB field START_DT) + End Date (DB field END_DT) specified in the incoming message should not exist in the ESTAR.ESTAR_ACCOUNTING_PERIODS DB table.
• The period Start Date – End Date specified in the incoming message should not overlap with any already existing periods START_DT – END_DT in ESTAR.ESTAR_ACCOUNTING_PERIODS for the same set of Entity Id + Accounting Basis.

For example, if the following Accounting Periods entry exists in DB:

The example of valid values of Start Date and Ent Date would be:

<startDate>2015-02-04</startDate>
<endDate>2015-02-06</endDate>

<startDate>2015-02-27</startDate>
<endDate>2015-02-28</endDate>

The examples of invalid values of Start Date – End Date would be (the specified Accounting Periods will overlap with existing in the database):

<startDate>2015-02-03</startDate>
<endDate>2015-02-04</endDate>

<startDate>2015-02-25</startDate>
<endDate>2015-02-27</endDate>

‘{n} overlapping period(s), new period(s) not added’

Mapping for SP mode

The following elements are be loaded from the incoming EagleML message directly to DB:

The following values are inserted by the stored procedure into other DB fields: