You are on page 1of 14

Truitt EBS Implementation

MD.050-Functional Specification Document


Delivery Note Report - REP.TRU.009

Author(s) : Hassan Syed


Creation Date : 19th September 2021
Last Updated : 2606-October-2021
Version : 0.321

MD050 Delivery Note Report – REP.TRU.009 Page 1 of 14


Document Reference and Location

1.1 Document Location: <SharePoint / Shared Drive Link>

1.2 Document Reference

ID Name Location Comments

Document Control

2.1 Change Record3


Date Author Version Change Reference
19/09/2021 Hassan Syed 0.1 Initial Document
05/10/2021 C Butchart(Baxters) 0.1 Review. Comments added. Please review
Amended the document based on review
06/10/2021 Hassan Syed 0.2
comments
Created new version as received from business the
new boiler plate text which added to the mock up
26/10/2021 C Butchart(Baxters) 0.3
docs.
Approved.

2.2 Reviewers
Name Position Company
Colin Butcharter Group IT Manager Baxters
Josh Nolte Senior Project Manager Baxters
Elaine McKechnie Group IT Director Baxters

2.3 Approvers
Name Position Company
Colin Butcher Group IT Manager Baxters
Josh Nolte Senior Project Manager Baxters
Elaine McKechnie Group IT Director Baxters

MD050 Delivery Note Report – REP.TRU.009 Page 2 of 14


MD050 Delivery Note Report – REP.TRU.009 Page 3 of 14
Table of Contents

1 OVERVIEW..............................................................................................................................................4

1.1 BUSINESS OBJECTIVES.............................................................................................................................4


1.2 MAJOR FEATURES..................................................................................................................................4
1.3 USE CASE BRIEF DESCRIPTION...................................................................................................................4
1.4 USER PROCEDURE..................................................................................................................................4
1.5 ASSUMPTIONS.......................................................................................................................................4

2 REPORT LAYOUT.....................................................................................................................................5

2.1 SETUP REQUIREMENTS............................................................................................................................6


2.2 REPORT PARAMETERS.............................................................................................................................6
2.3 OTHER REQUIREMENTS...........................................................................................................................6
1.3.1. VOLUME AND PERFORMANCE REQUIREMENTS................................................................................................6
1.3.2. SECURITY REQUIREMENTS...........................................................................................................................6
2.4 EXCEPTION AND ERROR HANDLING............................................................................................................6

3 OPEN AND CLOSED ISSUES FOR THIS DELIVERABLE.................................................................................7

3.1 OPEN ISSUES.........................................................................................................................................7


3.2 CLOSED ISSUES......................................................................................................................................7

APPENDIX.....................................................................................................................................................8

MD050 Delivery Note Report – REP.TRU.009 Page 4 of 14


1 Overview
Truitt requires a solution to print delivery note report in Oracle R12
The purpose of this document is to specify setup setups for generating the report as well as describe the
functional details and layout of the report for Delivery Note

1.1 Business Objectives


 Generating PDF reports for the items that are shipped.

1.2 Major Features


Below are the major features of customization to meet the business objectives mentioned above
 There will be a xml publisher template designed according to the Baxter’s format for delivery note report.
This template will ensure that delivery note report is generated in the required format.
 The report will be generated in PDF format and will follow the required naming convention.
 As the Delivery Note will be issued from two factory locations, Salem in Oregon and Kentucky, the factory
location address positioned underneath the boiler plate text ‘Delivery Advice Note’ will need to change
depending from which inventory organization the finished goods are shipped. For ORF use ORF’s address
and for KYF use the KYF address.
 The Warehouse field organization code needs to change depending from which inventory organization the
material is shipped from.
 The following new boiler plate text will be added to the document. This has been reviewed by the local
legal team and approved. The Delivery Note must contain the following boiler plate text:
 
"The property described herein, in apparent good order, except as noted (contents and condition of
contents of packages unknown), marked consigned, and destined as indicated herein, which said carrier,
(the word carrier being understood throughout this contract as meaning any person or corporation in
possession of the property under the contract) agrees to carry to its usual place of delivery at said
destination, if on its route, otherwise to deliver to another carrier on the route to said destination.  It is
mutually agreed, as to each carrier of all of said property over all or any portion of said route to destination,
and as to each party at any time interested in all or any of said property, that every service to be performed
hereunder shall be subject to all the terms and conditions of the Uniform Domestic Straight Bill of Lading set
for (1) in Uniform Freight Classification in effect on the date hereof, if this is a rail or rail water shipment, or
(2) in the applicable motor carrier classification of tariff if this is a motor carrier shipment.
 
Shipper hereby certifies that he is familiar with all the terms and conditions of this said bill of lading set
forth in the classification or tariff which governs the transportation of this shipment and the said terms and
conditions are hereby agreed to by the shipper and accepted for himself and his assigns.
 
If trailer seal has been removed or tampered with, the delivery is subject to rejection by consignee and will
result in freight claim against the carrier.  Only the consignee can break the seal upon delivery."

1.3 Use Case Brief Description


Following are the Use cases:
1. Shipping Execution of the sales order.

MD050 Delivery Note Report – REP.TRU.009 Page 5 of 14


1.4 User Procedure
Following will be the user procedures for the generation of report
 Once the release sales order is completed, the shipping pick release report would be triggered and the
data would be generated in the format specified.

1.5 Assumptions
 The customisation is only valid for the shippable sales order line type. Any other order line type is out of
scope
 The logic within the delivery report will remain the same as previous versions (for example Manor delivery
Note) apart from the changes described above.
 Report parameters will be the same as previous versions. See in next section below for parameters.
 The multiple copy types (Order copy, Haulier copy etc) will remain the same.
 The final sheet which lists lot numbers remains the same

MD050 Delivery Note Report – REP.TRU.009 Page 6 of 14


2 Report Layout

Delivery Note Report – Sample

MD050 Delivery Note Report – REP.TRU.009 Page 7 of 14


MD050 Delivery Note Report – REP.TRU.009 Page 8 of 14
MD050 Delivery Note Report – REP.TRU.009 Page 9 of 14
MD050 Delivery Note Report – REP.TRU.009 Page 10 of 14
2.1 Setup Requirements
 Business Group, LE, Ledger and CoA need to be configured
 Basic setups in Order Management like Order Types and Shipping Grants to be completed
 The xml publisher template should have the correct file version required to generate an output in the
specified format

2.2 Report Parameters

 Warehouse
 Delivery Name
 Print Customer Item
 Item Display Option
 Print Mode
 Sort Option
 Delivery Date (Low)
 Delivery Date (High)
 Freight Carrier
 Quantity Precision
 Display Unshipped Items
 Debug Flag

2.3 Other Requirements


1.1.
1.2.
1.3.
1.3.1. Volume and Performance Requirements
Delivery Note report can be run on weekly / bi-monthly / monthly/ ad hoc basis. It can also be scheduled on a
periodic basis.
The report willcan be run mutiple times in same day
1.3.2. Security Requirements
The program will be assigned to specific request groups and hence follow standard role-based access control /
security requirements.
The report will run through the Baxters Document Management Software

2.4 Exception and Error Handling


 Standard Exception and error handling to be done in case of system error
 Log message to be produced with the error details

MD050 Delivery Note Report – REP.TRU.009 Page 11 of 14


MD050 Delivery Note Report – REP.TRU.009 Page 12 of 14


3 Open and Closed Issues for this Deliverable

3.1 Open Issues

I Issue Resolution Responsibility Target Impact


D Date Date

3.2 Closed Issues


ID Issue Resolution Responsibility Target Date Impact
Date

MD050 Delivery Note Report – REP.TRU.009 Page 13 of 14


Appendix

MD050 Delivery Note Report – REP.TRU.009 Page 14 of 14

You might also like