- If a product is set to always drop ship (Product.requirementMethodEnumId == 'PRODRQM_DS').
- If a product is set to drop ship when inventory is low (Product.requirementMethodEnumId == 'PRODRQM_DSATP'). In this case, item quantities > ATP will be drop shipped.
- Items are reassigned to ship groups based on supplier.
- Ship groups are created if necessary.
- Suppliers are determined using by ProductSupplier.canDropShip == Y, and ProductSupplier.supplierPrefOrderId - main suppliers are used in preference to alternate suppliers.
- Changing Enumeration.enumId PRODRQM_DSQOH to PRODRQM_DSATP in ProductTypeData.xml.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@512373 13f79535-47bb-0310-9956-ffa450edef68
the primary key of the entity ProductStoreShipmentMeth is no more composed by:
productStoreId
shipmentMethodTypeId
partyId
roleTypeId
but by one (new) pk field :
productStoreShipMethId
Also modified existing business rules and demo data to reflect this change.
OFBIZ-735
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@511250 13f79535-47bb-0310-9956-ffa450edef68
- Adding logic to createInvoicesFromShipments service to deal with creating both purchase invoices for drop shipment orders and sales invoices for the sales order linked to drop shipment orders - a sales invoice is created if the createSalesInvoicesForDropShipments parameter is true.
- Adding createSalesInvoiceFromDropShipment service to wrap call to createInvoicesFromShipments, passing the createSalesInvoicesForDropShipments parameter.
- Adding SECAs on updateShipment to generate a purchase invoice when a drop shipment is shipped and a sales invoice when a drop shipment is received
- Adding quickDropShipOrder service, linked from orderview page, to create a drop shipment and set the shipment status to shipped and then received, in order to trigger the SECAs for drop shipment invoice generation.
- Fixed flaw in createInvoiceForOrder service - now pro-rating OrderAdjustments based on OrderItem quantity from the database instead of the passed-in OrderItem, in case the OrderItem quantity has been replaced upstream.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@510664 13f79535-47bb-0310-9956-ffa450edef68
Added a comment from David's advice to use the same metho than add to cart in all concerned files (category.bsh prodcut.bsh and main.bsh)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@509990 13f79535-47bb-0310-9956-ffa450edef68
Modify ShoppingCart/ShoppingCartHelper/ShoppingCartEvents.addOrderTerm, ShoppingCartHelper.selectAgreement and InvoiceServices.createInvoiceTerms methods to make them aware of the new description fields
Display OrderTerm.description in order headers and PDF
Fix order PDF so that there's a line break after each order term
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@508580 13f79535-47bb-0310-9956-ffa450edef68
in a standard way using _PREVIOUS_PARAM_ as recommended by David.
However I kept the category_id session attribute to deal with languages changes.
I quickly tried to come back to a product page if opened but I finally kept as it is (come back to the product's category page).
I open a trivial Jira issue for this case as I feel that I will need something like that in some future.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@508502 13f79535-47bb-0310-9956-ffa450edef68
- valid transitions from ORDER_APPROVED and to ORDER_APPROVED, ORDER_CANCELLED
- supporting links in orderview screen
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@508470 13f79535-47bb-0310-9956-ffa450edef68
"After choosing Sidedeepcategory and then getting loged in it shows the error like - Product Category Not Found for this Id!"
After some refactoring I applied his "patch" and extended it to deal with changes of languages case.
So now you can change the lanquages and keep the same category/product page open.
I can't see any problems. But please if you see an obvious one tell me, I will soon revert. Thanks
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@507698 13f79535-47bb-0310-9956-ffa450edef68
I kept how one-line getters and setters are formatted. Not sure it would be better to put them on more lines.
I deleted the "TODO: Bug: Clicking All so none are selected shows all orders anyway". Because I think this is a good behaviour (rechecking some options by default). Who would want to search for an empty list ?
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@503391 13f79535-47bb-0310-9956-ffa450edef68