Issuu on Google+

Ineffective Date Effectives 1.1

Version 1.0 02 July 2002 ď›™ Bristol Office Machines Ltd 2002. All rights reserved. No part of this publication may be reproduced or transmitted, in any form or by any means, without permission.

Caveat Any screenshots or data models within this document are intended as illustrations of proposed functionality and should not be perceived as the definitive end product. Due to the nature of the development process it is possible that changes will be made according to user requirements and best practice.

Bristol Office Machines Ltd. Clue House Petherton Road Hengrove Bristol BS14 9BZ Tel: +44 (0) 1275 890100


Ineffective Date Effectives 1.1

Revision history Version 1.0 1.1

Date 20 May 2002 02 July 2002

Changes First draft Updated rules governing Adding, Deleting and Editing, Date Effective, Ineffective Date Effective records and how they interact.

Location -

/mnt/tmp/tmpfY1kC3

Total sheets - 10

Page i


Ineffective Date Effectives 1.1

Contents 1. Introduction...........................................................................................................................................1 2. Changes to Product...............................................................................................................................2 2.1 Changes....................................................................................................................................2 2.2 Rules........................................................................................................................................2 2.3 Areas Of Functionality That Will Be Affected By Ineffective Date Effectives......................5

Page ii


Ineffective Date Effectives 1.1

1.

Introduction

BAL want to be able to extend the functionality of Date Effectives. At present a can either have a Start Date and an End Date or have just a Start and no End Date. However during the life span of any product there may be times where it needs to be inactive and re-activated at a specific time, automatically. For example 1 LTR GRAPPA Date 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 V V V V V D. Eff I. Dates

1 LTR Grappa starts on day 5 and ends on day 30. Before and after this the system knows to ignore it as it is not a valid product. However within this date range there are two other date ranges where the 1 LTR Grappa ‘dies’ and is ‘resurrected’. On day 10 it dies and on17 it comes back to life, likewise on the 23rd day it dies and comes back to life on the 30.

Page 1


Ineffective Date Effectives 1.1

2.

Changes to Product

2.1 Changes The main Product screen would change so that the Date Effective Details menu includes Inactive Date Effectives. The system would have to set the dates up something like

2.2

Rules

2.2.1

Rules for Normal Date Effectives

Page 2


Ineffective Date Effectives 1.1 The rules for normal Date Effectives are as follows:a.

Adding a record i. Start date must be in the future (field validation) ii. End date must be in the future or null (field validation) iii. End date >= start date (field validation) iv. No overlap with other records (validated on save)

b.

Deleting a Record i. Cannot delete if start date is not in the future

c.

Editing a record i. Start date can only be altered if it is in the future (field validation) ii. If start date is altered then its new value must be in the future (field validation) iii. End date can only be altered if it is in the future or null (field validation) iv. If end date is altered then its new value must be in the future or null (field validation) v. End date >= start date (field validation) vi. No overlap with other records (validated on save)

Thus the for the above 17 scenarios:a.

Adding a record 1. This is legal as both Start Date and End Date are in the future. 2. This is legal as the Start Date is in the future and the End Date is open ended. 3. This is illegal as the Start Date is today. 4. This is illegal as the End Date has been set for before the Start Date.

b.

Deleting a record 5. This is legal as both Start Date and End Date are in the future. 6. This is legal as the Start Date is in the future and the end Date is open ended. 7. This is illegal as the Start Date is in the past. 8. This is illegal as the Start Date is today.

c.

Editing a record 9. This is legal as both Start Date and End Date are in the future. 10. This is legal as both Start Date and End Date are in the future, and the new Start Date (S2) is in the future and before the End Date. 11. This is legal as both Start Date and End Date are in the future, and the new End Date (E2) is in the future and after the Start Date. 12. This is legal as both Start Date and End Date are in the future, and the new End Date (E2) is open ended and after the Start Date. 13. This is illegal as the Start Date is in the past. 14. This is illegal as the Start Date is today. 15. This is illegal as the new Start Date(S2) is in the past. 16. This is illegal as the new Start Date(S2) is today. 17. This is illegal as the new record (S2 > E2) is overlapping with an existing record and therefore may clash.

Page 3


Ineffective Date Effectives 1.1 2.2.2

Rules for Ineffective Date Effectives

The Rules for Ineffective Date Effectives are as follows. It is assumed that the Date Effective record is legal and saved as above:a.

Adding a record i. The IDE must be within the Date Effective, not outside nor have the same dates as the Date Effective. ii. The IDE must not overlap an existing IDE iii. The IDE must have an End Date

b.

Deleting a Record i. Cannot delete if start date is not in the future

c.

Editing a record i. Start date can only be altered if it is in the future (field validation) ii. If start date is altered then its new value must be in the future (field validation) iii. End date can only be altered if it is in the future or null (field validation) iv. End date >= start date (field validation) v. No overlap with other records (validated on save)

Thus the for the above 20 scenarios:a. Adding a record 1. This is legal as both Start Date and End Date are within the Date Effective record and in the future. 2. This is illegal as the End Date is open ended. 3. This is illegal as the End Date is outside the Date Effective. 4. This is illegal as both the Start and End Dates are outside the Date Effective record. 5. This is illegal as the Start Date is today. 6. This is illegal as the Start Date is in the past. 7. This is illegal as the End Date is before the Start Date.

Page 4


Ineffective Date Effectives 1.1 b.

Deleting a record 8. This is legal as both Start Date and End Date are in the future. 9. This is illegal as the Start Date is today. 10. This is illegal as the Start Date is in the past.

c.

Editing a record 11. This is legal as both Start Date and End Date are in the future. 12. This is legal as both Start Date and End Date are in the future, the new Start Date (S2) is in the future and before the End Date and the record is still within the Date Effective record. 13. This is legal as both Start Date and End Date are in the future, the new Start Date (E2) is in the future and before the End Date and the record is still within the Date Effective record. 14. This is legal as both Start Date and End Date are in the future, the new End Date (E2) is after the Start Date and the record is still within the Date Effective record. 15. This is illegal as the End Date is open ended. 16. This is illegal as the Start Date is today. 17. This is illegal as the Start Date is in the past. 18. This is illegal as the new End Date (e2) is in the past and before the Start Date. 19. This is illegal as the new End Date (e2) before the Start Date. 20. This is illegal as the new record (e >>> e2) is overlapping with an existing record and therefore may clash.

2.2.3 Interaction Between Date Effectives and Ineffective Date Effectives The following list what is to happen if an area of functionality has both Date Effective and Ineffective Date Effectives. a.

Adding a Date Effective record 1. The system should add the record as according to the above rules. As no Ineffective Date Effectives are present there will be no restrictions.

b.

Deleting a record 2. If the system detects that there are Ineffective Date Effectives present the system should disallow deletion of this record until such time as the Ineffective Date Effectives have been deleted first. Once the Ineffective Date Effectives have been removed the record may be deleted as per the above rules.

c.

Editing a record 3. If the system detects that there are Ineffective Date Effectives present the system should disallow amendment of this record until such time as the Ineffective Date Effectives have been deleted first. Once the Ineffective Date Effectives have been removed the record may be edited as per the above rules.

2.3

Areas Of Functionality That Will Be Affected By Ineffective Date Effectives • •

Stock Outs:o this also has a filter to “Include Expired Products” o Stock Outs report Dispatch o selecting a new bar will have to look at the Ineffective Date Effectives o “Add Products” will have to look at Ineffective Date Effectives o (not sure what to do with Re-Use Bars) Reports o Bar Packing  Cores, Add-On’s and Subassemblies will have to check Ineffective Date Effectives

Page 5


Ineffective Date Effectives 1.1  Full and Product Summary version Core Schedule  probably wont happen but if we have a Core with only 1 product and this product is in it’s Inactive phase then should report tell user effectively there is no Core on the flight? And o Planned Add-On’s  as per Core Schedule o Product  assuming that all the flight reports like “Picking List” are looking at PRDINABS data and thus have been sorted out during Dispatch Standard Components o building these will have to look at Ineffective Date Effectives Stowage Weight Report o these will have to exclude Ineffective Date Effectives Promotion Rules and Definitions o these will have to exclude Ineffective Date Effectives Maintain M Tax o these will have to exclude Ineffective Date Effectives Sales Reports o these will have to exclude Ineffective Date Effectives o (interface ok I think) o

• • • • •

Page 6


Ineffective Date Effectives