252125
252125-NW-7GBE8A Amend Bookings to ASN Date rather than Delivery Date
Copyright OBS Logistics © 2009
The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied
FUNCTIONAL OVERVIEW
Client Requirement
Amend Bookings to ASN date rather than Delivery Date.
Currently when an ASN is received the Booking is updated to a new schedule which reflects the delivery date of the order / booking from the ASN message. When the bookings are converted to orders this is done based on when the ASN is received and so may involve planning across multiple schedules. In order to make this easier for the planners the Booking should now be updated to the schedule that corresponds to the ASN date rather than the delivery date i.e. the date on which the booking is received and processed in MTS.
This change will need to be applied to the ASN date interfaced from SAP and also loaded manually via the import process as well as the manual change from Provisional to Confirmed.
As an addition the same type of change should also be applied to Bookings when they are first created i.e. the schedule date of a Provisional Booking should be the date it was received into MTS, this will then be moved to the schedule that corresponds to the date that the ASN is received.
Benefits: Planning can take place on one schedule meaning that the order dates should make more sense and create more coherent trips.
Solution
The booking will be placed on the schedule for the processing date instead of the delivery date when it is created via the SAP MDD booking message or the booking import.
The booking will be placed on the schedule for the (ASN) processing date when it is updated from ‘PROVISIONAL’ to ‘CONFIRMED’ status.
This will apply to the following methods of updating the booking status:
a) The SAP ASN booking message processed via the inbound EDI interface to MTS (this will apply to ‘INSERT’ and ‘UPDATE’ actions) b) The ‘ASN_BOOKING_IMPORT’ message processed via the ‘Import’ screen in MTS c) The ‘Edit Product Summary Record’ screen via the ‘Booking Order’ screen in MTS
The delivery date of the records will still be updated with the delivery date of the files sent or the delivery date that already exists if the booking status is updated manually. All other validation will not be changed. The link between schedule and delivery date will be broken by this development. The delivery date will continue to be used as an independent field which can be manually edited until the booking is set to CONFIRMED status.
The Booking processing date is stored as the ‘BKG_DATE’ of the ‘SCH_PRODUCT_SUMMARY’ table and the ASN processing date is stored as the ‘ASN_DATE’ of the ‘SCH_PRODUCT_SUMMARY’ table. These dates will be used to set the booking / ASN into an MTS schedule. If the schedule doesn’t exist it will be created by the interface process.
The order for a booking will no longer be placed on the schedule that matches its delivery date when transport instructions are created but the schedule for the ASN date of the booking; the schedule for the order will then match that of the booking. If transport instructions are reversed then the order will have a status of ‘DELETED’ but the booking and order will remain on the original schedule.
Note that if the schedule is changed for a booking in the ‘Edit Product Summary Record’ screen then the delivery date will no longer be updated to match the new schedule date. The delivery date will become an independent field not used to derive the schedule of the booking / ASN.
Scope
This change will be applied to system version 10.4.7 on SARTST and once approved SARPRD.
FUNCTIONAL DESCRIPTION
Creating Bookings
Bookings are loaded into MTS via the following methods:
a) The ‘Bookings’ screen b) The ‘MDD’ booking message c) The ‘MDD_BOOKING_IMPORT’ import
The bookings will be created and loaded onto the schedule for the processing date and not the delivery date provided.If a schedule does not exist for the processing date then one will be created.All other validation will not be changed.
Confirming Bookings
ASNs are loaded into MTS via the following methods:
a) The ‘Edit Product Summary Record’ screen b) The ‘ASN_BOOKING’ booking message c) The ‘ASN_BOOKING_IMPORT’ import
The status of the bookings is updated to ‘CONFIRMED‘ from ‘PROVISIONAL’ and the ASN will be loaded onto the schedule of the ‘ASN’ date.The delivery date of the records will continue to be updated with the delivery date provided from the files sent from SAP (MDD and ASN) or the delivery date that already exists if the booking status is updated manually.If a schedule does not exist for the ‘ASN’ date then one will be created.All other validation will not be changed.
Changing the Booking Schedule
The schedule for a booking may be changed in the ‘Edit Product Summary Record’ screen and the delivery date will not be updated to match the new schedule date. The delivery date will become an independent editable field up until the status of the booking is CONFIRMED by ASN.
Creating Transport Instructions
The transport instructions are created for the schedule date of the bookings and the orders created will be placed on the schedule for the ‘ASN’ date of the bookings.
Reversing Transport Instructions
The transport instructions are reversed for the schedule date of the bookings and the orders reversed will be updated to status ‘DELETED’ and will remain on the schedule for the ‘ASN’ date of the bookings.
Change to the ‘INT_MSG’ package
‘MDD’ booking message - Inserts and Updates
The ‘READ_MDD_BOOKING_FILE’ procedure will be changed so that if the schedule does not exist for the processing date then one will be created.
The ‘READ_MDD_BOOKING_FILE’ procedure will be changed so that the booking is placed on the schedule for the processing date instead of the delivery date provided.
‘MDD’ booking message - Deletions
The ‘READ_MDD_BOOKING_FILE’ procedure will be changed so that the schedule of the booking is used for deletions.
‘ASN_BOOKINGS’ booking message - Inserts and Updates
The ‘READ_ASN_BOOKING_FILE’ procedure will be changed so that if the schedule does not exist for the ‘ASN’ date then one will be created.
The ‘READ_ASN_BOOKING_FILE’ procedure will be changed so that the booking is placed on the schedule for the ‘ASN’ date instead of the delivery date provided when the status of a booking is updated to ‘CONFIRMED’ from ‘PROVISIONAL’.
‘ASN_BOOKINGS’ booking message - Deletions
The ‘ASN’ date will be passed to the ‘BKG.REVERSE_TIS’ procedure as the schedule to reverse any unscheduled orders that may exist and that may be reversed. When an order is reversed back to ‘PROVISIONAL’ status it will remain on the same schedule.
Change to the ‘IMP’ package
Inserts
The ‘PROCESS_ASN_BOOKING’ function will be changed so that if the schedule does not exist for the ‘ASN’ date then one will be created.
The ‘PROCESS_ASN_BOOKING’ function will be changed so that the booking is placed on the schedule for the ‘ASN’ date instead of the delivery date provided when the status of a booking is updated from ‘PROVISIONAL’ to ‘CONFIRMED’.
Change to the ‘CREATE_MULTIPLE_TIS2’ procedure
The ‘CREATE_MULTIPLE_TIS2’ function will be changed so that when transport instructions are being created in the ‘Bookings’ screen for ‘ALL’ bookings that the order is placed on the schedule for the ‘ASN’ date of the booking. The ‘GEN_TI.SINGLE_CREATE_BOOKING_TIS’ function will then receive the schedule of the booking and not the delivery date of the booking.
Change to the ‘CREATE_SINGLE_TIS’ procedure
The ‘CREATE_SINGLE_TIS’ function will be changed so that when transport instructions are being created in the ‘Bookings’ screen for a booking that the order is placed on the schedule for the ‘ASN’ date of the booking. The ‘GEN_TI.SINGLE_CREATE_BOOKING_TIS’ function will then receive the schedule of the booking and not the delivery date of the booking.
Change to the ‘BKG’ package
The ‘CREATE_PRODUCT_SUMMARY’ function will be changed so that the booking is placed on the schedule for the processing date instead of the delivery date provided. The ‘CREATE_BOOKING’ function will then receive the schedule of the processing date and not the delivery date of the booking but it will need to be changed so that the booking is placed on the schedule for the processing date instead of the delivery date provided. The ‘DELETE_BOOKINGS’ function will be changed so that the schedule of the booking is used to delete bookings.
Change to the ‘GEN_TI’ package
The ‘GENERATE_TIS’ function will be changed so that when an order is inserted it is placed on the schedule for the ‘ASN’ date of the booking. The ‘OMS.INSERT_EMPTY_ORDER’ function will then receive the schedule of the booking and not the delivery date of the booking.
Appendix A
TABLE AND TRIGGER DETAILS REQUIRED
a) The table ‘SCH_PRODUCT_SUMMARY’ requires the ‘BKG_DATE and ‘ASN_DATE’ column to exist:
| Column Name | Type | Nullable | Default | Storage | Comments |
| BKG_DATE | DATE | Y | |||
| ASN_DATE | DATE | Y |
b) The trigger ‘T_SCH_PRODUCT_SUMMARY_IUD’ must exist on the ‘SCH_PRODUCT_SUMMARY’ table to set the ‘ASN_DATE’ column for when the status of the booking is set to ‘CONFIRMED’.
References
| EST-252125 NW-7GBE8A | Initial Estimate | 1 | 17/07/08 |
Document History
| Initial version | ||||
| Reviewed and Issued | ||||
| Corrected a spelling mistake |
Authorised By
| Dave Meir | Development Manager | |
| Suk Sandhu | TMSCC MTS Product Manager |
