Pages

Thursday, March 10, 2011

How API Automates Shipment Cycle and Drastically Improves Performance

How API Automates Shipment Cycle and Drastically Improves Performance

1. Introduction

ABC manufacturing receives orders for 1000 metric tonnes. The shipment is made in trucks each having a limited capacity of 20 metric tonnes. Due to this, the ordered quantity is fulfilled over many months and it takes around 50 deliveries over 3 months to fulfill the entire order. Every delivery has a separate invoice which is based on the actual net weight. Net weight is computed as a difference between gross weight and tare weight of the truck. Gross weight is the weight of the truck after it loads the finished goods from the factory and tare weight is the weight of an empty truck. The user manually splits the line for an approximate quantity of 20. The weight is captured through an external system in the weighbridge. This information is brought into Oracle in the ‘Update quantity screen of the Transact Move Order form’ through a customization procedure. Additionally, the ship confirmation and the invoice depend on the net weight.

1.1 API - Current Process/ Steps

Split line
Launch pick release
Transact Move Order
Capture weight information through zoom functionality called from the ‘Transact Move Order’ form
Enter Additional Delivery Information – This includes contractor name, heat/lot number
Ship confirm the delivery
Generate customer invoice using auto invoice program

2. Problem Definition Re-Statement

Lengthy navigation to create transactions - splitting line, pick releasing, capturing weight information (through Zoom Screen), ship confirmation and auto invoicing
Manual intervention at every step of the shipment cycle
Reservations created do not get released as the split line quantity is different from the actual net weight. There is always a difference between the line split quantity (approximate) and the net weight quantity (invoiced). This ends up as reservations that need to be cleaned up later
Takes about 25 minutes for completing the cycle for one order

3. Technology Proposition

3.1. Re-engineered Process

A custom form is provided that captures all the requisite information to process the shipment cycle from line split up to invoicing.

Processes include the following steps:
Enter the details cited below in a CUSTOMform:

Order Number
Item
Tare weight - Captured through an external application by clicking ‘Get Weight’ button
Gross weight - Captured through an external application by clicking ‘Get Weight’ button
Truck Number
Transporter Name
Freight Term
Heat Number / Lot Number
Way Bill Number
Contractor Name
Ship Method

By clicking on the submit button, the system would sequentially execute the following processes:

Split line for the ‘Net Weight’
Pick Release
Create Delivery
Ship Confirm
Invoice

Download

Download full paper At
http://www.enjineer.com/forum

No comments:

Post a Comment