247174

247147-NW-7CHEWZ Booking EDI to inc Weight and Special Instructions

Copyright OBS Logistics © 2007

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

Add weight and special instructions to Booking Import function and Bookings Code.

Weight is currently held against a booking but cannot be imported. Weight should be added to both the import function and interface format. If a booking is split across multiple orders then the weight should be apportioned according to DU split. Special instructions should be added to the booking record and also the import and interface formats. The special instructions should be applied to all orders created from the booking record and subsequent orders treated in the same way – i.e. references highlighted to indicate special instructions exist

Solution

Weight. The weight field is already available on the bookings form but when bookings / edi messages loaded, the weight field is set to zero. The import and EDI functions will be enhanced to accommodate weight (and suggest volume) values. Weight (and volume) will be set against the booking record. As TIs are generated, should multiple orders be created, the total weight will be distributed according to the split of DUs.

Special Instructions. The booking database table (product summary) will be extended to accommodate a varchar(4000) field to store the special instructions. The product summary form will be enhanced to allow special instructions to be keyed, amended and viewed. The form dimensions will remain unchanged and scroll bars will enable navigation through larger text entries. The import and EDI load functions will be changed to accommodate a special instruction field. As TIs are generated, any special instructions on the booking will be copied to the special instructions field on the orders.

Functional areas of change are;

• Booking EDI flow to include weight (and Volume?) and special instructions extra columns, validation and interface errors tab – values to default if not provided from master data. • Booking form to allow weight (and Volume?) and special instructions insert, amend and display and associated searches and lookups to be modified to include these fields • TI generation process to use weight (and Volume?) and special instructions values from booking. • Booking Import function to be extended to capture weight (and Volume?) and special instructions from csv file.

Volume. Volume will be available to be loaded through EDI or through the CSV import as an optional field. If a value is passed into MTS, this value will be set in bookings and used in the TI generation (apportioned where necessary by DUs). MTS has an algorithm to derive a default volume automatically. This needs to be reviewed and remain an available function where volume is not specifically set in the bookings interfaces.

Scope

This change will be applied to system version 10.6.

FUNCTIONAL DESCRIPTION

EDI ChangesChanges to INT_MSG Package (and related changes to BKG)

In the READ_BOOKING_DETAIL procedure :-

The Weight (and Volume?) and Special Instructions will now be read from the detail section of the bookings EDI between <BOOKSTART> and <BOOKEND> as additional columns (11 and 12).

Currently in format :- From Location, To Location, Quantity, Delivery Date, Product Type, DU Type , Booking Reference, Trans Shipment Flag, Customer and Cost Centre

These new fields will be stored on INT_BOOKING_DETAIL in the new columns.

These new fields will need to be passed through the BKG.APPLY_PROD_SUM, BKG.CREATE_PRODUCT_SUMMARY and BKG.CREATE_BOOKING procedures in order for the insert into SCH_BOOKING. These are already overloaded functions so we just need to overload them again for the extra 2 parameters.

Example of current DSG Booking :-

<RECHEADSTART>DSGLV,DXN_BOOKINGS,1<RECHEADEND>

<BOOKSTART>07099,02404,1.103,12-12-2099,RDCAA,,02404123456,N<BOOKEND> <EOF>

Changes to INT_ERROR Form

We will need to check weight (and Volume?) and special instructions fields on the INT_BOOKING_DETAIL to ensure that the user doing the query has access to these interface errors.

The new fields Weight (and Volume?) and special instructions will need to be displayed in the detail section of the screen for the DSG Bookings Tab:-

 IMAGE

Bookings Form

Bookings Form New / Edit

Currently the ‘New’ button brings up the following canvas which will need the Special Instructions field to be added. The weight (and Volume?) field already exists.

IMAGE

Currently the Edit button brings up the following canvas and this will need the new field special Instructions adding with appropriate validation.

IMAGE

Generate TI’s

The ‘Create TI’s’ button on the Bookings form calls the procedure GEN_TI.CREATE_BOOKING_TI’s which will need changing to use the Weight (and Volume?) and special instructions fields from the SCH_BOOKING table when creating new records on the SCH_ORD table.

In the situation where multiple TIs (orders) are generated from a booking, the weight (and volume?) will be apportioned in line with the DU apportionment (which is current functionality). Any special instructions from bookings will be carried forward to associated orders when generating TIs.

Where the generate TIs function currently generates multiple orders to satisfy X-dock routes, each of the orders will be created with weight (and volume?) and special instructions.

Changes to IMPORT Functionality The standing data to support the new fields will need adding to allow the new fields Weight (and Volume?) and special instructions to be selected for inclusion on a Bookings format (see Data section above for details).

The IMP.PROCESS_BOOKINGS procedure will need changing to extract these fields from the csv if defined on appropriate format and provided in the file.

The process will then use these fields to pass through to the already changed procedure BKG.APPLY_PROD_SUM (see changes to BKG package in section above) for the creation of the booking.

A sample format for Bookings is :-

IMAGE

The new fields Weight (and Volume?) and Special instructions will now be able to be entered as a Field Types against formats which have an Imp Type of ‘Booking’.

References IMAGE

Glossary IMAGE

Document History IMAGE

Authorised By IMAGE