Vision Upload Format: AnalystEst

Vision Portfolio Management Application Layer: Data Feeds

| Application Feeds |

Data Feed: AnalystEst

Category: EntityExtenderFeed

Summary:

    The AnalystEst feed is used to create and update AnalystEstimate data record instances for companies. A separate AnalystEstimate record is created for each date for which data is available for a company. The data is accessed via the time series property analystEsts defined for the Company class.

    This feed can include data for any number of companies for any number of dates and can be used to initialize new dates, set initial values for properties and/or change existing values.

    This class is described in the Portfolio Management Application Supplemental Classes document.

Available Fields:

FieldAnalystEstimate
Property		TypeDescription
--- Required Fields ---
entityId entity String any valid company identifier
date date Date date of data
currencyId baseCurrency String id of currency for monetary data values
--- Suggested Fields ---
adjustmentDate adjsutmentDate Date date through which data values are adjusted
nextQuarterEnd nextQuarterEnd Date next fiscal quarter end date
nextYearEnd nextYearEnd Date next fiscal year end date
q1Est _q1Est Number estimate for next fiscal quarter
q2Est _q2Est Number estimate for following fiscal quarter
q3Est _q3Est Number estimate for following fiscal quarter
q4Est _q4Est Number estimate for following fiscal quarter
y1Est _y1Est Number estimate for next fiscal year end
y2Est _y2Est Number estimate for following fiscal year end
y3Est _y3Est Number estimate for following fiscal year end
analyst analyst Number id of existing Analyst instance

Special Processing Rules:

  • The entityId must correspond to an existing Company instance. Any valid company alias can be used to identify the company.

  • The date must be included and indicates the date of the data. It can be in any valid date format such as 9705 or 5/31/97. This date is used to update the Company time series property analystEsts.

  • If the entityId and date are valid and the date does not currently exist in the Company time series property analystEsts, a new AnalystEstimate instance is created and added to this time series on this date. Any items supplied by this feed are then set or refreshed. Note that you do not need to include all the items in a single feed.

  • The currencyId is used to identify the currency in which the data values are supplied. This currency can be different from the company's base currency. By default, the information is automatically converted into its company's base currency when it is accessed (in cases where the currencies are different). If the supplied currencyId does not map to an existing currency instance, the record's baseCurrency is set to the default currency.

  • The adjustmentDate is used to identify the date through which the data in the feed instance has been adjusted for splits. Normally, this date is the same as the record's date and this field need not be provided. When loading history and/or corrections, the values may be supplied unadjusted (i.e., the values that existed on the date) or adjusted (i.e., the values adjusted for any splits that have occurred since the date. If the data is unadjusted, the adjustmentDate field is not needed or can contain the same value as the date field. If the data has been adjusted to reflect splits that have occurred since the record date, this field should indicate the date through which splits have been applied.

    Note that you do not need to resend data that has changed as the result of a split adjustment. Only true data corrections need to be supplied using this feed.

  • The nextYearEnd date field is used to specify the next fiscal year end date for which estimates can be provided. This date will be a future date for companies that have reported the year-end data and will be a prior date for companies that have not yet reported. For example, if a company's fiscal year ends in December and it currently January 1998, the company will not have reported its December 1997 data. The next year end in this case would be 12/31/97. Once the company has reported its 1997 data, the next year end should be set to 12/31/98. The y1Est, y2Est, and y3Est values correspond to the annual estimates for the next three fiscal year ends.

  • The nextQuarterEnd date field is used to specify the next fiscal quarter end date for which estimates can be provided. This date will be a future date for companies that have reported their latest quarter-end data and will be a prior date for companies that have not yet reported. For example, if a company's fiscal quarter ends in December and it currently January 1998, the company will not have reported its December 1997 data. The next quarter end in this case would be 12/31/97. Once the company has reported its 12/97 data, the next quarter end should be set to 3/31/98. The q1Est, q2Est, q3Est, and q4Est values correspond to the quarterly estimates for the next four fiscal quarter ends.

Related Feeds:

Sample Upload:

The following tab-delimited feed could be used to create and refresh AnalystEstimate instances: 

Interface ExternalFeedManager upload: "AnalystEst" using:
     "entity     date     currency   nextYearEnd  y1Est   y2Est
      45920010   19980115 USD        12/31/97     12.3    15.4
      45920010   19980224 USD        12/31/98     15.4    18.3
      00036110   19980115 USD        05/31/98      9.2    10.4
     " ;