3.31 Defaulting of Price Date in Transaction Screens

This topic provides information on Defaulting of Price Date in Transaction Screens details.

While entering a transaction in any of the Transaction Detail screens, you will have to select the fund in which the requested transaction has to be put through. Once you choose the fund from the option list, the field From Price Date will be displayed.

The table below gives you four sets of conditions that will determine the price date that will be updated in the field From Price Date.

Table 3-173 Price Date details

Case	Post Priced	Forward Pricing	Specific Fund Price Frequency	Cut Off Basis	Adhoc Price Date
Case1	Yes	No	NA	NA	NA
Case2	Yes	Yes	User Defined	Cut Off Based on Price Date	NA
Case3	Yes	Yes	User Defined	Cut Off Based on Price Date	Maintained
Case4	Yes	Yes	Any option other than User Defined	Cut Off as an Independent Calendar	Maintained

Note:

When indicating the Adhoc Price Date you should have specified that the price entered is not meant for reporting alone, by not checking the box For Reporting.

NA, wherever present, denotes the field is Not Applicable given the set of conditions.

For each of the set of conditions given in the table above, the following will be the date that will be updated in the field From Price Date:

Case 1

The next scheduled price date.

Example

For a Fund, which is post priced (pricing will be of a daily frequency), the system by default the price to the current available price date.

Case 2

The next user defined price date taking into account the number of cut off days specified.

Example

For a fund, with the following set of maintenances, the allocation would be as follows:

Table 3-174 Price date taking into account the number of cut off days

Fund Name	Forward Pricing Applicable	Scheduled Price Date	Pricing Cut-Off (days)
Fund B	Yes	14-Apr-04	2
Fund B	Yes	17-Apr-04	2
Fund B	Yes	19-Apr-04	2
Fund B	Yes	21-Apr-04	2

For a transaction captured on 12th, the field From Price Date in the subscription transaction will be updated with the date 14th April 2004.

For a transaction captured on 13th, the field From Price Date in the subscription transaction will be updated with the date 19th April 2004 as the 17th is an AMC holiday.

Note:

For the transaction captured on the 13th in the above example, the default price date cannot be overridden to the adhoc date as it is not maintained but can be overridden to the 14th (the Scheduled Price Date), though it does not satisfy the pricing cut off limit.

Case 3

The next user defined price date taking into account the number of cut off days specified. You can change this price date and enter the Adhoc Price Date.Example

For a fund, with the following set of maintenances, the allocation would be as follows:

Table 3-175 Fund Details

Fund Name	Forward Pricing Applicable	Scheduled Price Date	Pricing Cut-Off (days)	Adhoc Date (Subscription)	Adhoc CutOff (days)
Fund B	Yes	14-Apr-04	2	12-Apr-04	0
Fund B	Yes	17-Apr-04	2	13-Apr-04	1
Fund B	Yes	19-Apr-04	2	15-Apr-04	2 - Flagged for reporting
Fund B	Yes	21-Apr-04	2	16-Apr-04	3

Assume, 15th is a Fund holiday and 17th April, 2004 is a AMC holiday.

For a transaction captured on the 12th, the field From Price Date in the subscription transaction will be updated with the date 14th April 2004.

The above defaulted price date 14th April 2004, can be overridden to the Adhoc Date 12th April 2004.

For a transaction captured on 13th, the field From Price Date in the subscription transaction will be updated with the date 19th April 2004 as the 17th is an AMC holiday.

In the above transaction, the default price date can be overridden to the Adhoc Date, 13th April 2004 as it does not satisfy the cut-off days limit. But the 14th (the Scheduled Price Date) can be applied.

Case 4

The next scheduled price date taking into account the number of cut off days specified. You can change this price date and enter the Adhoc Price Date.

Refer to the topic Setting Up Fund Rules (II) in the Fund Manager User Manual.

For further information on the Transaction Detail screens, refer to the topics Processing Transaction Requests and Processing Transaction Requests (II) in the Agency Branch User Manual.