Delivery Information

Process Name: Add A Carrier (1.4.2.2)

Input:

1. CarrierID
2. ZoneNumber
3. NameLast
4. NameFirst
5. TelephoneNumber
6. MailAddressStreet
7. MailAddressPC
8. DeliveryNotes

Output:

1. A new Carrier Record
2. Database key table's field for CarrierID updated

Assumptions:

1. The system provides a correct unique CarrierID

Errors:

1. User input is syntactically incorrect for data fields 5 or 7.
2. User attempts to add new record before all required fields have been populated with data.

Process Description:

System provides a unique CarrierID number upon initiation of the form.
User assigns the carrier to a delivery ZoneNumber available from a drop down list.
User enters all remaining data fields. Only DeliveryNotes may be omitted.
If fields 5 and 7 are syntactically correct, then record is added to database.
Else an error message is displayed indicating the syntax problem.

Process Name: Modify Carrier Information (1.4.2.3)

Input: Any one of the following

1. ZoneNumber
2. NameLast
3. NameFirst
4. TelephoneNumber
5. MailAddressStreet
6. MailAddressPC
7. DeliveryNotes
8. Carrier Record

Output:

1. A modified Carrier Record to the Carrier data table.

Assumptions: None

Errors:

1. User input is syntactically incorrect for data fields 4 or 6.

Process Description:

Process 1.4.2.1 is initiated upon selection of Edit.
If a Carrier record is found, then user can edit one or more fields except for the CarrierID field.
When editing is complete and if changes to fields 4 and 6 are syntactically correct, then the modified record is written to the database.

Process Name: Delete A Carrier (1.4.2.4)

Input:

1. Carrier Record

Output:

1. A Carrier record deleted from the database

Assumptions: None

Errors:

1. A request to delete a Carrier record before a replacement Carrier for the same DeliveryZone has been added to the database.

Process Description:

Process 1.4.2.1 is initiated upon selection of Delete.
If a Carrier record is found, then a query of the Carrier table, using the current Carrier record's DeliveryZone field, is automatically initiated.
If a replacement Carrier is found, then the current Carrier record can be deleted
Else a message is generated indicating that the Carrier cannot be deleted until the DeliveryZone is serviced with a replacement Carrier.

Process Name: Find Carrier Information (1.4.2.5)

Input: One or both of the following are required

1. CarrierID
2. NameLast

Output:

1. Carrier Record

Assumptions: None

Errors:

1. Carrier Record not found matching either or both search criteria fields

Process Description:

If only CarrierID field input, then query Carrier table for matching record and display

• If matching record found then display record
• Else report Carrier record does not exist

If only NameLast field input, then query Carrier table for all records matching NameLast

• If at least one record found then display record
• Else report Carrier record does not exist

If both CarrierID and NameLast fields input, then query Carrier table for a record matching CarrierID

• If at least one record found then display record
• Else report Carrier record does not exist

Process Name: Print Carrier Information (1.4.2.6)

Input:

1. Carrier Record

Output:

1. Carrier Record

Assumptions: None

Errors: None

Process Description:

Process 1.4.2.1 is initiated upon selection of Print.
If a Carrier record is found, then the record is printed.

Process Name: Add A Drop Location (1.4.3.2)

Input:

1. DropNumber
2. RouteNumber
3. RouteOrder
4. DropAddress
5. DeliveryNotes

Output:

1. A new Drop Location Record
2. Database key table's field for DropNumber updated

Assumptions:

1. The system provides a correct unique DropNumber

Errors:

1. User attempts to add new record before all required fields have been populated with data.

Process Description:

System provides a unique DropNumber number upon initiation of the form.
User assigns the Drop Location record to a delivery RouteNumber available from a drop down list.
User enters all remaining data fields. Only DeliveryNotes may be omitted.
If required fields have data, then

• the Drop Location, News Box and Retail Customer tables are queried to find all records such that
  (RouteNumber = new Drop Location.RouteNumber) and (RouteOrder greater or = new Drop Location.RouteOrder)
• the RouteOrder for all found records is incremented by 1.
• the new Drop Location record is added to the Drop Location table

Else an error message is displayed indicating the missing data problem.

Process Name: Modify A Drop Location (1.4.3.3)

Input: Any one of the following

1. RouteNumber
2. RouteOrder
3. DropAddress
4. DeliveryNotes
5. Drop Location Record

Output:

1. A modified Drop Location Record to the Drop Location data table.

Assumptions: None

Errors: None

Process Description:

Process 1.4.3.1 is initiated upon selection of Edit.
If a Drop Location record is found, then user can edit one or more fields except for the DropNumber field.
Save a copy of the RouteOrder (OldRouteOrder = RouteOrder)
One or more fields are edited
If the RouteOrder field is modified and

• If the RouteOrder is greater than OldRouteOrder, then
• the Drop Location, News Box and Retail Customer tables are queried to find all records with the same RouteNumber and such that their RouteOrder is greater than OldRouteOrder and less than or = to modified RouteOrder
• the RouteOrder for all found records is incremented by 1.
• Else the RouteOrder is less than OldRouteOrder
• the Drop Location, News Box and Retail Customer tables are queried to find all records with the same RouteNumber and such that their RouteOrder is greater than or = RouteOrder and less than OldRouteOrder
• the RouteOrder for all found records is incremented by 1.
• the modified Drop Location record is added to the Drop Location table

Else the modified Drop Location record is added to the Drop Location table.

Process Name: Delete A Drop Location (1.4.3.4)

Input:

1. Drop Location Record

Output:

1. A Drop Location record deleted from the database

Assumptions: None

Errors:

1. A request to delete a Drop Location record while one or more Household Delivery Zones are still associated with it.

Process Description:

Process 1.4.3.1 is initiated upon selection of Delete.
If a Drop Location record is found, then a query of the Household Delivery Zone table, using the current Drop Location record's DropNumber field, is automatically initiated.
If no related Household Delivery Zone records are found, then

• the Drop Location, News Box and Retail Customer tables are queried to find all records with the same RouteNumber and such that their RouteOrder is greater than the RouteOrder for the Drop Location record to be deleted
• the RouteOrder for all found records is decremented by 1.
• the current Drop Location record can be deleted

Else a message is generated indicating that the Drop Location cannot be deleted until the associated Household Delivery Zone(s) is serviced with a replacement Drop Location.

Process Name: Find Drop Location Information (1.4.3.5)

Input:

1. DropNumber

Output:

1. Drop Location Record

Assumptions: None

Errors:

1. Drop Location Record not found matching the search criteria field

Process Description:

If Drop Location record matching DropNumber found then display record
Else report Drop Location record does not exist

Process Name: Print Drop Location Information (1.4.2.6)

Input:

1. Drop Location Record

Output:

1. Drop Location Record

Assumptions: None

Errors: None

Process Description:

Process 1.4.3.1 is initiated upon selection of Print.
If a Drop Location record is found, then the record is printed.

Process Name: Add A Delivery Route (1.4.4.2)

Input:

1. RouteNumber
2. TruckNumber

Output:

1. A new Delivery Route Record
2. Database key table's field for RouteNumber updated

Assumptions:

1. The system provides a correct unique RouteNumber

Errors:

1. User attempts to add new record before all required fields have been populated with data.

Process Description:

System provides a unique RouteNumber number upon initiation of the form.
User enters all data fields.
If required fields have data, then

• the new Delivery Route record is added to the Delivery Route table

Else an error message is displayed indicating the missing data problem.

Process Name: Modify A Delivery Route (1.4.4.3)

Input:

1. TruckNumber
2. Delivery Route Record

Output:

1. A modified Delivery Route Record to the Delivery Route data table.

Assumptions: None

Errors: None

Process Description:

Process 1.4.4.1 is initiated upon selection of Edit.
If a Delivery Route record is found, then user can edit one or more fields except for the RouteNumber field.
Modified Delivery Route record is added to the Delivery Route table

Process Name: Delete A Delivery Route (1.4.4.4)

Input:

1. Delivery Route Record

Output:

1. A Delivery Route record deleted from the database

Assumptions: None

Errors:

1. A request to delete a Delivery Route Record while one or more Drop Location, News Box and or Retail Customer Records are associated with the Delivery Route.

Process Description:

Process 1.4.4.1 is initiated upon selection of Delete.
If a Delivery Route Record is found, then a query of the Drop Location, News Box and or Retail Customer tables, using the current Delivery Route Record's RouteNumber field, is automatically initiated.
If no related records from those tables are found, then

• the Delivery Route Record can be deleted

Else a message is generated indicating that the Delivery Route Record cannot be deleted until the associated records are reassigned to another Delivery Route.

Process Name: Find Route Information (1.4.4.5)

Input:

1. RouteNumber

Output:

1. Delivery Route Record

Assumptions: None

Errors:

1. Delivery Route Record not found matching the search criteria field

Process Description:

If Delivery Route Location record matching RouteNumber found then display record
Else report Delivery Route Location record does not exist

Process Name: Print Delivery Route Information (1.4.4.6)

Input:

1. Delivery Route Record

Output:

1. Delivery Route Record

Assumptions: None

Errors: None

Process Description:

Process 1.4.4.1 is initiated upon selection of Print.
If a Delivery Route record is found, then the record is printed.

Process Name: Add A District (1.4.5.2)

Input:

1. DistrictNumber
2. Additional data fields to be defined in future by customer

Output:

1. A new District Record
2. Database key table's field for DistrictNumber updated

Assumptions:

1. The system provides a correct unique DistrictNumber

Errors: None

Process Description:

System provides a unique DistrictNumber number upon initiation of the form.
User enters all data fields.
If required fields have data, then

• the new District Record is added to the District table

Else an error message is displayed indicating the missing data problem.

Process Name: Modify A District (1.4.5.3)

Input:

1. Data fields to be defined in future
2. District Record

Output:

1. A modified District Record to the District data table.

Assumptions: None

Errors: None

Process Description:

Process 1.4.5.1 is initiated upon selection of Edit.
If a District record is found, then user can edit one or more fields except for the DistrictNumber field.
Modified District Record is added to the District table

Process Name: Delete A District (1.4.5.4)

Input:

1. District Record

Output:

1. A District Record deleted from the database

Assumptions: None

Errors:

1. A request to delete a District Record while one or more Household Customer, News Box and or Retail Customer Records are associated with the District.

Process Description:

Process 1.4.5.1 is initiated upon selection of Delete.
If a District Record is found, then a query of the Household Customer, News Box and or Retail Customer tables, using the current District Record's DistrictNumber field, is automatically initiated.
If no related records from those tables are found, then

• the District Record can be deleted

Else a message is generated indicating that the District Record cannot be deleted until the associated records are reassigned to another District.

Process Name: Find District Information (1.4.5.5)

Input:

1. DistrictNumber

Output:

1. District Record

Assumptions: None

Errors:

1. District Record not found matching the search criteria field

Process Description:

If District Record matching DistrictNumber found then display record
Else report District Record does not exist

Process Name: Print District Information (1.4.5.6)

Input:

1. District Record

Output:

1. District Record

Assumptions: None

Errors: None

Process Description:

Process 1.4.5.1 is initiated upon selection of Print.
If a District Record is found, then the record is printed.

Process Name: Add A Household Delivery Zone (1.4.6.2)

Input:

1. ZoneNumber
2. DropNumber
3. TotalCustomers

Output:

1. A new Household Delivery Zone Record
2. Database key table's field for ZoneNumber updated

Assumptions:

1. The system provides a correct unique ZoneNumber

Errors: None

Process Description:

System provides a unique ZoneNumber number upon initiation of the form.
User enters all data fields.
If required fields have data, then

• the new Household Delivery Zone Record is added to the Household Delivery Zone table

Else an error message is displayed indicating the missing data problem.

Process Name: Modify A Household Delivery Zone (1.4.6.3)

Input:

1. DropNumber
2. TotalCustomers
3. Household Delivery Zone Record

Output:

1. A modified Household Delivery Zone Record to the Household Delivery Zone data table.

Assumptions: None

Errors: None

Process Description:

Process 1.4.6.1 is initiated upon selection of Edit.
If a record is found, then user can edit one or more fields except for the ZoneNumber field.
Modified Household Delivery Zone Record is added to the Household Delivery Zone table

Process Name: Delete A Household Delivery Zone (1.4.6.4)

Input:

1. Household Delivery Zone Record

Output:

1. A Household Delivery Zone Record deleted from the database

Assumptions: None

Errors:

1. A request to delete a Household Delivery Zone Record while one or more Household Customer and or Carrier Records are associated with the Household Delivery Zone.

Process Description:

Process 1.4.6.1 is initiated upon selection of Delete.
If a Household Delivery Zone Record is found, then a query of the Household Customer and tables, using the current Household Delivery Zone Record's ZoneNumber field, is automatically initiated.
If no related records from those tables are found, then

• the Household Delivery Zone Record can be deleted

Else a message is generated indicating that the Household Delivery Zone Record cannot be deleted until the associated records are reassigned to another Household Delivery Zone.

Process Name: Find Household Delivery Zone Information (1.4.6.5)

Input:

1. ZoneNumber

Output:

1. Household Delivery Zone Record

Assumptions: None

Errors:

1. Household Delivery Zone Record not found matching the search criteria field

Process Description:

If Household Delivery Zone Record matching ZoneNumber found then display record
Else report Household Delivery Zone Record does not exist

Process Name: Print Household Delivery Zone Information (1.4.6.6)

Input:

1. Household Delivery Zone Record

Output:

1. Household Delivery Zone Record

Assumptions: None

Errors: None

Process Description:

Process 1.4.6.1 is initiated upon selection of Print.
If a Household Delivery Zone Record is found, then the record is printed.

Process Name: Update News Box and Retail Consignments (1.4.7)

Input:

1. Date
2. AgreementNumber
3. QuantityReturned
4. Retail Consignment Records
5. News Box Consignment Records

Output:

1. Retail Consignment Records
2. News Box Consignment Records

Assumptions: None

Errors:

1. Retail Consignment or News Box Consignment Record not found for the specified Date and AgreementNumber

Process Description:

• While Date and AgreementNumber data exists
• query Retail Consignment and News Box Consignment Record tables to find the record matching Date and AgreementNumber
• If found update the QuantityReturned field
• Else report that a matching consignment record not found and report the data

Process Name: Generate Daily Delivery Orders (1.4.8)

Input:

1. Date
2. Delivery Route Records
3. Drop Location Records
4. News Box Records
5. Retail Customer Records
6. Household Delivery Zone Records
7. Carrier Records
8. Household Customer Records
9. Retail Magazine Consignment Agreement Records
10. Retail Newspaper Consignment Agreement Records
11. News Box Consignment Order Records
12. Household Magazine Subscription Records
13. Household Newspaper Subscription Records
14. Retail Consignment Records
15. News Box Consignment Records
16. Household Delivery Records
17. Customer Complaints Records

Output:

1. Route Delivery Orders
2. Truck Packing Orders
3. Carrier Delivery Orders

Assumptions:

1. All inputs are syntactically correct.

Errors: None

Process Description:

this process will concurrently produce a Product Delivery List and a Carrier Delivery List report to files.
For each Delivery Route RouteNumber

• query Drop Location, News Box and Retail Customer tables to produce a list of all associated Drop Locations, News Boxes and Retail Customers sorted in ascending order by RouteOrder
• for each query record
• if record is a Drop Location then for each Household Delivery Zone associated with the Drop Location
• add Drop Location and Household Delivery Zone information to Delivery List file
• query Carrier table and add Carrier information to Carrier Delivery List file
• for each Household Customer
• add Household Customer information to Carrier Delivery List File
• query each associated Household Magazine Subscription
• If (Now() = delivery date for the magazine) and (CopiesRemaining not= 0) then create a Household Delivery record and decrement CopiesRemaining by DeliveryQuantity. Add the magazine ProductID and DeliveryQuantity to the totals for this Drop Location. Add the delivery detail to the Carrier Delivery list file.
• query each associated Household NewsPaper Subscription
• If (a delivery quantity exists for current day of week) and (Now() is less than StopDate or greater than= StartDate) then create a Household Delivery record. Add the newspaper ProductID and DeliveryQuantity to the totals for this Drop Location. Add the delivery detail to the Carrier Delivery list file.
• if record is a News Box then
• add News Box information to the Delivery List
• query News Box Consignment Order table
• If (daily delivery quantity greater than 0) then create a News Box Consignment record. Add the Newspaper ProductID and DeliveryQuantity to the Delivery List.
• if record is a Retail Customer then
• add Retail Customer information to the Delivery List
• query each associated Retail Magazine Consignment Agreement
• If (Now() = delivery date for the magazine) then create a Retail Consignment record. Add the magazine ProductID and DeliveryQuantity to the totals to the Delivery List for this Retail Customer.
• query each associated Retail NewsPaper Consignment Agreement
• If (a delivery quantity exists for current day of week) then create a Retail Consignment record. Add the newspaper ProductID and DeliveryQuantity to the totals for the Delivery List for this Retail Customer.

Back To Top
Back to Process Spec Menu