http://ofbiz.116.s1.nabble.com/Dev-Fwd-Re-OFBiz-Users-ERRROR-No-ShipmentPackageRouteSegs-Moved-to-Dev-tp168073p168082.html
It might be more wise to consider a wider perspective on this and recognize that different companies do things very differently. OFBiz has been and is being used in high volume fulfillment environments, and the UI that exists is basically what we have been able to get back into the project from the work done for these companies.
Naturally if the flow and roles the company wants to use are different than what it has been designed for, then it won't work. For smaller companies that want to "fulfill" a bunch of orders in a single click, they'll have to design something for that because while the current UIs support various paths for pick, pack, etc operations they are mostly oriented to different groups of people in each of those roles that touch only one small part of the overall process. For example, they are designed for different groups of people doing picking (with someone managing the pick lists and assigning them, typically) and a group of people doing packing and starting their efforts by scanning a pick position sheet bar code, which is why the first page in the packing UI calls for just that.
Even with these sorts of things supporting high volume operations, most companies that need such a system will want to spend money on it to make sure it meets their needs, and in the case of something like OFBiz that means using those resources for customization.
The irony here from most of real world application that I've seen is that it is the smaller companies that make up any of a multitude of short-cuts to simplify their fulfillment process that really need such customizations to allow their smaller staff to skip steps that are normally part of a fulfillment process...
>>> yes I've looked at it but it will not fly with our users. They are
>>> accustomed to a web based proprietary package with a very intuitive UI.
>>> the picking/packing/shipping can be done from one screen. with a few
>>> clicks, dozens of orders are out the door, with tracking#. if I tell
>>> them they have to manually enter package weights I'll be taken out and
>>> shot. I was almost taken out and shot when they looked at the order
>>> manager. for now my goal is for them to not have to look at the facility
>>> part. I plan on adding quickship instock items and packingslips to the
>>> run action on the findorders list.
>> If it becomes feasible for us to implement OFBiz in some capacity
>> where I work, this is something I'd like to look into more closely.
>> The logic and data model is much better than our own app, but there is
>> no way a business can process a decent volume of orders with these
>> screens the way they are now. My boss' conclusion: that OFBiz is not
>> meant for 'serious' work. Should I manage to get the go ahead in any
>> case, I'd really like to discuss reworking that part of the UI, or
>> adding other paths through it that are more adept at handling higher
>> volumes.
>>
>> Ciao,
>> --
>> David N. Welton
>> -
http://www.dedasys.com/davidw/>>
>
> I agree. I made some consulting task (Prof Of Concept, POC) recently for an
> international company based in Paris. The backoffice UI was also the bad point
> of the story. Also when I recall myself discovering it one year ago I confess
> that I had a hard time. In fact now that I know more of the backoffice UI, I
> don't find it so bad. Of course there are some process (mainly in Order and
> Facilities, picking/packing/shipping is a good example) that must be improved
> but since one year now some has already be done. It can be done ! "Quick Ship
> Entire Order" is a good example of this even if it's not applicable by every
> type of activity.
>
> I think that the current UIs was designed as a POC and not intended to be the
> one finally used by customers. It's clear for frontal UIs (Ecommerce & POS) but
> less for backoffice because it involved more thinking and work. As David J.
> explained recently there are currently many tasks to be done before even
> thinking to change the backoffice UI. As suggested by David W. above, a good way
> to go would be to add some better workflows for tasks like
> picking/packing/shipping, etc. Everybody can help....
>
> The work Vinay is doing on adding a "Simple Commission Mechanism" (see Jira
> OFBIZ-853), is a good example of what may be done by someone who was a newbie 6
> months ago ! It's amazing to see how this is done with the help of vets.
>
> OK, that's only my feeling
>
> Jacques
>
>
> _______________________________________________
> Dev mailing list
>
[hidden email]
>
http://lists.ofbiz.org/mailman/listinfo/dev