Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[RESOLVED] Internal Stock Request - is this functionality complete?
10-18-2013, 06:48 PM, (This post was last modified: 10-19-2013, 01:45 PM by icedlava.)
[RESOLVED] Internal Stock Request - is this functionality complete?
I have been looking at Internal Stock Requests to see if it can be used in a specific client case.

I am unsure if the current Internal Stock Request script is meant to be finished or still requires some added functionality. Unfortunately it cannot be used for our specific problem as it currently is coded.

From what I can see:

1. Stock request is made

2. Stock request is approved

3. Stock request is fulfilled - but at this point script seems only half done.
a. Stock movement table is updated for RequestFrom location,
b. stock location qty table is updated for Request From location (reducing stock),
c. and the stock request table(s) are updated to reflect dispatched goods.

There seems :
- no way to print a dispatch docket (and each item is held with different reference in stock moves table)
- no way to receive in stock at receiving branch
- no stock in transfer state prior to receiving

I thought that as a dispatch, this transaction should also be treated like any other stock transfer and intergrated more fully with existing functionality eg:
- be inserted with a reference stock transfer id in the stock transfer table
- a stock transfer docket can be produced
- be able to be received in at receiving branch
- stock transfer id can be viewed (similar to other 'normal' transfers)
- stock moves and location quantities are updated accordingly

However, perhaps i misinterpreted or do no understand the objective of this script.

If this is something that has yet to be complete in internal stock transfer, I have to code this in any case, and could add it to the existing code. (As well as report of outstanding transfers at any specific time). In this case, I would appreciate any feedback to considerations that I should take to ensure maintaining of compatibility with existing possible scenarios.

If the internal stock transfer function is complete - then unfortunately we cannot use it, and must look to another solution, or code it in custom branch.

If there is anyone with some insight into the Internal Stock Request and possible solution to this problem, your feedback would be much appreciated. The general requirements we need to fulfill are outlined below.


Posted to forum and dev list

We have a requirement for the following:

1. Branch requests stock transfer from main warehouse to fulfill some current requirements, or to fulfill requirements at a future date after planning

2. Stock transfer is approved by relevant department

3. Stock is transferred out from main warehouse to branch, at the required date which may be some months in future (or some other alternative such as put on backorder and shipped when in stock, or outstanding cancelled). Dispatch docket printed.

3. Branch is notified, and receives in stock on arrival. Transfer note generated and used to check for received items and head branch notified if there are discrepancies.

4. Usual stock moves, stock quantities at location and dispatch records are updated in relevant tables at dispatch and receipt (or GL records if stock GL on).

4. A report of outstanding stock transfer requests for a given branch should be provided when required.

Note that I have added ability to print stock dispatch docket and transfer note at any time from an amended Inventory -> Stock Transfer Note report option to solve some of this issue.

10-19-2013, 12:07 AM,
RE: Internal Stock Request - is this functionality complete?
Thanks to those that provided feedback via email.

Quote:Doesn't the existing stock location transfer facility do this anyway?

Yes it handles the main underlying dispatch and receive process and table updates required. However, I believe the client is after a particular workflow which for them, seems to be along the lines of the Internal Transfer Request functionality.

The transfer should have all the underlying functionality of a normal bulk transfer with dispatch and receiving. However on top of that there should be request functionality, approval process, and ability to place and manage requests and filling of those requests for any required delivery date into the future.

There needs to be a restriction on stock, via categories for example, that the branch office can request so they only see their own relevant stock categories and the Internal Transfer Request offers this already.
There should be validation process integrated for receipt of stock received (eg checked stock transfer note).

The branches require regular reports of all stock transfer requests they have outstanding with requested delivery dates (and other specialised requirements that i can add in a custom report).

There will also be requirements for return stock handling and the usual accounting, but these could be handled i'm guessing through existing functions. It will need to be integrated into the work flow.

I'm not sure the existing stock request tables holds all necessary information at the moment (or the stock transfer tables) - something for me to look at.

It seems that for this user case, the way to go would be to integrate the Internal Stock Request approval/filling with all the functionality that the bulk dispatch and receive process offers, and add the custom report(s).

I might be misunderstanding existing functionality in webERP, but i can't see how we can fulfil the requirement without some extra code. Please correct me if i've missed it. A new script based on Internal Stock Request might best and would be easier for maintenance/upgrade.
10-19-2013, 01:44 PM,
RE: Internal Stock Request - is this functionality complete?
After some discussions on the developer list and via email, and Ricard's suggestions, I think I might be able to modify the existing Internal Stock Request to fit our needs, while keeping the existing functionality as a default.

I will see how this goes, but if anyone has further suggestions or concerns on this I'd be pleased to hear from them.


Forum Jump:

Users browsing this thread: 1 Guest(s)