\

 

Bill of Lading

A bill of lading is a document which is issued by the transportation carrier to the shipper acknowledging that they have received the shipment of goods and that they have been placed on board a particular vessel which is bound for a particular destination and states the terms in which these goods received are to be carried. Separate bills of lading are issued for the inland or domestic portion of the transportation and the ocean or air transportation, or a through bill of lading can be obtained covering all modes of transporting goods to their destination.

Bills of lading, whether inland or ocean, can be issued in either non-negotiable (straight) form or in negotiable form. If the bill of lading is specified as being non-negotiable, the transportation carrier must deliver it only to the consignee named in the bill of lading, thus the bill of lading acts both as a receipt of goods and as an agreement to transport these goods to a specific destination and consignee in return for payment of the transportation charges. If the bill of lading is specifically labeled as being negotiable, ownership to the goods and the right to re-route the shipment are with the person who has ownership of the bill of lading properly issued or negotiated to it. Such bills of lading are issued to shipper's order, rather than to a specific, named consignee. Where collection and payment is through banking channels, such as under a letter of credit or documentary collection, negotiable bills of lading are required (except for air shipments). The exporter must endorse the bill of lading and deliver it to the bank in order to receive payment

Through the BFIv2 solution, both Bill of Ladings and Master Bill of Ladings can be generated, a feature not provided in Syspro.

 

 

 

Barcode For Impact provides a full comprehensive bin table which is used to validate users' input of bins.


Fast Zero Degree Processing

All processing of transactions in BFIV2 follows a zero degree processing model. Zero Degree Processing For example, if a stockcode is not Lot Traceable, the user is never asked or shown a LOT number input prompt. In manyThis means that if an item is not LOT Traceable, the user is never asked for a LOT number.

Single Tier Power Processing: An Example

Due to the single tier architecture, the wireless or wedge scanning application is directly interacting with live data stored in the Syspro database tables. This feature is a major reason behind the blazing product speed and superb reliability.

Consider an example in which a warehouse employee is moving 1000 units of a lot traceable stockcode "ITEMSAMPLE" from Bin A1200 to Bin W12O1A. For added complexity, in the starting bin, Bin A1200 the company has stored two lots: LOT 1200A with a quantity on hand of 400, of which 300 have been allocated to sales orders, and the second lot "1200B" has an on hand quantity of 3000, of which 200 are allocated to sales orders.

 
Single Tier Bin Transfers Three Tier Bin Transfers

Step 1: Input Starting Bin

The input bin is validated directly against a Barcode Partners Bin Table. If the bin entered/scanned is valid, the user is permitted to proceed to Step 2: Input StockCode.

Step 2: Input StockCode

Once the stockcode is entered, it is directly validated against the Syspro™ Inventory Master Table. If valid, the bin/stockcode combination is validated against the StockCode Multiple Bin table of Syspro™. If invalid, the user is stopped due to invalid data being input.

Step 3: Input Lot Number

Lot number is immediately validated against the Lot Table in Syspro. If quantity for this lot is available (ie, qty on hand minus qty allocated) then the user is permitted to proceed to Step 4.

Step 4: Input Qty to Transfer

If the user inputs a quantity equal to or less than the quantity available for the lot, the user is moved to Step 5.

Warehouse user drives forklift 400 feet to target bin.

Step 5: Input Target Bin

Target bin is validated immediately against a warehouse bin table. If a valid bin was input, a summary of the transaction is presented, Syspro updated with the bin transfer and an audit trail for the bin transaction created.
Step 1: Input Starting Bin

Because Syspro does not provide a valid table of valid warehouse bins, no validation of the starting bin is possible. Crossing our fingers that a mistake has not occurred, the user is moved to
Step  2: Input StockCode.

Step 2: Input StockCode, Qty Entered, Lot Number, Serial Number prompted

In order to minimize processing delays involved with a three tier architecture, software developers would simply present a screen which would capture all of the possible data items needed for completing the transaction. This forces warehouse employees to know that the item which they are moving is lot traceable and/or serialized. The screen shown to the warehouse employee is characterized by containing by required and non-require fields.

Developers at this time, could choose to determine

• if the item is lot traceable: (6 XML based hops)

• validate the stockcode/bin combination (6 XML based hops)

• validate the lot number/ stockcode/ bin/ qty input combination (6 XML based hops)

Grand Total 18 XML based hops.

In order to speed up the application responsiveness, developers could avoid the 18 XML based hops and aasume that the warehouse employee was able to input perfect data.

Warehouse user drives forklift 400 feet to the target bin.

Step 3: Input Target Bin

With all required data being available to the application, a posting request through the three tier architecture would be submitted. Score 6 XML hops to determine either if a transaction success is accepted or rejected.

If the developer has written the application to avoid the 18 XML based hops required for data validation, then the number of potential reasons for a failed transaction include:

• Invalid lot number
• Invalid StockCode
• Invalid StockCode/Bin combination
• Invalid StockCode/Bin/Lot Number combination
• Invalid quantity being moved

No audit trail for the bin transfer is generated.

In addition to the failure in updating Syspro for the bin transfer due to incorrect/invalid data, the forklift operator has not moved the inventory 400 feet to a new location. Since Syspro has not been updated with the bin transfer, the forklift operator should return the inventory back to the starting bin. This results in 800 feet traveled without a valid transaction.

 

 

For additional insight into operational performance between single and three tier architecture environments see Single Tier

 

Operational Features of Bin Transfers

•

•

•

•

•

•

 

 

 
Operational Benefits of Bin Transfers

•

•

•

•

•

•

 

 

 
Additional Supporting Information

• Demo of Bin Transfer Task Setup

•

•

•

•

•

 

 

 

 

 

 

 

© 2005 Barcode Partners II, Inc. All rights reserved.